# CVE-2020-29510: Other in Go

> Attackers can craft XML inputs that behave inconsistently during tokenization, potentially bypassing security checks in downstream applications using the Go encoding/xml package.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2020
- **Updated:** 16 Sep 2024
- **Also known as:** BIT-golang-2020-29510, DEBIAN-CVE-2020-29510, GHSA-p6mv-vmpw-j23r, UBUNTU-CVE-2020-29510

## What is CVE-2020-29510?

CVE-2020-29510 is a critical vulnerability in Golang Go, published on 14 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The encoding/xml package in Go versions 1.15 and earlier does not correctly preserve the semantics of directives during tokenization round-trips, which allows an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications.

Weakness: CWE-115 (Misinterpretation of Input)

## Which versions are affected by CVE-2020-29510?

1 open source package ship an affected version, including golang. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.15.1 |

Products: Golang Go, Netapp Trident.

## How do I fix CVE-2020-29510?

Upgrade golang to 1.15.1 or later.

## Is CVE-2020-29510 being exploited?

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

## Other vulnerabilities in Golang Go

- [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild)
- [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8)
- [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8)
- [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8)
- [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-29510 and fix it if it is affected.

What it is: CVE-2020-29510 is a critical vulnerability in Golang Go, published on 14 Dec 2020. 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-2020-29510 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.15.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-2020-29510/ (Markdown: https://insights.sbomify.com/CVE-2020-29510/index.md)
```

## Sources

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

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