Skip to content
Fencer Intel
medium 5.5

CVE-2011-1488 json

A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled.

published 2019-11-14 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1491

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent within short periods of time.

Patch / fix

  • rsyslog rsyslog 5.7.6
  • rsyslog Debian 14, Debian 13, Debian 12 5.7.6-1

debian advisories DEBIAN-CVE-2011-1488

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-1488 updated cvss 1.9

rsyslog: Memory leak when $RepeatedMsgReduction turned on

  • Red Hat Enterprise Linux 5 rsyslog Red Hat Enterprise Linux 6 rsyslog, rsyslog-relp, rsyslog-snmp, rsyslog-mysql, rsyslog-pgsql, rsyslog-gnutls, +1 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-1488 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:N/A:P

Affected products

  • rsyslog rsyslog

Classification

Weakness
  • CWE-772 Missing Release of Resource after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.