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

Published Aug 29, 2022
·
Updated

A flaw was found in go-yaml. This issue causes the consumption of excessive amounts of CPU or memory when attempting to parse a large or maliciously crafted YAML document.

Other sources

Excessive resource consumption in gopkg.in/yaml.v2

Microsoft

Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.

Ubuntu

Affected Software

15 affected componentsFixes available
redhat/etcd<0:3.3.23-12.el8
0:3.3.23-12.el8
redhat/etcd<0:3.4.14-3.el9
0:3.4.14-3.el9
ubuntu/golang-yaml.v2<2.2.4
2.2.4
ubuntu/golang-yaml.v2<0.0+
0.0+
ubuntu/golang-yaml.v2<2.2.2-1ubuntu0.1
2.2.2-1ubuntu0.1
ubuntu/golang-yaml.v2<0.0+
0.0+
debian/golang-yaml.v2<=2.2.2-1
2.2.2-1+deb10u12.4.0-12.4.0-4
Yaml Project Yaml Go<2.2.4
go/gopkg.in/yaml.v2<2.2.4
2.2.4
IBM Edge Application Manager<=4.5
redhat/gopkg.in/yaml.v2<2.2.4
2.2.4
Microsoft cbl2 application-gateway-kubernetes-ingress 1.4.0-25
Microsoft azl3 packer 1.9.5-1
Microsoft azl3 packer 1.9.5-9
Microsoft cm1 etcd 3.5.0-9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/etcd to a version that resolves this vulnerability.

    Fixed in 0:3.3.23-12.el8
  2. Upgrade

    Upgrade redhat/etcd to a version that resolves this vulnerability.

    Fixed in 0:3.4.14-3.el9
  3. Upgrade

    Upgrade ubuntu/golang-yaml.v2 to a version that resolves this vulnerability.

    Fixed in 2.2.4
  4. Upgrade

    Upgrade ubuntu/golang-yaml.v2 to a version that resolves this vulnerability.

    Fixed in 0.0+
  5. Upgrade

    Upgrade ubuntu/golang-yaml.v2 to a version that resolves this vulnerability.

    Fixed in 2.2.2-1ubuntu0.1
  6. Upgrade

    Upgrade debian/golang-yaml.v2 to a version that resolves this vulnerability.

    Fixed in 2.2.2-1+deb10u1Fixed in 2.4.0-1Fixed in 2.4.0-4
  7. Upgrade

    Upgrade go/gopkg.in/yaml.v2 to a version that resolves this vulnerability.

    Fixed in 2.2.4
  8. Upgrade

    Upgrade redhat/gopkg.in/yaml.v2 to a version that resolves this vulnerability.

    Fixed in 2.2.4
  9. Upgrade

    Upgrade gopkg.in/yaml.v2 (go-yaml) to a version that resolves this vulnerability.

    Fixed in v2.2.4
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch GO-2022-0956

Event History

Aug 29, 2022
CVE Published
12:00 AM
Dec 27, 2022
CVE Published
via MITRE·09:17 PM
Data Sourced
via MITRE·09:17 PM
DescriptionWeakness
Dec 28, 2022
Advisory Published
via GitHub·12:30 AM
Jan 23, 2023
Data Sourced
via Red Hat·04:54 AM
DescriptionSeverityAffected Software
Jan 12, 2024
Data Sourced
via Launchpad·12:08 AM
Description
Aug 20, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-3064?

CVE-2022-3064 is a vulnerability that can cause the consumption of excessive amounts of CPU or memory when attempting to parse a large or maliciously crafted YAML document.

2

What is the severity of CVE-2022-3064?

The severity of CVE-2022-3064 is high, with a CVSS score of 7.5.

3

Which software is affected by CVE-2022-3064?

The affected software includes go-yaml version up to 2.2.4, golang-yaml.v2 up to version 2.2.4 on Ubuntu, golang-yaml.v2 version up to 2.2.2-1ubuntu0.1 on Ubuntu Focal, golang-yaml.v2 version up to 0.0+ on Ubuntu Xenial, golang-yaml.v2 version up to 0.0+ on Ubuntu Bionic, golang-yaml.v2 version up to 2.2.2-1 on Debian, gopkg.in/yaml.v2 version up to 2.2.4 on Red Hat, etcd version up to 3.3.23-12.el8 on Red Hat, etcd version up to 3.4.14-3.el9 on Red Hat, and gopkg.in/yaml.v2 version up to 2.2.4 on Go.

4

How can I fix CVE-2022-3064 in go-yaml version up to 2.2.4?

To fix CVE-2022-3064 in go-yaml, you should update to version 2.2.4 or later.

5

Where can I find more information about CVE-2022-3064?

You can find more information about CVE-2022-3064 at the following references: [Link 1](https://github.com/go-yaml/yaml/commit/f221b8435cfb71e54062f6c6e99e9ade30b124d5), [Link 2](https://github.com/go-yaml/yaml/releases/tag/v2.2.4), [Link 3](https://lists.debian.org/debian-lts-announce/2023/07/msg00001.html).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203