{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-8900 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8900 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8900 is a medium-severity code injection vulnerability in Apple SecureROM, published on 21 Feb 2025. 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-2019-8900 and fix it if it is affected.\n\nWhat it is: CVE-2019-8900 is a medium-severity code injection vulnerability in Apple SecureROM, published on 21 Feb 2025. 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-2019-8900 in the wild and no public exploit code.\n\nAffected product: Apple SecureROM. 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-2019-8900/ (Markdown: https://insights.sbomify.com/CVE-2019-8900/index.md)","id":"CVE-2019-8900","markdown":"https://insights.sbomify.com/CVE-2019-8900/index.md","name":"CVE-2019-8900","record":{"aliases":["GHSA-rq4h-cqfg-pj23"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Apple SecureROM","requires_auth":"none","summary":"An attacker with physical access can execute arbitrary code on Apple devices during boot in DFU mode via a SecureROM vulnerability.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apple","cpe":[{"product":"securerom","vendor":"apple"}],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"A vulnerability in the SecureROM of some Apple devices can be exploited by an unauthenticated local attacker to execute arbitrary code upon booting those devices. This vulnerability allows arbitrary code to be executed on the device. Exploiting the vulnerability requires physical access to the device: the device must be plugged in to a computer upon booting, and it must be put into Device Firmware Update (DFU) mode. The exploit is not persistent; rebooting the device overrides any changes to the device's software that were made during an exploited session on the device. Additionally, unless an attacker has access to the device's unlock PIN or fingerprint, an attacker cannot gain access to information protected by Apple's Secure Enclave or Touch ID features.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-03","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-03T15:23:50Z","kind":"github_poc","ref":"https://github.com/Weeabo-Inc/a9pwn","stars":1,"title":"checkm8 (CVE-2019-8900) for Apple A9, native to Linux — and a verdict system that never confuses 'this host cannot reset' with 'the exploit did not work'."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in SecureROM","id":"CVE-2019-8900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in iOS and iPadOS","id":"CVE-2019-8901"},"packages":[],"prev":{"headline":"This candidate is unused by its CNA.","id":"CVE-2019-8899"},"products":["SecureROM"],"published":"2025-02-21","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-22","vendors":["Apple"]},"summary":"An attacker with physical access can execute arbitrary code on Apple devices during boot in DFU mode via a SecureROM vulnerability.","url":"https://insights.sbomify.com/CVE-2019-8900/"}