FedoraOperating system · Fedoraproject
CVE-2019-19722
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 Dovecot before 2.3.9.2, an attacker can crash a push-notification driver with a crafted email when push notifications are used, because of a NULL Pointer Dereference. The email must use a group address as either the sender or the recipient.
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 confidenceIn Dovecot before 2.3.9.2, the push notification subsystem fails to properly handle emails with group addresses (as sender or recipient), leading to a NULL pointer dereference that crashes the push-notification driver. This allows remote attackers to cause a denial of service by sending specially crafted emails.
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
= 30= 31< 2.3.9.2CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Identify installed Dovecot versionRun 'dovecot --version' or check the package version using your system's package manager (e.g., 'rpm -q dovecot' on RHEL/Fedora, 'dpkg -l dovecot-core' on Debian/Ubuntu)Affected if The installed version is lower than 2.3.9.2 (e.g., 2.3.9, 2.3.8, 2.3.7, etc.)
-
Confirm push notification plugin is loadedCheck Dovecot configuration files (typically in /etc/dovecot/conf.d/ or /etc/dovecot/dovecot.conf) for lines containing 'push_notification' or 'push-notification' in the mail_plugins or plugin settingsAffected if The push notification plugin is explicitly loaded in the Dovecot configuration
-
Check for push notification driver configurationExamine Dovecot configuration files for any push_notify_* settings or a push-notification driver configuration sectionAffected if A push notification driver is configured and enabled in the Dovecot settings
-
Verify operating system version (if Fedora)Run 'cat /etc/fedora-release' or 'rpm -q fedora-release' to check the Fedora versionAffected if The system is running Fedora 30 or Fedora 31 with an affected Dovecot version and push notifications enabled
A user is affected if they are running Dovecot version lower than 2.3.9.2 with the push notification plugin loaded and configured, particularly on Fedora 30 or 31.
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 data2.3.9.2
Upgrade Dovecot to version 2.3.9.2 or later. If immediate patching is not feasible, consider temporarily disabling push notifications as a workaround.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19722 — 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-19722 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