Skip to content
Fencer Vulns
low 3.6

CVE-2019-3884 json

A vulnerability exists in the garbage collection mechanism of atomic-openshift.

published 2019-08-01 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-13494

cvss
3.6
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

A vulnerability exists in the garbage collection mechanism of atomic-openshift. An attacker able spoof the UUID of a valid object from another namespace is able to delete children of those objects. Versions 3.6, 3.7, 3.8, 3.9, 3.10, 3.11 and 4.1 are affected.

Patch / fix

  • cri-o openshift 4.7 1.20.0-0.rhaos4.7.git8921e00.el7.51
  • cri-o openshift 4.7 1.20.0-0.rhaos4.7.git8921e00.el8.51
  • ignition openshift 4.7 2.9.0-2.rhaos4.7.git1d56dc8.el8
  • cri-tools openshift 4.7 1.18.0-3.el7
  • cri-tools openshift 4.7 1.20.0-1.el8
  • openshift openshift 4.7 4.7.0-202102060108.p0.git.97095.7271b90.el7
  • openshift openshift 4.7 4.7.0-202102060108.p0.git.97095.7271b90.el8
  • python-rsa openshift 4.7 4.7-1.el8

red hat advisories RHSA-2020:5634

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-3884 updated cvss 3.6

atomic-openshift: cross-namespace owner references can trigger deletions of valid children

  • Red Hat OpenShift Container Platform 3.6 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +9 more Red Hat OpenShift Container Platform 3.7 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +10 more
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 3.9 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +8 more Red Hat OpenShift Container Platform 3.10 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more Red Hat OpenShift Container Platform 3.11 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift Container Platform 4.7 openshift 4.7.0-202102060108.p0.git.97095.7271b90.el7, openshift 4.7.0-202102060108.p0.git.97095.7271b90.el8, openshift-hyperkube 4.7.0-202102060108.p0.git.97095.7271b90.el7, openshift-hyperkube 4.7.0-202102060108.p0.git.97095.7271b90.el8
    fixed: vendor fix RHSA-2020:5634
  • Red Hat OpenShift Container Platform 3.4 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +6 more Red Hat OpenShift Container Platform 3.5 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +6 more Red Hat OpenShift Container Platform 4.7 jq 1.6-2.el7, jq 1.6-2.el8, clevis 15-1.el8, faq 0.0.6-5.el8, bootupd 0.2.5-2.el8, ostree 2020.7-1.el8, +264 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 3.6 CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Red Hat atomic-openshift

Classification

Weakness
  • CWE-290 Authentication Bypass by Spoofing
  • CWE-287 Improper Authentication

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.