CVE-2022-3064: GO-2022-0956 - Excessive resource consumption in gopkg.in/yaml.v2

CVE-2022-3064 · Severity: low · CVSS 3.1 · Published 2022-08-29

Excessive resource consumption in gopkg.in/yaml.v2

Technologies: gopkg.in/yaml.v2 (Go). Vendors: Go.

Quick answers

Is CVE-2022-3064 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-3064 being exploited in the wild.
How severe is CVE-2022-3064?
Low severity, with a CVSS score of 3.1, published 29 August 2022.
Which products and versions are affected?
gopkg.in/yaml.v2 (Go) SEMVER:introduced=0,fixed=2.2.4.
Is there a fix for CVE-2022-3064?
Yes. gopkg.in/yaml.v2 (Go): upgrade to 2.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-3064?
Check whether you run gopkg.in/yaml.v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • gopkg.in/yaml.v2 (Go): upgrade to 2.2.4 or later
    go get gopkg.in/yaml.v2@v2.2.4

Affected products

  • gopkg.in/yaml.v2 (Go) SEMVER:introduced=0,fixed=2.2.4

Identifiers

  • CVE-2022-3064
  • GHSA-6q6q-88xp-6f2r
  • GO-2022-0956

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.