Cyber Resilience

CVE-2025-12515

Azure-Access Blu-Ic2 Firmware ≤ 1.20

Published
30 October 2025
Modified
10 November 2025
Patch / advisory
View advisory
CVSS Score v4 10.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0034 27th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2025-12515 is a critical-severity Unexpected Status Code or Return Value (CWE-394) vulnerability in Azure-Access Blu-Ic2 Firmware. Its CVSS base score is 10.0 (Critical).

Operationally, ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

Systemic Internal Server Errors - HTTP 500 ResponseThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .

CWE(s)
CWE-394

Related Threats

CVEs Like This One

CVE-2025-12516Same product: Azure-Access Blu-Ic2
CVE-2025-11925Same product: Azure-Access Blu-Ic2
CVE-2025-12001Same product: Azure-Access Blu-Ic2
CVE-2025-12285Same product: Azure-Access Blu-Ic2
CVE-2025-12423Same product: Azure-Access Blu-Ic2
CVE-2025-12602Same product: Azure-Access Blu-Ic2
CVE-2025-12284Same product: Azure-Access Blu-Ic2
CVE-2025-12218Same product: Azure-Access Blu-Ic2
CVE-2025-12517Same product: Azure-Access Blu-Ic2
CVE-2025-12479Same product: Azure-Access Blu-Ic2

Affected Assets

azure-access
blu-ic2 firmware
≤ 1.20
azure-access
blu-ic4 firmware
≤ 1.20

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation at post-design stages will find missing or incorrect checks for unexpected but valid return values.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can mandate exhaustive checking of all function return values.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles such as defensive programming and complete return-value checking stop the weakness from being introduced in code.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper validation of all function return values and status codes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing checks for unexpected but valid return values.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires handling of all return values and status codes.

A.8.26 Application security requirements partial match
prevents

Application security requirements include proper validation of function results and error conditions.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly mandate checking all legitimate return values and status codes.

References