dbcve.org
Enterprise Linux ServerOperating system · Redhat

CVE-2022-2738

HIGH · 7.5 CVSS v3.1 Published 2022-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The version of podman as released for Red Hat Enterprise Linux 7 Extras via RHSA-2022:2190 advisory included an incorrect version of podman missing the fix for CVE-2020-8945, which was previously fixed via RHSA-2020:2117. This issue could possibly be used to crash or cause potential code execution in Go applications that use the Go GPGME wrapper library, under certain conditions, during GPG signature verification.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This CVE describes a regression in podman for RHEL 7 Extras where RHSA-2022:2190 distributed an incorrect version missing the previously-fixed CVE-2020-8945. The vulnerability exists in the Go GPGME wrapper library used by Go applications, allowing potential code execution or denial of service during GPG signature verification under certain conditions.

MitigationUpdate podman to the corrected version that includes the CVE-2020-8945 fix (the proper version via RHSA-2022:2190 that contains the RHSA-2020:2117 patch), or upgrade to a supported podman version beyond the affected RHEL 7 Extras package.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0
PodmanApplication
Affected:= 1.6.4-32.el7_9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify RHEL 7 distribution variant and version
    Run 'cat /etc/redhat-release' to confirm the system is Red Hat Enterprise Linux Server or Workstation version 7.0
    Affected if The system is RHEL Server 7.0 or RHEL Workstation 7.0
  2. Check if Podman is installed
    Run 'rpm -q podman' to see if the podman package is present on the system
    Affected if Podman is installed
  3. Determine installed Podman version
    Run 'rpm -q --qf '%{VERSION}-%{RELEASE}' podman' to get the exact version number
    Affected if The version is exactly 1.6.4-32.el7_9
  4. Verify GPG signature verification is in use
    Inspect podman usage for image pull operations with signature verification by checking for 'podman pull' commands or /etc/containers/registries.conf with signature verification enabled
    Affected if GPG signature verification is configured or used with podman images

A user is affected if they are on RHEL 7.0 Server or Workstation, have podman version 1.6.4-32.el7_9 installed, and use GPG signature verification for container images.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update podman to the corrected version that includes the CVE-2020-8945 fix (the proper version via RHSA-2022:2190 that contains the RHSA-2020:2117 patch), or upgrade to a supported podman version beyond the affected RHEL 7 Extras package.

Recommended fix Moderate confidence

Latest podman version available via RHEL 7 Extras repository (refer to RHSA-2022:2190 and subsequent updates)

  1. Identify the current podman version: rpm -q podman
  2. Check for available errata updates: yum update --listonly or yum check-update
  3. Update podman to the latest available version in RHEL 7 Extras: yum update podman
  4. Verify the new version includes the fix for CVE-2020-8945 by checking the advisory RHSA-2022:2190 (or subsequent errata)
Caveat Minimal risk; this is a security patch update within the same major version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2738 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data