Container security: Privilege escalation bug patched in Docker Engine


Adam Bannister

09 February 2021 at 12:47 UTC

Updated: 09 February 2021 at 12:59 UTC

‘An odd one, impact wise’

A vulnerability in a Docker Engine security feature potentially allowed attackers to escalate privileges from a remapped user to root.

“The two avenues of exploitation I found would allow writing of arbitrary files as the real root user” or seizing ownership of files previously accessible only by the root user, security researcher Alex Chapman, who unearthed the flaw, tells The Daily Swig.

The vulnerable function in question – ‘ – “is an optional security enhancement which isolates container users within a user namespace”, he explains.

“What this means is that, when enabled, the ‘root’ user within the container is actually mapped to a non-privileged user in the container host.”

RELATED Security pro Alex Chapman on the future of ethical hacking

If an attacker has root access to, and can escape, a Docker container, “the user they can run commands as on the host is not the privileged root user”, he adds.

“This bug allowed this non-privileged, remapped user to escalate to the real ‘root’ user by exploiting various race conditions in Docker when building or starting containers.”

The flaw (CVE-2021-21284) resides in the Docker Engine package, .

Limited exploitation

If is enabled and “the root user in the remapped namespace has access to the host filesystem, they can modify files under that cause writing files with extended privileges.”

A security advisory posted by Docker’s Moby Project to GitHub on February 1 actually classifies the bug as ‘low’ impact, but Chapman describes it as “an odd one, impact wise” and said he “would have preferred medium impact”.

Read more of the latest cloud security news

However, the researcher acknowledged that “exploitation is a little limited”, given its contingency on escaping the container, and “another user (or system service) creating or building a container” so the attacker can “replace files written during the container creation or build process”.

Moreover, “as far as I am aware the ‘’ is not that widely used”, he adds.

The flaw was fixed in docker-ce versions 19.03.15 and 20.10.3. All previous versions on those release lines were affected by the vulnerability.

YOU MIGHT ALSO LIKE Skype spoofing vulnerabilities could be a haven for social engineering attacks





Source link