Stack exhaustion in all Parse functions in go/parser
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.3epss 0.8%
exploitation probability
0.8%top 44% of all CVEs
observed exploitation
nono source reports it
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Affected products
Go standard library · go/parser