Skip to content
NewA calmer, faster ZeroHour

rsyslog 5.7.1 and later imuxsock PID bug causes local DoS

Original title: rsyslog >= 5.7.1 imuxsock empty-TAG PID underwrite

oss-security ()
Part of a story covered by 4 sourcesoss-security posts four local rsyslog imuxsock flawsMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

An empty TAG makes fixPID() write before the buffer when system PID rewriting is enabled.

Rainer Gerhards reported a local denial-of-service flaw in rsyslog imuxsock's PID rewriting path, affecting rsyslog 5.7.1 and later. When UsePIDFromSystem or SysSock.UsePIDFromSystem is enabled, a local sender that can write to the affected Unix datagram socket can submit a message with an empty TAG. The fixPID() code searches from an invalid offset and writes before the TAG buffer. The post is cut off before describing the full crash behavior or a fix.

Unconfirmed: The truncated post does not state a fixed version or confirm crashes in the wild.

Key facts
  • Affected releases are rsyslog 5.7.1 and later.
  • UsePIDFromSystem or SysSock.UsePIDFromSystem must be enabled.
  • The sender needs write access to the affected Unix datagram socket.
  • The trigger is a message with an empty TAG.
Security assessment · AI, from the article

Impact: local denial of service via PID rewriting

ProductAffected
rsyslog>= 5.7.1
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

Posted by Rainer Gerhards on Nov 17 rsyslog imuxsock empty-TAG PID underwrite (local denial of service) rsyslog has a local denial-of-service vulnerability in imuxsock's PID rewriting path. When UsePIDFromSystem or SysSock. UsePIDFromSystem is enabled, a local sender that can write to the affected Unix datagram socket can submit a message with an empty TAG.

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.