CVE-2022-2989: Podman's incorrect handling of the supplementary groups may lead to data disclosure, modification

CVE-2022-2989 · Severity: low · CVSS 3.1 · Published 2022-09-14

Podman's incorrect handling of the supplementary groups may lead to data disclosure, modification

Technologies: github.com/containers/podman/v3 (Go), github.com/containers/podman/v4 (Go). Vendors: Go.

Quick answers

Is CVE-2022-2989 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-2989 being exploited in the wild.
How severe is CVE-2022-2989?
Low severity, with a CVSS score of 3.1, published 14 September 2022.
Which products and versions are affected?
github.com/containers/podman/v3 (Go) SEMVER:introduced=0,fixed=3.0.1; github.com/containers/podman/v4 (Go) SEMVER:introduced=0,fixed=4.2.0.
Is there a fix for CVE-2022-2989?
Yes. github.com/containers/podman/v3 (Go): upgrade to 3.0.1 or later; github.com/containers/podman/v4 (Go): upgrade to 4.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-2989?
Check whether you run github.com/containers/podman/v3 (Go) or github.com/containers/podman/v4 (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/containers/podman/v3 (Go): upgrade to 3.0.1 or later
    go get github.com/containers/podman/v3@v3.0.1
  • github.com/containers/podman/v4 (Go): upgrade to 4.2.0 or later
    go get github.com/containers/podman/v4@v4.2.0

Affected products

  • github.com/containers/podman/v3 (Go) SEMVER:introduced=0,fixed=3.0.1
  • github.com/containers/podman/v4 (Go) SEMVER:introduced=0,fixed=4.2.0

Identifiers

  • CVE-2022-2989
  • GHSA-4wjj-jwc9-2x96

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