CVE-2022-2989: High severity centos podman vulnerability

Published Aug 22, 2022
·
Updated

An incorrect handling of the supplementary groups in the Podman container engine might lead to the sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

Affected Software

12 affected componentsFixes available
redhat/buildah<1:1.27.0-2.el9
1:1.27.0-2.el9
redhat/podman<2:4.2.0-7.el9_1
2:4.2.0-7.el9_1
ubuntu/libpod<3.4.4+
3.4.4+
debian/libpod
3.0.1+dfsg1-3+deb11u54.3.1+ds1-84.9.2+ds1-2
Podman Project Podman
redhat OpenShift Container Platform=3.11
redhat OpenShift Container Platform=4.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
go/github.com/containers/podman/v3<3.0.1
3.0.1
go/github.com/containers/podman/v4<4.2.0
4.2.0

Event History

Aug 22, 2022
CVE Published
12:00 AM
Aug 25, 2022
Data Sourced
via Red Hat·01:30 PM
DescriptionSeverityAffected Software
Sep 13, 2022
CVE Published
via MITRE·01:41 PM
Data Sourced
via MITRE·01:41 PM
DescriptionWeakness
Sep 14, 2022
Advisory Published
via GitHub·12:00 AM
Data Sourced
via GitHub·12:00 AM
DescriptionSeverityWeaknessAffected Software
Jan 12, 2024
Data Sourced
via Launchpad·12:08 AM
Description

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2022-2989?

CVE-2022-2989 is a vulnerability in the Podman container engine that involves incorrect handling of supplementary groups, potentially leading to sensitive information disclosure or data modification.

2

What is the severity of CVE-2022-2989?

CVE-2022-2989 has a severity rating of 7.1 (High).

3

Which software is affected by CVE-2022-2989?

The software affected by CVE-2022-2989 includes buildah (version 1.27.0-2.el9), podman (version 4.2.0-7.el9_1), libpod (version 3.4.4+), and github.com/containers/podman/v3 (version 3.0.1), among others.

4

How can CVE-2022-2989 be mitigated?

To mitigate CVE-2022-2989, it is recommended to apply the appropriate software updates provided by the respective vendors.

5

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

More information about CVE-2022-2989 can be found at the following references: <ul><li><a href="https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/" target="_blank">https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/</a></li><li><a href="https://github.com/containers/podman/commit/5c7f28336171f0a5137edd274e45608120d31289" target="_blank">https://github.com/containers/podman/commit/5c7f28336171f0a5137edd274e45608120d31289</a></li><li><a href="https://github.com/containers/podman/pull/15696" target="_blank">https://github.com/containers/podman/pull/15696</a></li></ul>

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