CyberSecBulletin
CVE-2022-2879NVD status: Modified

archive/tar: Allocation of Resources Without Limits or Throttling

Published Updated By the CyberSecBulletin desk

CVE-2022-2879 is a high-severity allocation of resources without limits or throttling vulnerability in archive/tar from Go standard library, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 1.18.7, 1.19.2 as the first without the flaw, so updating archive/tar to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.01% chance of exploitation within 30 days, higher than 81% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update archive/tar to 1.18.7 or 1.19.2, whichever matches your release line, or a later version.
  2. Update Go to 1.18.7 or 1.19.2, whichever matches your release line, or a later version.
  3. Read the advisory on pkg.go.dev for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Go standard libraryarchive/tarbefore 1.18.7; 1.19.0-0 up to, but not including, 1.19.21.18.7, 1.19.2
GoGobefore 1.18.7; 1.19.0 up to, but not including, 1.19.21.18.7, 1.19.2

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How developers prevent this class of flaw

  • Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
  • Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Third-party and government advisories

Recent Allocation of Resources Without Limits or Throttling vulnerabilities

Spotted an error? Tell us.