Authentication bypass via all-interface API binding
Published Aug 20, 2025 · Updated Dec 23, 2025
Authentication bypass in Cryostat before 4.0.2 allows remote attackers within the cluster to access its HTTP API directly. A Dockerfile system property binds Quarkus to 0.0.0.0 and takes precedence over the deployment's host environment setting. When NetworkPolicy enforcement is unsupported or disabled, direct requests to port 8181 bypass the OAuth proxy and expose API-authorized data and actions without authentication.
Summary
What happened
Authentication bypass in Cryostat before 4.0.2 allows remote attackers within the cluster to access its HTTP API directly. A Dockerfile system property binds Quarkus to 0.0.0.0 and takes precedence over the deployment's host environment setting. When NetworkPolicy enforcement is unsupported or disabled, direct requests to port 8181 bypass the OAuth proxy and expose API-authorized data and actions without authentication.
The record
- CVE
- CVE-2025-8415
- Published
- Aug 20, 2025
- Updated
- Dec 23, 2025
- Vendor
- 389 Directory Server
- Product
- Cryostat
- Classifications
- CWE-289, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2025CVE publishedPublication date reported by the CVE source.
- Dec 23, 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 <4.0.2
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