BLU-IC2/IC4 Firmware CVE-2025-12478
CRITICALAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain man-in-the-middle position on network path
-
ExploitForce TLS downgrade or exploit weak cipher
-
ExecutionDecrypt or tamper with intercepted traffic
-
ImpactCapture credentials or forge access-control commands
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Encryption strength requirements
|
| Exploitation Conditions | The affected BLU-IC2/BLU-IC4 firmware (through 1.19.5) ships with a non-compliant TLS configuration (CWE-326 inadequate encryption strength - e.g. weak ciphers or outdated protocol versions), so the condition is simply running the default/shipped firmware at or below 1.19.5; no special feature toggle is required. The key LIMITING factor is that exploitation of a transport-crypto weakness realistically requires the attacker to obtain a man-in-the-middle / on-path network position between the client and the device to intercept, downgrade, or manipulate the TLS session - it is not a point-and-click remote exploit against an exposed port despite the AV:N rating. Devices segmented on isolated access-control VLANs with no untrusted on-path presence are substantially less exposed. |
| Impact | Signals conflict sharply and should temper the headline score. The vendor-supplied CVSS 4.0 vector rates this 10.0 Critical with full confidentiality, integrity, AND availability impact on both the vulnerable and subsequent systems (VC/VI/VA:H, SC/SI/SA:H), implying complete remote compromise. That is difficult to reconcile with the actual weakness class, CWE-326 (Inadequate Encryption Strength) described only as a 'Non-Compliant TLS Configuration' - a weak-crypto/transport issue that typically enables interception or manipulation of traffic by a man-in-the-middle, not direct arbitrary code execution or system takeover. The scope-change/availability metrics appear inflated for a TLS hardening defect and should be verified against the vendor advisory. Corroborating exploitation signals are low: EPSS is 0.24% (14th percentile), there is no CISA KEV listing, and no public exploit was identified in the provided data. Net assessment: despite the 10.0 label, real-world risk is more consistent with a Medium/High transport-security exposure requiring a privileged network position, not a wormable unauthenticated RCE. Treat it as a meaningful hardening priority for exposed BLU-IC2/IC4 deployments, but the Critical rating likely overstates exploitability - confirm concrete impact with the Azure Access advisory before emergency prioritization. |
| Exploit ScenarioDerived | An attacker positioned on the network path between a client and a BLU-IC2 or BLU-IC4 door-station (through firmware 1.19.5) exploits the weak/non-compliant TLS configuration to intercept or downgrade the encrypted channel, decrypting or tampering with access-control traffic such as credentials, door-release commands, or intercom data. No public exploit code was identified at time of analysis, and the attack depends on achieving a man-in-the-middle position rather than directly reaching the device over the open internet. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
BLU-IC2 and BLU-IC4 firmware through version 1.19.5 ships with a non-compliant TLS configuration (CWE-326, inadequate encryption strength), meaning transport sessions can be protected by deprecated protocol versions, weak cipher suites, or insufficient key lengths. An attacker who can obtain a man-in-the-middle position on the network path between a client and the device could intercept, downgrade, or manipulate those sessions to disclose or alter data in transit. The vendor assigns a maximum 10.0 CVSS 4.0 score, but exploitation realistically depends on an on-path presence rather than direct remote access to an exposed service, integrity impact is limited, and no public exploit has been identified at time of analysis; EPSS is 0.24% (14th percentile).
RemediationAI
No vendor-released patch or specific fixed firmware version is identified in the available data, so treat all deployments at or below 1.19.5 as unmitigated and monitor https://azure-access.com/security-advisories for a corrected firmware release, planning to upgrade both BLU-IC2 and BLU-IC4 units as soon as one is published. Until then, the effective control is removing the on-path attacker: place devices on an isolated management/access-control VLAN with no untrusted hosts, and block management traffic from crossing untrusted network segments so ARP spoofing or route injection cannot position an adversary in the TLS path. Where the firmware exposes selectable TLS settings, disable TLS 1.0/1.1 and weak or export cipher suites and pin clients to TLS 1.2+ with strong AEAD suites - the trade-off is that older clients or integrations may fail the handshake and need updating. Fronting the devices with a TLS-terminating reverse proxy or VPN concentrator that enforces a modern cipher policy similarly reduces exposure, at the cost of added infrastructure and a new component to keep patched. Finally, enable logging of handshake failures and anomalous renegotiations and watch for certificate warnings or downgrade attempts, which provide detection but do not prevent interception.
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 a transport-layer crypto policy weakness rather than a memory-safety or injection defect: CWE-326 (Inadequate Encryption Strength) covers the use of weak or deprecated cryptographic primitives, which in a TLS stack typically means TLS 1.0/1.1 still being negotiable, export or 3DES/RC4-class cipher suites left enabled, short RSA/DH key sizes, or missing forward secrecy. Because the flaw lives in the shipped configuration rather than in an application endpoint, it affects every deployment of the device that has not overridden the defaults - the CPE entries (cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware, any version) confirm the impact is scoped to the firmware image itself. The practical attack is an active on-path adversary who forces a downgrade during the handshake or passively decrypts once a weak suite is negotiated; note that the vendor's CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N with High impacts on the vulnerable and subsequent systems) assumes straightforward network reachability, whereas independent analysis treats the crypto weakness as AC:H with limited integrity/availability impact.
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
Weak TLS config requires an on-path MITM position (AC:H) and no auth (PR:N); impact is primarily confidentiality of intercepted access-control traffic (C:H) with limited tampering (I:L) and no availability effect.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Non-Compliant TLS Configuration.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
Executive ViewAI
BLU-IC2 and BLU-IC4 devices with firmware through version 1.19.5 use weak TLS configurations that could allow an attacker positioned on the network path to intercept or alter communications. Although the vendor assigns a maximum severity score, exploitation requires a man-in-the-middle position and no public exploit has been identified, so the immediate business risk is concentrated in network segments where these devices carry sensitive traffic.
No vendor patch is available. Interim mitigations include network segmentation to limit on-path exposure, restricting device communications to trusted network paths, enforcing TLS 1.2 or higher with strong cipher suites where configurable, using VPN or TLS inspection overlays, and monitoring for anomalous traffic or downgrade attempts.
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 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 attackers can retrieve server version information from Azure Access BLU-IC2 and BLU-IC4 physical
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
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB