Authentication bypass via parent-route provider misassociation
Published Aug 12, 2022 · Updated Aug 3, 2024
Improper authentication in JetBrains Ktor before 2.1.0 allows remote attackers to access protected routes through the wrong provider. Route.authenticate() stored each provider-name list on the parent route, so nested route traversal could collect a sibling provider instead of the authenticated child route's provider. Exploitation requires multiple named providers on nested routes and user interaction; the published impact is unauthorized disclosure of protected data.
Summary
What happened
Improper authentication in JetBrains Ktor before 2.1.0 allows remote attackers to access protected routes through the wrong provider. Route.authenticate() stored each provider-name list on the parent route, so nested route traversal could collect a sibling provider instead of the authenticated child route's provider. Exploitation requires multiple named providers on nested routes and user interaction; the published impact is unauthorized disclosure of protected data.
The record
- CVE
- CVE-2022-38180
- Published
- Aug 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- JetBrains
- Product
- Ktor
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=2.1.0 <2.1.0
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