CVE-2022-4123

• • cpe:2.3:a:podman_project:podman:4.1.0:-:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.1.0:rc1:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.1.0:rc2:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.1.1:*:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.2.0:-:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.2.0:rc1:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.2.0:rc2:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.2.0:rc3:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.2.1:*:*:*:*:*:*:*
• • cpe:2.3:a:podman_project:podman:4.3.0:-:*:*:*:*:*:*
• • cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
• • cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
• • cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*

This CVE has no assigned vulnerable Common Criteria or FIPS 140 certificates.