Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65397: n/a

0
Medium
VulnerabilityCVE-2025-65397cvecve-2025-65397
Published: Wed Jan 14 2026 (01/14/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

An insecure authentication mechanism in the safe_exec.sh startup script of Blurams Flare Camera version 24.1114.151.929 and earlier allows an attacker with physical access to the device to execute arbitrary commands with root privileges, if file /opt/images/public_key.der is not present in the file system. The vulnerability can be triggered by providing a maliciously crafted auth.ini file on the device's SD card.

AI-Powered Analysis

AILast updated: 01/21/2026, 19:14:07 UTC

Technical Analysis

CVE-2025-65397 identifies a security vulnerability in the Blurams Flare Camera firmware version 24.1114.151.929 and earlier. The vulnerability stems from an insecure authentication mechanism implemented in the safe_exec.sh startup script. Specifically, if the file /opt/images/public_key.der is absent, the script fails to properly verify the authenticity of configuration files. An attacker with physical access to the device can exploit this by inserting a maliciously crafted auth.ini file onto the device's SD card. Upon device startup, the script processes this file without adequate validation, allowing arbitrary command execution with root privileges. This can lead to full compromise of the device, including unauthorized access to video streams, manipulation of device settings, or pivoting to other networked systems. The vulnerability is categorized under CWE-287 (Improper Authentication) and CWE-20 (Improper Input Validation). The CVSS v3.1 base score is 6.8, reflecting a medium severity with a vector indicating physical attack vector (AV:P), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H). No patches or exploits are currently documented, but the risk is significant due to root-level command execution capability.

Potential Impact

For European organizations, this vulnerability poses a significant risk especially in sectors relying on Blurams Flare Cameras for security monitoring, such as retail, manufacturing, healthcare, and critical infrastructure. Successful exploitation can lead to full device compromise, enabling attackers to intercept or manipulate video feeds, disable security monitoring, or use the compromised device as a foothold for lateral movement within internal networks. This can result in breaches of sensitive data, disruption of security operations, and potential physical security risks. The requirement for physical access limits remote exploitation but does not eliminate risk in environments where devices are accessible to unauthorized personnel or where insider threats exist. Additionally, compromised cameras in public or semi-public spaces could be used to undermine privacy and surveillance integrity. The medium severity score reflects the balance between high impact and the physical access requirement.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Verify the presence of the /opt/images/public_key.der file on all Blurams Flare Cameras to ensure proper authentication mechanisms are in place. 2) Restrict physical access to camera devices by deploying them in secure enclosures or monitored locations to prevent unauthorized SD card insertion. 3) Regularly audit and inventory deployed cameras to identify vulnerable firmware versions and affected devices. 4) Engage with the vendor to obtain and apply firmware updates or patches as soon as they become available. 5) Implement physical tamper-evident measures and monitor device integrity to detect unauthorized modifications. 6) Use network segmentation to isolate camera devices from critical systems, limiting potential lateral movement if a device is compromised. 7) Train staff on the risks of physical device tampering and establish protocols for reporting suspicious activity. These measures go beyond generic advice by focusing on physical security controls and proactive device validation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-18T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6967d378d0ff220b95084e5d

Added to database: 1/14/2026, 5:33:44 PM

Last enriched: 1/21/2026, 7:14:07 PM

Last updated: 2/5/2026, 2:51:18 AM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats