dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12478

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-29
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
Non-Compliant TLS Configuration.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

Non-compliant TLS configuration in BLU-IC2 and BLU-IC4 devices (versions through 1.19.5) allowing weak or outdated TLS protocols/ciphers, likely enabling man-in-the-middle attacks or cryptographic compromise.

MitigationHarden TLS configuration to disable weak protocols (SSLv3, TLS 1.0, TLS 1.1) and weak ciphers; enforce TLS 1.2 or 1.3 with strong cipher suites; verify compliance with current security standards.

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. Determine firmware version
    Access the device management interface or use the vendor-provided command/script to query the installed firmware version. Common methods include: logging into the web UI and checking the status/diagnostics page, using SNMP, or consulting the device's system information via CLI.
    Affected if Firmware version is below 1.20 (for either BLU-IC2 or BLU-IC4)
  2. Identify TLS protocol configuration
    Locate the TLS/SSL configuration settings in the device management interface, typically found under Network Settings, Security, or TLS Configuration. Check which protocol versions are enabled or advertised.
    Affected if SSLv3, TLS 1.0, or TLS 1.1 are enabled or permitted
  3. Examine cipher suite settings
    Review the cipher suite configuration in the device settings. Look for the list of allowed or preferred ciphers, often presented as a selectable list or in a configuration file.
    Affected if Weak or deprecated ciphers such as NULL, EXPORT, RC4, DES, 3DES, or MD5-based ciphers are enabled or present in the allowed list
  4. Verify compliance with current TLS standards
    If available, use the device's built-in compliance checker or security audit feature to assess TLS configuration against modern standards. Alternatively, compare the enabled protocols and ciphers against known secure configurations (TLS 1.2/1.3 with AEAD ciphers).
    Affected if The configuration does not enforce TLS 1.2 or higher with strong cipher suites, or fails compliance checks for modern TLS standards

A user is affected if the device runs BLU-IC2 or BLU-IC4 firmware below version 1.20 AND has weak TLS protocols (SSLv3, TLS 1.0, TLS 1.1) or weak ciphers enabled in the configuration.

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

Harden TLS configuration to disable weak protocols (SSLv3, TLS 1.0, TLS 1.1) and weak ciphers; enforce TLS 1.2 or 1.3 with strong cipher suites; verify compliance with current security standards.

Recommended fix High confidence

Blu Ic2 Firmware 1.20 and Blu Ic4 Firmware 1.20

  1. Obtain the Blu Ic2 or Blu Ic4 firmware version 1.20 from the vendor's official distribution channel (azure-access.com or vendor support)
  2. Backup current device configuration before initiating the firmware update
  3. Follow the vendor's documented firmware upgrade procedure for the BLU-IC2 or BLU-IC4 device to apply version 1.20
  4. After upgrade, verify the device is running firmware 1.20 or later
  5. Confirm the TLS configuration is now compliant with current standards
Caveat Review vendor release notes for any configuration or behavioral changes in firmware 1.20 before upgrading

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

Fix this in Blu Ic2 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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