BLU-IC2 Firmware
CVE-2025-12365
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device web interface over network
-
ExploitSend request triggering error condition
-
ImpactRead sensitive error data leaked in HTTP header
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Error message sanitization
MITRE ATT&CK
1 technique across 1 tactic: Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to the HTTP/web management interface of a BLU-IC2 or BLU-IC4 device running firmware at or below 1.19.5, plus the ability to induce an error condition whose message the firmware then wraps into an HTTP response header. Per the CVSS vector (PR:N/UI:N) no authentication or user interaction is needed, but realistic risk is limited by the fact that these are specialized access-control/intercom appliances typically deployed on internal or segmented networks, so exposure depends on whether the management interface is reachable by the attacker. Impact is bounded to disclosure of sensitive information contained in error output - not direct code execution or data modification. |
| Impact | This is a moderate-to-low real-world priority despite a CVSS 4.0 base score of 6.9. The provided CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) indicates a network-reachable, low-complexity, unauthenticated flaw, which raises the nominal score, but the underlying weakness is CWE-209 (error message containing sensitive information) - an information-disclosure issue, not code execution. The input vector asserts VC:L/VI:L/VA:L (low confidentiality, integrity AND availability impact), which is inconsistent with the description and CWE: an error-message-in-HTTP-header leak realistically affects confidentiality only, so the integrity/availability impacts appear over-stated - verify against the vendor advisory. The EPSS score is low at 0.25% (15th percentile), consistent with no KEV listing and no identified public exploit, so there is no evidence of active or imminent widespread exploitation. Net: a genuine but low-severity information-disclosure bug in niche access-control hardware - patch in normal maintenance cycles rather than treating as an emergency. |
| Exploit ScenarioDerived | A remote attacker on a network that can reach the device's web interface sends requests crafted to trigger error conditions, causing the firmware to embed internal error details into an HTTP response header. The attacker reads these leaked details (e.g., stack/path/configuration fragments) to fingerprint the device and aid further attacks. No public exploit code has been identified, and the low-complexity network vector means no special tooling beyond an HTTP client is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Error output produced by the web management interface of BLU-IC2 and BLU-IC4 access-control appliances (firmware through 1.19.5) is wrapped into HTTP response headers, disclosing sensitive diagnostic detail to any remote client able to induce a failure condition. The CVSS 4.0 base score is 6.9, but our assessment bounds real impact to low-confidentiality information disclosure - no code execution, data modification, or denial of service - on appliances that are normally deployed on internal or segmented networks. No public exploit code or active exploitation has been identified at time of analysis (EPSS 0.25%, 15th percentile).
RemediationAI
No vendor-released patch has been identified at time of analysis, and the provided reference data contains no fixed version number; the vendor advisory at https://azure-access.com/security-advisories should be monitored for a firmware update for BLU-IC2 and BLU-IC4 above 1.19.5, which should be applied as soon as it is published. Until then, the effective controls are exposure reduction and header hygiene: restrict the device web management interface to a dedicated administrative VLAN and firewall it to known management hosts (side effect: administrators lose ad-hoc access from general user subnets), and front the appliances with a reverse proxy or WAF configured to strip or normalize non-standard and diagnostic response headers before they reach clients and logs (side effect: added hop, TLS termination considerations, and possible breakage of vendor management features that depend on custom headers). Where the firmware exposes a verbose/debug error or diagnostic mode, disable it if configurable, and scrub existing HTTP access and proxy logs that may already contain leaked diagnostic strings.
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-209, Generation of Error Message Containing Sensitive Information, applied here in the specific form of error text being emitted inside HTTP response headers rather than (or in addition to) the response body. The affected devices are embedded firmware images for the Azure Access BLU-IC2 and BLU-IC4 access-control/intercom appliances, identified by the CPE entries cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware. Because the leak occurs in a header, the exposed content is not confined to the browser view of the requesting client: intermediate proxies, load balancers, WAFs, and HTTP access logs commonly record response headers, so diagnostic strings containing internal paths, stack or module identifiers, backend addresses, or device state can propagate into monitoring and log infrastructure well beyond the original requester. Header-borne error text also raises the possibility of header splitting or response-splitting behavior if attacker-influenced input reaches the same code path, although the CVE as described is scoped to information disclosure. The upstream CVSS 4.0 vector (6.9) and our assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) agree on unauthenticated network reachability and no user interaction; we rate only confidentiality as affected, with no scope change, whereas the 4.0 vector carries low values across integrity and availability.
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:L/VI:L/VA:L/SC:L/SI:L/SA:L
Remote, low-complexity, unauthenticated trigger of error output (AV:N/AC:L/PR:N/UI:N); CWE-209 leaks information so C:L only, with no integrity or availability impact.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Error Messages Wrapped In HTTP Header.This 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