How severe is CVE-2008-5618?

CVE-2008-5618 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2008-5618 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2008-5618?

CVE-2008-5618 primarily affects Rsyslog. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2008-5618?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2008-5618 published?

CVE-2008-5618 was published on 2008-12-17 and last updated on 2026-06-16.

CVE-2008-5618

CVE-2008-5618 is a medium-severity vulnerability in Rsyslog with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.0)
EPSS exploit prediction: 1% (64th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Rsyslog
Published: 2008-12-17
Last modified: 2026-06-16

Description

imudp in rsyslog 4.x before 4.1.2, 3.21 before 3.21.9 beta, and 3.20 before 3.20.2 generates a message even when it is sent by an unauthorized sender, which allows remote attackers to cause a denial of service (disk consumption) via a large number of spurious messages.

Frequently asked questions

What is CVE-2008-5618?: imudp in rsyslog 4.x before 4.1.2, 3.21 before 3.21.9 beta, and 3.20 before 3.20.2 generates a message even when it is sent by an unauthorized sender, which allows remote attackers to cause a denial of service (disk consumption) via a large number of spurious messages.
How severe is CVE-2008-5618?: CVE-2008-5618 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2008-5618 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-5618?: CVE-2008-5618 primarily affects Rsyslog. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2008-5618?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2008-5618 published?: CVE-2008-5618 was published on 2008-12-17 and last updated on 2026-06-16.

References

http://www.rsyslog.com/Topic4.phtml

Affected products (4)

cpe:2.3:a:rsyslog:rsyslog:3.12.1:*:*:*:*:*:*:*
cpe:2.3:a:rsyslog:rsyslog:3.20.0:*:*:*:*:*:*:*
cpe:2.3:a:rsyslog:rsyslog:4.1.0:*:*:*:*:*:*:*
cpe:2.3:a:rsyslog:rsyslog:4.1.1:*:*:*:*:*:*:*

More vulnerabilities in Rsyslog

CVE-2019-17042 — Critical (CVSS 9.8): An issue was discovered in Rsyslog v8.1908.0. contrib/pmcisconames/pmcisconames.c has a heap overflow in the parser for…
CVE-2019-17041 — Critical (CVSS 9.8): An issue was discovered in Rsyslog v8.1908.0. contrib/pmaixforwardedfrom/pmaixforwardedfrom.c has a heap overflow in…
CVE-2019-17040 — Critical (CVSS 9.8): contrib/pmdb2diag/pmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is mishandled.
CVE-2017-12588 — Critical (CVSS 9.8): The zmq3 input and output modules in rsyslog before 8.28.0 interpreted description fields as format strings, possibly…
CVE-2008-5617 — High (CVSS 8.5): The ACL handling in rsyslog 3.12.1 to 3.20.0, 4.1.0, and 4.1.1 does not follow $AllowedSender directive, which allows…
CVE-2022-24903 — High (CVSS 8.1): Rsyslog is a rocket-fast system for log processing. Modules for TCP syslog reception have a potential heap buffer…

All CVEs affecting Rsyslog →