CVE-2019-10214 [Medium] | Security Vulnerability in Buildah

The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-01	0.47%	0.41%	-0.06%
2	2026-02-16	0.41%	0.47%	+0.06%
3	2026-01-03	—	0.41%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-01

0.47%

0.41%

-0.06%

2026-02-16

0.41%

0.47%

+0.06%

2026-01-03

—

0.41%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.9	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.2	3.6	[email protected]
6.4	3.0	MEDIUM	`CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.2	5.2	[email protected]
4.3	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:N/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:N) No availability impact.	8.6	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.9

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.2

3.6

[email protected]

6.4

3.0

MEDIUM

CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.2

5.2

[email protected]

4.3

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:N): No availability impact.

8.6

2.9

[email protected]

OS Trackers for CVE-2019-10214

vendor	priority	summary	link
`debian`	unimportant	CVE-2019-10214 unimportant priority: Debian including 1 source packages (golang-github-containers-image), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2019-10214
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2019-10214
`suse`	medium	CVE-2019-10214 severity moderate: SUSE including 126 source package names (1.37.1.8.5.1:skopeo-0.1.41-4.11.1, 1.43.0.16.7:skopeo-0.1.41-4.11.1, …), 193 product×package rows across 60 product lines (Container suse/sles/15.3/cdi-importer, Container suse/sles/15.4/cdi-importer, … (60 product lines)): Fixed 134, Known Not Affected 59.	https://www.suse.com/security/cve/CVE-2019-10214/
`ubuntu`	medium	CVE-2019-10214 medium priority: Ubuntu including 2 source packages (golang-github-containers-image, singularity-container), 32 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 13, ignored 8, needs-triage 6, not-affected 4, released 1.	https://ubuntu.com/security/CVE-2019-10214

Affected software / configurations for CVE-2019-10214

Vendor	Product	Version	Raw CPE
buildah_project	buildah	—	cpe:2.3:a:buildah_project:buildah:-:::::::*
libpod_project	libpod	—	cpe:2.3:a:libpod_project:libpod:-:::::::*
redhat	openshift_container_platform	4.1	cpe:2.3:a:redhat:openshift_container_platform:4.1:::::::*
skopeo_project	skopeo	—	cpe:2.3:a:skopeo_project:skopeo:-:::::::*
redhat	enterprise_linux	8.0	cpe:2.3:o:redhat:enterprise_linux:8.0:::::::*
opensuse	leap	15.1	cpe:2.3:o:opensuse:leap:15.1:::::::*

References for CVE-2019-10214

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00035.html	Mailing List Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html	Mailing List Third Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10214	Issue Tracking Patch Vendor Advisory

URL

CVE-2019-10214

Exploit prediction scoring system (EPSS) score for CVE-2019-10214

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10214

Weakness enumeration for CVE-2019-10214

GitHub Security Advisory for CVE-2019-10214

OS Trackers for CVE-2019-10214

Affected software / configurations for CVE-2019-10214

References for CVE-2019-10214