Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-55634: n/a

0
High
VulnerabilityCVE-2025-55634cvecve-2025-55634
Published: Fri Aug 22 2025 (08/22/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

Incorrect access control in the RTMP server settings of Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime - firmware v3.0.0.4662_2503122283 allows unauthorized attackers to cause a Denial of Service (DoS) via initiating a large number of simultaneous ffmpeg-based stream pushes.

AI-Powered Analysis

AILast updated: 08/22/2025, 17:18:02 UTC

Technical Analysis

CVE-2025-55634 is a vulnerability identified in the RTMP server settings of the Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime, specifically in firmware version 3.0.0.4662_2503122283. The flaw stems from incorrect access control mechanisms within the RTMP server configuration, which allows unauthorized attackers to exploit the device by initiating a large number of simultaneous ffmpeg-based stream pushes. This results in a Denial of Service (DoS) condition, effectively overwhelming the device's streaming capabilities and rendering it unavailable or unresponsive. The vulnerability does not require authentication, meaning any attacker with network access to the device can attempt exploitation. The attack leverages ffmpeg, a widely used multimedia framework, to push multiple streams concurrently, exploiting the device's insufficient restrictions on stream initiation. No CVSS score has been assigned yet, and no known exploits have been reported in the wild. The lack of patch links suggests that a fix may not yet be publicly available or disclosed. This vulnerability primarily impacts the availability of the affected device, disrupting its core functionality as a video doorbell and potentially causing broader network disruptions if the device is part of a larger security or IoT ecosystem.

Potential Impact

For European organizations, especially those deploying Reolink Smart 2K+ Wi-Fi Video Doorbells in residential, commercial, or critical infrastructure environments, this vulnerability poses a significant risk to operational continuity and physical security monitoring. A successful DoS attack could disable video surveillance capabilities, leading to gaps in security coverage and increasing the risk of unauthorized physical access or undetected incidents. Organizations relying on these devices for real-time monitoring or integration with broader security systems may experience cascading effects, including delayed incident response and compromised situational awareness. Additionally, if these devices are connected to corporate or home networks, the DoS condition could cause network congestion or instability, affecting other connected systems. The ease of exploitation without authentication further elevates the threat, as attackers do not need prior access or credentials. While no known exploits are currently active, the public disclosure of this vulnerability could prompt attackers to develop exploit tools, increasing the risk over time.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should first verify if their Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell devices are running the affected firmware version 3.0.0.4662_2503122283. If so, they should monitor Reolink's official channels for firmware updates or patches addressing this issue and apply them promptly once available. In the interim, network-level controls should be implemented to restrict access to the RTMP server ports from untrusted networks, ideally limiting connections to trusted IP addresses or VLANs. Deploying network segmentation to isolate IoT devices like video doorbells from critical infrastructure and corporate networks can reduce the attack surface. Rate limiting or traffic shaping on the network edge can help mitigate the impact of multiple simultaneous stream requests. Additionally, organizations should audit their device configurations to disable unnecessary streaming services or features if possible. Continuous monitoring for unusual network traffic patterns indicative of ffmpeg stream flood attempts should be established, with alerts configured to detect potential exploitation attempts. Finally, organizations should consider alternative or additional physical security measures to compensate for potential video monitoring outages.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2025-08-13T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68a8a2b8ad5a09ad00208652

Added to database: 8/22/2025, 5:02:48 PM

Last enriched: 8/22/2025, 5:18:02 PM

Last updated: 10/6/2025, 5:01:01 PM

Views: 34

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 are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats