CVE-2022-48521 json
An issue was discovered in OpenDKIM through 2.10.3, and 2.11.x through 2.11.0-Beta2.
published 2023-07-11 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-51217
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
An issue was discovered in OpenDKIM through 2.10.3, and 2.11.x through 2.11.0-Beta2. It fails to keep track of ordinal numbers when removing fake Authentication-Results header fields, which allows a remote attacker to craft an e-mail message with a fake sender address such that programs that rely on Authentication-Results from OpenDKIM will treat the message as having a valid DKIM signature when in fact it has none.
Patch / fix
- opendkim Debian 12 2.11.0~beta2-8+deb12u1
- opendkim Debian 14, Debian 13 2.11.0~beta2-9
debian advisories DEBIAN-CVE-2022-48521
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-2022-48521 updated
opendkim: Authentication-Results fields are not removed correctly
-
Red Hat All currently supported Red Hat productsnot 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
0.74% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
References
-
github.com
/trusteddomainproject/OpenDKIM/issues/148
issue-tracking
-
lists.debian.org
/debian-lts-announce/2023/12/msg00002.html
mailing-list
Sources
- CVE List CVE-2022-48521
- NVD CVE-2022-48521
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.