Unauthenticated log injection via the CSP violation report endpoint
Résumé
Impact
The currently unused /report/csp_violations endpoint, allowed writing of attacker-controlled content into the server logs without neutralizing control characters. The endpoint is unauthenticated and present on every deployment, so any unauthenticated user could POST a crafted report...
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| Zulip server |
<= 12.2 |
12.3 |
Description d'origine La description telle que publiée par la source (souvent en anglais).
Impact
The currently unused /report/csp_violations endpoint, allowed writing of attacker-controlled content into the server logs without neutralizing control characters. The endpoint is unauthenticated and present on every deployment, so any unauthenticated user could POST a crafted report to inject arbitrary content - including newlines - into /var/log/zulip/server.log and /var/log/zulip/errors.log. This could be used to forge or obscure log entries, undermining the reliability of logs used for monitoring and incident response.
Patches
Fixed in Zulip server 12.3.
Source: GitHub Repository Security Advisories (Game のスタック) GitHub Advisory OSV
Références
- GITHUB_REPO_ADVISORY zulip/zulip