7.5
CWE
119
Advisory Published
CVE Published
Updated

CVE-2017-15275: Buffer Overflow

First published: Mon Nov 13 2017(Updated: )

As per upstream samba advisory: All versions of Samba from 3.6.0 onwards are vulnerable to a heap memory information leak, where server allocated heap memory may be returned to the client without being cleared. There is no known vulnerability associated with this error, but uncleared heap memory may contain previously used data that may help an attacker compromise the server via other methods. Uncleared heap memory may potentially contain password hashes or other high-value data.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
debian/samba
2:4.9.5+dfsg-5+deb10u3
2:4.9.5+dfsg-5+deb10u4
2:4.13.13+dfsg-1~deb11u5
2:4.17.11+dfsg-0+deb12u1
2:4.17.12+dfsg-0+deb12u1
2:4.19.1+dfsg-4
2:4.19.2+dfsg-1
Samba>=3.6.0<4.5.15
Samba>=4.6.0<4.6.11
Samba>=4.7.0<4.7.3
Ubuntu Linux=14.04
Ubuntu Linux=16.04
Ubuntu Linux=17.04
Ubuntu Linux=17.10
Debian GNU/Linux=8.0
Debian GNU/Linux=9.0
redhat enterprise Linux desktop=6.0
redhat enterprise Linux desktop=7.0
redhat enterprise Linux server=6.0
redhat enterprise Linux server=7.0
redhat enterprise Linux workstation=6.0
redhat enterprise Linux workstation=7.0

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-2017-15275?

    CVE-2017-15275 is considered a moderate severity vulnerability due to the potential exposure of sensitive data through an information leak.

  • How do I fix CVE-2017-15275?

    To fix CVE-2017-15275, ensure that your Samba version is updated to a patched release that addresses this vulnerability.

  • What versions of Samba are affected by CVE-2017-15275?

    CVE-2017-15275 affects all Samba versions from 3.6.0 onwards, up to but not including the patched versions.

  • Is there a known exploit for CVE-2017-15275?

    There is currently no known exploit associated with CVE-2017-15275, but the vulnerability does allow for potential data exposure.

  • What should I do if I cannot update Samba for CVE-2017-15275?

    If you cannot update Samba for CVE-2017-15275, consider implementing additional security controls to mitigate the risk of information exposure.

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