# CVE-2020-14370: Information disclosure in podman > An attacker controlling subsequent containers can access sensitive environment variables leaked from previous containers via deprecated APIs. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Sep 2020 - **Updated:** 4 Aug 2024 - **Also known as:** ALSA-2021:0531, DEBIAN-CVE-2020-14370, GHSA-c3wv-qmjj-45r6, GO-2024-2766, RHSA-2021:0531, RLSA-2021:0531, SUSE-SU-2020:3378-1, openSUSE-SU-2020:2039-1, openSUSE-SU-2020:2063-1 ## What is CVE-2020-14370? CVE-2020-14370 is a medium-severity vulnerability in Fedoraproject Fedora, published on 23 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description An information disclosure vulnerability was found in containers/podman in versions before 2.0.5. When using the deprecated Varlink API or the Docker-compatible REST API, if multiple containers are created in a short duration, the environment variables from the first container will get leaked into subsequent containers. An attacker who has control over the subsequent containers could use this flaw to gain access to sensitive information stored in such variables. Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer) ## Which versions are affected by CVE-2020-14370? 4 open source packages ship an affected version, including github.com/containers/podman/v2, github.com/containers/libpod and github.com/containers/libpod/v2. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containers/podman/v2` | Go | All versions | 2.0.5 | | `github.com/containers/podman/v2` | Go | All versions | 2.0.5 | | `github.com/containers/libpod` | Go | All versions | None | | `github.com/containers/libpod/v2` | Go | All versions | 2.0.5 | | `crit` | AlmaLinux:8 | All versions | 3.15-1.module_el8.6.0+2876+9ed4eae2 | | `criu` | AlmaLinux:8 | All versions | 3.15-1.module_el8.6.0+2876+9ed4eae2 | | `libslirp` | AlmaLinux:8 | All versions | 4.3.1-1.module_el8.6.0+2876+9ed4eae2 | | `libslirp-devel` | AlmaLinux:8 | All versions | 4.3.1-1.module_el8.6.0+2876+9ed4eae2 | | `python-podman-api` | AlmaLinux:8 | All versions | 1.2.0-0.2.gitd0a45fe.module_el8.5.0+108+00865455 | | `python-podman-api` | AlmaLinux:8 | All versions | 1.2.0-0.2.gitd0a45fe.module_el8.5.0+2635+e4386a39 | | `python3-criu` | AlmaLinux:8 | All versions | 3.15-1.module_el8.6.0+2876+9ed4eae2 | | `slirp4netns` | AlmaLinux:8 | All versions | 1.1.8-1.module_el8.6.0+2876+9ed4eae2 | | `udica` | AlmaLinux:8 | All versions | 0.2.4-1.module_el8.6.0+2876+9ed4eae2 | | `buildah` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.16.7-4.module+el8.3.1+9857+68fb1526 | | `buildah-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.16.7-4.module+el8.3.1+9857+68fb1526 | | `buildah-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.16.7-4.module+el8.3.1+9857+68fb1526 | | `buildah-tests` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.16.7-4.module+el8.3.1+9857+68fb1526 | | `buildah-tests-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.16.7-4.module+el8.3.1+9857+68fb1526 | | `cockpit-podman` | Red Hat:enterprise_linux:8::appstream | All versions | 0:27.1-3.module+el8.3.1+9857+68fb1526 | | `conmon` | Red Hat:enterprise_linux:8::appstream | All versions | 2:2.0.22-3.module+el8.3.1+9857+68fb1526 | | `conmon-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 2:2.0.22-3.module+el8.3.1+9857+68fb1526 | | `conmon-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 2:2.0.22-3.module+el8.3.1+9857+68fb1526 | | `container-selinux` | Red Hat:enterprise_linux:8::appstream | All versions | 2:2.155.0-1.module+el8.3.1+9857+68fb1526 | | `containernetworking-plugins` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.9.0-1.module+el8.3.1+9857+68fb1526 | | `containernetworking-plugins-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.9.0-1.module+el8.3.1+9857+68fb1526 | | `containernetworking-plugins-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.9.0-1.module+el8.3.1+9857+68fb1526 | | `containers-common` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.2.0-9.module+el8.3.1+9857+68fb1526 | | `crit` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.15-1.module+el8.3.1+9857+68fb1526 | | `criu` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.15-1.module+el8.3.1+9857+68fb1526 | | `criu-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.15-1.module+el8.3.1+9857+68fb1526 | | `criu-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.15-1.module+el8.3.1+9857+68fb1526 | | `crun` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.16-2.module+el8.3.1+9857+68fb1526 | | `crun-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.16-2.module+el8.3.1+9857+68fb1526 | | `crun-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.16-2.module+el8.3.1+9857+68fb1526 | | `fuse-overlayfs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-2.module+el8.3.1+9857+68fb1526 | | `fuse-overlayfs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-2.module+el8.3.1+9857+68fb1526 | | `fuse-overlayfs-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-2.module+el8.3.1+9857+68fb1526 | | `libslirp` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.1-1.module+el8.3.1+9803+64eb0fd6 | | `libslirp-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.1-1.module+el8.3.1+9803+64eb0fd6 | | `libslirp-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.3.1-1.module+el8.3.1+9803+64eb0fd6 | Products: Fedoraproject Fedora, Podman Project Podman, Redhat Enterprise Linux, Redhat Openshift Container Platform. ## How do I fix CVE-2020-14370? Upgrade github.com/containers/podman/v2 to 2.0.5 or later. ## Is CVE-2020-14370 being exploited? There is no known exploitation of CVE-2020-14370 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-14370 and fix it if it is affected. What it is: CVE-2020-14370 is a medium-severity vulnerability in Fedoraproject Fedora, published on 23 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-14370 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/containers/podman/v2 (Go): affected all versions; fixed in 2.0.5 - github.com/containers/podman/v2 (Go): affected all versions; fixed in 2.0.5 - github.com/containers/libpod (Go): affected all versions; no fix listed - github.com/containers/libpod/v2 (Go): affected all versions; fixed in 2.0.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-14370/ (Markdown: https://insights.sbomify.com/CVE-2020-14370/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14370 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14370 - OSV: https://osv.dev/vulnerability/CVE-2020-14370 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-14370/ Summaries are generated and may contain mistakes; the official description above is the record.