Unbounded memory consumption when reading headers in archive/tar
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 1.7%
exploitation probability
1.7%top 25% of all CVEs
observed exploitation
nono source reports it
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.
Affected products
Go standard library · archive/tar