Bug 1828430 (CVE-2019-20790, CVE-2020-12272) - CVE-2020-12272 CVE-2019-20790 opendmarc: Two vulnerabilities in openDMARC 1.3.2
Summary: CVE-2020-12272 CVE-2019-20790 opendmarc: Two vulnerabilities in openDMARC 1.3.2
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-20790, CVE-2020-12272
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1828431 1828432
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-27 17:17 UTC by Pedro Sampaio
Modified: 2020-04-27 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-27 22:31:46 UTC


Attachments (Terms of Use)

Description Pedro Sampaio 2020-04-27 17:17:50 UTC
Two vulnerabilities in openDMARC 1.3.2:

OpenDMARC through 1.3.2 and 1.4.x allows attacks that inject authentication results to provide false information about the domain that originated an e-mail message. This is caused by incorrect parsing and interpretation of SPF/DKIM authentication results, as demonstrated by the example.net(.example.com substring.

https://sourceforge.net/p/opendmarc/tickets/237/
https://www.usenix.org/system/files/sec20fall_chen-jianjun_prepub_0.pdf

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.

https://bugs.launchpad.net/pypolicyd-spf/+bug/1838816
https://sourceforge.net/p/opendmarc/tickets/235/
https://www.usenix.org/system/files/sec20fall_chen-jianjun_prepub_0.pdf

Comment 1 Pedro Sampaio 2020-04-27 17:18:20 UTC
Created opendmarc tracking bugs for this issue:

Affects: epel-all [bug 1828432]
Affects: fedora-all [bug 1828431]

Comment 2 Product Security DevOps Team 2020-04-27 22:31:46 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.