Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12422

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-28

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

NVD · unedited

Vulnerable Upgrade Feature (Arbitrary File Write) may lead to obtaining super user permissions on board.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

Technical summary

dbcve analysis · moderate confidence

Arbitrary file write vulnerability in the upgrade feature of BLU-IC2 and BLU-IC4 devices allows attackers to overwrite system files and obtain super user (root) privileges. The vulnerability exists through version 1.19.5 and is rated critical due to the trivial privilege escalation path.

MitigationUpgrade BLU-IC2 and BLU-IC4 devices to a patched version beyond 1.19.5. If no patched firmware is available, restrict network access to the upgrade feature and monitor for unauthorized access attempts.

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

Affected products & versions

NVD · CPE data

Blu Ic2 FirmwareOperating system

Affected:< 1.20

Blu Ic4 FirmwareOperating system

Affected:< 1.20

CVSS breakdown

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?

dbcve checks

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

Identify device model

Access the device web interface or CLI and locate the device information page to confirm the model is BLU-IC2 or BLU-IC4

Affected if Device is a BLU-IC2 or BLU-IC4 unit
Check firmware version

Navigate to the device status or system information page in the web interface, or run the appropriate CLI command (such as 'show version' or 'system info'), and note the firmware version number

Affected if Firmware version is below 1.20 (for example, 1.19.5 or earlier)
Verify upgrade interface exposure

Check if the upgrade or firmware update interface is accessible from the network. This may be a web endpoint (such as /upgrade or /firmware-update), a dedicated management port, or accessible via protocols used for device management

Affected if The upgrade interface is exposed and reachable on the network
Inspect for unauthorized firmware files

If you have administrative access, review the device's firmware storage area or configuration directory for any unexpected or unauthorized firmware files that differ from the expected installed version

Affected if Unexpected firmware files are present or the installed firmware does not match the expected version

Your device is affected if it is a BLU-IC2 or BLU-IC4 running firmware version 1.19.5 or any version below 1.20, and the upgrade feature is network-accessible.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.20 or later

Fixed in 1.20

Interim mitigation

Upgrade BLU-IC2 and BLU-IC4 devices to a patched version beyond 1.19.5. If no patched firmware is available, restrict network access to the upgrade feature and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Blu Ic2 Firmware >= 1.20 and Blu Ic4 Firmware >= 1.20

Obtain the latest firmware version 1.20 or later from the official Blu device vendor
Download the firmware update package from a verified source
Consult the device documentation for the specific firmware upgrade procedure
Follow the vendor's recommended steps to apply the firmware update to BLU-IC2
Follow the vendor's recommended steps to apply the firmware update to BLU-IC4
Verify the firmware version after upgrade confirms 1.20 or later is installed

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 / QA4.0 h

22.0 hours of engineering $3,860

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

azure-access.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-12422?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 1.20 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Blu Ic2 Firmware

Remediation

A high-priority fix

Fix this in Blu Ic2 Firmware 22 hrs · High

Typical engagement from $3,860

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-12422 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References