CVE-2025-12552: Azure Access Technology BLU-IC2 · Weak Password Requirements
Affects Azure Access Technology BLU-IC2Source CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.19.6 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- 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.
- Patch
- Available – fixed in 1.19.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Upgrade Azure Access Technology BLU-IC2 to 1.19.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Azure Access Technology BLU-IC2 | Affected
| Fixed in
|
AI-suggested
European organizations should immediately review and strengthen password policies within BLU-IC2 and BLU-IC4 deployments, enforcing complexity requirements such as minimum length, character variety, and prohibition of common passwords. Implementing multi-factor authentication (MFA) is critical to mitigate risks from compromised passwords. Network-level protections, including rate limiting and account lockout mechanisms, should be enabled to prevent brute-force attacks. Monitoring and alerting on suspicious authentication attempts can provide early detection of exploitation attempts. Organizations should maintain close communication with Azure Access Technology for timely patch releases and apply updates promptly once available. Additionally, conducting regular security audits and penetration testing focused on authentication mechanisms will help identify residual weaknesses. Where possible, segmenting access control systems from broader networks can limit potential lateral movement by attackers. Finally, educating users about strong password practices and phishing risks complements technical controls.
Description
Insufficient Password Policy.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.