International
The Morning Dev

Only the news worth knowing

‹
 

SecurityFan score 22 · Tier C3 sources

rsyslog imuxsock TAG parser out-of-bounds read

oss-security ·

The Brief · written from 3 sources

  • Three rsyslog advisories were posted to the oss-security list on 2026-11-17, covering a crash in low-year weekday formatting (GHSA-5pc2-f2v7-5w5p) and two imuxsock memory-safety bugs in the system-timestamp and TAG parsing code.
  • The weekday formatting issue can crash rsyslogd in versions 8.3.2 and later.
  • The imuxsock flaws are an out-of-bounds read and an out-of-bounds write that a local sender can trigger; the write can go beyond a received message's raw buffer.

Why it matters

Any system running rsyslog 8.3.2 or later may have rsyslogd crash, and local senders can reach memory-safety bugs in the imuxsock input, so logging infrastructure should be checked against the advisories.

Who’s affected

  • rsyslog users on version 8.3.2 and later
  • Systems using the rsyslog imuxsock input

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…

Timeline

  1. Advisories for the rsyslog issues posted to the oss-security list

  2. Open Source Security

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

  3. Open Source Security

    rsyslog imuxsock system-timestamp out-of-bounds write

  4. Open Source Security

    rsyslog imuxsock TAG parser out-of-bounds read

Full coverage · 3 sources

How do you feel about this?

0 Comments

    rsyslog imuxsock TAG parser out-of-bounds read – The Morning Dev