{"answers":{"affected":"It affects 29 products.","exploited":"There is no known exploitation of CVE-2014-9998 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-9998 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-9998 is a critical vulnerability in Qualcomm Ipq4019 Firmware, published on 18 Apr 2018."},"fix_prompt":"Check this codebase for CVE-2014-9998 and fix it if it is affected.\n\nWhat it is: CVE-2014-9998 is a critical vulnerability in Qualcomm Ipq4019 Firmware, published on 18 Apr 2018. \nExploitation: There is no known exploitation of CVE-2014-9998 in the wild and no public exploit code.\n\nAffected product: Qualcomm Ipq4019 Firmware. 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-2014-9998/ (Markdown: https://insights.sbomify.com/CVE-2014-9998/index.md)","id":"CVE-2014-9998","markdown":"https://insights.sbomify.com/CVE-2014-9998/index.md","name":"CVE-2014-9998","record":{"aliases":["GHSA-jpxh-mq89-hwp3"],"analysis":null,"analysis_generated_by":null,"assigner":"qualcomm","cpe":[{"product":"ipq4019_firmware","vendor":"qualcomm"},{"product":"ipq8064_firmware","vendor":"qualcomm"},{"product":"mdm9206_firmware","vendor":"qualcomm"},{"product":"mdm9607_firmware","vendor":"qualcomm"},{"product":"mdm9635m_firmware","vendor":"qualcomm"},{"product":"mdm9640_firmware","vendor":"qualcomm"},{"product":"mdm9645_firmware","vendor":"qualcomm"},{"product":"mdm9650_firmware","vendor":"qualcomm"},{"product":"qca4531_firmware","vendor":"qualcomm"},{"product":"qca6174a_firmware","vendor":"qualcomm"},{"product":"qca6574au_firmware","vendor":"qualcomm"},{"product":"qca6584_firmware","vendor":"qualcomm"},{"product":"qca6584au_firmware","vendor":"qualcomm"},{"product":"qca9377_firmware","vendor":"qualcomm"},{"product":"qca9378_firmware","vendor":"qualcomm"},{"product":"qca9379_firmware","vendor":"qualcomm"},{"product":"qca9558_firmware","vendor":"qualcomm"},{"product":"qca9880_firmware","vendor":"qualcomm"},{"product":"qca9886_firmware","vendor":"qualcomm"},{"product":"qca9980_firmware","vendor":"qualcomm"},{"product":"sd_205_firmware","vendor":"qualcomm"},{"product":"sd_210_firmware","vendor":"qualcomm"},{"product":"sd_212_firmware","vendor":"qualcomm"},{"product":"sd_425_firmware","vendor":"qualcomm"},{"product":"sd_625_firmware","vendor":"qualcomm"},{"product":"sd_808_firmware","vendor":"qualcomm"},{"product":"sd_810_firmware","vendor":"qualcomm"},{"product":"sd_820_firmware","vendor":"qualcomm"},{"product":"sdx20_firmware","vendor":"qualcomm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ4019, IPQ8064, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, QCA4531, QCA6174A, QCA6574AU, QCA6584, QCA6584AU, QCA9377, QCA9378, QCA9379, QCA9558, QCA9880, QCA9886, QCA9980, SD 210/SD 212/SD 205, SD 425, SD 625, SD 808, SD 810, SD 820, and SDX20, while processing firmware image signature, the internal buffer may overflow if the firmware signature size is large.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ40","id":"CVE-2014-9998","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:ipq4019_firmware","products":["qualcomm:ipq4019_firmware","qualcomm:ipq8064_firmware","qualcomm:mdm9206_firmware","qualcomm:mdm9607_firmware","qualcomm:mdm9635m_firmware","qualcomm:mdm9640_firmware","qualcomm:mdm9645_firmware","qualcomm:mdm9650_firmware","qualcomm:qca6174a_firmware","qualcomm:qca6574au_firmware","qualcomm:qca6584_firmware","qualcomm:qca6584au_firmware","qualcomm:qca9377_firmware","qualcomm:qca9379_firmware","qualcomm:qca9880_firmware","qualcomm:qca9886_firmware","qualcomm:qca9980_firmware","qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_425_firmware","qualcomm:sd_625_firmware","qualcomm:sd_808_firmware","qualcomm:sd_810_firmware","qualcomm:sd_820_firmware","qualcomm:sdx20_firmware"],"type":null,"year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2014-9999"},"packages":[],"prev":{"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-9997"},"products":["Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-11172","kev_date_added":null,"published":"2020-11-02"},{"cvss_score":9.8,"headline":"Command injection in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Wired Infrastructure and Networking","id":"CVE-2020-11117","kev_date_added":null,"published":"2020-09-08"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-10045","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-9988","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9120","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9143","kev_date_added":null,"published":"2018-04-18"}],"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-17","vendors":["Qualcomm, Inc."]},"summary":null,"url":"https://insights.sbomify.com/CVE-2014-9998/"}