BLU-IC2/IC4 Firmware CVE-2025-12516
CRITICALAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device HTTP interface over network
-
DeliverySend malformed/unexpected request
-
ExploitTrigger unhandled 5xx error
-
ExecutionObserve leaked error response
-
ImpactHarvest disclosed information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Status code handling
|
| Exploitation Conditions | Requires network reachability to the HTTP service of a BLU-IC2 or BLU-IC4 device running firmware 1.19.5 or earlier; the CVSS vector's PR:N/UI:N indicates no authentication or user interaction is needed to reach the vulnerable error path. The trigger is a request that drives the server into an unhandled error state returning HTTP 5xx. Limiting factors: these are special-purpose access-control appliances that in well-segmented physical-security deployments are typically not exposed to the public internet, so exploitation usually presupposes attacker access to the management/LAN segment; the realistic impact also depends on what the error response actually discloses, which the description does not specify. |
| Impact | Signals conflict sharply and this must be flagged before any prioritization. The input CVSS 4.0 vector rates this 10.0 (AV:N/AC:L/AT:N/PR:N/UI:N) with HIGH confidentiality, integrity AND availability on both the vulnerable and subsequent systems, implying full remote unauthenticated compromise. However, the description (CWE-394, 'Lack of Graceful Error Handling - HTTP 5xx Error') and the 'Information Disclosure' tag describe only an unhandled error condition that returns a 5xx response - a vulnerability class that typically yields minor information leakage or denial-of-service symptoms, NOT total system takeover. This is a material discrepancy: the scored impact is far more severe than the described defect, so the 10.0 should be treated as unverified until the vendor advisory is read. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no public exploit identified at time of analysis and no evidence of real-world exploitation. Combined with a niche access-control product footprint, realistic priority is LOWER than the raw 10.0 suggests - treat as 'high CVSS, impact unconfirmed, low observed exploitation' pending vendor confirmation of what the error handler actually exposes. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a malformed or unexpected HTTP request to the web/management interface of a BLU-IC2 or BLU-IC4 door-access device running firmware 1.19.5 or earlier, triggering an ungracefully handled server error (HTTP 5xx). Depending on what the error path leaks, the response may disclose internal state, stack or configuration details useful for further attack. No public exploit code is known at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Unhandled error conditions in the HTTP service of BLU-IC2 and BLU-IC4 access-control appliances running firmware 1.19.5 or earlier cause the devices to return HTTP 5xx responses that can leak implementation details, an information-disclosure weakness classified as CWE-394 (Unexpected Status Code or Return Value). The authoritative assessment scores this CVSS 3.1 as AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - unauthenticated network reachability, no user interaction, low confidentiality impact only - while the published CVSS 4.0 score of 10.0 asserts high confidentiality, integrity and availability impact across scope; that discrepancy is material and must be resolved before prioritization. No public exploit code and no CISA KEV entry were identified at time of analysis, though the appliances are typically segmented on physical-security networks rather than internet-exposed.
RemediationAI
No fixed firmware version is stated in the available data, so the first step is to obtain the vendor's patched build from the advisory at https://azure-access.com/security-advisories and upgrade BLU-IC2 and BLU-IC4 units currently on 1.19.5 or earlier; treat any build number above the affected range as unconfirmed until the vendor documents it. Where an immediate upgrade is not possible, compensate for the error-path exposure rather than for a memory-safety bug: restrict reachability of the device HTTP management interface to a dedicated administrative VLAN with allow-listed source addresses via firewall ACLs, which removes the unauthenticated network path the assessed vector depends on but requires disciplined address management and can lock out responders during an incident; front the interface with an authenticating reverse proxy or management jump host so that only authenticated, brokered sessions reach the appliance, at the cost of added infrastructure and a single point of failure; and, if the firmware exposes configurable error-page or debug/diagnostic verbosity settings, disable verbose error output and diagnostic endpoints so 5xx bodies do not carry stack traces or internal paths, noting that this only reduces the disclosure payload and does not fix the unhandled exception. Add monitoring for bursts of HTTP 5xx responses from these appliances and capture response bodies from suspicious requests to determine what is actually being leaked, since the description does not specify the disclosure content. Because the published CVSS 4.0 score (10.0) and the assessed CVSS 3.1 score (low confidentiality only) conflict sharply, confirm the true impact with the vendor advisory before committing to emergency change windows, and do not treat this record as equivalent to an actively exploited remote code execution issue - no public exploit code or KEV listing was identified at time of analysis.
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 class is CWE-394, Unexpected Status Code or Return Value: the embedded HTTP/web management service on these appliances does not gracefully handle malformed or unexpected requests and propagates the fault upward as an unhandled error, returning HTTP 5xx responses instead of a sanitized error page. In embedded firmware, such error paths frequently emit stack traces, internal file paths, framework or build identifiers, and backend service names in the response body - which is the information-disclosure angle reflected in the tags. The CPE entries (cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware) mark this as a firmware-level defect in the BLU-IC access-control product line rather than in a separately versioned application library, meaning remediation requires a firmware update from the vendor. The CVSS 4.0 vector supplied with the record (AV:N/AC:L/AT:N/PR:N/UI:N with VC/VI/VA:H and SC/SI/SA:H) describes a fully unauthenticated, no-interaction, total-impact compromise, but the assessed 3.1 vector reduces this to confidentiality-only (C:L) with no integrity or availability effect; the technical evidence in the description - a 5xx error-handling flaw tagged as information disclosure - is consistent only with the latter, since no code execution, authentication bypass, or memory-corruption primitive is described.
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
Network-reachable, unauthenticated unhandled-error path (CWE-394/'Information Disclosure') realistically yields limited info leakage, so C:L and I/A:N - far below the input's full-CIA 10.0.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Lack of Graceful Error Handling - HTTP 5xx ErrorThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
Executive ViewAI
BLU-IC2 and BLU-IC4 access-control appliances running firmware 1.19.5 or earlier remain without a vendor patch, leaving facilities that rely on them for physical access control with an unresolved information-exposure risk that could support follow-on attacks against security infrastructure. Leadership should care because these devices typically sit on sensitive physical-security networks, and the published CVSS 10.0 conflicts with the authoritative CVSS 3.1 assessment; prioritization should pause pending vendor/scoring clarification while exposure is reduced.
No vendor-released patch identified at time of analysis; interim mitigations include restricting HTTP management access to trusted administrative VLANs, blocking internet exposure, enforcing network ACLs and segmentation, disabling unnecessary HTTP services, monitoring HTTP 5xx responses and anomalous requests, and opening a vendor case for patch timeline and scoring clarification.
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