dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12218

CRITICAL · 9.1 CVSS v3.1 Published 2025-10-25
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
Weak Default Credentials.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 devices up to version 1.19.5 ship with weak default credentials, allowing unauthenticated attackers to gain administrative access to the devices.

MitigationImmediately change all default credentials on affected devices to strong, unique passwords following organizational policy, and restrict network access to trusted users only.

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
None

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

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 BLU-IC2 or BLU-IC4 devices on your network
    Review network inventory, device discovery logs, or physically inspect devices for 'BLU-IC2' or 'BLU-IC4' model labels. Check DHCP lease tables or network scans for devices with hostname containing 'BLU-IC' or vendor 'Azure Access Blu'.
    Affected if Any BLU-IC2 or BLU-IC4 device is found on the network
  2. Check firmware version on BLU-IC devices
    Log into the device web interface or CLI and navigate to System > About, Settings > Firmware Info, or run 'show version' command. Compare the displayed firmware version against the affected range of < 1.20.
    Affected if Firmware version is 1.19.5 or lower, or any version starting with 1.1x
  3. Verify default credentials are still active
    Attempt to log into the device admin interface using the default credential pair (consult device documentation for the default username/password combination, typically admin/admin or admin/password). If login succeeds without password change, default credentials are active.
    Affected if Default username and password still grant administrative access
  4. Check device admin interface network exposure
    Scan your network perimeter or review firewall rules for ports 80, 443, or device-specific admin ports (check device documentation) exposed to untrusted networks. Use nmap: nmap -p 80,443 --open <your-network-range> to identify exposed web interfaces.
    Affected if Device admin web interface is accessible from untrusted networks or the internet

You are affected if you have BLU-IC2 or BLU-IC4 devices running firmware below version 1.20 that still use default credentials and have their admin interface accessible to attackers.

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

Immediately change all default credentials on affected devices to strong, unique passwords following organizational policy, and restrict network access to trusted users only.

Recommended fix Moderate confidence

Blu Ic2 Firmware 1.20 and Blu Ic4 Firmware 1.20

  1. Obtain firmware version 1.20 or later for your specific device (BLU-IC2 or BLU-IC4) from the vendor's official support portal or by contacting the vendor directly
  2. Access the device administration interface via its IP address or hostname
  3. Locate the firmware update or system settings section in the web interface
  4. Upload and apply the firmware version 1.20 or later following the vendor's documented upgrade procedure
  5. After successful firmware upgrade, access the device administration panel and change all default credentials to strong, unique passwords
  6. Verify the firmware version has been updated to 1.20 or later in the system information or about section
Caveat Review vendor release notes for any configuration or feature changes that may require adjustment after upgrading

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12218 — 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-12218 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