LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43784: Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc, netlink is used internally as a serialization system for specifying the relevant container configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration. This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one may try disallowing untrusted namespace paths from your container. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.

MediumCVSS 6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-43784 affects runc before 1.0.3, the low-level runtime used to start Linux containers. A malicious container configuration can abuse an integer overflow to change namespace setup and weaken container isolation. Risk is highest where untrusted users can supply container images or configurations.

Executive priority

Prioritize remediation on multi-tenant or shared container platforms first. The vulnerability is not reported as actively exploited in the supplied sources, but successful abuse can undermine the isolation boundary that containerized workloads depend on.

Technical view

runc used netlink internally to pass container configuration to C setup code. Its encoder mishandled overflow in a 16-bit byte-array length field, allowing oversized malicious attributes to be interpreted as additional netlink configuration messages. With container configuration control, an attacker could bypass namespace restrictions, including disabling namespaces.

Likely exposure

Organizations running runc versions earlier than 1.0.3 are exposed, especially shared container infrastructure accepting untrusted images or untrusted container configurations. Single-tenant environments with tightly controlled images and runtime configuration have lower practical exposure.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires low privileges plus some control over container configuration, and the CVSS vector marks attack complexity high. The impact is container isolation bypass, not a simple unauthenticated remote takeover.

Researcher notes

Focus analysis on runc netlink configuration serialization and the 16-bit byte-array length overflow. The advisory states attackers need configuration influence. Avoid assuming exposure in higher-level container products unless their deployed runtime includes affected runc versions.

Mitigation direction

  • Upgrade runc to version 1.0.3 or later.
  • Apply vendor or distribution security updates for bundled runc packages.
  • Avoid running untrusted images with untrusted container configurations.
  • Disallow untrusted namespace paths where supported.
  • Review vendor guidance before applying nonstandard runtime mitigations.

Validation and detection

  • Inventory runc versions on container hosts and build images.
  • Confirm all affected hosts run runc 1.0.3 or a patched vendor build.
  • Identify platforms that accept untrusted images or container configuration.
  • Review controls around namespace paths and runtime configuration injection.
  • Check change records for Debian or vendor runc security updates.
Prepared
Confidence
high
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container 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 lookup
cve · low confidence lookup

CVE-2021-43784 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L1.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6Medium
CVSS 3.1 vector shape for CVE-2021-43784Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
opencontainersrunc< 1.0.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.