cve.bz

CVE-2020-29509 Misinterpretation of Input

5.6 mediumEPSS 2.1%Fix available

Medium (5.6). EPSS 2.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/russellhaering/gosaml2 0.6.0.

On this page
The encoding/xml package in Go (all versions) does not correctly preserve the semantics of attribute 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.

Severity

CVSS 3.1

5.6 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
2.1% (unchanged from 2.1% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-115 Misinterpretation of Input
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-29509 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-29509?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-29509?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-29509 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
golang:gobefore 1.17

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xhqq-x44f-9fggGogithub.com/russellhaering/gosaml2<0.6.00.6.0
GO-2021-0060Gogithub.com/russellhaering/gosaml2<0.6.00.6.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11golang-1.15no fix listedDEBIAN-CVE-2020-29509
Ubuntu14.04:LTSgolang-1.10no fix listedUBUNTU-CVE-2020-29509
Ubuntu16.04:LTSgolang-1.6, golang-1.10no fix listedUBUNTU-CVE-2020-29509
Ubuntu18.04:LTSgolang-1.8, golang-1.9, golang-1.10no fix listedUBUNTU-CVE-2020-29509
Ubuntu20.04:LTSgolang-1.13, golang-1.14no fix listedUBUNTU-CVE-2020-29509
UbuntuPro:16.04:LTS, Pro:18.04:LTS, Pro:22.04:LTSgolang-1.13no fix listedUBUNTU-CVE-2020-29509
Alpinev3.18, v3.19, v3.20 and 4 morego1.17-r0ALPINE-CVE-2020-29509
Azure Linux2golang1.20.10-1AZL-6448
Azure Linux3golangno fix listedAZL-78900

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine.

Red Hat

Red Hat rates this Low.

Red Hat's statement

All uses of xml/encoding package in OpenShift Container Platform, OpenShift Jaeger, OpenShift Service Mesh (OSSM), OpenShift Virtualization and OpenShift Container Storage do not rely on XML stability. We have assigned CVE-2020-27846 for crewjam/saml, and CVE-2020-27847 for dexidp/dex Go modules which are known to use encoding/xml in an unsafe way.

As it is unlikely for there to be any fix for this issue in Go's encoding/xml library, and the library should not be relied upon for security-sensitive protocols such as SAML and XML-DSig, there is currently no plan to fix this in golang as shipped in Red Hat Enterprise Linux 7, 8, or Red Hat Developer Tools.

Red Hat's mitigation

While there is unlikely to be any fix for this issue Go's encoding/xml library affected users can workaround the vulnerability by using Mattermost's xml-roundtrip-validator [1].

[1] https://github.com/mattermost/xml-roundtrip-validator

ProductPackageStateAdvisory
Distributed Tracing Jaeger 1distributed-tracing/jaeger-all-in-one-rhel7Not affected
Distributed Tracing Jaeger 1distributed-tracing/jaeger-all-in-one-rhel8Not affected
Distributed Tracing Jaeger 1distributed-tracing/jaeger-collector-rhel7Not affected
Distributed Tracing Jaeger 1distributed-tracing/jaeger-collector-rhel8Not affected
Distributed Tracing Jaeger 1distributed-tracing/jaeger-rhel7-operatorNot affected
Distributed Tracing Jaeger 1distributed-tracing/jaeger-rhel8-operatorNot affected
OpenShift Service Mesh 2.0servicemeshNot affected
OpenShift Service Mesh 2.0servicemesh-operatorNot affected
OpenShift Service Mesh 2.0servicemesh-prometheusNot affected
Red Hat Enterprise Linux 7golangWill not fix
Red Hat Enterprise Linux 8go-toolset:rhel8/golangWill not fix
Red Hat OpenShift Container Platform 3.11atomic-enterprise-service-catalogNot affected
Red Hat OpenShift Container Platform 3.11atomic-openshiftNot affected
Red Hat OpenShift Container Platform 3.11atomic-openshift-cluster-autoscalerNot affected
Red Hat OpenShift Container Platform 3.11atomic-openshift-deschedulerNot affected
Red Hat OpenShift Container Platform 3.11atomic-openshift-dockerregistryNot affected
Red Hat OpenShift Container Platform 3.11atomic-openshift-metrics-serverNot affected
Red Hat OpenShift Container Platform 3.11atomic-openshift-web-consoleNot affected
Red Hat OpenShift Container Platform 3.11openshift-enterprise-autohealNot affected
Red Hat OpenShift Container Platform 3.11openshift-enterprise-cluster-capacityNot affected
31 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-29509.

References

Check your stackJSON