{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8419 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-8419 is a high-severity memory corruption vulnerability in n/a, published on 2 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-8419 and fix it if it is affected.\n\nWhat it is: CVE-2017-8419 is a high-severity memory corruption vulnerability in n/a, published on 2 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-8419 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2017-8419/ (Markdown: https://insights.sbomify.com/CVE-2017-8419/index.md)","id":"CVE-2017-8419","markdown":"https://insights.sbomify.com/CVE-2017-8419/index.md","name":"CVE-2017-8419","record":{"aliases":["DEBIAN-CVE-2017-8419","GHSA-fg7v-43m7-5p33","UBUNTU-CVE-2017-8419"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LAME audio encoder","requires_auth":"none","summary":"Remote attackers can cause denial of service or potential code execution via crafted WAV or AIFF files due to integer handling errors in the LAME library.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lame","vendor":"lame_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"LAME through 3.99.5 relies on the signed integer data type for values in a WAV or AIFF header, which allows remote attackers to cause a denial of service (stack-based buffer overflow or heap-based buffer overflow) or possibly have unspecified other impact via a crafted file, as demonstrated by mishandling of num_channels.","ecosystems":[],"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":"Memory corruption in n/a","id":"CVE-2017-8419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-8420"},"packages":[],"prev":{"headline":"RuboCop gem Insecure use of /tmp","id":"CVE-2017-8418"},"products":["n/a"],"published":"2017-05-02","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2017-11720","kev_date_added":null,"published":"2017-07-28"},{"cvss_score":7.8,"headline":"Null dereference in n/a","id":"CVE-2017-15019","kev_date_added":null,"published":"2017-10-04"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9871","kev_date_added":null,"published":"2017-06-25"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9872","kev_date_added":null,"published":"2017-06-25"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2017-13712","kev_date_added":null,"published":"2017-08-28"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2017-15045","kev_date_added":null,"published":"2017-10-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-16","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service or potential code execution via crafted WAV or AIFF files due to integer handling errors in the LAME library.","url":"https://insights.sbomify.com/CVE-2017-8419/"}