rsyslog imuxsock can write past a message buffer on timestamp rewrite
Original title: rsyslog imuxsock system-timestamp out-of-bounds write
A local sender with access to the Unix datagram socket can force the write using an overlong PRI and a short timestamp.
Rainer Gerhards reported that rsyslog's imuxsock special parser can write beyond a received message's raw buffer when it replaces the message timestamp with the system timestamp. A local sender able to write to a directly accessible imuxsock Unix datagram socket can combine an overlong invalid PRI with a short timestamp accepted by the permissive RFC3164 parser. The fixed 16-byte in-place rewrite then has insufficient remaining space. The note credits @karimabisaad; the snippet names no CVE or fixed release.
Unconfirmed: The post is truncated and does not state affected versions, a CVE, or a fix.
- A local process must be able to write to the imuxsock Unix datagram socket.
- The trigger pairs an overlong invalid PRI with a short RFC3164 timestamp.
- The in-place system-timestamp rewrite is a fixed 16-byte operation.
Impact: local out-of-bounds write past the message buffer
| Product | Affected |
|---|---|
| rsyslog | — |
From the original article
Posted by Rainer Gerhards on Nov 17 Credit: Reported by @karimabisaad. rsyslog's imuxsock special parser can write beyond a received message's raw buffer when replacing the message timestamp with the system timestamp. A local sender able to write to a directly accessible imuxsock Unix datagram socket can combine an overlong invalid PRI with a short timestamp accepted by the permissive RFC3164 parser.
seclists.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.