{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65396 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65396 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65396 is a medium-severity vulnerability in n/a, published on 14 Jan 2026. 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-2025-65396 and fix it if it is affected.\n\nWhat it is: CVE-2025-65396 is a medium-severity vulnerability in n/a, published on 14 Jan 2026. 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-2025-65396 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-65396/ (Markdown: https://insights.sbomify.com/CVE-2025-65396/index.md)","id":"CVE-2025-65396","markdown":"https://insights.sbomify.com/CVE-2025-65396/index.md","name":"CVE-2025-65396","record":{"aliases":["GHSA-vfm3-wj3m-76mr"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Blurams Flare Camera","requires_auth":"none","summary":"A physically proximate attacker can short SPI pins to dump firmware, exposing keys and gaining bootloader shell access on Blurams cameras.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dome_flare_firmware","vendor":"blurams"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-1274","name":"Improper Access Control for Volatile Memory Containing Boot Code"},{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability in the boot process of Blurams Flare Camera version 24.1114.151.929 and earlier allows a physically proximate attacker to hijack the boot mechanism and gain a bootloader shell via the UART interface. This is achieved by inducing a read error from the SPI flash memory during the boot, by shorting a data pin of the IC to ground. An attacker can then dump the entire firmware, leading to the disclosure of sensitive information including cryptographic keys and user configurations.","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 n/a","id":"CVE-2025-65396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-65397"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-65380"},"products":["n/a"],"published":"2026-01-14","related":[{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2025-65397","kev_date_added":null,"published":"2026-01-14"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"A physically proximate attacker can short SPI pins to dump firmware, exposing keys and gaining bootloader shell access on Blurams cameras.","url":"https://insights.sbomify.com/CVE-2025-65396/"}