dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-11832

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 1.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Allocation of Resources Without Limits or Throttling vulnerability in Azure Access Technology BLU-IC2, Azure Access Technology BLU-IC4 allows Flooding.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The BLU-IC2 and BLU-IC4 access control devices contain a resource exhaustion vulnerability where the system fails to impose proper limits or throttling on resource allocation, enabling attackers to flood the device with requests or traffic. This critical flaw (CVSS 9.8) affects all versions through 1.19.5 and could lead to denial of service or system instability.

MitigationUpgrade BLU-IC2 and BLU-IC4 firmware to a version beyond 1.19.5 that addresses the resource throttling weakness; if no patched version is available, implement network-level rate limiting and traffic filtering to mitigate flooding attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Blu Ic2 FirmwareOperating system
Affected:< 1.20
Blu Ic4 FirmwareOperating system
Affected:< 1.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device web interface or check the physical device label to confirm the model is BLU-IC2 or BLU-IC4
    Affected if Device is a BLU-IC2 or BLU-IC4 unit
  2. Check firmware version
    Log into the device administrative interface and navigate to the firmware or system information page to view the installed firmware version
    Affected if Firmware version is listed as 1.19.5 or lower, or any version below 1.20
  3. Verify device is network accessible
    Confirm the device has an active IP address and responds to ping or network requests from your management station
    Affected if Device is reachable over the network, allowing external resource request flooding
  4. Confirm no rate limiting is visible
    Check device configuration pages for any throttling, rate limiting, or request queue settings related to resource consumption
    Affected if No explicit throttling controls are configured or visible in the device settings

If the device is a BLU-IC2 or BLU-IC4 with firmware version 1.19.5 or lower and is network accessible, the environment is affected by this resource exhaustion vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.20 or later
Fixed in 1.20
Interim mitigation

Upgrade BLU-IC2 and BLU-IC4 firmware to a version beyond 1.19.5 that addresses the resource throttling weakness; if no patched version is available, implement network-level rate limiting and traffic filtering to mitigate flooding attempts.

Recommended fix Moderate confidence

Firmware 1.20 for BLU-IC2 and BLU-IC4

  1. Identify the specific model (BLU-IC2 or BLU-IC4) of the Azure Access Technology device
  2. Access the device management interface or console
  3. Check the current firmware version to confirm it is below 1.20
  4. Obtain the firmware version 1.20 from the vendor (Azure Access Technology) through their official support channels or website
  5. Follow the vendor's standard firmware upgrade procedure, typically involving uploading the firmware file through the device's web interface or CLI
  6. After upgrade, verify the firmware version has been successfully updated to 1.20
  7. Confirm the vulnerability is resolved by checking that resource allocation now has proper limits or throttling in place
Caveat No specific breaking changes documented in the provided material; standard firmware upgrade precautions apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blu Ic2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11832 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data