Authentication-header disclosure through exception messages
Published Jun 1, 2023 · Updated Jan 8, 2025
Information exposure in JetBrains Ktor before 2.3.1 allows local users to read authentication headers from exception messages. An undisclosed exception-construction path included authentication-bearing request headers in exception text instead of excluding sensitive header values. Access to an affected application's exception output is required, and the reported impact is limited to disclosure of header-contained credentials.
Summary
What happened
Information exposure in JetBrains Ktor before 2.3.1 allows local users to read authentication headers from exception messages. An undisclosed exception-construction path included authentication-bearing request headers in exception text instead of excluding sensitive header values. Access to an affected application's exception output is required, and the reported impact is limited to disclosure of header-contained credentials.
The record
- CVE
- CVE-2023-34339
- Published
- Jun 1, 2023
- Updated
- Jan 8, 2025
- Vendor
- JetBrains
- Product
- Ktor
- Classifications
- CWE-209
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Jan 8, 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 <2.3.1
What conditions does exploitation require?
What is affected?
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