FedoraOperating system · Fedoraproject
CVE-2019-11494
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the IMAP Server in Dovecot 2.3.3 through 2.3.5.2, the submission-login service crashes when the client disconnects prematurely during the AUTH command.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial-of-service vulnerability exists in the IMAP submission-login service of Dovecot versions 2.3.3 through 2.3.5.2. When a client disconnects prematurely during the AUTH command, the submission-login service crashes, causing service interruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 29= 30>= 2.3.3, <= 2.3.5.2= 15.0= 15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Dovecot is installedRun 'rpm -q dovecot' on Fedora/RHEL or 'rpm -qa | grep -i dovecot' on OpenSUSE to see if the dovecot package is presentAffected if Dovecot package is not installed - not affected; if installed, proceed to version check
-
Determine installed Dovecot versionRun 'dovecot --version' or 'rpm -q dovecot --qf "%{VERSION}-%{RELEASE}"' to get the exact version numberAffected if Version number is within range >= 2.3.3 and <= 2.3.5.2 - likely affected
-
Verify submission-login service is enabledCheck configuration files in /etc/dovecot/ for 'submission' in enabled services, or check for 'submission-login' in dovecot.conf or conf.d/ directoriesAffected if The submission-login service is explicitly configured/enabled - vulnerable to the crash condition
-
Check for submission service configurationLook for 'submission' in /etc/dovecot/dovecot.conf or any file under /etc/dovecot/conf.d/ that enables the submission protocolAffected if Submission service is enabled in configuration - attack surface exists
User is affected if Dovecot version is between 2.3.3 and 2.3.5.2 AND the submission-login service is enabled in the configuration, as the crash only occurs when a client disconnects prematurely during the AUTH command on that specific service.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Dovecot to a version newer than 2.3.5.2 where the crash condition is fixed, or apply the vendor patch if available for your version.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11494 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-11494 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data