Syft versions before v1.52.0 was sizing internal buffers, scan window sizes, and loop boundaries using header fields from scanned file artifacts. This could result in a small file triggering a large allocation leading to resource exhaustion rather than a recoverable panic.
This resource exhaustion could result in users of Syft scanning content that could cause Syft to crash instead of recovering from the error. By not exiting gracefully, Syft will not write output documents or clean up temporary files.
The patch has been released in v1.52.0
Syft now fails gracefully when encountering file artifacts with headers fields that would cause a large allocation.
There are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files.
References Pull requests related to this fix: