In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign...
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| golang.org/x/net | golang.org/x/net/html |
< 0.62.0 |
0.62.0 |
| Go | golang.org/x/net |
< 0.62.0 |
0.62.0 |
Original description The description as published by the source.
In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found. However, that integration point may itself be a descendant of an element that was foster-parented into a foreign namespace (such as or fostered under ), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the rendered output. Continue walking the full ancestor chain and verify that every transition from a non-empty namespace occurs at an HTML integration point before emitting literal text.
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory
References
- web go.dev
- web go.dev
- web groups.google.com
- web pkg.go.dev
- web nvd.nist.gov
- web github.com