tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.
Metrics
Affected Vendors & Products
References
History
Thu, 30 Oct 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Thu, 30 Oct 2025 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Golang
Golang archive |
|
| Vendors & Products |
Golang
Golang archive |
Wed, 29 Oct 2025 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations. | |
| Title | Unbounded allocation when parsing GNU sparse map in archive/tar | |
| References |
|
Status: PUBLISHED
Assigner: Go
Published: 2025-10-29T22:10:14.376Z
Updated: 2025-10-30T14:23:16.066Z
Reserved: 2025-08-27T14:50:58.691Z
Link: CVE-2025-58183
Updated: 2025-10-30T14:23:04.000Z
Status : Awaiting Analysis
Published: 2025-10-29T23:16:19.357
Modified: 2025-10-30T15:15:39.793
Link: CVE-2025-58183
No data.