Account compromise via insufficient password strength enforcement
Published Oct 27, 2025 · Updated Oct 27, 2025
Weak password requirements in Azure Access Technology BLU-IC2 and BLU-IC4 through 1.19.5 allow remote attackers to compromise accounts. The firmware authentication policy accepts passwords that do not meet adequate strength requirements, reducing the search space for guessing. Network access to a controller login and a known username are required; the vendor has not published the exact missing rules or affected account classes.
Summary
What happened
Weak password requirements in Azure Access Technology BLU-IC2 and BLU-IC4 through 1.19.5 allow remote attackers to compromise accounts. The firmware authentication policy accepts passwords that do not meet adequate strength requirements, reducing the search space for guessing. Network access to a controller login and a known username are required; the vendor has not published the exact missing rules or affected account classes.
The record
- CVE
- CVE-2025-12364
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- Azure Access Technology
- Product
- BLU-IC4
- Classifications
- CWE-521, CAPEC-49, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.19.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo