BLU-IC2/IC4 Firmware CVE-2025-12552
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device login interface over network
-
ExploitEnumerate/guess weak credentials via brute force
-
ExecutionAuthenticate to device account
-
ImpactAccess intercom/access-control functions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Password strength requirements
|
| Exploitation Conditions | Exploitation requires network access to the device's authentication/login interface and depends on the firmware (BLU-IC2 and BLU-IC4 through 1.19.5) accepting weak passwords and lacking sufficient brute-force protection (CWE-521) - the weakness only yields access when a reachable account has a guessable password. Limiting factors: the device must be network-exposed (these access-control/intercom units are often on segmented or internal networks, which sharply reduces real-world reachability), success still hinges on an administrator having chosen a weak credential, and the per-success impact is Low (VC:L/VI:L/VA:L) rather than full takeover. There is no CISA KEV listing and no public exploit identified at time of analysis. |
| Impact | This is a genuine but moderate-priority issue, not an urgent one. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated weakness, and CWE-521 (Weak Password Requirements) combined with the 'Brute Force' tag indicates the device permits weak passwords that can be guessed remotely. However, the base score of 6.9 reflects only Low confidentiality/integrity/availability impact (VC:L/VI:L/VA:L), meaning a single successful guess yields limited direct impact rather than full compromise. Exploitation signals are weak: EPSS is 0.34% (26th percentile), there is no CISA KEV listing, and no public exploit was identified - so this is a latent configuration/design weakness rather than something under active mass exploitation. One conflict to verify: PR:N is scored as unauthenticated, yet the vulnerability class (insufficient password policy enabling brute force) only matters when accounts and a login interface exist, so real impact depends on an operator having set a weak password and on the device's authentication endpoint being network-exposed. Overall: patch/mitigate on a normal cadence and prioritize if these intercoms are internet-facing, but this does not carry the emergency weight of a remote code execution flaw. |
| Exploit ScenarioDerived | An attacker with network reachability to a BLU-IC2 or BLU-IC4 device's login interface runs an automated brute-force or credential-guessing attack, succeeding because the firmware (through 1.19.5) does not enforce strong password requirements or adequate lockout. No public exploit code is required - standard password-spraying tooling suffices - and the low attack complexity (AC:L) means no special timing or conditions are needed once the interface is reachable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Azure Access BLU-IC2 and BLU-IC4 access-control/intercom units running firmware through version 1.19.5 do not enforce an adequate password policy, letting remote attackers reach the login interface and repeatedly guess credentials because weak passwords are accepted and brute-force protections are insufficient. Successful guessing yields only low-impact access (confidentiality, integrity and availability all rated Low) rather than full device takeover, and reachability is further limited because these units typically sit on segmented or internal networks. There is no CISA KEV listing and no public exploit identified at time of analysis, and EPSS is low at 0.34% (26th percentile), so this is a genuine but moderate-priority hardening issue rather than an urgent one.
RemediationAI
No vendor-released patch identified at time of analysis - the only reference is the vendor advisory index at https://azure-access.com/security-advisories, which should be monitored for a firmware release later than 1.19.5 covering BLU-IC2 and BLU-IC4; do not assume a fixed build exists until the vendor publishes it. Until then, apply compensating controls in order of value: place the devices behind firewall ACLs or a management VLAN so the login interface is reachable only from trusted administrative hosts (the trade-off is that remote administration and some intercom/cloud integrations require explicit allow-listing); enforce strong, unique administrative passwords and remove or disable default and unused accounts, accepting the operational cost of credential management; and add rate limiting or account lockout at the network layer (reverse proxy, IPS login-guessing signatures, or NAC) together with alerting on repeated failed logins, recognizing that aggressive lockout can be abused to deny administrative access to the unit. Because the device itself does not reliably throttle guessing, network-layer brute-force protection is the substitute for the missing firmware control and should be treated as required rather than optional.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-521 (Weak Password Requirements) implemented in the firmware of two related Azure Access devices, identified by CPE as cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware, both flagged with wildcard versions for all releases through 1.19.5. The login/authentication service exposed on the network accepts passwords that do not meet modern length or complexity expectations and does not apply adequate throttling, lockout, or anti-automation controls, which turns ordinary credential guessing into a viable attack path. The weakness is a configuration/policy class defect rather than a memory-safety or injection flaw: nothing is corrupted or executed, the device simply fails to make guessing impractical. Because exploitation depends entirely on a reachable account already having a guessable password, the practical severity tracks password hygiene and network exposure rather than the flaw itself; the vendor's CVSS 4.0 scoring and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) agree that the outcome is unauthenticated network reachability with Low per-object impact.
Know when Brute Force gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L
Network-reachable login brute force with no prior privilege (AV:N/PR:N); low complexity because the policy permits weak passwords; limited per-account impact gives C:L/I:L/A:L.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Insufficient Password Policy.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
More in Brute Force
View allRuggedCom Rugged Operating System (ROS) before 3.3 has a factory account with a password derived from the MAC Address fi
An issue in the password change function of Silverpeas v6.4.2 and lower allows for the bypassing of password complexity
Victure RX1800 EN_V1.0.0_r12_110933 was discovered to utilize a weak default password which includes the last 8 digits o
Critical authentication bypass vulnerability in OpenC3 COSMOS v6.0.0 caused by weak password requirements that enable br
QaTraq 6.9.2 ships with administrative account credentials which are enabled in default installations and permit immedia
I-doit pro 25 and below and I-doit open 25 and below employ weak password requirements for Administrator account creatio
Weak Password Requirements in GitHub repository modoboa/modoboa prior to 2.1.0. Rated critical severity (CVSS 9.8), this
Weak Password Requirements in GitHub repository janeczku/calibre-web prior to 0.6.20. Rated critical severity (CVSS 9.8)
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity (CVSS 9.8), t
Beijing Zed-3 Technologies Co.,Ltd VoIP simpliclty ASG 8.5.0.17807 (20181130-16:12) has a Weak password vulnerability. R
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8. Rated critical severity (CVSS 9.8), th
Weak Password Requirements in GitHub repository ikus060/minarca prior to 4.2.2. Rated critical severity (CVSS 9.8), this
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB