Security readout for executives and security teams
CVE-2016-3697 is an old container runtime privilege issue. runC, used by Docker, could mis-handle a numeric user ID as a possible username. A local user inside a container with a numeric username entry could gain elevated privileges. Evidence points to affected runC before 0.1.0 and Docker before 1.11.2. Exposure is most likely in legacy Docker or runC deployments, especially old Linux distribution packages from 2016 or earlier. Modern supported container stacks are less likely exposed, but backported vendor package versions must be checked against distro advisories. Treat this as a cleanup and legacy-risk item unless exposed systems are still running old container runtimes. Prioritize internet-facing or multi-tenant container hosts first because local privilege flaws can raise containment and isolation concerns. Mitigation focus: Upgrade runC to 0.1.0 or a vendor-fixed later package.; Upgrade Docker to 1.11.2 or a vendor-fixed later package.; Apply applicable Red Hat, SUSE, or Gentoo security updates..
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.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2016-3697 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/releases/tag/v0.1.0CVE reference · x_refsource_CONFIRM
- https://github.com/docker/docker/issues/21436CVE reference · x_refsource_CONFIRM
- https://github.com/opencontainers/runc/pull/708CVE reference · x_refsource_CONFIRM
- https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091CVE reference · x_refsource_CONFIRM
- GLSA-201612-28CVE reference · vendor-advisory, x_refsource_GENTOO
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.
