A vulnerability exists in the garbage collection mechanism of atomic-openshift.
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: cri-o (Red Hat:openshift:4.7::el7) 0:1.20.0-0.rhaos4.7.git8921e00.el7.51; cri-o-debuginfo (Red Hat:openshift:4.7::el7) 0:1.20.0-0.rhaos4.7.git8921e00.el7.51; cri-tools (Red Hat:openshift:4.7::el7) 0:1.18.0-3.el7.
Low priority for now. Upgrade to cri-o (Red Hat:openshift:4.7::el7) 0:1.20.0-0.rhaos4.7.git8921e00.el7.51; cri-o-debuginfo (Red Hat:openshift:4.7::el7) 0:1.20.0-0.rhaos4.7.git8921e00.el7.51; cri-tools (Red Hat:openshift:4.7::el7) 0:1.18.0-3.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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.
- Published
- Aug 1, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 48th percentile
- CWE
- CWE-290
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 5.4
- CNA · redhat
- 3.6
- 1.8 point gap
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | openshift | cpe:2.3:a:redhat:openshift |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat openshift3.10
- redhat openshift3.11
- redhat openshift3.6
- redhat openshift3.7
- redhat openshift3.8
- redhat openshift3.9
- redhat openshift4.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.
Red Hat atomic-openshift
- 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 4.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:openshift:4.7::el7 | cri-o | before 0:1.20.0-0.rhaos4.7.git8921e00.el7.51 | 0:1.20.0-0.rhaos4.7.git8921e00.el7.51 |
| Red Hat:openshift:4.7::el7 | cri-o-debuginfo | before 0:1.20.0-0.rhaos4.7.git8921e00.el7.51 | 0:1.20.0-0.rhaos4.7.git8921e00.el7.51 |
| Red Hat:openshift:4.7::el7 | cri-tools | before 0:1.18.0-3.el7 | 0:1.18.0-3.el7 |
| Red Hat:openshift:4.7::el7 | cri-tools-debuginfo | before 0:1.18.0-3.el7 | 0:1.18.0-3.el7 |
| Red Hat:openshift:4.7::el7 | openshift | before 0:4.7.0-202102060108.p0.git.97095.7271b90.el7 | 0:4.7.0-202102060108.p0.git.97095.7271b90.el7 |
| Red Hat:openshift:4.7::el7 | openshift-hyperkube | before 0:4.7.0-202102060108.p0.git.97095.7271b90.el7 | 0:4.7.0-202102060108.p0.git.97095.7271b90.el7 |
| Red Hat:openshift:4.7::el8 | cri-o | before 0:1.20.0-0.rhaos4.7.git8921e00.el8.51 | 0:1.20.0-0.rhaos4.7.git8921e00.el8.51 |
| Red Hat:openshift:4.7::el8 | cri-o-debuginfo | before 0:1.20.0-0.rhaos4.7.git8921e00.el8.51 | 0:1.20.0-0.rhaos4.7.git8921e00.el8.51 |
| Red Hat:openshift:4.7::el8 | cri-o-debugsource | before 0:1.20.0-0.rhaos4.7.git8921e00.el8.51 | 0:1.20.0-0.rhaos4.7.git8921e00.el8.51 |
| Red Hat:openshift:4.7::el8 | cri-tools | before 0:1.20.0-1.el8 | 0:1.20.0-1.el8 |
| Red Hat:openshift:4.7::el8 | cri-tools-debuginfo | before 0:1.20.0-1.el8 | 0:1.20.0-1.el8 |
| Red Hat:openshift:4.7::el8 | cri-tools-debugsource | before 0:1.20.0-1.el8 | 0:1.20.0-1.el8 |
| Red Hat:openshift:4.7::el8 | ignition | before 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 |
| Red Hat:openshift:4.7::el8 | ignition-debuginfo | before 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 |
| Red Hat:openshift:4.7::el8 | ignition-debugsource | before 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 |
| Red Hat:openshift:4.7::el8 | ignition-validate | before 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 |
| Red Hat:openshift:4.7::el8 | ignition-validate-debuginfo | before 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 |
| Red Hat:openshift:4.7::el8 | openshift | before 0:4.7.0-202102060108.p0.git.97095.7271b90.el8 | 0:4.7.0-202102060108.p0.git.97095.7271b90.el8 |
| Red Hat:openshift:4.7::el8 | openshift-hyperkube | before 0:4.7.0-202102060108.p0.git.97095.7271b90.el8 | 0:4.7.0-202102060108.p0.git.97095.7271b90.el8 |
| Red Hat:openshift:4.7::el8 | python-rsa | before 0:4.7-1.el8 | 0:4.7-1.el8 |
| Red Hat:openshift:4.7::el8 | python3-rsa | before 0:4.7-1.el8 | 0:4.7-1.el8 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-3496cartridge_repository.rb in OpenShift Origin and Enterprise 1.2.8 through 2.1.1 allows remote attackers to execute arbitrary commands via she42Plan
- CVE-2013-2060The download_from_url function in OpenShift Origin allows remote attackers to execute arbitrary commands via shell metacharacters in the URL41Plan
- CVE-2014-0234The default configuration of broker.conf in Red Hat OpenShift Enterprise 2.x before 2.1 has a password of "mooo" for a Mongo account, which 40Plan
- CVE-2013-4561In a openshift node, there is a cron job to update mcollective facts that mishandles a temporary file.36Monitor
- CVE-2014-0163Openshift has shell command injection flaws due to unsanitized data being passed into shell commands.36Monitor
- CVE-2018-1102A flaw was found in source-to-image function as shipped with Openshift Enterprise 3.x.36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:cri-o | 0:1.20.0-0.rhaos4.7.git8921e00.el7.51 · Red Hat:openshift:4.7::el7 | Package registry (OSV) |
| red hat:cri-o-debuginfo | 0:1.20.0-0.rhaos4.7.git8921e00.el7.51 · Red Hat:openshift:4.7::el7 | Package registry (OSV) |
| red hat:cri-tools | 0:1.18.0-3.el7 · Red Hat:openshift:4.7::el7 | Package registry (OSV) |
| red hat:ignition | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 · Red Hat:openshift:4.7::el8 | Package registry (OSV) |
| red hat:ignition-debuginfo | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 · Red Hat:openshift:4.7::el8 | Package registry (OSV) |
| red hat:ignition-debugsource | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 · Red Hat:openshift:4.7::el8 | Package registry (OSV) |
| red hat:ignition-validate | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 · Red Hat:openshift:4.7::el8 | Package registry (OSV) |
| red hat:ignition-validate-debuginfo | 0:2.9.0-2.rhaos4.7.git1d56dc8.el8 · Red Hat:openshift:4.7::el8 | Package registry (OSV) |
| red hat:openshift | 0:4.7.0-202102060108.p0.git.97095.7271b90.el7 · Red Hat:openshift:4.7::el7 | Package registry (OSV) |
| red hat:openshift-hyperkube | 0:4.7.0-202102060108.p0.git.97095.7271b90.el7 · Red Hat:openshift:4.7::el7 | Package registry (OSV) |
| red hat:python-rsa | 0:4.7-1.el8 · Red Hat:openshift:4.7::el8 | Package registry (OSV) |
| red hat:python3-rsa | 0:4.7-1.el8 · Red Hat:openshift:4.7::el8 | Package 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.
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.
No commit or PR link among the references.
Credits
All researchersFinders, 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
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-290 · Authentication Bypass by SpoofingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-461High
- Signature SpoofCAPEC-473
- Signature Spoofing by MisrepresentationCAPEC-476likelihood: Low · High
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- Masquerading: Invalid Code SignatureT1036.001
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls: Code SigningT1553.002
- Adversary-in-the-MiddleT1557
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.