dbcve.org
Enterprise Linux ServerOperating system · Redhat

CVE-2022-2739

MEDIUM · 5.3 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 →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

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-14370, which was previously fixed via RHSA-2020:5056. This issue could possibly allow an attacker to gain access to sensitive information stored in environment variables.

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 is a regression vulnerability where the podman package shipped in RHEL 7 Extras via RHSA-2022:2190 did not include the fix for CVE-2020-14370, which had been previously addressed in RHSA-2020:5056. The missing fix allows attackers to access sensitive information stored in environment variables, likely through container escape or improper isolation of environment variables between host and container contexts.

MitigationApply the corrected podman version from the appropriate RHSA advisory that includes the CVE-2020-14370 fix, or upgrade to a supported RHEL version as RHEL 7 Extras reaches end of life.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify the operating system version
    Run 'cat /etc/redhat-release' to confirm the system is RHEL 7.x
    Affected if The OS is not RHEL 7 (the regression only applies to RHEL 7 systems)
  2. Check if podman is installed
    Run 'rpm -q podman' to determine if the podman package is present
    Affected if Podman is not installed - the CVE only affects systems with podman present
  3. Determine the installed podman version
    Run 'rpm -q podman' to get the exact version string (for example: podman-1.6.4-32.el7_9.x86_64)
    Affected if The version is exactly 1.6.4-32.el7_9, which is the affected version that lacks the CVE-2020-14370 fix
  4. Verify the advisory source of the package
    Run 'rpm -q --changelog podman | head -20' to check which RHSA the installed package was delivered through
    Affected if The package originated from RHSA-2022:2190, which is the advisory that introduced the regression by omitting the CVE-2020-14370 fix

A system is affected if it runs RHEL 7 with podman version 1.6.4-32.el7_9 installed via RHSA-2022:2190, as this version lacks the environment variable isolation fix from the original CVE-2020-14370.

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

Apply the corrected podman version from the appropriate RHSA advisory that includes the CVE-2020-14370 fix, or upgrade to a supported RHEL version as RHEL 7 Extras reaches end of life.

Recommended fix High confidence

Migrate to RHEL 8 or RHEL 9 (or equivalent supported distribution)

  1. RHEL 7 reached end of life in June 2024 and no longer receives official security updates from Red Hat.
  2. If systems must remain on RHEL 7, monitor Red Hat's errata archive (access.redhat.com/errata) for any potential backported patches for this specific CVE.
  3. Consider migrating to a supported RHEL version (RHEL 8 or RHEL 9) which include properly fixed podman versions.
  4. If using CentOS or Rocky Linux equivalents, check their repositories for updated podman packages that include the CVE-2020-14370 fix.
Caveat RHEL 7 EOL means no further security updates; migration to RHEL 8/9 required for continued support

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

Fix this in Enterprise Linux Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2739 — 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-2739 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