Skip to content
NewA calmer, faster ZeroHour

rsyslog 8.3.2 and later can crash on low-year weekday formatting

Original title: rsyslog >=8.3.2: low-year weekday formatting can crash rsyslogd (GHSA-5pc2-f2v7-5w5p)

oss-security ()
AI summary · x-ai/grok-4.7Summaries by Vani AI

A crafted RFC5424 year-0001 timestamp can SIGSEGV rsyslogd when a template formats it as a weekday name.

Rainer Gerhards reported GHSA-5pc2-f2v7-5w5p. rsyslogd accepts an RFC5424 timestamp with year 0001, and the shared weekday calculation can return a negative C remainder. date-wdayname then uses that value to index a seven-element weekday-name table. In a normal build, one crafted message accepted through imtcp and routed to such an action template caused a SIGSEGV.

Unconfirmed: The post is truncated and does not name a fixed release or say whether authentication is required.

Key facts
  • The issue affects rsyslog releases at or after 8.3.2.
  • The parser accepts an RFC5424 timestamp with year 0001.
  • date-wdayname indexes a seven-element table using a negative remainder.
  • The crash was shown through imtcp with an action template.
Security assessment · AI, from the article

Impact: crash of rsyslogd from one crafted message

ProductAffected
rsyslog>=8.3.2
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 GHSA-5pc2-f2v7-5w5p: rsyslogd can crash when a template formats a crafted low-year reported timestamp as a weekday name. An RFC5424 timestamp with year 0001 is accepted by the parser. The shared weekday calculation can return a negative C remainder, and date-wdayname uses it to index a seven-element weekday-name table.

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.