CVE-2019-19680
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 · uneditedA file-extension filtering vulnerability in Proofpoint Enterprise Protection (PPS / PoD), in the unpatched versions of PPS through 8.9.22 and 8.14.2 respectively, allows attackers to bypass protection mechanisms (related to extensions, MIME types, virus detection, and journal entries for transmitted files) by sending malformed (not RFC compliant) multipart email.
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 · moderate confidenceA file-extension filtering bypass vulnerability in Proofpoint Enterprise Protection allows attackers to circumvent security controls by sending malformed multipart emails that don't comply with RFC standards. This enables malicious attachments to bypass extension filtering, MIME type validation, virus detection, and journal entry logging for transmitted files.
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<= 8.9.22<= 8.14.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Determine installed Proofpoint Enterprise Protection versionAccess the Proofpoint admin console or use the command line interface (CLI) with administrative credentials to retrieve the current software version. Typically found under System > About or using 'pp version' command via CLI.Affected if The installed version is 8.9.22 or lower in the 8.x line, or 8.14.2 or lower in the 8.14.x line.
-
Verify email filtering is activeConfirm that the Proofpoint Enterprise Protection gateway is actively processing inbound and outbound email traffic. Check the admin console for active mail processing status or review mail flow statistics.Affected if Email filtering is enabled and the system is processing mail (the vulnerability only affects filtered traffic).
-
Review mail logs for unexpected attachment processingExamine the Proofpoint mail logs, particularly journal and filtering logs, for any instances where attachments with unusual or mismatched file extensions were processed without standard filtering being applied. Look for non-standard MIME multipart structures.Affected if Logs show attachments bypassing extension checks, MIME validation, or virus scanning that should have been blocked.
-
Compare version against affected rangesIf version cannot be directly retrieved, consult Proofpoint release notes, support documentation, or contact Proofpoint support to confirm the exact version running in your environment.Affected if Version cannot be determined or确认ed as patched (8.9.23+ for 8.x line or 8.14.3+ for 8.14.x line).
You are affected if Proofpoint Enterprise Protection version is 8.9.22 or lower (8.x line) or 8.14.2 or lower (8.14.x line) AND the system is actively processing email through its filtering engine.
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 Proofpoint Enterprise Protection to version 8.9.22 or later (for 8.x) or 8.14.2 or later (for 8.14.x), as these versions contain the patch for this vulnerability. Validate that mail flow and filtering functions continue to operate correctly post-upgrade.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19680 — 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-19680 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