CVE-2022-0811: GO-2022-0354 - Code Injection in CRI-O in github.com/cri-o/cri-o

CVE-2022-0811 · Severity: low · CVSS 3.1 · Published 2024-08-21

Code Injection in CRI-O in github.com/cri-o/cri-o

Technologies: github.com/cri-o/cri-o (Go). Vendors: Go.

Quick answers

Is CVE-2022-0811 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-0811 being exploited in the wild.
How severe is CVE-2022-0811?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/cri-o/cri-o (Go) SEMVER:introduced=1.19.0,fixed=1.19.6, SEMVER:introduced=1.19.0,fixed=1.19.6,introduced=1.20.0,fixed=1.20.7,introduced=1.21.0,fixed=1.21.6,introduced=1.22.0,fixed=1.22.3,introduced=1.23.0,fixed=1.23.2.
Is there a fix for CVE-2022-0811?
Yes. github.com/cri-o/cri-o (Go): upgrade to 1.19.6, 1.23.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-0811?
Check whether you run github.com/cri-o/cri-o (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

  • github.com/cri-o/cri-o (Go): upgrade to 1.19.6, 1.23.2 or later
    go get github.com/cri-o/cri-o@v1.23.2

Affected products

  • github.com/cri-o/cri-o (Go) SEMVER:introduced=1.19.0,fixed=1.19.6, SEMVER:introduced=1.19.0,fixed=1.19.6,introduced=1.20.0,fixed=1.20.7,introduced=1.21.0,fixed=1.21.6,introduced=1.22.0,fixed=1.22.3,introduced=1.23.0,fixed=1.23.2

Identifiers

  • CVE-2022-0811
  • GHSA-6x2m-w449-qwx7
  • GO-2022-0354

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