Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri, 3 Oct 2014 09:12:28 +0000
From: mancha <>
Subject: sysklogd vulnerability (CVE-2014-3634)

Vendors et al.

Many thanks to Rainer Gerhards, rsyslog project lead, for identifying a
problem with how rsyslog's rsyslogd and sysklogd's syslogd check for
invalid priority values (CVE-2014-3634). For details please refer to
Rainer's well-written issue description. [1]

In sysklogd's syslogd, invalid priority values between 192 and 1023
(directly or arrived at via overflow wraparound) can propagate through
code causing out-of-bounds access to the f_pmask array within the
'filed' structure by up to 104 bytes past its end. Though most likely
insufficient to reach unallocated memory because there are around 544
bytes past f_pmask in 'filed' (mod packing and other differences),
incorrect access of fields at higher positions of the 'filed' structure
definition can cause unexpected behavior including message
mis-classification, forwarding issues, message loss, or other.

I've been unable to contact sysklogd's maintainer (the project is no
longer active) but, given some vendors ship sysklogd as their system
logging daemon, it was important to share a fix.

Fix for sysklogd 1.5 is available at:

Note: publication of this patch was intentionally delayed to afford the
rsyslog project time to correct their initial fix set which was
vulnerable to integer overflows (CVE-2014-3683). [2]



Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.