Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 7.8 HIGHCVSS 2.0 · [email protected] · Primary 2.1 LOWCVSS_V3 Publisher rating HIGHFixed by github.com/opencontainers/runc 0.1.0osv · severity unknownFixed by github.com/opencontainers/runc 0.1.0KEV status unknown

cve-program · CVE-2016-3697

Published

libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.

Read the publisher's advisory

euvd · EUVD-2021-2563

Published

libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.

Read the publisher's advisory

nvd · CVE-2016-3697

Published

libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.

Read the publisher's advisory

osv · GHSA-q3j5-32m5-58c2

Published

libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.

Read the publisher's advisory

osv · GO-2021-0070

Published

GetExecUser in the github.com/opencontainers/runc/libcontainer/user package will improperly interpret numeric UIDs as usernames. If the method is used without verifying that usernames are formatted as expected, it may allow a user to gain unexpected privileges.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2016-3697 · CVE overview and exploitation status

EUVD-2021-2563

GHSA-q3j5-32m5-58c2

GO-2021-0070

cve-program · CVE-2016-3697

euvd · EUVD-2021-2563

nvd · CVE-2016-3697

osv · GHSA-q3j5-32m5-58c2

osv · GO-2021-0070

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current