Security readout for executives and security teams
Plain-English summary
This issue affects Blurams Flare Camera firmware version 24.1114.151.929 and earlier, according to the description. A nearby attacker with physical access could interfere with boot and reach a bootloader shell, enabling firmware extraction and exposure of keys and device configuration. It is not described as a remote attack.
Executive priority
Handle as a targeted physical-access risk, not an emergency internet-wide threat. Prioritize cameras in exposed locations because compromise could reveal cryptographic material and private configuration data.
Technical view
The vulnerability is in the boot process. The source describes boot hijack through UART after inducing an SPI flash read error during startup. Successful access can allow full firmware dumping, with confidentiality and integrity impact from exposed cryptographic keys and user configurations. CVSS 3.1 is 6.1 with physical attack vector.
Likely exposure
Exposure is limited to organizations using Blurams Flare Camera version 24.1114.151.929 or earlier where attackers can physically reach the device or its internals.
Exploitation context
No KEV listing or cited source indicates active exploitation. The attack requires physical proximity and hardware-level access during boot, reducing broad internet-scale risk but increasing concern for cameras in public, shared, or hostile locations.
Researcher notes
The record has useful technical detail, but structured affected fields are listed as n/a. Analysis relies on the description naming Blurams Flare Camera version 24.1114.151.929 and earlier. No source-provided patch, workaround, or exploitation-in-the-wild evidence was included.
Mitigation direction
- Check Blurams support or advisories for firmware updates or official mitigations.
- Restrict physical access to deployed cameras, especially in public or shared spaces.
- Replace or remove cameras that cannot be physically protected.
- Treat physically tampered devices as compromised and rotate exposed credentials or keys.
- Review procurement standards for secure boot and debug-interface controls.
Validation and detection
- Inventory Blurams Flare Camera deployments and record firmware versions.
- Identify cameras at or below version 24.1114.151.929.
- Assess whether attackers can physically access device enclosures or ports.
- Inspect high-risk devices for signs of tampering.
- Monitor vendor sources for confirmed patches or configuration guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-1274: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-65396 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N0.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://lessonsec.com/cve/cve-2025-65396/CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control for Volatile Memory Containing Boot Code
Improper Access Control for Volatile Memory Containing Boot Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.