{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-10055 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-10055 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-10055 is a high-severity vulnerability in Qualcomm Sd 400 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-10055 and fix it if it is affected.\n\nWhat it is: CVE-2014-10055 is a high-severity vulnerability in Qualcomm Sd 400 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-10055 in the wild and no public exploit code.\n\nAffected product: Qualcomm Sd 400 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-10055/ (Markdown: https://insights.sbomify.com/CVE-2014-10055/index.md)","id":"CVE-2014-10055","markdown":"https://insights.sbomify.com/CVE-2014-10055/index.md","name":"CVE-2014-10055","record":{"aliases":["GHSA-gjcm-jj24-9jc7"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Qualcomm Snapdragon Mobile","requires_auth":"none","summary":"Attackers can leak protected contents from OCMEM if the Host OS fails to request security restoration, affecting Qualcomm Snapdragon devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"sd_400_firmware","vendor":"qualcomm"},{"product":"sd_800_firmware","vendor":"qualcomm"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 400 and SD 800, there could be leakage of protected contents if HLOS doesn't request for security restoration for OCMEM xPU's.","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":"Information disclosure in Snapdragon Mobile","id":"CVE-2014-10055","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:sd_400_firmware","products":["qualcomm:sd_400_firmware","qualcomm:sd_800_firmware"],"type":"information_disclosure","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2014-10056"},"packages":[],"prev":{"headline":"Privilege escalation in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2014-10054"},"products":["Snapdragon Mobile"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2014-9994","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2014-9995","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2014-9996","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2015-9133","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2015-9219","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Mobile","id":"CVE-2015-9221","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Null dereference in Snapdragon Mobile","id":"CVE-2016-10489","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":"Attackers can leak protected contents from OCMEM if the Host OS fails to request security restoration, affecting Qualcomm Snapdragon devices.","url":"https://insights.sbomify.com/CVE-2014-10055/"}