Azure Access BLU CVE-2025-12477
CRITICALAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device over network
-
ExploitSend unauthenticated request to server interface
-
ImpactRetrieve exposed server version information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Affected devices are BLU-IC2 and BLU-IC4 running firmware version 1.19.5 or earlier; the fix presumably lies in a later firmware release (not specified in input). Per the CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:N), exploitation requires only network reachability to the device's server/web interface with no authentication, no user interaction, and no special attack requirements - so the primary limiting factor is network exposure of the device. In practice these are physical access-control intercom appliances typically deployed on internal or management networks, so exploitation is constrained to attackers who can route to the device; internet-exposed units would be directly reachable. As literally described, the triggered condition is disclosure of the server version; whether the unauthenticated path enables more (as CWE-306 implies) is not established by the Description. |
| Impact | The signals here are sharply contradictory and must be reconciled before prioritization. The vendor-supplied CVSS 4.0 vector scores 10.0 (AV:N/AC:L/AT:N/PR:N/UI:N with high impact to both the vulnerable and subsequent systems across confidentiality, integrity and availability), the CWE is CWE-306 (Missing Authentication for a Critical Function), and the tag set includes 'Authentication Bypass' - all of which describe a remote, unauthenticated, full-compromise flaw. Yet the human-readable Description reads only 'Server Version Disclosure,' which is a classic low-severity information-exposure issue (normally CWE-200, ~CVSS 5.3), not a total compromise. This is a direct, unresolved conflict: the title implies a minor information leak while the metadata implies critical missing authentication. EPSS is low at 0.35% (27th percentile), the CVE is NOT on CISA KEV, and no POC is referenced, so there is no public evidence of exploitation. Net assessment: if the CWE-306/CVSS 10.0 metadata is accurate, this is a genuine critical priority on exposed devices; if the Description is accurate, it is a modest information-disclosure issue over-scored by the metadata. Given the low EPSS, absence of KEV, no POC, and the niche deployment footprint of these access-control devices, this is unlikely to be mass-exploited in the near term, but the severity of the underlying flaw cannot be confirmed from the conflicting data and MUST be verified against the vendor advisory before final triage. |
| Exploit ScenarioDerived | An attacker with network reachability to an exposed BLU-IC2 or BLU-IC4 device (firmware ≤1.19.5) sends an unauthenticated request to the device's server interface and receives server/version information back, per the Description. If the CWE-306 'Missing Authentication' metadata is accurate, the same unauthenticated access path could extend beyond version disclosure to unauthorized control of the intercom/access-control function. No public exploit code is referenced, so exploitation would currently require custom tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Unauthenticated remote attackers can retrieve server version information from Azure Access BLU-IC2 and BLU-IC4 physical access-control intercom appliances running firmware 1.19.5 or earlier, exposing fingerprinting data that aids follow-on targeting. The CWE-306 classification (Missing Authentication for Critical Function) hints that the underlying weakness may be a missing authentication check rather than a purely cosmetic banner leak, but the description as written establishes only version disclosure, and our assessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - confidentiality-only, no integrity or availability impact. EPSS is 0.35% (27th percentile), there is no CISA KEV entry, and no public exploit code has been identified at time of analysis; the practical risk is gated almost entirely by whether these appliances are reachable from untrusted networks.
RemediationAI
Upgrade BLU-IC2 and BLU-IC4 appliances to a firmware release later than 1.19.5 as directed by the vendor advisory at https://azure-access.com/security-advisories; the provided data identifies 1.19.5 as the last affected version but does not specify the exact fixed build, so confirm the target version with Azure Access support before rolling out, and stage the upgrade because these are door-control devices where a failed flash can leave an entry point inoperative. Where immediate upgrade is not possible, apply specific compensating controls: place all BLU-IC2/IC4 devices behind firewall rules or ACLs that permit the web/server interface only from the management subnet or integration hosts that actually need it (trade-off: administrators must use jump hosts or VPN, and remote integrations may break); never publish these appliances directly to the internet and verify with an external scan that no management port is internet-reachable; segment the devices onto a dedicated IoT/physical-security VLAN with no outbound path to corporate IT (trade-off: adds routing complexity and may disrupt cloud-based access-control integrations); and monitor device logs and network flows for repeated or anomalous requests to the version-serving endpoint as a fingerprinting indicator. Version disclosure reduces the value of banner suppression alone, so treat network restriction as the primary interim control rather than relying on hiding the banner, which is unlikely to be configurable on this firmware.
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
BLU-IC2 and BLU-IC4 are embedded-Linux intercom/door-entry controllers that expose a local web/server interface used for configuration and integration, and the firmware images are catalogued as cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware. The reported weakness is server version disclosure, an information-exposure pattern in which the appliance's HTTP service or another listening daemon returns a banner, header, or error page identifying the exact firmware/build, letting an attacker map the device to known vulnerabilities for its version. The CWE mapping is CWE-306, Missing Authentication for Critical Function, which is a materially different root cause from banner leakage: it describes an endpoint or operation that should require authentication but does not, and it carries a far higher potential impact than the description substantiates. That mismatch is the central analytic problem. The published CVSS 4.0 vector scores 10.0 with high confidentiality, integrity and availability impact (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H), which would imply a remotely exploitable, fully unauthenticated compromise of the device - inconsistent with a version-string leak. Our reconciled CVSS 3.1 assessment (C:L only, S:U) treats the confirmed behavior as information disclosure and explicitly does not credit impact that the description does not establish. The CVSS 4.0 vector does agree on the attack surface: AV:N/AC:L/AT:N/PR:N/UI:N, meaning no authentication, no user interaction, and no special preconditions beyond network reachability, so any remediation must assume the vulnerable service should never be exposed.
Know when Blu Ic2 Firmware 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:H/VI:H/VA:H/SC:H/SI:H/SA:H
Description states only unauthenticated network-reachable server version disclosure (C:L, I/A:N); vendor's CWE-306/10.0 implies far greater impact but is unverified, so I scored the disclosure actually described.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Server Version Disclosure.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
Executive ViewAI
Azure Access BLU-IC2 and BLU-IC4 physical access-control intercoms running firmware 1.19.5 or earlier expose version information to unauthenticated remote users, enabling fingerprinting that could support follow-on targeting. Leadership should focus on exposure: no public exploit identified at time of analysis, the scoring vector indicates confidentiality-only impact, and no vendor-released patch identified at time of analysis, so risk is concentrated in any units reachable from untrusted networks.
No vendor-released patch identified at time of analysis; restrict network reachability to trusted management networks, segment BLU-IC2 and BLU-IC4 appliances on dedicated VLANs, enforce VPN or jump-host administration, and monitor for reconnaissance against firmware 1.19.5 or earlier.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
More in Blu Ic2 Firmware
View allUnauthenticated remote command execution affects Azure Access BLU-IC2 and BLU-IC4 firmware through version 1.19.5, where
Arbitrary file write via path traversal in the firmware upgrade feature of Azure Access BLU-IC2 and BLU-IC4 boards (firm
Outdated third-party UI dependencies in BLU-IC2 and BLU-IC4 firmware through 1.19.5 can expose the management web interf
Network-reachable BLU-IC2 and BLU-IC4 devices running firmware through 1.19.5 embed BusyBox 1.31.1 and are exposed to mu
Azure Access OS firmware through 1.19.5 on BLU-IC2 and BLU-IC4 physical access controllers contains unspecified vulnerab
Denial-of-service conditions in Azure Access Technology BLU-IC2 and BLU-IC4 firmware through 1.19.5 allow remote attacke
Unauthenticated remote access to a critical function in Azure Access BLU-IC2/IC4 firmware through 1.19.5 lets a network
Local privilege escalation in Azure Access BLU-IC2 and BLU-IC4 intercom firmware through 1.19.5 allows a lower-privilege
Weak password policy in Azure Access BLU-IC2 and BLU-IC4 intercom access controller firmware through version 1.19.5 can
BLU-IC2 and BLU-IC4 access-control/intercom units running firmware 1.19.5 or earlier ship with a factory default passwor
BLU-IC2 and BLU-IC4 firmware through 1.19.5 contain undocumented administrative accounts that allow network-reachable at
Denial of service in Azure Access BLU-IC2 and BLU-IC4 firmware through 1.19.5 allows unauthenticated network attackers w
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB