Unauthenticated impact via unexpected HTTP status handling
Published Oct 30, 2025 · Updated Oct 30, 2025
Unexpected status-code handling in Azure Access Technology BLU-IC2 and BLU-IC4 through 1.19.5 allows remote attackers unspecified impact. The vendor identifies only HTTP 5xx error handling and has not published the affected endpoint, triggering input, unexpected return path, or resulting operation. No authentication or user interaction is required, but the public disclosure does not establish whether exploitation discloses data, changes state, or interrupts service.
Summary
What happened
Unexpected status-code handling in Azure Access Technology BLU-IC2 and BLU-IC4 through 1.19.5 allows remote attackers unspecified impact. The vendor identifies only HTTP 5xx error handling and has not published the affected endpoint, triggering input, unexpected return path, or resulting operation. No authentication or user interaction is required, but the public disclosure does not establish whether exploitation discloses data, changes state, or interrupts service.
The record
- CVE
- CVE-2025-12516
- Published
- Oct 30, 2025
- Updated
- Oct 30, 2025
- Vendor
- Azure Access Technology
- Product
- BLU-IC4
- Classifications
- CWE-394, CAPEC-116
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 30, 2025CVE publishedPublication date reported by the CVE source.
- Oct 30, 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.
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