CVE-2017-15132
CVE-2017-15132 Vulnerability Analysis & Exploit Intelligence
A flaw was found in dovecot 2.0 up to 2.2.33 and 2.3.0. An abort of SASL authentication results in a memory leak in dovecot's 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.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Weakness & attack patterns
- CWE-400
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1499Endpoint Denial of Service
References
7 on the record
- github.com/dovecot/core/commit/1a29ed2f96da1be22fa5a4d96c7583aa81b8b060.patch
x_refsource_CONFIRM
- lists.debian.org/debian-lts-announce/2018/03/msg00036.html
mailing-list, x_refsource_MLIST
- bugzilla.redhat.com/show_bug.cgi?id=1532768
x_refsource_CONFIRM
- www.debian.org/security/2018/dsa-4130
vendor-advisory, x_refsource_DEBIAN
- usn.ubuntu.com/3556-1/
vendor-advisory, x_refsource_UBUNTU
- usn.ubuntu.com/3556-2/
vendor-advisory, x_refsource_UBUNTU
- www.dovecot.org/list/dovecot-news/2018-February/000370.html
mailing-list, x_refsource_MLIST
Elsewhere on this site
- the dovecot projectevery CVE for this vendor
- CWE-400other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.