Name | CVE-2020-29511 |
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. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
golang-1.15 (PTS) | bullseye | 1.15.15-1~deb11u4 | vulnerable |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
golang-1.11 | source | (unstable) | (unfixed) | unimportant | | |
golang-1.15 | source | (unstable) | (unfixed) | unimportant | | |
golang-1.7 | source | (unstable) | (unfixed) | unimportant | | |
golang-1.8 | source | (unstable) | (unfixed) | unimportant | | |
Notes
[stretch] - golang-1.8 <ignored> (deemed unfixable by upstream who shifts responsibility to saml packages we don't ship)
[stretch] - golang-1.7 <ignored> (deemed unfixable by upstream who shifts responsibility to saml packages we don't ship)
https://github.com/golang/go/issues/43168
https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/
Upstream considers this WONTFIX and requires validation/updates in potentially affected SAML libs