{"answers":{"affected":"5 open source packages ship an affected version, including claxon. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20992 in the wild and no public exploit code.","fix":"Upgrade claxon to a fixed version for your release line: 0.3.2 or 0.4.1.","what":"CVE-2018-20992 is a medium-severity vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-20992 and fix it if it is affected.\n\nWhat it is: CVE-2018-20992 is a medium-severity vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-20992 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- claxon (crates.io): affected all versions; fixed in 0.3.2\n- claxon (crates.io): affected all versions; fixed in 0.3.2\n- claxon (crates.io): affected from 0.0.0-0; fixed in 0.3.2, 0.4.1\n- claxon (crates.io): affected from 0.4.0; fixed in 0.4.1\n- claxon (crates.io): affected from 0.4.0; fixed in 0.4.1\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-2018-20992/ (Markdown: https://insights.sbomify.com/CVE-2018-20992/index.md)","id":"CVE-2018-20992","markdown":"https://insights.sbomify.com/CVE-2018-20992/index.md","name":"CVE-2018-20992","record":{"aliases":["GHSA-8c6g-4xc5-w96c","RUSTSEC-2018-0004"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust audio library","requires_auth":"none","summary":"Attackers can read uninitialized memory from the claxon Rust crate due to mishandled decode buffer sizes, potentially exposing sensitive data.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"claxon","vendor":"claxon_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the claxon crate before 0.4.1 for Rust. Uninitialized memory can be exposed because certain decode buffer sizes are mishandled.","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":"Uninitialized memory exposure in claxon","id":"CVE-2018-20992","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":5,"n_references":1,"next":{"headline":"Uncontrolled recursion in rust-yaml","id":"CVE-2018-20993"},"packages":[{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0"],"last_affected":[],"package":"claxon","purl":null,"source":"GHSA-8c6g-4xc5-w96c"},{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0"],"last_affected":[],"package":"claxon","purl":"pkg:cargo/claxon","source":"GHSA-8c6g-4xc5-w96c"},{"ecosystem":"crates.io","fixed":["0.3.2","0.4.1"],"introduced":["0.0.0-0","0.4.0-0"],"last_affected":[],"package":"claxon","purl":"pkg:cargo/claxon","source":"RUSTSEC-2018-0004"},{"ecosystem":"crates.io","fixed":["0.4.1"],"introduced":["0.4.0"],"last_affected":[],"package":"claxon","purl":null,"source":"GHSA-8c6g-4xc5-w96c"},{"ecosystem":"crates.io","fixed":["0.4.1"],"introduced":["0.4.0"],"last_affected":[],"package":"claxon","purl":"pkg:cargo/claxon","source":"GHSA-8c6g-4xc5-w96c"}],"prev":{"headline":"Double free in smallvec","id":"CVE-2018-20991"},"products":["n/a"],"published":"2019-08-26","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-05","vendors":["n/a"]},"summary":"Attackers can read uninitialized memory from the claxon Rust crate due to mishandled decode buffer sizes, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2018-20992/"}