CVE-2022-1708: GO-2022-0480 - Node DOS by way of memory exhaustion through ExecSync request in CRI-O in github.com/cri-o/cri-o

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

Node DOS by way of memory exhaustion through ExecSync request 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-1708 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-1708 being exploited in the wild.
How severe is CVE-2022-1708?
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=0,fixed=1.22.5,introduced=1.23.0,fixed=1.23.3,introduced=1.24.0,fixed=1.24.1, SEMVER:introduced=1.24.0,fixed=1.24.1.
Is there a fix for CVE-2022-1708?
Yes. github.com/cri-o/cri-o (Go): upgrade to 1.24.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-1708?
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.24.1 or later
    go get github.com/cri-o/cri-o@v1.24.1

Affected products

  • github.com/cri-o/cri-o (Go) SEMVER:introduced=0,fixed=1.22.5,introduced=1.23.0,fixed=1.23.3,introduced=1.24.0,fixed=1.24.1, SEMVER:introduced=1.24.0,fixed=1.24.1

Identifiers

  • CVE-2022-1708
  • GHSA-fcm2-6c3h-pg6j
  • GO-2022-0480

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