API secret disclosure via result logging
Published Apr 21, 2022 · Updated Apr 23, 2025
Sensitive-data exposure in CVE Services 1.1.1 and earlier allows attackers with log access to read user API secrets from application logs. The createUser path assigns a generated API key to result.secret before serializing and writing the result object through logger.info. Exploitation requires read access to application log files, and the exposed secret belongs to the newly created user represented in that logged result.
Summary
What happened
Sensitive-data exposure in CVE Services 1.1.1 and earlier allows attackers with log access to read user API secrets from application logs. The createUser path assigns a generated API key to result.secret before serializing and writing the result object through logger.info. Exploitation requires read access to application log files, and the exposed secret belongs to the newly created user represented in that logged result.
The record
- CVE
- CVE-2022-24875
- Published
- Apr 21, 2022
- Updated
- Apr 23, 2025
- Vendor
- CVE Program
- Product
- CVE Services
- Classifications
- CWE-532, CWE-779, T1552.001
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=<= 1.1.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