CWE
119
Advisory Published
CVE Published
Updated

CVE-2017-15670: Buffer Overflow

First published: Fri Oct 20 2017(Updated: )

A buffer overflow vulnerability caused by an off-by-one error was found in glibc. It is possible that an attacker might use this to escalate his privileges or execute code. Upstream patch: <a href="http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=2d1bd71ec70a31b01d01b734faa66bb1ed28961f">http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=2d1bd71ec70a31b01d01b734faa66bb1ed28961f</a> Upstream issue: <a href="https://sourceware.org/bugzilla/show_bug.cgi?id=22320">https://sourceware.org/bugzilla/show_bug.cgi?id=22320</a>

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/glibc<2.27
2.27
debian/glibc
2.31-13+deb11u11
2.31-13+deb11u10
2.36-9+deb12u8
2.36-9+deb12u7
2.40-3
GNU C Library (glibc)<=2.26

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 CVE-2017-15670?

    CVE-2017-15670 is a vulnerability in the GNU C Library (glibc) before version 2.27 that leads to a heap-based buffer overflow.

  • What is the severity of CVE-2017-15670?

    CVE-2017-15670 has a severity rating of 9.8, which is considered critical.

  • How does CVE-2017-15670 impact the GNU C Library?

    CVE-2017-15670 affects the glob function in glob.c, which leads to a heap-based buffer overflow in glibc.

  • Which versions of glibc are affected by CVE-2017-15670?

    Versions before 2.27 of the GNU C Library (glibc) are affected by CVE-2017-15670.

  • Is there a fix available for CVE-2017-15670?

    Yes, the vulnerability can be remediated by updating glibc to version 2.27 or later.

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