CVE-2020-29511 Other in Go
Attackers can craft XML inputs causing inconsistent processing in Go applications due to namespace prefix handling flaws in the encoding/xml package.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-29511?
CVE-2020-29511 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 (all versions) does not correctly preserve the semantics of element namespace prefixes 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
Which versions are affected by CVE-2020-29511?
1 open source package ship an affected version, including golang. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
golang Bitnami | All versions | 1.17.0 |
Products include Golang Go, Netapp Trident.
How do I fix CVE-2020-29511?
Upgrade golang to 1.17.0 or later.
Is CVE-2020-29511 being exploited?
There is no known exploitation of CVE-2020-29511 in the wild and no public exploit code.
Other vulnerabilities in Golang Go
- CVE-2020-0601 Microsoft Windows CryptoAPI Spoofing
- CVE-2026-27143 Missing bound checks can lead to memory corruption in safe Go in cmd/compile
- CVE-2024-24790 Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip
- CVE-2023-39320 Arbitrary code execution via go.mod toolchain directive in cmd/go
- CVE-2023-24540 Improper handling of JavaScript whitespace in html/template
Sources
Also known as AZL-6449, AZL-78896, BIT-golang-2020-29511, DEBIAN-CVE-2020-29511, GHSA-g7v2-7v9m-q9j4, UBUNTU-CVE-2020-29511.