Cyber Resilience

CVE-2025-12365

Info Disclosure in Azure-Access Blu-Ic2 Firmware ≤ 1.20

Published
27 October 2025
Modified
10 November 2025
Patch / advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/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.0023 14th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2025-12365 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Azure-Access Blu-Ic2 Firmware. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 14th 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 SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Error Messages Wrapped In HTTP Header.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance
Adversaries may gather information about the victim's host software that can be used during targeting.
T1082 System Information Discovery Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
T1595 Active Scanning Reconnaissance
Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-12363Same product: Azure-Access Blu-Ic2
CVE-2025-12221Same product: Azure-Access Blu-Ic2
CVE-2025-12552Same product: Azure-Access Blu-Ic2
CVE-2025-12554Same product: Azure-Access Blu-Ic2
CVE-2025-12600Same product: Azure-Access Blu-Ic2
CVE-2025-12423Same product: Azure-Access Blu-Ic2
CVE-2025-12599Same product: Azure-Access Blu-Ic2
CVE-2025-12478Same product: Azure-Access Blu-Ic2
CVE-2025-12285Same product: Azure-Access Blu-Ic2
CVE-2025-12284Same product: Azure-Access Blu-Ic2

Affected Assets

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

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

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 sanitized error handling to prevent sensitive data disclosure.

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.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.

prevents

Application security requirements can specify safe error messaging.

prevents

Secure architecture principles include proper exception handling.

References