Skip to main content
VulnerabilityPublished

CVE-2025-12423: Azure Access Technology BLU-IC2 · Uncaught Exception

Affects Azure Access Technology BLU-IC2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Azure Access Technology BLU-IC2Affected
  • =0
  • <=1.19.5
Fixed in–

AI-suggested

  1. Immediate network-level filtering: Implement strict ingress and egress filtering to detect and block anomalous or malformed protocol messages targeting BLU-IC2 and BLU-IC4 components.
  2. Deploy intrusion detection/prevention systems (IDS/IPS) with updated signatures or heuristics to identify exploitation attempts related to protocol manipulation.
  3. Isolate affected systems within segmented network zones to limit potential impact and lateral movement in case of exploitation.
  4. Monitor system logs and network traffic for signs of crashes, exceptions, or unusual protocol activity indicative of exploitation attempts.
  5. Engage with Azure Access Technology support channels to obtain early access to patches or workarounds as they become available.
  6. Conduct thorough risk assessments to identify all instances of BLU-IC2 and BLU-IC4 deployments across the organization and third-party partners.
  7. Develop and test incident response plans specifically addressing denial of service scenarios caused by this vulnerability.
  8. Consider temporary disabling or restricting access to vulnerable components if feasible until patches are applied.
  9. Educate security teams about the nature of CWE-248 vulnerabilities and the importance of robust exception handling in protocol implementations.
  10. Maintain updated asset inventories and vulnerability management processes to ensure rapid identification and remediation of affected systems.

Description

Protocol manipulation might lead to denial of service.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .

References

Community reviews

Loading reviews…