ACL bypass via ignored PROXY client address
Published Jun 19, 2025 · Updated Jun 20, 2025
Improper access control in Apache Traffic Server 9.0.0 through 9.2.10 and 10.0.0 through 10.0.6 allows remote attackers to bypass IP ACLs. The ip_allow.config and remap.config ACL paths evaluate the TCP peer address instead of the originating address supplied by PROXY protocol. Exposure requires PROXY protocol on the listening port and an IP-based ACL, allowing unauthorized access to resources restricted by client address.
Summary
What happened
Improper access control in Apache Traffic Server 9.0.0 through 9.2.10 and 10.0.0 through 10.0.6 allows remote attackers to bypass IP ACLs. The ip_allow.config and remap.config ACL paths evaluate the TCP peer address instead of the originating address supplied by PROXY protocol. Exposure requires PROXY protocol on the listening port and an IP-based ACL, allowing unauthorized access to resources restricted by client address.
The record
- CVE
- CVE-2025-31698
- Published
- Jun 19, 2025
- Updated
- Jun 20, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2025CVE publishedPublication date reported by the CVE source.
- Jun 20, 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=10.0.0 <=10.0.6
- Affected versionversion=9.0.0 <=9.2.10
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