BLU-IC2/IC4 Firmware CVE-2025-12424
CRITICALAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privilege foothold on device
-
DeliveryLocate vulnerable SUID binary
-
ExploitExecute binary to abuse elevated privileges
-
ExecutionObtain root on intercom
-
ImpactFull device compromise / access-control bypass
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local code-execution access to the device as a lower-privileged account in order to invoke the mis-privileged SUID-bit binary on BLU-IC2/BLU-IC4 firmware at or below version 1.19.5; the escalation is a post-access primitive, not a condition-free remote vector. Limiting factors: the attacker must first reach the device and run the binary (the SUID class contradicts the input vector's unauthenticated-network claim), only firmware ≤1.19.5 is affected, and the footprint is confined to these two specific intercom models. No special non-default feature toggle is named in the description - the vulnerable binary appears present in default firmware. |
| Impact | Signals conflict sharply and must be reconciled before prioritization. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with full VC/VI/VA and subsequent-system C/I/A High) yields a 10.0 that is inconsistent with the vulnerability class: a SUID-bit binary privilege escalation (CWE-269) is, by definition, a local primitive requiring an attacker to already execute code on the device as a lower-privileged user. AV:N and PR:N are therefore almost certainly incorrect for the root cause described - verify with the vendor advisory. The corroborating data points to genuinely lower real-world urgency: EPSS is 0.34% (26th percentile), there is no CISA KEV listing, and no public exploit was identified in the provided sources, so this is 'no public exploit identified at time of analysis.' Net assessment: this is a high-impact-if-reached issue (local root on an access-control intercom is serious) but NOT a drive-by remote 10.0; realistic risk is that of a local/post-access privilege escalation on a niche appliance, not a wormable internet-facing flaw. Treat the vendor's 10.0 as metadata to be challenged, not a confirmed remote-unauth rating. |
| Exploit ScenarioDerived | An attacker who has already obtained low-privileged code execution on a BLU-IC2 or BLU-IC4 intercom (e.g. via a web/service account, a chained remote bug, or physical/console access) invokes the vulnerable setuid binary to escalate to root and take full control of the device firmware (≤1.19.5). No public exploit code was identified in the provided sources, and realistic exploitation depends on first gaining a local foothold despite the input vector's AV:N claim. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Local privilege escalation in Azure Access BLU-IC2 and BLU-IC4 intercom firmware through 1.19.5 allows a lower-privileged local user to abuse a misconfigured SUID-bit binary and obtain elevated privileges. The authoritative assessment rates this as local, low-complexity, low-privilege exploitation (CVSS 3.1 AV:L/PR:L), which conflicts with the supplied CVSS 4.0 network/no-auth vector and should take precedence for prioritization. EPSS is 0.34% (26th percentile), and no CISA KEV entry or public exploit code is identified in the provided data.
RemediationAI
Upgrade BLU-IC2 and BLU-IC4 firmware to a release later than 1.19.5 as directed by the vendor advisory at https://azure-access.com/security-advisories; the provided data does not specify the exact fixed version, so confirm the patched release with Azure Access before rollout. Until patched, restrict local console, SSH, or shell access to trusted administrators and enforce least privilege, because the escalation requires an existing low-privileged foothold. If operationally feasible, identify and remove the SUID bit from the vulnerable binary, for example with chmod u-s on that file, or restrict its execution to a trusted group; this breaks any intended privileged functionality that depends on the SUID behavior and must be tested. Monitor device logs for unexpected invocation of SUID binaries by non-admin accounts.
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-269 improper privilege management: a SUID-bit binary on the firmware executes with the file owner's privileges, typically root, and a flaw in how it validates or handles caller input or arguments lets a local user leverage that inherited privilege. The CPE entries identify embedded firmware for Azure Access BLU-IC2 (cpe:2.3:o:azure-access:blu-ic2_firmware:*:*:*:*:*:*:*:*) and BLU-IC4 (cpe:2.3:o:azure-access:blu-ic4_firmware:*:*:*:*:*:*:*:*); the wildcard version fields mean CPE alone does not constrain the affected range, so the description's 'through 1.19.5' is the reliable boundary. This is a post-access escalation primitive on intercom devices, not a condition-free remote compromise; exploitation requires the attacker to already run code as a lower-privileged account on the device. The provided CVSS 4.0 vector's AV:N/PR:N claim is inconsistent with the SUID local mechanism and the authoritative assessment.
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
SUID-binary escalation is a local primitive needing a prior low-privileged foothold, so AV:L and PR:L; successful abuse grants full root, giving C:H/I:H/A:H with unchanged scope.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Privilege Escalation through SUID-bit Binary.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
Executive ViewAI
Azure Access BLU-IC2 and BLU-IC4 intercom firmware through version 1.19.5 contains a local privilege escalation flaw that allows a low-privileged local user to gain elevated control, and no vendor patch is currently available. Facilities relying on these intercoms for physical access control could face tampering or unauthorized door control if an attacker gains local access, though exploitation requires an authenticated local presence and no public exploit identified at time of analysis. Leadership should prioritize inventory and hardening of exposed units until a fix is released.
No vendor-released patch identified at time of analysis; restrict physical and local console access to authorized personnel, remove unnecessary local accounts, segment intercom devices on isolated VLANs, audit and correct SUID binary permissions, and monitor device logs for privilege escalation activity.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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
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