dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12599

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
Multiple Devices are Sharing the Same Secrets for SDKSocket (TCP/5000).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

Multiple BLU-IC2 and BLU-IC4 devices are shipped with identical cryptographic secrets (keys, passwords, or certificates) hardcoded or pre-provisioned in firmware for the SDKSocket service on TCP port 5000. An attacker who obtains the shared secret from any single device can authenticate to all other vulnerable devices, enabling mass compromise.

MitigationReplace hardcoded/shared secrets with unique, device-specific credentials per device; implement proper secret generation, storage, and rotation mechanisms; update firmware to version 1.19.6 or later if available.

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
    Determine if the device is an Azure Access BLU-IC2 or BLU-IC4 by checking the device label, management interface, or system information
    Affected if Device is a BLU-IC2 or BLU-IC4 model
  2. Check firmware version
    Access the device management interface or use firmware version checking command/tools provided by the vendor to retrieve the current installed firmware version
    Affected if Firmware version is below 1.20 (any version 1.19.x or earlier)
  3. Verify SDKSocket service exposure
    Scan TCP port 5000 on the device to determine if the SDKSocket service is listening and network-accessible
    Affected if Port 5000 is open and accessible from any network segment that includes untrusted users
  4. Test for default hardcoded credentials
    Attempt to authenticate to the SDKSocket service on port 5000 using the documented hardcoded secrets (if known) or by consulting the vulnerability disclosure for the specific default credentials
    Affected if Authentication succeeds with the factory default hardcoded secrets, indicating the device is vulnerable

A device is affected if it is a BLU-IC2 or BLU-IC4 running firmware version below 1.20 with the SDKSocket service on port 5000 accessible and authenticating using the hardcoded default secrets.

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

Replace hardcoded/shared secrets with unique, device-specific credentials per device; implement proper secret generation, storage, and rotation mechanisms; update firmware to version 1.19.6 or later if available.

Recommended fix Moderate confidence

Blu Ic2 Firmware 1.20 and Blu Ic4 Firmware 1.20 (or later stable release)

  1. 1. Identify all BLU-IC2 and BLU-IC4 devices in your environment currently running firmware versions prior to 1.20
  2. 2. Review the device firmware upgrade documentation from the vendor (azure-access.com or relevant manufacturer)
  3. 3. Download the official firmware version 1.20 or later for your specific device model (BLU-IC2 or BLU-IC4)
  4. 4. Schedule a maintenance window to minimize operational impact
  5. 5. Backup current device configuration before initiating the firmware upgrade
  6. 6. Apply firmware version 1.20 to each affected device via the manufacturer's recommended upgrade procedure
  7. 7. Verify the upgrade was successful by checking the firmware version on each device
  8. 8. Confirm that SDKSocket (TCP/5000) is now using device-unique secrets rather than shared secrets
Caveat Review release notes for any configuration or compatibility 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
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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