# CVE-2024-24784: Comments in display names are incorrectly handled in net/mail

> The Go net/mail library mishandles comments in display names, potentially causing inconsistent trust decisions across different parsers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 5 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** AZL-37466, AZL-37519, AZL-79048, AZL-98655, BELL-CVE-2024-24784, BIT-golang-2024-24784, DEBIAN-CVE-2024-24784, GHSA-fgq5-q76c-gx78, GO-2024-2609, MINI-9wp8-cj7p-m32h, MINI-gfw9-p2q5-vxmq, MINI-r8v4-v3vw-mm6c, OESA-2024-1432, UBUNTU-CVE-2024-24784

## What is CVE-2024-24784?

CVE-2024-24784 is a high-severity vulnerability in Go standard library net/mail, published on 5 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

## Which versions are affected by CVE-2024-24784?

2 open source packages ship an affected version, including golang and stdlib.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.21.8, 1.22.1 |
| `stdlib` | Go | All versions | 1.21.8, 1.22.1 |

## How do I fix CVE-2024-24784?

Upgrade golang to a fixed version for your release line: 1.21.8 or 1.22.1.

## Is CVE-2024-24784 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24784 and fix it if it is affected.

What it is: CVE-2024-24784 is a high-severity vulnerability in Go standard library net/mail, published on 5 Mar 2024. 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-2024-24784 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.21.8, 1.22.1
- stdlib (Go): affected all versions; fixed in 1.21.8, 1.22.1

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-2024-24784/ (Markdown: https://insights.sbomify.com/CVE-2024-24784/index.md)
```

## Sources

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

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