Skip to content
Noroxi
CVE-2017-14461· NVD / CVE Program· CNA talos

A specially crafted email delivered over SMTP and passed on to Dovecot by MTA can trigger an out of bounds read resulting in potential sensi

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.

HighCVSS 7.1 · v3.0—No exploit Fix available
Published
Mar 2, 2018
Updated
Jun 16, 2026
EPSS
16.7% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 16.7%

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.

Affected systems

VendorProduct
dovecotdovecot
debiandebian linux
ubuntuubuntu

Using dovecot? Add it to your stack and be the first to know about CVEs like this one. (Email server)

Add to my stack

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

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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10dovecotbefore 2.3.1-r02.3.1-r0
Alpine:v3.7dovecotbefore 2.2.34-r02.2.34-r0
Debian:12dovecotbefore 1:2.2.34-11:2.2.34-1
Debian:7dovecotbefore 1:2.1.7-7+deb7u21:2.1.7-7+deb7u2
Debian:8dovecotbefore 1:2.2.13-12~deb8u41:2.2.13-12~deb8u4
Debian:9dovecotbefore 1:2.2.27-3+deb9u21:2.2.27-3+deb9u2
openSUSE:Tumbleweeddovecot23before 2.3.16-1.62.3.16-1.6
openSUSE:Tumbleweeddovecot24before 2.4.0-1.12.4.0-1.1
SUSE:Linux Enterprise Software Development Kit 12 SP3dovecot22before 2.2.31-19.8.12.2.31-19.8.1

Other 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 demonstrated
    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
  • CVE-2026-27851When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabli
    36Monitor
  • CVE-2022-30550An issue was discovered in the auth component in Dovecot 2.2 and 2.3 before 2.3.20.
    36Monitor
  • CVE-2026-24031Dovecot SQL based authentication can be bypassed when auth_username_chars is cleared by admin.
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Alpine:dovecot2.3.1-r0 · Alpine:v3.10Package registry (OSV)
Debian:dovecot1:2.2.34-1 · Debian:12Package registry (OSV)
openSUSE:dovecot232.3.16-1.6 · openSUSE:TumbleweedPackage registry (OSV)
openSUSE:dovecot242.4.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
SUSE:dovecot222.2.31-19.8.1 · SUSE:Linux Enterprise Software Development Kit 12 SP3Package 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.

EPSS, last 120 days-1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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 Read

CVSS 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.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records