dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12603

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-01
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
/etc/timezone can be Arbitrarily Written.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 vulnerability allows an unauthenticated attacker to write arbitrary content to /etc/timezone on affected BLU-IC2 and BLU-IC4 devices running firmware through version 1.19.5. This arbitrary file write could enable privilege escalation, denial of service, or further system compromise depending on the system's configuration and the attacker's payload.

MitigationApply the vendor-supplied patch (version 1.19.6 or later) when available. If immediate patching is not possible, restrict network access to the device and monitor /etc/timezone for unauthorized modifications.

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 the device model
    Locate the device label or check the device information page via the web management interface or CLI. Confirm it is either BLU-IC2 or BLU-IC4.
    Affected if The device is a BLU-IC2 or BLU-IC4 unit.
  2. Check firmware version
    Access the device web interface or CLI and navigate to the firmware or system information section. Compare the installed version number against the affected range (anything below version 1.20).
    Affected if Firmware version is below 1.20.
  3. Verify management interface accessibility
    Determine if the device web management interface is reachable from the network. Check network ACLs or firewall rules protecting the device management ports.
    Affected if The management interface is exposed to untrusted networks.
  4. Inspect /etc/timezone for tampering
    If you have CLI or SSH access to the device, examine the /etc/timezone file. Compare its contents to the expected timezone for your deployment or check file metadata for recent modification timestamps.
    Affected if The /etc/timezone file contains an unexpected value or shows recent unauthorized changes.

You are affected if you have a BLU-IC2 or BLU-IC4 device running firmware version below 1.20 with an accessible management interface.

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

Apply the vendor-supplied patch (version 1.19.6 or later) when available. If immediate patching is not possible, restrict network access to the device and monitor /etc/timezone for unauthorized modifications.

Recommended fix High confidence

Firmware version 1.20 or later

  1. 1. Backup the current firmware configuration and any critical data on the BLU-IC2 or BLU-IC4 device.
  2. 2. Obtain the firmware version 1.20 or later from the vendor's official distribution channel (azure-access.com or official vendor support).
  3. 3. Access the device management interface via the administrative console or CLI.
  4. 4. Navigate to the firmware update section of the device management interface.
  5. 5. Upload the firmware version 1.20 image file for your specific device model (BLU-IC2 or BLU-IC4).
  6. 6. Initiate the firmware upgrade process and confirm the operation.
  7. 7. Allow the device to complete the upgrade process without interruption.
  8. 8. After reboot, verify the firmware version has been updated to 1.20 or later.

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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