dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12217

CRITICAL · 9.1 CVSS v3.1 Published 2025-10-25
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
SNMP Default Community String (public).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 · high confidence

The BLU-IC2 and BLU-IC4 devices running SNMP service through version 1.19.5 are configured with the default community string 'public', allowing unauthenticated remote attackers to retrieve sensitive system information, network topology, and device configurations via simple SNMP GET requests.

MitigationChange the default SNMP community string from 'public' to a strong, unique value on all affected devices, or disable SNMP if not required. If SNMP is necessary, consider migrating to SNMPv3 with authentication and encryption.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
    Check the device label, web interface, or SNMP sysDescr OID (.1.3.6.1.2.1.1.1.0) to confirm the device is a BLU-IC2 or BLU-IC4
    Affected if Device is not a BLU-IC2 or BLU-IC4 - not affected by this CVE
  2. Check firmware version
    Inspect the firmware version via the device web interface, SNMP sysUpTime (.1.3.6.1.2.1.1.3), or check the device info page. Compare against the affected range: < 1.20
    Affected if Firmware version is 1.20 or higher - not affected by this CVE
  3. Verify SNMP service is enabled
    Attempt an SNMP query to the device (snmpwalk -v2c -c public <device_ip> system) or check the device SNMP configuration page for enabled status
    Affected if SNMP is disabled - not affected by this vulnerability
  4. Inspect SNMP community string
    Review the SNMP community string configuration in the device web interface under SNMP settings, or query snmpCommunityName OID (.1.3.6.1.6.3.18.1.1.1) if SNMP is accessible
    Affected if The community string is set to 'public' - device is vulnerable

A user is affected if they own a BLU-IC2 or BLU-IC4 device running firmware below version 1.20 with SNMP enabled and configured with the default 'public' community string.

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

Change the default SNMP community string from 'public' to a strong, unique value on all affected devices, or disable SNMP if not required. If SNMP is necessary, consider migrating to SNMPv3 with authentication and encryption.

Recommended fix Moderate confidence

Firmware 1.20

  1. Identify the current firmware version of BLU-IC2 and BLU-IC4 devices
  2. Obtain firmware version 1.20 or later from the vendor (Blu or azure-access.com)
  3. Follow the vendor's official firmware upgrade procedure to update BLU-IC2 from any version < 1.20 to 1.20 or later
  4. Follow the vendor's official firmware upgrade procedure to update BLU-IC4 from any version < 1.20 to 1.20 or later
  5. After upgrading, change the default SNMP community string from 'public' to a strong, unique community string
  6. Verify the firmware version has been successfully updated on both devices
  7. Verify that SNMP access now requires the new community string
Caveat Review vendor release notes for any changes in functionality or configuration requirements in firmware 1.20

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-12217 — 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-12217 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