Skip to content
Fencer Vulns
critical 9.8

CVE-2019-20790 json

OpenDMARC through 1.3.2 and 1.4.x, when used with pypolicyd-spf 2.0.2, allows attacks that bypass SPF and DMARC authentication in situation…

published 2020-04-27 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-11327

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

OpenDMARC through 1.3.2 and 1.4.x, when used with pypolicyd-spf 2.0.2, allows attacks that bypass SPF and DMARC authentication in situations where the HELO field is inconsistent with the MAIL FROM field.

Patch / fix

  • opendmarc Debian 14, Debian 13, Debian 12 1.4.0~beta1+dfsg-4

debian advisories DEBIAN-CVE-2019-20790

  • opendmarc Arch Linux 1.4.1.1-1

arch linux advisories AVG-1375

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-20790 updated

opendmarc: Two vulnerabilities in openDMARC 1.3.2

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.45% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • sourceforge.net https://sourceforge.net/p/opendmarc/tickets/235/ referenced PoC, tagged "exploit" by a source, unverified
  • bugs.launchpad.net https://bugs.launchpad.net/pypolicyd-spf/+bug/1838816 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-290 Authentication Bypass by Spoofing

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.