Affected versions
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
Rsyslog is a rocket-fast system for log processing. From versions 1.15.0 to 8.2610.0, rsyslog's omfile dynaFile facility intentionally allows templates to generate flexible output paths. This supports valid deployments that route logs into different directories or use dynamically generated file names. A deployment becomes unsafe when a dynaFile template uses a value influenced by untrusted input as a path component without explicit secure-path handling. In that configuration, the rendered path can escape the operator's intended log directory. This is not limited to the RFC5424 HOSTNAME field. Any untrusted value that reaches a dynaFile path component can create the condition. At time of publication, there are no publicly available patches.
A flaw was found in rsyslog. This path traversal vulnerability allows a remote attacker to write log files outside the intended logging directory. When dynamic file generation (dynaFile) templates incorporate untrusted input without proper path validation, crafted log messages can escape the designated path. An attacker can exploit this condition to create or overwrite files in arbitrary locations on the host system.

