dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12031

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to 1.20 or later.
See remediation →
62/100
Remediation priority · Elevated
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
HTTP Security Misconfiguration - Lacking Secure and HTTPOnly Attribute may allow reading the sensitive cookies from the javascript contextThis 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

This is a cookie security misconfiguration in BLU-IC2 and BLU-IC4 devices where sensitive cookies are not set with the Secure and HTTPOnly flags. Without these attributes, cookies can potentially be accessed via JavaScript (enabling XSS cookie theft) or transmitted over insecure HTTP connections.

MitigationConfigure cookies to include both the Secure flag (restrict to HTTPS only) and HTTPOnly flag (prevent JavaScript access) to protect sensitive session data.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 device model and firmware version
    Log into the Azure Access BLU-IC2 or BLU-IC4 web interface and navigate to the System Information or About page to find the firmware version number. Alternatively, check the device's administration dashboard or firmware update page.
    Affected if The device is a BLU-IC2 or BLU-IC4 and the firmware version is below 1.20
  2. Capture HTTP response headers from login or session initialization
    Use a browser's developer tools (Network tab) or a tool like curl to capture the HTTP response headers when authenticating to the device web interface. Look for Set-Cookie headers in the response.
    Affected if Set-Cookie headers are present and do not include the Secure and HttpOnly attributes for session cookies
  3. Inspect cookie attributes via browser developer tools
    In the browser's developer console, navigate to the Application or Storage tab and examine the cookies set by the device. Check each cookie's attributes column for Secure and HttpOnly flags.
    Affected if Any sensitive session cookies (such as session IDs, authentication tokens) are missing the Secure flag, the HttpOnly flag, or both

You are affected if you have a BLU-IC2 or BLU-IC4 device running firmware version below 1.20, and the web interface sets cookies without both the Secure and HttpOnly attributes.

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

Configure cookies to include both the Secure flag (restrict to HTTPS only) and HTTPOnly flag (prevent JavaScript access) to protect sensitive session data.

Recommended fix Moderate confidence

BLU-IC2 and BLU-IC4 Firmware version 1.20

  1. Identify the BLU-IC2 or BLU-IC4 device model and current firmware version via the device management interface
  2. Download the official firmware version 1.20 or later from the vendor's support portal (azure-access.com or official BLU support channels)
  3. Review the firmware upgrade instructions provided by the vendor
  4. Connect to the device via the recommended administrative interface (web UI, console, or management tool)
  5. Upload the firmware 1.20 binary to the device
  6. Initiate the firmware upgrade process and wait for completion
  7. Verify the upgrade was successful by checking the new firmware version
  8. Confirm that the HttpOnly and Secure attributes are now set on sensitive cookies by inspecting HTTP responses in browser developer tools or using a web vulnerability scanner
Caveat Review vendor release notes for any configuration or behavioral changes between 1.19.x and 1.20 that may affect existing integrations

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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