CVE-2011-1951
First published: Mon May 30 2011(Updated: )
A denial of service flaw was found in the way syslog-ng processed certain log patterns, when 'global' flag was speficied and PCRE backend was used for matching. A remote attacker could use this flaw to cause excessive memory use by the syslog-ng process via specially-crafted pattern. References: [1] <a href="http://www.securityfocus.com/bid/47800/info">http://www.securityfocus.com/bid/47800/info</a> [2] <a href="https://lists.balabit.hu/pipermail/syslog-ng/2011-May/016576.html">https://lists.balabit.hu/pipermail/syslog-ng/2011-May/016576.html</a> Upstream patch: [3] <a href="http://git.balabit.hu/?p=bazsi/syslog-ng-3.2.git;a=commit;h=09710c0b105e579d35c7b5f6c66d1ea5e3a3d3ff">http://git.balabit.hu/?p=bazsi/syslog-ng-3.2.git;a=commit;h=09710c0b105e579d35c7b5f6c66d1ea5e3a3d3ff</a>
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| OneIdentity Syslog-ng | <3.2.4 | |
| PCRE | =8.12 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/47800
- http://lists.fedoraproject.org/pipermail/package-announce/2011-June/062107.html
- http://www.openwall.com/lists/oss-security/2011/05/26/1
- https://bugzilla.redhat.com/show_bug.cgi?id=709088
- http://secunia.com/advisories/45122
- http://git.balabit.hu/?p=bazsi/syslog-ng-3.2.git%3Ba=commit%3Bh=09710c0b105e579d35c7b5f6c66d1ea5e3a3d3ff
- http://www.securityfocus.com/bid/47800/info
- https://lists.balabit.hu/pipermail/syslog-ng/2011-May/016576.html
- http://git.balabit.hu/?p=bazsi/syslog-ng-3.2.git;a=commit;h=09710c0b105e579d35c7b5f6c66d1ea5e3a3d3ff
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=709092
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=709093
- https://access.redhat.com/security/cve/CVE-2011-1951
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=709088#c4
- http://git.balabit.hu/?p=bazsi/syslog-ng-3.1.git;a=commitdiff;h=35de55e53dd653c50c8da5daf41a99ab22e7e8aa
- https://lists.balabit.hu/pipermail/syslog-ng/2011-April/016444.html
- https://lists.balabit.hu/pipermail/syslog-ng/2011-May/016503.html
- https://lists.balabit.hu/pipermail/syslog-ng/2011-May/016537.html
Frequently Asked Questions
What is the severity of CVE-2011-1951?
CVE-2011-1951 has been classified as a denial of service vulnerability.
How do I fix CVE-2011-1951?
To fix CVE-2011-1951, upgrade syslog-ng to version 3.2.4 or later.
What can an attacker achieve with CVE-2011-1951?
An attacker can cause excessive memory usage in the syslog-ng process through specially-crafted log patterns.
Which versions of syslog-ng are affected by CVE-2011-1951?
Syslog-ng versions prior to 3.2.4 are affected by CVE-2011-1951.
Does CVE-2011-1951 affect the PCRE version?
CVE-2011-1951 specifically affects syslog-ng when the PCRE backend is used for matching.
- collector/nvd-historical
- agent/type
- agent/remedy
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/severity
- agent/references
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2011-1951
- agent/event
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/oneidentity
- canonical/oneidentity syslog-ng
- vendor/pcre
- canonical/pcre
- version/pcre/8.12