cve/2023/CVE-2023-22481.md

### [CVE-2023-22481](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22481)
![](https://img.shields.io/static/v1?label=Product&message=FreshRSS&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3D%20%3E%3D%201.9.0%2C%20%3C%201.21.0%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-532%3A%20Insertion%20of%20Sensitive%20Information%20into%20Log%20File&color=brighgreen)

### Description

FreshRSS is a self-hosted RSS feed aggregator. When using the greader API, the provided password is logged in clear in `users/_/log_api.txt` in the case where the authentication fails. The issues occurs in `authorizationToUser()` in `greader.php`. If there is an issue with the request or the credentials, `unauthorized()` or `badRequest()` is called. Both these functions are printing the return of `debugInfo()` in the logs. `debugInfo()` will return the content of the request. By default, this will be saved in `users/_/log_api.txt` and if the const `COPY_LOG_TO_SYSLOG` is true, in syslogs as well. Exploiting this issue requires having access to logs produced by FreshRSS. Using the information from the logs, a malicious individual could get users' API keys (would be displayed if the users fills in a bad username) or passwords.

### POC

#### Reference
- https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-8vvv-jxg6-8578

#### Github
No PoCs found on GitHub currently.