{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2014-9985 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-9985 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-9985 is a critical vulnerability in Qualcomm Mdm9635m Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-9985 and fix it if it is affected.\n\nWhat it is: CVE-2014-9985 is a critical vulnerability in Qualcomm Mdm9635m Firmware, published on 18 Apr 2018. 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-2014-9985 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9635m 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-9985/ (Markdown: https://insights.sbomify.com/CVE-2014-9985/index.md)","id":"CVE-2014-9985","markdown":"https://insights.sbomify.com/CVE-2014-9985/index.md","name":"CVE-2014-9985","record":{"aliases":["GHSA-68c5-rcxp-23hp"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon Mobile","requires_auth":"none","summary":"A time-of-check time-of-use race condition in Qualcomm Snapdragon Mobile allows bypassing error checks, potentially leading to undefined behavior.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9635m_firmware","vendor":"qualcomm"},{"product":"sd_400_firmware","vendor":"qualcomm"},{"product":"sd_800_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-388","name":null}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9635M, SD 400, and SD 800, TOCTOU condition may result in bypassing error condition checks, leading to undefined behavior.","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":"Race condition in Snapdragon Mobile","id":"CVE-2014-9985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9635m_firmware","products":["qualcomm:mdm9635m_firmware","qualcomm:sd_400_firmware","qualcomm:sd_800_firmware"],"type":"race_condition","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-9986"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2014-9984"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2017-18160","kev_date_added":null,"published":"2019-01-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10494","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10495","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Mobile","id":"CVE-2016-10496","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":8.1,"headline":"Race condition in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2016-10433","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":7.8,"headline":"Integer overflow in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2017-18172","kev_date_added":null,"published":"2018-10-23"}],"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":"A time-of-check time-of-use race condition in Qualcomm Snapdragon Mobile allows bypassing error checks, potentially leading to undefined behavior.","url":"https://insights.sbomify.com/CVE-2014-9985/"}