Vulnerability in Golang Go
CVE-2020-29511
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.020 (79.6th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 80th percentile — 79.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.019 · newest: 0.020 · change: +0.000
Affected products
- Golang Go — versions All versions
- NetApp Trident
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-e… (Third Party Advisory)
- security.netapp.com/advisory/ntap-20210129-0006/ (Third Party Advisory)
Frequently asked questions
- What is CVE-2020-29511?
- CVE-2020-29511 is a critical-severity vulnerability in Golang Go, classified under CWE-115. CVSS score: 9.8/10. Published 2020-12-14.
- How severe is CVE-2020-29511?
- Critical severity. CVSS v3 base score is 9.8 out of 10.
- Is CVE-2020-29511 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.