{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2014-10039 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-10039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-10039 is a critical memory corruption vulnerability in Qualcomm Mdm9625 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-10039 and fix it if it is affected.\n\nWhat it is: CVE-2014-10039 is a critical memory corruption vulnerability in Qualcomm Mdm9625 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-10039 in the wild and no public exploit code.\n\nAffected product: Qualcomm Mdm9625 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-10039/ (Markdown: https://insights.sbomify.com/CVE-2014-10039/index.md)","id":"CVE-2014-10039","markdown":"https://insights.sbomify.com/CVE-2014-10039/index.md","name":"CVE-2014-10039","record":{"aliases":["GHSA-7gj3-3h2f-v346"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon firmware","requires_auth":"none","summary":"An attacker can exploit improper stack restoration in Qualcomm Snapdragon firmware to execute arbitrary code via unexpected control flow.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"mdm9625_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-19","name":null}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9625, SD 400, and SD 800, calling qsee_app_entry_return() without first calling qsee_app_entry() will cause the stack to be restored to an older state resulting in a return to an unexpected location.","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":"Memory corruption in Snapdragon Mobile","id":"CVE-2014-10039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:mdm9625_firmware","products":["qualcomm:mdm9625_firmware","qualcomm:sd_400_firmware","qualcomm:sd_800_firmware"],"type":"memory_corruption","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-10043"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2014-10038"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9108","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9109","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9111","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9112","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9113","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Other in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2015-9115","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":"An attacker can exploit improper stack restoration in Qualcomm Snapdragon firmware to execute arbitrary code via unexpected control flow.","url":"https://insights.sbomify.com/CVE-2014-10039/"}