{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2018-11257 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11257 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11257 is a high-severity vulnerability in Qualcomm Sd 205 Firmware, published on 6 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11257 and fix it if it is affected.\n\nWhat it is: CVE-2018-11257 is a high-severity vulnerability in Qualcomm Sd 205 Firmware, published on 6 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-11257 in the wild and no public exploit code.\n\nAffected product: Qualcomm Sd 205 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-2018-11257/ (Markdown: https://insights.sbomify.com/CVE-2018-11257/index.md)","id":"CVE-2018-11257","markdown":"https://insights.sbomify.com/CVE-2018-11257/index.md","name":"CVE-2018-11257","record":{"aliases":["GHSA-95j3-3r8c-7w6p"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Snapdragon Mobile","requires_auth":"low_privilege","summary":"An insecure option allows RPMB erase on secure devices, bypassing security controls in Qualcomm Snapdragon Mobile firmware.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"sd_205_firmware","vendor":"qualcomm"},{"product":"sd_210_firmware","vendor":"qualcomm"},{"product":"sd_212_firmware","vendor":"qualcomm"},{"product":"sd_845_firmware","vendor":"qualcomm"},{"product":"sd_850_firmware","vendor":"qualcomm"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Permissions, Privileges, and Access Controls in TA in Snapdragon Mobile has an options that allows RPMB erase for secure devices in versions SD 210/SD 212/SD 205, SD 845, SD 850.","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":"Security feature bypass in Snapdragon Mobile","id":"CVE-2018-11257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:sd_205_firmware","products":["qualcomm:sd_205_firmware","qualcomm:sd_210_firmware","qualcomm:sd_212_firmware","qualcomm:sd_845_firmware","qualcomm:sd_850_firmware"],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear","id":"CVE-2018-11258"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2018-11256"},"products":["Snapdragon Mobile"],"published":"2018-07-06","related":[{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2014-10056","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile, Snapdragon Wear","id":"CVE-2015-9205","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10407","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10458","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Weak cryptography in Snapdragon Automobile, Snapdragon Mobile","id":"CVE-2016-10467","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Integer overflow in Snapdragon Mobile","id":"CVE-2016-10475","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":9.8,"headline":"Memory corruption in Snapdragon Mobile","id":"CVE-2016-10477","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Qualcomm, Inc."]},"summary":"An insecure option allows RPMB erase on secure devices, bypassing security controls in Qualcomm Snapdragon Mobile firmware.","url":"https://insights.sbomify.com/CVE-2018-11257/"}