Credential disclosure via failed API request logging
Published Mar 6, 2023 · Updated Feb 25, 2025
Sensitive data exposure in FreshRSS 1.9.0 through 1.20.2 allows local users with log access to read API passwords and keys. In greader.php, authorizationToUser() routes failed requests to unauthorized() or badRequest(), which logs debugInfo() output containing the unredacted request body. API access must be enabled, a user must submit incorrect credentials, and log access then exposes the submitted secret without permitting data modification.
Summary
What happened
Sensitive data exposure in FreshRSS 1.9.0 through 1.20.2 allows local users with log access to read API passwords and keys. In greader.php, authorizationToUser() routes failed requests to unauthorized() or badRequest(), which logs debugInfo() output containing the unredacted request body. API access must be enabled, a user must submit incorrect credentials, and log access then exposes the submitted secret without permitting data modification.
The record
- CVE
- CVE-2023-22481
- Published
- Mar 6, 2023
- Updated
- Feb 25, 2025
- Vendor
- FreshRSS
- Product
- FreshRSS
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 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.9.0, < 1.21.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.
Weakness, pattern, technique
Public exploit references
- Failed GReader login reproduction stepsproof of concept · demonstrated
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