Access-control bypass via noncanonical URL paths
Published Nov 11, 2024 · Updated Nov 12, 2024
Improper URL handling in the PingAccess rules engine allows remote attackers to bypass request access rules with encoded paths. The engine evaluates rules without first canonicalizing empty or dot path segments containing encoded slashes or periods, so alternate encodings evade the intended match. Exploitation requires a crafted request to a protected route and passive user interaction; the bounded result is unauthorized functionality and downstream integrity impact.
Summary
What happened
Improper URL handling in the PingAccess rules engine allows remote attackers to bypass request access rules with encoded paths. The engine evaluates rules without first canonicalizing empty or dot path segments containing encoded slashes or periods, so alternate encodings evade the intended match. Exploitation requires a crafted request to a protected route and passive user interaction; the bounded result is unauthorized functionality and downstream integrity impact.
The record
- CVE
- CVE-2024-23983
- Published
- Nov 11, 2024
- Updated
- Nov 12, 2024
- Vendor
- Ping Identity
- Product
- PingAccess
- Classifications
- CWE-177, CWE-20, CAPEC-1, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 11, 2024CVE publishedPublication date reported by the CVE source.
- Nov 12, 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=6.0.0 <6.3.9
- Affected versionversion=7.0.0 <7.0.8
- Affected versionversion=7.1.0 <7.1.5
- Affected versionversion=7.2.0 <7.2.4
- Affected versionversion=7.3.0 <7.3.5
- Affected versionversion=8.0.0 <8.0.4
- Affected versionversion=8.1.0 <8.1.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