Downstream data access and modification via request smuggling
Published May 31, 2024 · Updated Aug 1, 2024
HTTP request desynchronization in Ping Identity PingAccess before 8.0.1 allows remote attackers to smuggle requests through its proxy. The connection-request-header handler interprets specially crafted HTTP headers inconsistently with a downstream server, shifting request boundaries. This requires a proxied HTTP/1.1 path with differing parsers and permits unauthorized access to or modification of downstream application data.
Summary
What happened
HTTP request desynchronization in Ping Identity PingAccess before 8.0.1 allows remote attackers to smuggle requests through its proxy. The connection-request-header handler interprets specially crafted HTTP headers inconsistently with a downstream server, shifting request boundaries. This requires a proxied HTTP/1.1 path with differing parsers and permits unauthorized access to or modification of downstream application data.
The record
- CVE
- CVE-2024-23316
- Published
- May 31, 2024
- Updated
- Aug 1, 2024
- Vendor
- Ping Identity
- Product
- PingAccess
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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 <8.0.1
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