{"answers":{"affected":"3 open source packages ship an affected version, including postscript. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-26953 in the wild and no public exploit code.","fix":"Upgrade postscript to 0.14.0 or later.","what":"CVE-2021-26953 is a high-severity vulnerability in n/a, published on 9 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-26953 and fix it if it is affected.\n\nWhat it is: CVE-2021-26953 is a high-severity vulnerability in n/a, published on 9 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-26953 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- postscript (crates.io): affected all versions; fixed in 0.14.0\n- postscript (crates.io): affected all versions; fixed in 0.14.0\n- postscript (crates.io): affected from 0.0.0-0; fixed in 0.14.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-26953/ (Markdown: https://insights.sbomify.com/CVE-2021-26953/index.md)","id":"CVE-2021-26953","markdown":"https://insights.sbomify.com/CVE-2021-26953/index.md","name":"CVE-2021-26953","record":{"aliases":["GHSA-fhvc-gp6c-h2wx","RUSTSEC-2021-0017"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust PostScript library","requires_auth":"none","summary":"Attackers can read sensitive data from uninitialized memory in the postscript crate via a malicious Read implementation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postscript","vendor":"postscript_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the postscript crate before 0.14.0 for Rust. It might allow attackers to obtain sensitive information from uninitialized memory locations via a user-provided Read implementation.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Read on uninitialized buffer in postscript","id":"CVE-2021-26953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"insert_slice_clone can double drop if Clone panics.","id":"CVE-2021-26954"},"packages":[{"ecosystem":"crates.io","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"postscript","purl":null,"source":"GHSA-fhvc-gp6c-h2wx"},{"ecosystem":"crates.io","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"postscript","purl":"pkg:cargo/postscript","source":"GHSA-fhvc-gp6c-h2wx"},{"ecosystem":"crates.io","fixed":["0.14.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"postscript","purl":"pkg:cargo/postscript","source":"RUSTSEC-2021-0017"}],"prev":{"headline":"Use of Uninitialized Resource in ms3d","id":"CVE-2021-26952"},"products":["n/a"],"published":"2021-02-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can read sensitive data from uninitialized memory in the postscript crate via a malicious Read implementation.","url":"https://insights.sbomify.com/CVE-2021-26953/"}