CVE-2025-12477
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 · uneditedServer Version Disclosure.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 confidenceServer version disclosure vulnerability in BLU-IC2 and BLU-IC4 devices up to firmware version 1.19.5. The embedded server exposes version information in responses, allowing attackers to enumerate exact firmware versions and identify known vulnerabilities for exploitation.
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< 1.20< 1.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify BLU-IC2 or BLU-IC4 devices on the networkLocate Azure Access BLU-IC2 or BLU-IC4 industrial control devices by reviewing network inventory, device discovery logs, or scanning for known device fingerprintsAffected if Any BLU-IC2 or BLU-IC4 device is present on the network
-
Determine installed firmware versionAccess the device management interface or use vendor-provided tools to retrieve the current firmware version (commonly found in system status, about, or firmware information pages)Affected if The retrieved firmware version is less than 1.20
-
Test for version disclosure in server responsesSend an HTTP request to the device's web interface (such as a GET request to the root or common endpoints) and inspect all response headers and body content for version strings, server banners, or firmware identifiersAffected if The HTTP response contains explicit version information such as server version, firmware version, or build numbers in headers or HTML
-
Check for version disclosure in error pages or API endpointsSend requests to non-existent pages or API endpoints and examine any error messages, stack traces, or diagnostic outputs that may reveal version detailsAffected if Error responses disclose version numbers or build identifiers
-
Verify network exposure of affected devicesReview firewall rules, access control lists, and network segmentation to determine if the BLU-IC2 or BLU-IC4 devices are accessible from untrusted networks or the internetAffected if The device with firmware < 1.20 is reachable from untrusted networks without adequate filtering
You are affected if you have any BLU-IC2 or BLU-IC4 devices running firmware version less than 1.20 that expose version information in server responses.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.20
Update to patched firmware version when available from vendor; otherwise, implement network segmentation and firewall rules to limit exposure of these industrial control devices to untrusted networks.
Blu Ic2 Firmware >= 1.20 and Blu Ic4 Firmware >= 1.20
- Obtain the Blu Ic2 and Blu Ic4 firmware version 1.20 or later from the device manufacturer or official support渠道
- Backup current device configuration before proceeding with firmware update
- Follow the manufacturer's standard firmware upgrade procedure for Blu Ic2/Ic4 devices
- Verify that the firmware has been successfully updated to version 1.20 or later
- Confirm the authentication vulnerability is resolved by testing access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12477 in production — separate from our analysis above.
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.
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.
- 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