Authenticated component-version misrepresentation via credits page
Published Oct 30, 2025 · Updated Oct 30, 2025
Incorrect UI output in Azure Access Technology BLU-IC2 and BLU-IC4 1.19.5 and earlier allows remote authenticated users to see false version data. The firmware credits page reports component versions that do not match those actually in use; no deeper rendering or data-selection locus is disclosed. Access requires low privileges and passive user interaction, and the reported consequence is misleading version information, not code execution or service interruption.
Summary
What happened
Incorrect UI output in Azure Access Technology BLU-IC2 and BLU-IC4 1.19.5 and earlier allows remote authenticated users to see false version data. The firmware credits page reports component versions that do not match those actually in use; no deeper rendering or data-selection locus is disclosed. Access requires low privileges and passive user interaction, and the reported consequence is misleading version information, not code execution or service interruption.
The record
- CVE
- CVE-2025-12517
- Published
- Oct 30, 2025
- Updated
- Oct 30, 2025
- Vendor
- Azure Access Technology
- Product
- BLU-IC4
- Classifications
- CWE-448, CAPEC-36
- Attack vector
- network
- Privileges
- authenticated
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.
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