Security readout for executives and security teams
This flaw affects runc, a low-level container runtime. In vulnerable versions before 1.0.0-rc95, a container setup using specific mounts could let an attacker break out of the intended container filesystem boundary. Exploitation requires the attacker to create multiple containers with a particular configuration, so exposure depends heavily on who can create containers and mounts. Most relevant exposure is in container platforms using runc before 1.0.0-rc95, especially where tenants, CI jobs, or users can create containers with custom mount settings. Systems using vendor backports may be fixed without showing the upstream version number. Prioritize remediation on shared container infrastructure, CI runners, and any environment where untrusted users can launch containers. The business risk is highest where a container boundary failure could expose host files or cross-tenant data. Mitigation focus: Upgrade runc to 1.0.0-rc95 or a later fixed release.; Apply distribution or vendor security updates for runc packages.; Confirm whether vendor packages include a backported fix..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-30465 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/opencontainers/runc/releasesCVE reference
- https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7rCVE reference
- FEDORA-2021-2eb67ba3c2CVE reference · vendor-advisory
- FEDORA-2021-0440f235a0CVE reference · vendor-advisory
- https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595fCVE reference
- https://bugzilla.opensuse.org/show_bug.cgi?id=1185405CVE reference
- https://security.netapp.com/advisory/ntap-20210708-0003/CVE reference
- GLSA-202107-26CVE reference · vendor-advisory
- [debian-lts-announce] 20230327 [SECURITY] [DLA 3369-1] runc security updateCVE reference · mailing-list
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
