Skip to content
Noroxi
CVE-2019-10152· NVD / CVE Program· CNA redhat

A path traversal vulnerability has been discovered in podman before version 1.4.0 in the way it handles symlinks inside containers.

A path traversal vulnerability has been discovered in podman before version 1.4.0 in the way it handles symlinks inside containers. An attacker who has compromised an existing container can cause arbitrary files on the host filesystem to be read/written when an administrator tries to copy a file from/to the container.

HighCVSS 7.2 · v3.1—No exploit Fix available
Published
Jul 30, 2019
Updated
Jun 16, 2026
EPSS
0.5% · 38th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CNA vs NVD score

NVD
7.2
CNA · redhat
7.5
0.3 point gap

CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
libpod projectlibpod
opensuseleap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • libpod project libpodbefore 1.4.0
  • opensuse leap15.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Podman podman

    • fixed in 1.4.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/containers/podmanbefore 1.4.01.4.0
openSUSE:Leap 15.1fuse-overlayfsbefore 0.4.1-lp151.2.10.4.1-lp151.2.1
openSUSE:Leap 15.1fuse3before 3.6.1-lp151.2.13.6.1-lp151.2.1
openSUSE:Leap 15.1libcontainers-commonbefore 20190401-lp151.2.3.120190401-lp151.2.3.1
openSUSE:Leap 15.1podmanbefore 1.4.4-lp151.3.3.11.4.4-lp151.3.3.1
openSUSE:Leap 15.1slirp4netnsbefore 0.3.0-lp151.2.3.10.3.0-lp151.2.3.1
openSUSE:Tumbleweedlibcontainers-commonbefore 20210626-5.120210626-5.1
openSUSE:Tumbleweedpodmanbefore 3.3.1-2.13.3.1-2.1
Red Hat:rhel_extras_other:7podmanbefore 0:1.4.4-2.el70:1.4.4-2.el7
Red Hat:rhel_extras_other:7podman-debuginfobefore 0:1.4.4-2.el70:1.4.4-2.el7
Red Hat:rhel_extras_other:7podman-dockerbefore 0:1.4.4-2.el70:1.4.4-2.el7
SUSE:Linux Enterprise Module for Basesystem 15 SP1libcontainers-commonbefore 20190401-3.3.520190401-3.3.5
SUSE:Linux Enterprise Module for Containers 15 SP1fuse-overlayfsbefore 0.4.1-3.3.80.4.1-3.3.8
SUSE:Linux Enterprise Module for Containers 15 SP1fuse3before 3.6.1-3.3.83.6.1-3.3.8
SUSE:Linux Enterprise Module for Containers 15 SP1podmanbefore 1.4.4-4.8.11.4.4-4.8.1
SUSE:Linux Enterprise Module for Containers 15 SP1slirp4netnsbefore 0.3.0-3.3.30.3.0-3.3.3

Other highest-scoring records for the same primary product.

  • CVE-2018-10856It has been discovered that podman before version 0.6.1 does not drop capabilities when executing a container as a non-root user.
    35Monitor
  • CVE-2020-1726A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are
    24Monitor
  • CVE-2019-18466An issue was discovered in Podman in libpod before 1.6.0.
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/containers/podman1.4.0Package registry (OSV)
opensuse:fuse-overlayfs0.4.1-lp151.2.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:fuse33.6.1-lp151.2.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:libcontainers-common20190401-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:podman1.4.4-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:slirp4netns0.3.0-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:podman0:1.4.4-2.el7 · Red Hat:rhel_extras_other:7Package registry (OSV)
red hat:podman-debuginfo0:1.4.4-2.el7 · Red Hat:rhel_extras_other:7Package registry (OSV)
red hat:podman-docker0:1.4.4-2.el7 · Red Hat:rhel_extras_other:7Package registry (OSV)
suse:fuse-overlayfs0.4.1-3.3.8 · SUSE:Linux Enterprise Module for Containers 15 SP1Package registry (OSV)
suse:fuse33.6.1-3.3.8 · SUSE:Linux Enterprise Module for Containers 15 SP1Package registry (OSV)
suse:libcontainers-common20190401-3.3.5 · SUSE:Linux Enterprise Module for Basesystem 15 SP1Package registry (OSV)
suse:podman1.4.4-4.8.1 · SUSE:Linux Enterprise Module for Containers 15 SP1Package registry (OSV)
suse:slirp4netns0.3.0-3.3.3 · SUSE:Linux Enterprise Module for Containers 15 SP1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records