Overview
CVE-2025-55634 is a critical vulnerability that affects the RTMP server settings of the Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime. This vulnerability, due to incorrect access control, could potentially allow an unauthorized attacker to cause a Denial of Service (DoS) by initiating a large number of simultaneous ffmpeg-based stream pushes. Given the increasing use of smart devices, this security flaw is significant and requires immediate attention.
Vulnerability Summary
CVE ID: CVE-2025-55634
Severity: High (7.5)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Denial of Service, potential system compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime | v3.0.0.4662_2503122283
How the Exploit Works
The CVE-2025-55634 vulnerability arises due to incorrect access control in the RTMP server settings of the affected device. An attacker can exploit this vulnerability by initiating a large number of simultaneous ffmpeg-based stream pushes. This could cause an overload of the system resources, leading to a denial of service. In certain circumstances, this could potentially lead to system compromise or data leakage.
Conceptual Example Code
While the exact method of exploiting this vulnerability may differ based on the attacker’s approach, a conceptual example might involve sending a series of commands to initiate numerous ffmpeg-based stream pushes. Note that this is a conceptual example and may not represent a real-world attack scenario.
for i in {1..10000}
do
ffmpeg -i rtsp://target.ip.address:554/stream -f flv rtmp://target.ip.address/live/stream$i &
done
In this example, the attacker initiates 10,000 simultaneous ffmpeg-based stream pushes, which could potentially overwhelm the system, causing a denial of service.
