Skip to main content
No exploitation reportedFix available

CVE-2020-12272

No exploitation reported by the sources we read.

  • Published2020-04-27
  • WeaknessCWE-290

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2020-04-2714:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-12272?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-12272?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Fedoraproject fedora
BranchAffectedFixed in
33.x= 33no fix published
34.x= 34no fix published
Trusteddomain opendmarc
BranchAffectedFixed in
1.x≥ 1.0.0, ≤ 1.3.2no fix published
1.4= 1.4.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • opendmarcUbuntu:Pro:16.04:LTSall versions · fixed in 1.3.1+dfsg-3ubuntu0.1~esm1
  • opendmarcUbuntu:20.04:LTSall versions · fixed in 1.3.2-7ubuntu0.1
  • opendmarcUbuntu:18.04:LTSall versions · fixed in 1.3.2-3ubuntu0.2
  • opendmarcMageia:8all versions · fixed in 1.4.1.1-1.mga8
  • opendmarcDebian:14all versions · fixed in 1.4.0~beta1+dfsg-4
  • opendmarcDebian:13all versions · fixed in 1.4.0~beta1+dfsg-4
  • opendmarcDebian:12all versions · fixed in 1.4.0~beta1+dfsg-4
  • opendmarcDebian:10all versions · fixed in 1.3.2-6+deb10u3

Vendor advisories

  • CVE-2020-12272 Red Hat Product Security

    opendmarc: Two vulnerabilities in openDMARC 1.3.2

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.15.3read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-290read 2026-10-23
  • FIRST EPSSEPSS score2.2 %2026-11-03
  • OSVaffected packages—

Identifiers

  • EUVD-2020-4585same flawENISA EUVD · LicenseRef-ENISA-legal-notice
  • DLA-3546-1advisory covering several CVEsDebian · LicenseRef-unstated
  • MGASA-2021-0462advisory covering several CVEsMageia · LicenseRef-unstated
  • USN-6356-1advisory covering several CVEsUbuntu

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Published
2020-04-27
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2020-12272?

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.

Is CVE-2020-12272 actively exploited?

Active exploitation of CVE-2020-12272 has not been confirmed. Its EPSS score was 2.2% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-12272?

CVE-2020-12272 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.

Running opendmarc? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record