rsyslog imuxsock TAG parser has local out-of-bounds read
Original title: rsyslog imuxsock TAG parser out-of-bounds read
A local sender that can write the imuxsock Unix datagram socket can trigger the read with a crafted TAG.
Rainer Gerhards reported an out-of-bounds read in rsyslog’s imuxsock TAG parser, found during an internal security review. When the special parser uses the system timestamp, an accepted short timestamp can leave the TAG cursor and remaining length referring to different positions. A local sender with a valid PRI and a long nonspace TAG suffix can reach the bug. The post names no CVE or fixed version.
Unconfirmed: Affected releases and whether a fix is available are not stated in the post.
- The bug requires write access to a directly accessible imuxsock socket.
- Credit is rsyslog’s internal security review, not an external report.
Impact: local out-of-bounds read of message data
| Product | Affected |
|---|---|
| rsyslog imuxsock | — |
From the original article
Posted by Rainer Gerhards on Nov 17 Credit: Discovered during rsyslog's internal security review. rsyslog's imuxsock input has an out-of-bounds read in TAG parsing when the special parser uses the system timestamp. An accepted short timestamp can leave the TAG cursor and remaining length referring to different positions in the raw message.
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.