VYPR
Unrated severityNVD Advisory· Published Mar 2, 2018· Updated Sep 16, 2024

CVE-2017-14461

CVE-2017-14461

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Members only

The AI Insight narrative is available to signed-in members. Sign in or create a free account to read it.

Affected products

7

Patches

Members only

Discovered fix commits and diffs is available to signed-in members. Sign in or create a free account to read it.

Vulnerability mechanics

Root cause

"The RFC822 parser in Dovecot does not properly validate buffer boundaries when parsing email addresses, leading to out-of-bounds reads."

Attack vector

An attacker can trigger this vulnerability by sending a specially crafted email over SMTP to a Dovecot server. The email must contain malformed address fields, such as those with unbalanced parentheses or unclosed brackets within quoted strings or domain literals. When Dovecot's MTA passes this email to the parser, functions like `rfc822_skip_comment`, `rfc822_parse_domain_literal`, or `rfc822_parse_quoted_string` can be invoked with invalid context, leading to an out-of-bounds read [ref_id=1].

Affected code

The vulnerability resides in the RFC822 parser implementation within Dovecot. Specifically, the functions `rfc822_skip_comment`, `rfc822_parse_domain_literal`, and `rfc822_parse_quoted_string` are identified as being susceptible to triggering an out-of-bounds read due to improper handling of input data [ref_id=1]. The issue stems from how the parser increments its data pointer without sufficient checks against buffer boundaries.

What the fix does

The advisory does not specify a patch or provide details on how the vulnerability is fixed. However, it indicates that the issue lies within the RFC822 parser's handling of email addresses, specifically in functions like `rfc822_skip_comment`, `rfc822_parse_domain_literal`, and `rfc822_parse_quoted_string` [ref_id=1]. A fix would likely involve adding boundary checks to prevent the parser from reading beyond allocated memory buffers.

Preconditions

  • networkThe attacker must be able to send emails to the target server via SMTP.
  • inputThe attacker must send a specially crafted email with malformed address fields.

Generated on Jun 5, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

7

News mentions

0

No linked articles in our index yet.