CVE-2025-12517
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 · uneditedCredits Page not Matching Versions in Use in the FirmwareThis 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 confidenceThe firmware's credits page displays incorrect version information that does not match the actual versions in use. This creates an information integrity issue where administrators cannot reliably identify the firmware version running on BLU-IC2 or BLU-IC4 devices, potentially obscuring vulnerable versions and complicating vulnerability management and incident response.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the actual firmware versionAccess the device administrative interface or use the device's version checking command/API to retrieve the true firmware version currently running on the BLU-IC2 or BLU-IC4 deviceAffected if The actual running firmware version is below 1.20
-
Access the credits pageNavigate to the firmware credits page on the device (typically found in the device settings or about section of the web interface)Affected if The credits page is accessible and displays version information
-
Compare displayed vs actual versionNote the version number shown on the credits page and compare it to the actual firmware version determined in step 1Affected if The version displayed on the credits page does not match the actual firmware version in use - this indicates the information integrity flaw is present
-
Identify product typeConfirm whether the device is a BLU-IC2 or BLU-IC4 model running Azure Access firmwareAffected if The device is an Azure Access BLU-IC2 or BLU-IC4 with firmware version below 1.20
A device is affected if it is a BLU-IC2 or BLU-IC4 running Azure Access firmware below version 1.20 AND the version shown on the credits page differs from the actual firmware version in use.
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 the credits page in the firmware to accurately reflect the current versions in use. Verify version consistency across all documentation and build artifacts.
Blu Ic2 Firmware 1.20 and Blu Ic4 Firmware 1.20
- Identify the exact model of Blu device (IC2 or IC4) requiring remediation
- Locate the firmware update mechanism for the specific device (typically via vendor's management interface or update tool)
- Download firmware version 1.20 or later from the vendor (azure-access.com)
- Apply the firmware update following the vendor's documented upgrade procedure
- Verify the firmware version has been successfully applied by checking the device credits/about page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12517 — 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-12517 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