Description

Smart Video Intercom System developed by Kingdom Communication Associated has a Missing Brute-force Protection vulnerability. Unauthenticated remote attackers can gain access to valid accounts through a large number of login attempts.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.5",
  "pubDate": "2026-09-11T08:16:48.377Z",
  "pubdate": "2026-09-11T08:16:48.377Z",
  "executiveSummary": "The Smart Video Intercom System, developed by Kingdom Communication Associated, is susceptible to a missing brute-force protection vulnerability. This security deficiency permits unauthenticated remote attackers to perform automated, high-frequency login attempts against the system's authentication interface.\nThe vulnerability stems from the absence of rate-limiting, account lockout mechanisms, or CAPTCHA-based challenges, which are standard security controls for identifying and mitigating programmatic login abuse. By systematically iterating through credential dictionaries or applying credential stuffing techniques, an attacker can bypass traditional authentication barriers.\nSuccessful exploitation allows unauthorized actors to gain access to valid user accounts. Given that the product is a video intercom system, compromised accounts may provide attackers with unauthorized access to sensitive functionalities, such as remote door unlocking, live audio-video surveillance streams, and system configuration settings. This poses significant physical and digital security risks to the environment where the system is deployed.\nThe vulnerability is remotely exploitable over the network without requiring prior authentication or administrative privileges. As there are no restrictions on the frequency of login requests, the system is highly vulnerable to automated exploitation scripts. Immediate implementation of access control mechanisms is required to prevent unauthorized system entry.",
  "technicalDetails": "The root cause of this vulnerability is the failure of the Kingdom Communication Associated Smart Video Intercom System to implement effective authentication throttling or request rate-limiting on its login endpoint. In a secure architecture, the application should monitor authentication requests and enforce constraints based on source IP address, session identifiers, or specific user accounts to detect and block abnormal traffic patterns.\nThe exploitation flow begins with an attacker identifying the target system's authentication service, typically exposed via a web-based management interface or an API endpoint over HTTP/HTTPS. Because the application logic does not track or limit the number of failed login attempts, an attacker can initiate a brute-force attack using automated tools, such as specialized credential stuffing scripts or distributed botnets.\nDuring the attack, the adversary sends a continuous stream of login requests, each containing a unique combination of username and password. The system processes these requests sequentially or in parallel without validation delays. Since the application does not trigger an account lockout or an exponential back-off timer after successive failed attempts, the attacker can iterate through large wordlists until a valid credential pair is discovered.\nThe vulnerability is considered high-risk due to the lack of secondary security controls. The absence of CAPTCHA challenges or multi-factor authentication (MFA) requirements allows scripts to bypass human verification entirely. Furthermore, the protocol does not enforce temporary account suspension, enabling an attacker to maintain a sustained and persistent brute-force attack indefinitely until the correct credentials are guessed.\nPost-exploitation impact is severe, as the attacker achieves authorized access to the device. Once authenticated, the attacker may exploit administrative privileges to manipulate system configurations, modify firmware settings, or intercept live video feeds, thereby compromising the privacy and physical security of the premises. The lack of anomalous behavior detection at the application level means the attack can often proceed undetected by standard logging mechanisms, as the system treats these brute-force requests as valid, albeit failed, authentication attempts."
}