External risk intelligence

BLU-IC Access Control Mail Configuration Manipulation and Command Execution

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2025-12275

The affected products, BLU-IC2 and BLU-IC4, are access control and identity management hardware appliances. These devices are commonly deployed as edge-facing gateways to manage physical access and network entry, making their administrative and management interfaces frequently accessible via the network to facilitate remote management and connectivity.

Azure Access Blu Ic2 Firmware

before 1.20

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists within certain Azure-Access BLU-IC hardware, potentially allowing unauthorized individuals to manipulate configurations and execute commands remotely. This issue impacts network-connected devices used for access control and identity management. The primary concern is to confirm if these specific devices are in use and, if so, to understand their exposure level.

  • Allows remote control of access devices.
  • Critical for managing sensitive entry points.
  • Confirm device presence and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could remotely access and manipulate a mail configuration file, which could then lead to command execution on the affected systems.

  • No authentication or network access required.
  • Attacker manipulates a mail configuration file.
  • Full system compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute arbitrary commands on the affected systems by manipulating configuration files. The potential impact includes unauthorized access and control over the system's services and data.

  • System configuration and data.
  • Remote manipulation of configuration files.
  • Unauthorized command execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

The affected BLU-IC2 and BLU-IC4 devices, likely managed by infrastructure or platform teams, require an immediate inventory to identify their presence and network exposure. Confirming business criticality and accountable ownership is the first step to prioritizing remediation efforts, which may involve coordination with the vendor, Azure-Access.

  • Identify and confirm accountable ownership.
  • Verify network reachability and business criticality.
  • Plan remediation, potentially coordinating with vendor.

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-IC series?

The BLU-IC2 and BLU-IC4 are physical access control and identity management hardware appliances. They function as edge-facing gateways that oversee entry points and network access, often sitting between physical infrastructure and the management network to enable remote connectivity.

What does CVE-2025-12275 mean for my device?

This vulnerability is classified as CWE-20: Improper Input Validation. In plain terms, the software fails to properly check data sent to it. An attacker can exploit this to alter mail configuration files, which acts as a bridge to execute unauthorized commands on the underlying system, potentially granting them full control.

How can an attacker trigger this vulnerability?

The flaw is triggered by sending specially crafted input that the system processes without authentication. Because the issue stems from configuration file manipulation, actions that do not involve interacting with the mail settings or the specific configuration interface will not trigger the command execution path.

Is my device at risk if it is behind a firewall?

According to Halo Surface Signal, these appliances are frequently deployed as edge-facing gateways for remote management, making them common targets. If your BLU-IC2 or BLU-IC4 is reachable via the network—even if intended for internal use—it may be exposed to this risk. Devices not connected to any network are less likely to be impacted.

How should I respond to this vulnerability?

First, conduct an immediate inventory to locate all BLU-IC2 and BLU-IC4 units in your environment. Confirm who owns these devices and assess their network reachability. Once identified, evaluate their business criticality and prepare to engage with Azure-Access to coordinate necessary security updates or configuration changes.

References