CWE
119
Advisory Published
CVE Published
Updated

CVE-2016-9011: Buffer Overflow

First published: Tue Oct 25 2016(Updated: )

A memory allocation failure in function wmf_malloc in api.c was reported in libwmf. Opening a maliciously crafted file could cause the application to crash. References: <a href="http://seclists.org/oss-sec/2016/q4/176">http://seclists.org/oss-sec/2016/q4/176</a> External References: <a href="https://blogs.gentoo.org/ago/2016/10/18/libwmf-memory-allocation-failure-in-wmf_malloc-api-c/">https://blogs.gentoo.org/ago/2016/10/18/libwmf-memory-allocation-failure-in-wmf_malloc-api-c/</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
libwmf=0.2.8.4

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.

Frequently Asked Questions

  • What is the severity of CVE-2016-9011?

    CVE-2016-9011 is classified with a moderate severity due to its potential to cause application crashes.

  • How do I fix CVE-2016-9011?

    To fix CVE-2016-9011, update libwmf to version 0.2.8.5 or later where the vulnerability is patched.

  • What does CVE-2016-9011 affect?

    CVE-2016-9011 affects libwmf, specifically version 0.2.8.4, and allows the application to crash when processing malicious files.

  • What are the consequences of exploiting CVE-2016-9011?

    Exploiting CVE-2016-9011 can lead to a denial of service (DoS) as the application crashes upon handling a crafted file.

  • Is CVE-2016-9011 easy to exploit?

    CVE-2016-9011 can be considered easy to exploit as it requires a specially crafted file to trigger the memory allocation failure.

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