Allocation of Resources Without Limits or Throttling Affecting skopeo package, versions <1.20.0-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMUSLATEST-SKOPEO-12301637
  • published31 Aug 2025
  • disclosed28 Aug 2025

Introduced: 28 Aug 2025

NewCVE-2025-58058  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Minimus:latest skopeo to version 1.20.0-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream skopeo package and not the skopeo package as distributed by Minimus. See How to fix? for Minimus:latest relevant fixed versions and status.

xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.

CVSS Base Scores

version 3.1