CVE-2024-37654VulnerabilityPublished 21 Jun 2024Updated 21 Nov 2024

CVE-2024-37654: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium · fixed in 3.9.2 : update affected systems when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.9.2

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-37654, organizations should immediately verify and apply firmware updates from BAS-IP, ensuring devices run version 3.9.2 or later where the vulnerability is addressed. Network segmentation should be enforced to isolate BAS-IP devices from untrusted networks and restrict access to management interfaces to authorized personnel only. Implement strict firewall rules to limit HTTP access to these devices, preferably allowing only trusted IP addresses. Employ network monitoring and intrusion detection systems to identify anomalous HTTP GET requests targeting BAS-IP devices. Disable or restrict remote management features if not required, and enforce strong authentication mechanisms for device access. Regularly audit device configurations and logs for signs of unauthorized access attempts. Additionally, educate staff about the risks of interacting with suspicious links or requests that could trigger exploitation. If vendor patches are delayed, consider temporary compensating controls such as web application firewalls with custom rules to block malicious request patterns targeting the vulnerability.

Description

An issue in BAS-IP AV-01D, AV-01MD, AV-01MFD, AV-01ED, AV-01KD, AV-01BD, AV-01KBD, AV-02D, AV-02IDE, AV-02IDR, AV-02IPD, AV-02FDE, AV-02FDR, AV-03D, AV-03BD, AV-04AFD, AV-04ASD, AV-04FD, AV-04SD, AV-05FD, AV-05SD, AA-07BD, AA-07BDI, BA-04BD, BA-04MD, BA-08BD, BA-08MD, BA-12BD, BA-12MD, CR-02BD before 3.9.2 allows a remote attacker to obtain sensitive information via a crafted HTTP GET request.

Impact

The primary impact of CVE-2024-37654 is unauthorized disclosure of sensitive information from BAS-IP intercom and access control devices. This can lead to exposure of configuration settings, user credentials, or network topology details, which attackers could leverage for further attacks such as lateral movement, privilege escalation, or physical security bypass. Organizations relying on these devices for building access control, visitor management, or security monitoring may face increased risk of targeted intrusions or espionage. Although the vulnerability does not directly affect device integrity or availability, the confidentiality breach can undermine trust in security controls and lead to compliance violations, especially in regulated industries. The requirement for user interaction and local network access somewhat limits remote exploitation, but insider threats or compromised internal hosts could exploit this vulnerability. The absence of known exploits reduces immediate risk but does not preclude future attacks. Overall, the vulnerability poses a moderate risk to organizations with BAS-IP deployments, particularly in sectors such as government, critical infrastructure, corporate campuses, and residential complexes.

Summary

CVE-2024-37654 is a vulnerability identified in a broad range of BAS-IP intercom and access control devices, including models AV-01D through BA-12MD and CR-02BD, affecting firmware versions before 3.9.2. The flaw allows a remote attacker to extract sensitive information by crafting a specific HTTP GET request to the device's web interface or API endpoints. The vulnerability stems from improper access control or insufficient validation of HTTP requests (CWE-922), enabling unauthorized information disclosure. The CVSS 3.1 base score is 6.1, reflecting a medium severity level, with attack vector local (AV:L), low attack complexity (AC:L), no privileges required (PR:N), and user interaction required (UI:R). The scope is unchanged (S:U), with high confidentiality impact (C:H), low integrity impact (I:L), and no availability impact (A:N). This suggests that while the attacker cannot modify or disrupt device operation, they can gain access to sensitive data, potentially including configuration details, user credentials, or network information. No public exploits have been reported yet, but the vulnerability's presence in widely deployed BAS-IP devices used in physical security systems makes it a concern. The lack of a patch link indicates that users should verify firmware updates from the vendor and apply version 3.9.2 or later to remediate the issue.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/DrieVlad/BAS-IP-vulnerabilities (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 05:17 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats