# CVE-2022-48521: Security feature bypass in n/a

> Remote attackers can bypass DKIM signature verification by crafting emails with fake Authentication-Results headers, causing systems to trust unsigned messages.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jul 2023
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-48521, DLA-3680-1, GHSA-3q5m-9r3g-pqfj, UBUNTU-CVE-2022-48521

## What is CVE-2022-48521?

CVE-2022-48521 is a medium-severity vulnerability in n/a, published on 11 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2022-48521?

It affects 1 product.


Products: Opendkim Opendkim.

## How do I fix CVE-2022-48521?

Apply the vendor's patch.

## Is CVE-2022-48521 being exploited?

There is no known exploitation of CVE-2022-48521 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-35766](https://insights.sbomify.com/CVE-2020-35766/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48521 and fix it if it is affected.

What it is: CVE-2022-48521 is a medium-severity vulnerability in n/a, published on 11 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48521 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48521/ (Markdown: https://insights.sbomify.com/CVE-2022-48521/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48521
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48521
- OSV: https://osv.dev/vulnerability/CVE-2022-48521

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48521/
Summaries are generated and may contain mistakes; the official description above is the record.