medium
5
CWE
119
Advisory Published
CVE Published
Updated

CVE-2011-3200: Buffer Overflow

First published: Tue Aug 02 2011(Updated: )

Description of problem: If we send to syslog a specially crafted log message, stack guard variable protecting bufParseTAG array in parseLegacySyslogMsg() gets rewritten and rsyslog gets terminated. Version-Release number of selected component (if applicable): rsyslog-4.6.2-3.el6_1.1.i686 How reproducible: everytime on ia-32 on x86-64 stack guard variable won't get rewritten as it is located 8 bytes above bufParseTAG array Actual results: glibc prints the following message and rsyslog gets terminated: *** stack smashing detected ***: rsyslogd terminated Expected results: No abortion. Additional info: For more info, please, see the following private comment.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/rsyslog<4.6.8
4.6.8
redhat/rsyslog<5.8.5
5.8.5
Ubuntu Rsyslog=4.6.6
Ubuntu Rsyslog=4.6.7
Ubuntu Rsyslog=4.6.3
Ubuntu Rsyslog=4.6.4
Ubuntu Rsyslog=4.6.1
Ubuntu Rsyslog=4.6.2
Ubuntu Rsyslog=4.6.0
Ubuntu Rsyslog=4.6.5
Ubuntu Rsyslog=5.5.6
Ubuntu Rsyslog=5.5.7
Ubuntu Rsyslog=5.4.2
Ubuntu Rsyslog=5.5.0
Ubuntu Rsyslog=5.5.4
Ubuntu Rsyslog=5.5.1
Ubuntu Rsyslog=5.6.1
Ubuntu Rsyslog=5.3.6
Ubuntu Rsyslog=5.8.3
Ubuntu Rsyslog=5.6.4
Ubuntu Rsyslog=5.7.5
Ubuntu Rsyslog=5.5.3
Ubuntu Rsyslog=5.8.0
Ubuntu Rsyslog=5.8.2
Ubuntu Rsyslog=5.6.2
Ubuntu Rsyslog=5.6.0
Ubuntu Rsyslog=5.6.5
Ubuntu Rsyslog=5.7.7
Ubuntu Rsyslog=5.7.9
Ubuntu Rsyslog=5.4.0
Ubuntu Rsyslog=5.7.2
Ubuntu Rsyslog=5.3.1
Ubuntu Rsyslog=5.7.4
Ubuntu Rsyslog=5.7.10
Ubuntu Rsyslog=5.2.0
Ubuntu Rsyslog=5.3.7
Ubuntu Rsyslog=5.2.2
Ubuntu Rsyslog=5.8.1
Ubuntu Rsyslog=5.3.3
Ubuntu Rsyslog=5.7.6
Ubuntu Rsyslog=5.3.2
Ubuntu Rsyslog=5.7.8
Ubuntu Rsyslog=5.6.3
Ubuntu Rsyslog=5.5.2
Ubuntu Rsyslog=5.2.1
Ubuntu Rsyslog=5.4.1
Ubuntu Rsyslog=5.7.0
Ubuntu Rsyslog=5.7.3
Ubuntu Rsyslog=5.5.5
Ubuntu Rsyslog=5.3.4
Ubuntu Rsyslog=5.7.1
Ubuntu Rsyslog=5.3.5
Ubuntu Rsyslog=5.8.4

Remedy

http://git.adiscon.com/?p=rsyslog.git;a=commit;h=1ca6cc236d1dabf1633238b873fb1c057e52f95e

Remedy

http://www.rsyslog.com/potential-dos-with-malformed-tag/

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=727644

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2011-3200?

    CVE-2011-3200 is considered a high severity vulnerability that can lead to denial of service.

  • How do I fix CVE-2011-3200?

    To fix CVE-2011-3200, upgrade to rsyslog version 4.6.8 or 5.8.5 or later.

  • What systems are affected by CVE-2011-3200?

    CVE-2011-3200 affects multiple versions of rsyslog, specifically 4.6.0 to 4.6.7 and 5.4.0 to 5.8.4.

  • What is the impact of CVE-2011-3200?

    The impact of CVE-2011-3200 is that an attacker can terminate the rsyslog service by sending a specially crafted log message.

  • Can CVE-2011-3200 be exploited remotely?

    Yes, CVE-2011-3200 can be exploited remotely if an attacker can send crafted syslog messages to the affected rsyslog service.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203