rsyslog imuxsock can spoof trusted-property sender identity
Original title: rsyslog imuxsock trusted-property attribution spoofing (GHSA-w259-2hhm-9vr7)
A local process can inject delimiter characters so consumers misread unescaped annotation fields as kernel identity.
rsyslog fixed a local integrity issue in imuxsock plain trusted-property annotation, tracked as GHSA-w259-2hhm-9vr7. With annotation enabled in plain mode, a local process can put field delimiters in its process name or executable path, producing duplicate-looking identity fields. A downstream consumer that treats those unescaped fields as kernel-derived identity may misattribute the sender. The issue requires Linux and a writable affected path; the post is cut off before the full conditions.
Unconfirmed: The post is truncated and does not name a fixed version or confirm exploitation.
- The issue is GHSA-w259-2hhm-9vr7 in imuxsock plain mode.
- Delimiters in the process name or executable path alter the annotation.
- Misattribution depends on a consumer trusting the unescaped fields.
- The reported conditions include Linux and a writable affected resource.
Impact: local spoofing of trusted sender identity fields
| Product | Affected |
|---|---|
| rsyslog | — |
From the original article
Posted by Rainer Gerhards on Nov 17 rsyslog has fixed a local integrity issue in imuxsock plain trusted-property annotation. When annotation is enabled in plain mode, a local process can include field delimiters in its process name or executable path. The resulting annotation can contain duplicate-looking identity fields.
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.