External risk intelligence

BLU-IC2 and BLU-IC4 Authentication Bypass

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2025-12476

The BLU-IC2 and BLU-IC4 are physical access control panels typically deployed as edge or gateway devices to manage facility entry. As network-connected controllers that manage security infrastructure, these products are designed to be reachable via the network to facilitate authentication and management, making them inherently public-facing or edge-adjacent in most standard deployment configurations.

Missing Authentication

Azure Access Blu Ic2 Firmware

before 1.20

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in Azure Access BLU-IC devices that could allow unauthorized access. This issue stems from a lack of proper authentication, meaning systems may not verify the identity of users or devices attempting to interact with them, potentially exposing sensitive operations.

  • Unauthenticated access is possible.
  • Leadership should track vendor response.
  • Confirm relevance and exposure of devices.

Attack Path

How an attacker could exploit the issue

An attacker can reach the vulnerable component by initiating network requests to the affected devices. Because the component lacks authentication, any unauthenticated user can interact with it. Successful interaction with this vulnerable component could lead to a complete compromise of the system, as indicated by the critical severity.

  • No authentication is required.
  • Network requests trigger the vulnerability.
  • Complete system compromise is possible.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, systems could be exposed to unauthorized access. This vulnerability may affect critical components due to a lack of authentication checks.

  • System data and functionality at risk.
  • Unauthorized network access can occur.
  • Complete compromise of device control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Azure-Access BLU-IC devices are likely managed by a combination of infrastructure and security teams, with application owners or system administrators responsible for the specific instances. The initial practical step is to identify all deployed BLU-IC devices, assess their network reachability and business criticality, and then assign ownership for remediation planning.

  • Identify affected BLU-IC instances.
  • Verify network exposure and critical systems.
  • Plan coordinated vendor remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Azure Access BLU-IC2 and BLU-IC4?

These are physical access control panels used to manage entry to facilities. They serve as edge or gateway devices within a building's security infrastructure, acting as the decision-making point for granting access to secured doors and areas.

What does CWE-306 mean for CVE-2025-12476?

CWE-306 refers to 'Missing Authentication for Critical Function.' In the context of this CVE, it means the device fails to verify the identity of someone requesting to perform an action. Because there is no check, the system treats an unverified network request as if it were legitimate.

How is this vulnerability triggered?

The vulnerability is triggered by sending a specific network request to the device. Because the system lacks an authentication gate, the bug does not require any credentials or previous interaction to succeed. It is not triggered by physical interaction, only by network-based communication.

Is my device at risk based on Halo Surface Signal?

According to Halo Surface Signal, these devices are designed as network-connected controllers, making them typically reachable via the network. Because they are often deployed at the edge to manage physical security, they are classified as highly likely to be network-accessible or public-facing.

How should I respond to this advisory?

Begin by creating an inventory of all BLU-IC2 and BLU-IC4 devices in your environment. Once identified, map out their network reachability to understand which units are accessible from broader network segments. Finally, coordinate with your infrastructure and security teams to monitor for updates from the vendor to remediate the authentication gap.

References