7.5
CWE
772 400
Advisory Published
CVE Published
Updated

CVE-2017-15132

First published: Tue Jan 09 2018(Updated: )

A flaw was found in dovecot 2.0 up to 2.2.33 and 2.3.0. A abort of SASL authentication results in a memory leak in Dovecot auth client used by login processes. The leak has impact in high performance configuration where same login processes are reused and can cause the process to crash due to memory exhaustion. Upstream patch: <a href="https://github.com/dovecot/core/commit/1a29ed2f96da1be22fa5a4d96c7583aa81b8b060.patch">https://github.com/dovecot/core/commit/1a29ed2f96da1be22fa5a4d96c7583aa81b8b060.patch</a> <a href="https://github.com/dovecot/core/commit/a9b135760aea6d1790d447d351c56b78889dac22.patch">https://github.com/dovecot/core/commit/a9b135760aea6d1790d447d351c56b78889dac22.patch</a>

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/dovecot<2.2.34
2.2.34
redhat/dovecot<2.3.1
2.3.1
debian/dovecot
1:2.3.13+dfsg1-2+deb11u1
1:2.3.13+dfsg1-2+deb11u2
1:2.3.19.1+dfsg1-2.1+deb12u1
1:2.3.21.1+dfsg1-1
Dovecot Dovecot>=2.0.0<=2.2.33
Dovecot Dovecot=2.3.0
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Ubuntu Linux=12.04
Ubuntu Linux=14.04
Ubuntu Linux=16.04
Ubuntu Linux=17.10

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 vulnerability ID for the dovecot memory leak vulnerability?

    The vulnerability ID for the dovecot memory leak vulnerability is CVE-2017-15132.

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

    The severity of CVE-2017-15132 is high with a severity value of 7.5.

  • Which versions of dovecot are affected by CVE-2017-15132?

    The versions of dovecot affected by CVE-2017-15132 are 2.0 up to 2.2.33 and 2.3.0.

  • How does the vulnerability CVE-2017-15132 impact high performance configuration?

    The CVE-2017-15132 vulnerability can cause a memory leak in dovecot's auth client used by login processes, which can result in a process crash in high performance configurations.

  • How can I fix the CVE-2017-15132 vulnerability?

    To fix the CVE-2017-15132 vulnerability, it is recommended to update to the latest patched version of dovecot.

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