Coraza: Native audit-log format allows CRLF injection and log forgery via request body and header fields

Why it is Yellow

• CVSS 5.8 medium
• Public exploit or proof of concept referenced
• On your watchlist: Go

Affected packages

References

• https://github.com/advisories/GHSA-prpw-wwv7-xjjr
• https://github.com/corazawaf/coraza/security/advisories/GHSA-prpw-wwv7-xjjr
• https://github.com/corazawaf/coraza/commit/a3079325547c7c1e08522aed4d6468f25d080e25
• https://github.com/corazawaf/coraza/releases/tag/v3.8.0
• https://github.com/advisories/GHSA-prpw-wwv7-xjjr

Original description

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.0.0 until 3.8.0, the Native audit-log formatter in internal/auditlog/formats.go writes attacker-influenced request and response fields without neutralizing carriage returns or line feeds. When SecAuditLogFormat Native is enabled, injected line breaks can create forged lines inside a transaction record. An attacker who controls request or response body, header, error-message, or matched-rule data can inject carriage returns and line feeds that appear as forged audit lines within a transaction record. The forged content can mislead operators and line-oriented SIEM processing, although the unpredictable transaction boundary prevents straightforward impersonation of a separate complete session. This issue is fixed in version 3.8.0.