Skip to main content

BLU-IC2/IC4 Firmware CVE-2025-12478

CRITICAL
Inadequate Encryption Strength (CWE-326)
2025-10-29 a0340c66-c385-4f8b-991b-3d05f6fd5220
10.0
CVSS 4.0 · Vendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain man-in-the-middle position on network path
  2. Exploit
    Force TLS downgrade or exploit weak cipher
  3. Execution
    Decrypt or tamper with intercepted traffic
  4. Impact
    Capture 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.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220) PRIMARY 10.0 CRITICAL
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
vuln.today AI 6.5 MEDIUM

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.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).

CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

Non-Compliant TLS Configuration.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .

Executive ViewAI

Why It Matters

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.

Business Impact: Medium
Compensating Controls

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

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Low
niche physical-access-control intercom hardware, limited industry-specific footprint
Data Quality
3 sources
Confidence: Low

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Medium

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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

cpe:2.3:o:azure-access:blu-ic2_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:azure-access:blu-ic4_firmware:*:*:*:*:*:*:*:*
CVE-2025-12275 CRITICAL
10.0 Oct 26

Unauthenticated remote command execution affects Azure Access BLU-IC2 and BLU-IC4 firmware through version 1.19.5, where

CVE-2025-12422 CRITICAL
10.0 Oct 28

Arbitrary file write via path traversal in the firmware upgrade feature of Azure Access BLU-IC2 and BLU-IC4 boards (firm

CVE-2025-12104 CRITICAL
10.0 Oct 23

Outdated third-party UI dependencies in BLU-IC2 and BLU-IC4 firmware through 1.19.5 can expose the management web interf

CVE-2025-12220 CRITICAL
10.0 Oct 25

Network-reachable BLU-IC2 and BLU-IC4 devices running firmware through 1.19.5 embed BusyBox 1.31.1 and are exposed to mu

CVE-2025-12219 CRITICAL
10.0 Oct 25

Azure Access OS firmware through 1.19.5 on BLU-IC2 and BLU-IC4 physical access controllers contains unspecified vulnerab

CVE-2025-11832 CRITICAL
10.0 Oct 15

Denial-of-service conditions in Azure Access Technology BLU-IC2 and BLU-IC4 firmware through 1.19.5 allow remote attacke

CVE-2025-12477 CRITICAL
10.0 Oct 29

Unauthenticated remote attackers can retrieve server version information from Azure Access BLU-IC2 and BLU-IC4 physical

CVE-2025-12476 CRITICAL
10.0 Oct 29

Unauthenticated remote access to a critical function in Azure Access BLU-IC2/IC4 firmware through 1.19.5 lets a network

CVE-2025-12424 CRITICAL
10.0 Oct 28

Local privilege escalation in Azure Access BLU-IC2 and BLU-IC4 intercom firmware through 1.19.5 allows a lower-privilege

CVE-2025-12364 CRITICAL
10.0 Oct 27

Weak password policy in Azure Access BLU-IC2 and BLU-IC4 intercom access controller firmware through version 1.19.5 can

CVE-2025-12285 CRITICAL
10.0 Oct 26

BLU-IC2 and BLU-IC4 access-control/intercom units running firmware 1.19.5 or earlier ship with a factory default passwor

CVE-2025-12176 CRITICAL
10.0 Oct 24

BLU-IC2 and BLU-IC4 firmware through 1.19.5 contain undocumented administrative accounts that allow network-reachable at

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy