CVE-2017-14461: A specially crafted email delivered over SMTP and passed on to Dovecot by MTA can trigger an out of bounds read resulting in potential…
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 16.6% (FIRST EPSS); higher than 97% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: dovecot (Alpine:v3.10) 2.3.1-r0; dovecot (Alpine:v3.7) 2.2.34-r0; dovecot (Debian:12) 1:2.2.34-1.
Low priority for now. Upgrade to dovecot (Alpine:v3.10) 2.3.1-r0; dovecot (Alpine:v3.7) 2.2.34-r0; dovecot (Debian:12) 1:2.2.34-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A specially crafted email delivered over SMTP and passed on to Dovecot by MTA can trigger an out of bounds read resulting in potential sensitive information disclosure and denial of service. In order to trigger this vulnerability, an attacker needs to send a specially crafted email message to the server.
- Published
- Mar 2, 2018
- Updated
- Jun 16, 2026
- EPSS
- 16.6% · 97th percentile
- CWE
- CWE-125
Report tools
Action score
33
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 16.6%
CNA vs NVD score
- NVD
- 7.1
- CNA · talos
- 5.9
- 1.2 point gap
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dovecot | dovecot | cpe:2.3:a:dovecot:dovecot |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| ubuntu | ubuntu | cpe:2.3:o:ubuntu:ubuntu |
Using dovecot? Add it to your stack and be the first to know about CVEs like this one. (Email server)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.
The Dovecot Project Dovecot
- 2.2.33.2affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dovecot dovecot2.2.33.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | dovecot | before 2.3.1-r0 | 2.3.1-r0 |
| Alpine:v3.7 | dovecot | before 2.2.34-r0 | 2.2.34-r0 |
| Debian:12 | dovecot | before 1:2.2.34-1 | 1:2.2.34-1 |
| Debian:7 | dovecot | before 1:2.1.7-7+deb7u2 | 1:2.1.7-7+deb7u2 |
| Debian:8 | dovecot | before 1:2.2.13-12~deb8u4 | 1:2.2.13-12~deb8u4 |
| Debian:9 | dovecot | before 1:2.2.27-3+deb9u2 | 1:2.2.27-3+deb9u2 |
| openSUSE:Tumbleweed | dovecot23 | before 2.3.16-1.6 | 2.3.16-1.6 |
| openSUSE:Tumbleweed | dovecot24 | before 2.4.0-1.1 | 2.4.0-1.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP3 | dovecot22 | before 2.2.31-19.8.1 | 2.2.31-19.8.1 |
Same product
dovecot: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11500In Dovecot before 2.2.36.4 and 2.3.x before 2.3.7.2 (and Pigeonhole before 0.5.7.2), protocol processing can fail for quoted strings.58Plan
- CVE-2020-7046lib-smtp in submission-login and lmtp in Dovecot 2.3.9 before 2.3.9.3 mishandles truncated UTF-8 data in command parameters, as…45Plan
- CVE-2016-8652The auth component in Dovecot before 2.2.27, when auth-policy is configured, allows a remote attackers to cause a denial of service (crash)…37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-3420Sep 19, 2017 · The ssl-proxy-openssl.c function in Dovecot before 2.2.17, when SSLv3 is disabled, allow remote attackers to cause a denial of service…24Monitor
- ← EarlierCVE-2017-15132Jan 25, 2018 · A flaw was found in dovecot 2.0 up to 2.2.33 and 2.3.0.31Monitor
- Later →CVE-2017-15130Mar 2, 2018 · A denial of service flaw was found in dovecot before 2.2.34.24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:dovecot | 2.3.1-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:dovecot | 1:2.2.34-1 · Debian:12 | Package registry (OSV) |
| opensuse:dovecot23 | 2.3.16-1.6 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:dovecot24 | 2.4.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:dovecot22 | 2.2.31-19.8.1 · SUSE:Linux Enterprise Software Development Kit 12 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.