rpm package
suse/dovecot22&distro=SUSE Linux Enterprise Server 12-LTSS
pkg:rpm/suse/dovecot22&distro=SUSE%20Linux%20Enterprise%20Server%2012-LTSS
Vulnerabilities (3)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2019-7524 | — | < 2.2.31-19.14.2 | 2.2.31-19.14.2 | Mar 28, 2019 | In Dovecot before 2.2.36.3 and 2.3.x before 2.3.5.1, a local attacker can cause a buffer overflow in the indexer-worker process, which can be used to elevate to root. This occurs because of missing checks in the fts and pop3-uidl components. | ||
| CVE-2019-3814 | — | < 2.2.31-19.14.2 | 2.2.31-19.14.2 | Mar 27, 2019 | It was discovered that Dovecot before versions 2.2.36.1 and 2.3.4.1 incorrectly handled client certificates. A remote attacker in possession of a valid certificate with an empty username field could possibly use this issue to impersonate other users. | ||
| CVE-2017-15130 | — | < 2.2.31-19.11.1 | 2.2.31-19.11.1 | Mar 2, 2018 | A denial of service flaw was found in dovecot before 2.2.34. An attacker able to generate random SNI server names could exploit TLS SNI configuration lookups, leading to excessive memory usage and the process to restart. |
- CVE-2019-7524Mar 28, 2019affected < 2.2.31-19.14.2fixed 2.2.31-19.14.2
In Dovecot before 2.2.36.3 and 2.3.x before 2.3.5.1, a local attacker can cause a buffer overflow in the indexer-worker process, which can be used to elevate to root. This occurs because of missing checks in the fts and pop3-uidl components.
- CVE-2019-3814Mar 27, 2019affected < 2.2.31-19.14.2fixed 2.2.31-19.14.2
It was discovered that Dovecot before versions 2.2.36.1 and 2.3.4.1 incorrectly handled client certificates. A remote attacker in possession of a valid certificate with an empty username field could possibly use this issue to impersonate other users.
- CVE-2017-15130Mar 2, 2018affected < 2.2.31-19.11.1fixed 2.2.31-19.11.1
A denial of service flaw was found in dovecot before 2.2.34. An attacker able to generate random SNI server names could exploit TLS SNI configuration lookups, leading to excessive memory usage and the process to restart.