BLU-IC2/IC4 Firmware CVE-2025-12284
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device web UI over network
-
ExploitSubmit crafted unvalidated input
-
ExecutionTrigger input-validation flaw (CWE-20)
-
ImpactDisclose or alter limited device data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Requires network reachability to the web management interface of a BLU-IC2 or BLU-IC4 device running firmware version 1.19.5 or earlier; per the CVSS vector no authentication (PR:N) or user interaction (UI:N) is needed. The primary limiting factor is exposure: these are access-control/intercom appliances whose web UIs are typically on internal or management networks rather than internet-facing, substantially narrowing the realistic attack surface. The description does not name a specific feature or non-default setting, so exploitation appears tied to the standard web UI rather than an optional configuration. |
| Impact | Signals are consistent and point to a MODERATE, low-urgency issue rather than a top priority. The vendor's CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw, but every impact metric is only Low (VC:L/VI:L/VA:L and subsequent SC:L/SI:L/SA:L), yielding a 6.9 MEDIUM score - meaning limited, not total, compromise. EPSS strongly corroborates low real-world risk: 0.19% probability at the 9th percentile, indicating exploitation is unlikely in the near term. There is no CISA KEV listing and no known public exploit code, so this is not confirmed as actively exploited. No SSVC decision data was provided. The one tension worth flagging: the description is extremely vague ('might lead to potential exploitation'), so the Low-across-the-board impact rating cannot be independently validated and the CWE-20 (Improper Input Validation) root cause could manifest more severely than the vendor's scoring implies - verify specifics with Azure Access. Net: patch in normal cycle, not emergency. |
| Exploit ScenarioDerived | A remote attacker with network access to a BLU-IC2 or BLU-IC4 device's web management UI submits crafted input to a field that lacks proper validation, causing the device to disclose information or behave unexpectedly. Per the CVSS vector, no authentication or user interaction is required and attack complexity is low, but the impact is limited to partial confidentiality/integrity/availability effects. No public proof-of-concept exploit is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Improper input validation in the web management interface of Azure Access BLU-IC2 and BLU-IC4 access-control/intercom appliances running firmware 1.19.5 and earlier lets unauthenticated remote attackers submit crafted input that yields limited confidentiality, integrity, and availability impact (CVSS 4.0 base 6.9; vendor-tagged as an information disclosure issue). Per the CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:N) no credentials or user interaction are required, so exposure is governed almost entirely by whether the device's web UI is reachable - these appliances normally sit on internal or management networks rather than the public internet. Risk is moderate and low-urgency: EPSS is 0.19% (9th percentile) and no public exploit code or CISA KEV entry was identified at time of analysis.
RemediationAI
No vendor-released patch with an exact fix version was identified at time of analysis, so the first step is to check the Azure Access security advisory page at https://azure-access.com/security-advisories for a fixed firmware build for BLU-IC2 and BLU-IC4 and apply it as soon as it is published, validating on a spare unit before fleet rollout because firmware updates on access-control hardware can reset configuration or briefly interrupt door/intercom service. Until a fixed build is confirmed, apply compensating controls around exposure: place the appliances' web management interfaces on a dedicated management VLAN and block inbound access to them from user, guest, and IoT segments at the firewall (trade-off: administrators need a jump host or VPN path to reach the UI); front the interfaces with an authenticating reverse proxy or network-level access control list restricted to admin source addresses (trade-off: adds a hop and a credential layer to maintain); and never publish these management ports to the internet, auditing existing NAT/port-forward rules to confirm. Because exploitation requires only reachability and no credentials, enable and forward HTTP/audit logging from the devices to a SIEM and alert on anomalous request patterns or error spikes against the web UI (trade-off: modest log volume and tuning effort).
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 affected components are the embedded firmware images for two Azure Access (Azure Access Control) physical access-control devices, BLU-IC2 and BLU-IC4, identified by the CPEs cpe:2.3:o:azure-access:blu-ic2_firmware and cpe:2.3:o:azure-access:blu-ic4_firmware. The weakness class is CWE-20 (Improper Input Validation): the firmware's HTTP/HTTPS administrative web interface accepts user-supplied data without adequately validating its form, length, or content before processing, which can lead to unexpected application behavior, error-driven information leakage, or limited state manipulation rather than direct code execution. Because the flaw lives in the web layer, the attack path is ordinary HTTP requests to the management port on the device; no authentication or user interaction is required per the assessed vector, meaning the only real barrier is network segmentation between the attacker and the appliance's management interface. The vendor's own tagging as "Information Disclosure" alongside low-severity confidentiality, integrity, and availability ratings indicates the practical effect is more likely partial data exposure or interface misbehavior than full device compromise, and the vendor description does not name a specific feature or non-default configuration, so the standard web UI is the surface.
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
Vendor vector and description indicate network, low-complexity, unauthenticated access to the web UI (AV:N/AC:L/PR:N/UI:N) with only partial impacts, so C/I/A each Low.
Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).
CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
DescriptionCVE.org
Lack of Input Validation in the web UI might lead to potential exploitation.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