Bug 1180025 - (CVE-2020-29510) VUL-0: CVE-2020-29510: go1.14,go1.15: 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
(CVE-2020-29510)
VUL-0: CVE-2020-29510: go1.14,go1.15: The encoding/xml package in Go versions...
Status: RESOLVED WONTFIX
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Major
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/273374/
CVSSv3.1:SUSE:CVE-2020-29510:7.5:(AV:...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-12-15 06:50 UTC by Marcus Meissner
Modified: 2021-01-20 09:52 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2020-12-15 06:50:19 UTC
CVE-2020-29510

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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29510
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29510
https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md
Comment 1 Wolfgang Frisch 2021-01-20 09:52:51 UTC
Upstream golang declared this bug as WONTFIX [1].

>If you are using one of the affected SAML libraries, the solution is to
>update to the latest version of that library. Because we didn't make any
>changes in Go 1.14 or Go 1.15, the update should work regardless of
>which Go version you are using.

[1] https://github.com/golang/go/issues/43211