Approved changes feed: RSS · Atom

cpe:2.3:a:rsyslog:rsyslog:8.1908.0:*:*:*:*:*:*:*

part: a version: 8.1908.0 update: *

VendorRsyslog (f723e340-bdcc-534e-a8e1-517ee98711af)
ProductRsyslog (be151fcf-b724-5377-925d-129803ae9e9b)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/rsyslog purl2cpe 2026-06-01 10:14:18.711767
pkg:deb/ubuntu/rsyslog purl2cpe 2026-06-01 10:14:18.711768
pkg:github/rsyslog/rsyslog purl2cpe 2026-06-01 10:14:18.711770
pkg:rpm/fedora/rsyslog purl2cpe 2026-06-01 10:14:18.711771
pkg:rpm/opensuse/rsyslog purl2cpe 2026-06-01 10:14:18.711773

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2019-17042 vulnerable 2026-06-08 05:13:09.804700 Details available
An issue was discovered in Rsyslog v8.1908.0. contrib/pmcisconames/pmcisconames.c has a heap overflow in the parser for Cisco log messages. The parser tries to locate a log message delimiter (in this case, a space or a colon), but fails to account for strings that do not satisfy this constraint. If the string does not match, then the variable lenMsg will reach the value zero and will skip the sanity check that detects invalid log messages. The message will then be considered valid, and the parser will eat up the nonexistent colon delimiter. In doing so, it will decrement lenMsg, a signed integer, whose value was zero and now becomes minus one. The following step in the parser is to shift left the contents of the message. To do this, it will call memmove with the right pointers to the target and destination strings, but the lenMsg will now be interpreted as a huge value, causing a heap overflow.
Published: 2019-10-07T15:34:04.000Z
Updated: 2024-08-05T01:24:48.684Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-17041 vulnerable 2026-06-08 05:13:09.804146 Details available
An issue was discovered in Rsyslog v8.1908.0. contrib/pmaixforwardedfrom/pmaixforwardedfrom.c has a heap overflow in the parser for AIX log messages. The parser tries to locate a log message delimiter (in this case, a space or a colon) but fails to account for strings that do not satisfy this constraint. If the string does not match, then the variable lenMsg will reach the value zero and will skip the sanity check that detects invalid log messages. The message will then be considered valid, and the parser will eat up the nonexistent colon delimiter. In doing so, it will decrement lenMsg, a signed integer, whose value was zero and now becomes minus one. The following step in the parser is to shift left the contents of the message. To do this, it will call memmove with the right pointers to the target and destination strings, but the lenMsg will now be interpreted as a huge value, causing a heap overflow.
Published: 2019-10-07T15:31:17.000Z
Updated: 2024-08-05T01:24:48.725Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-17040 vulnerable 2026-06-08 05:13:09.803487 Details available
contrib/pmdb2diag/pmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is mishandled.
Published: 2019-09-30T13:06:43.000Z
Updated: 2024-08-05T01:24:48.756Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.