CVE-2019-11254: GO-2020-0036 - Excessive resource consumption in YAML parsing in gopkg.in/yaml.v2

CVE-2019-11254 · Severity: low · CVSS 3.1 · Published 2021-04-14

Excessive resource consumption in YAML parsing in gopkg.in/yaml.v2

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

Quick answers

Is CVE-2019-11254 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-11254 being exploited in the wild.
How severe is CVE-2019-11254?
Low severity, with a CVSS score of 3.1, published 14 April 2021.
Which products and versions are affected?
github.com/go-yaml/yaml (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.1.0; gopkg.in/yaml.v2 (Go) SEMVER:introduced=0,fixed=2.2.8.
Is there a fix for CVE-2019-11254?
Yes. gopkg.in/yaml.v2 (Go): upgrade to 2.2.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-11254?
Check whether you run github.com/go-yaml/yaml (Go) or 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.8 or later
    go get gopkg.in/yaml.v2@v2.2.8

Affected products

  • github.com/go-yaml/yaml (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.1.0
  • gopkg.in/yaml.v2 (Go) SEMVER:introduced=0,fixed=2.2.8

Identifiers

  • CVE-2019-11254
  • GHSA-wxc4-f4m6-wwqv
  • GO-2020-0036

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