BLU-IC2/IC4 Firmware CVE-2025-12031
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain XSS foothold or MITM position
-
ExploitAccess victim cookie via JS or cleartext HTTP
-
ExecutionExfiltrate session cookie
-
ImpactReplay cookie to hijack session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V3 - Web Frontend Security HttpOnly cookie flag
|
| Exploitation Conditions | Exploitation is not standalone: because the cookies lack HttpOnly, an attacker must already be able to execute JavaScript in the device's web context (i.e. an existing XSS vulnerability) to read them from the JS context; because they lack Secure, an attacker alternatively needs a network man-in-the-middle position to capture cookies transmitted over cleartext HTTP. Limiting factors: the target must be a BLU-IC2 or BLU-IC4 running firmware at or below 1.19.5, a valid authenticated session cookie must exist to steal, and the device web interface must be reachable by the attacker. The CVSS PR:L indicates some privilege/authentication context is involved rather than fully anonymous access. |
| Impact | This is a low-to-moderate priority issue that the raw CVSS 4.0 score of 5.3 (MEDIUM) slightly overstates. The vulnerability is CWE-1004 - sensitive cookies issued by BLU-IC2/BLU-IC4 firmware (through 1.19.5) lacking the HttpOnly and Secure attributes - which is a contributing/enabling weakness, not a directly exploitable code-execution flaw. Exploitation signals are weak: EPSS is 0.21% (10th percentile), there is no CISA KEV listing, and no public exploit has been identified, so this is neither actively exploited nor broadly weaponizable. The provided CVSS 4.0 vector (AV:N/AC:L/PR:L with low impact across VC/VI/VA and subsequent-system SC/SI/SA) appears inflated for a cookie-attribute weakness: integrity and availability impact (VI:L/VA:L) and subsequent-system impacts are hard to justify for missing HttpOnly/Secure flags, which realistically affect only confidentiality and only once a secondary condition is met (an XSS payload to read the cookie from the JavaScript context, or a network man-in-the-middle position to capture a cookie sent over cleartext HTTP). No SSVC decision data was provided. Net: a genuine hardening defect worth patching on these access-control devices, but not an urgent, standalone remote-compromise risk. Verify the inflated I/A metrics with the vendor advisory. |
| Exploit ScenarioDerived | An attacker who already has a cross-site scripting foothold in the BLU-IC2/IC4 web interface, or who can intercept cleartext HTTP traffic to the device, reads a session cookie that was issued without HttpOnly/Secure protection. The stolen cookie is then replayed to hijack the authenticated session of a device operator. No public proof-of-concept exists; real impact depends on a second, enabling vulnerability or a MITM position. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Session cookies issued by the BLU-IC2 and BLU-IC4 device web interfaces (firmware through 1.19.5) are set without the Secure and HttpOnly attributes, so any party able to run JavaScript inside the device's web context or to intercept cleartext HTTP traffic can read those cookies and replay them to hijack an authenticated administrative session. Exploitation is not standalone: it requires a pre-existing script-injection (XSS) foothold or a network man-in-the-middle position, plus a live authenticated session cookie and reachability to the web UI, so despite the raw CVSS 4.0 score of 5.3 the practical risk is low-to-moderate. No public exploit code was identified at time of analysis, the issue is not KEV-listed, and EPSS is only 0.21% (10th percentile).
RemediationAI
No vendor-released patch identified at time of analysis, and no fixed firmware version is stated in the available data; administrators should monitor https://azure-access.com/security-advisories for an updated BLU-IC2/BLU-IC4 firmware release and treat builds at or below 1.19.5 as unpatched. Until a fix ships, apply compensating controls targeting the two exploitation paths: (1) disable or firewall the appliance web UI so it is reachable only from a dedicated management VLAN or a short allowlist of administrative jump hosts, which removes the MITM opportunity but complicates remote support and break-glass access; (2) force HTTPS-only management access and disable the cleartext HTTP listener or redirect it, which blocks passive cookie capture at the cost of breaking older management scripts and tools that hardcode http:// URLs; (3) reduce the XSS precondition by hardening the surrounding exposure - strict Content-Security-Policy on any fronting reverse proxy, input validation, and prompt patching of any other web-interface vulnerabilities - since without a script-injection foothold the missing HttpOnly flag cannot be exercised; (4) shorten administrative session lifetimes and force re-authentication where the platform allows, and rotate administrator credentials after any suspected compromise, accepting the added operational friction. Because stolen cookies cannot be distinguished from legitimate ones server-side, log and alert on concurrent sessions or unexpected source IPs for the management interface.
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-1004 (Sensitive Cookie Without 'HttpOnly' Flag) combined with a missing Secure attribute on session cookies served by the BLU-IC2 and BLU-IC4 web management interfaces. HttpOnly instructs the browser to hide a cookie from document.cookie and the JavaScript DOM, which is the primary defense against session theft via cross-site scripting; Secure instructs the browser to transmit the cookie only over TLS, which prevents passive capture on cleartext HTTP connections. Because neither flag is applied, the cookies are readable from the JavaScript context and are eligible to be sent over unencrypted channels. CPE data identifies the affected assets as the firmware of these appliances (cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware), with all versions through 1.19.5 affected per the vendor description. Note that the vulnerability class is a weakness amplifier rather than a standalone entry point: it converts an otherwise limited XSS or a plaintext-HTTP interception opportunity into full session compromise.
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:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L
Missing HttpOnly/Secure only yields impact when paired with XSS or MITM, so AC:H; it exposes cookie confidentiality only, hence C:L with I:N/A:N and no scope change.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
HTTP Security Misconfiguration - Lacking Secure and HTTPOnly Attribute may allow reading the sensitive cookies from the javascript contextThis 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 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