Private-key disclosure via exception message
Published Jul 6, 2023 · Updated Nov 6, 2024
Sensitive-data exposure in OAuth2 Server 8.3.2 through 8.4.1 and 8.5.0 through 8.5.2 allows attackers to read a private key in an exception. CryptKey treats a string-supplied key as a file path when key loading fails and appends that value to a LogicException message. Exposure requires an application to pass key contents as a string, supply an invalid required passphrase, and reveal the resulting exception.
Summary
What happened
Sensitive-data exposure in OAuth2 Server 8.3.2 through 8.4.1 and 8.5.0 through 8.5.2 allows attackers to read a private key in an exception. CryptKey treats a string-supplied key as a file path when key loading fails and appends that value to a LogicException message. Exposure requires an application to pass key contents as a string, supply an invalid required passphrase, and reveal the resulting exception.
The record
- CVE
- CVE-2023-37260
- Published
- Jul 6, 2023
- Updated
- Nov 6, 2024
- Vendor
- OAuth.js
- Product
- OAuth2 Server
- Classifications
- CWE-209, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 6, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 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=8.3.2 <8.5.3
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