RHSA-2022:8431: Low: podman security, bug fix, and enhancement update

Published Nov 15, 2022
·
Updated

The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.Security Fix(es): podman: possible information disclosure and modification (CVE-2022-2989) buildah: possible information disclosure and modification (CVE-2022-2990) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Bug Fix(es): (podman image trust) does not support the new trust type "sigstoreSigned " (BZ#2120436) dnf-update broken for podman/catatonit (BZ#2123319) podman creates lock file in /etc/cni/net.d/cni.lock instead of /run/lock/ (BZ#2123905) podman kill may deadlock [RHEL 9.1] (BZ#2124716) containers config.json gets empty after sudden power loss (BZ#2136278) PANIC podman API service endpoint handler panic (BZ#2136287) Enhancement(s): Podman volume plugin timeout should be configurable [rhel-9.1.0 Z] (BZ#2124676) [RFE]Podman support to perform custom actions on unhealthy containers (BZ#2136281)

Affected Software

49 affected componentsFixes available
redhat/podman<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-catatonit<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-catatonit-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-debugsource<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-docker<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-gvproxy<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-gvproxy-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-plugins<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-plugins-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-remote<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-remote-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-tests<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-catatonit<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-catatonit-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-debugsource<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-gvproxy<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-gvproxy-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-plugins<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-plugins-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-remote<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-remote-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-tests<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-catatonit<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-catatonit-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-debugsource<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-gvproxy<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-gvproxy-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-plugins<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-plugins-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-remote<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-remote-debuginfo<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman-tests<4.2.0-7.el9_1
4.2.0-7.el9_1
redhat/podman<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-catatonit<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-catatonit-debuginfo<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-debuginfo<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-debugsource<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-gvproxy<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-gvproxy-debuginfo<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-plugins<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-plugins-debuginfo<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-remote<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-remote-debuginfo<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa
redhat/podman-tests<4.2.0-7.el9_1.aa
4.2.0-7.el9_1.aa

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 4.2.0-7.el9_1
  2. Upgrade

    Upgrade redhat/podman-catatonit to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  3. Upgrade

    Upgrade redhat/podman-catatonit-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  4. Upgrade

    Upgrade redhat/podman-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  5. Upgrade

    Upgrade redhat/podman-debugsource to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  6. Upgrade

    Upgrade redhat/podman-docker to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  7. Upgrade

    Upgrade redhat/podman-gvproxy to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  8. Upgrade

    Upgrade redhat/podman-gvproxy-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  9. Upgrade

    Upgrade redhat/podman-plugins to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  10. Upgrade

    Upgrade redhat/podman-plugins-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  11. Upgrade

    Upgrade redhat/podman-remote to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  12. Upgrade

    Upgrade redhat/podman-remote-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  13. Upgrade

    Upgrade redhat/podman-tests to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  14. Upgrade

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

    Fixed in 4.2.0-7.el9_1.aa
  15. Upgrade

    Upgrade redhat/podman-catatonit to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  16. Upgrade

    Upgrade redhat/podman-catatonit-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  17. Upgrade

    Upgrade redhat/podman-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  18. Upgrade

    Upgrade redhat/podman-debugsource to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  19. Upgrade

    Upgrade redhat/podman-gvproxy to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  20. Upgrade

    Upgrade redhat/podman-gvproxy-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  21. Upgrade

    Upgrade redhat/podman-plugins to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  22. Upgrade

    Upgrade redhat/podman-plugins-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  23. Upgrade

    Upgrade redhat/podman-remote to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  24. Upgrade

    Upgrade redhat/podman-remote-debuginfo to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  25. Upgrade

    Upgrade redhat/podman-tests to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1.aa
  26. Upgrade

    Upgrade podman to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  27. Upgrade

    Upgrade podman-catatonit to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  28. Upgrade

    Upgrade podman-docker to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  29. Upgrade

    Upgrade podman-gvproxy to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  30. Upgrade

    Upgrade podman-plugins to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  31. Upgrade

    Upgrade podman-remote to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1
  32. Upgrade

    Upgrade podman-tests to a version that resolves this vulnerability.

    Fixed in 4.2.0-7.el9_1

Event History

Aug 9, 2026
Advisory Published
via Red Hat·12:07 AM
Data Sourced
via Red Hat·12:07 AM
RemedyDescriptionAffected 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 the severity of RHSA-2022:8431?

The severity of RHSA-2022:8431 is classified as critical due to potential information disclosure and modification risks.

2

How do I fix RHSA-2022:8431?

To fix RHSA-2022:8431, you should upgrade to the podman package version 4.2.0-7.el9_1 or later.

3

What vulnerabilities are addressed in RHSA-2022:8431?

RHSA-2022:8431 addresses vulnerabilities in the podman tool related to possible information disclosure and modification.

4

Which versions of podman are affected by RHSA-2022:8431?

Versions of podman prior to 4.2.0-7.el9_1 are affected by RHSA-2022:8431.

5

Is RHSA-2022:8431 applicable to all distributions?

RHSA-2022:8431 specifically applies to the Red Hat distribution of podman.

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