U.S. flag   An official website of the United States government
Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock (Dot gov) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

National Vulnerability Database

National Vulnerability Database

NVD

National Vulnerability Database

Vulnerability Change Records for CVE-2020-5291

Change History

CVE Modified by GitHub, Inc. 3/31/2020 3:15:14 PM

Action Type Old Value New Value
Changed Description 
Bubblewrap (bwrap) before version 0.4.1, if installed in setuid mode and the kernel supports unprivileged user namespaces,
then the `bwrap --userns2` option can be used to make the setuid process keep running as root while being traceable.
This can in turn be used to gain root permissions.

Note that this only affects the combination of bubblewrap in setuid mode (which is typically used when unprivileged user namespaces
are not supported) and the support of unprivileged user namespaces.

Known to be affected are:
 * Debian testing/unstable, if unprivileged user namespaces enabled (not default)
 * Debian buster-backports, if unprivileged user namespaces enabled (not default)
 * Arch if using `linux-hardened`, if  unprivileged user namespaces enabled (not default)
 * Centos 7 flatpak COPR, if unprivileged user namespaces enabled (not default)

This has been fixed in the 0.4.1 release, and all affected users should update.
 
Bubblewrap (bwrap) before version 0.4.1, if installed in setuid mode and the kernel supports unprivileged user namespaces, then the `bwrap --userns2` option can be used to make the setuid process keep running as root while being traceable. This can in turn be used to gain root permissions. Note that this only affects the combination of bubblewrap in setuid mode (which is typically used when unprivileged user namespaces are not supported) and the support of unprivileged user namespaces. Known to be affected are: * Debian testing/unstable, if unprivileged user namespaces enabled (not default) * Debian buster-backports, if unprivileged user namespaces enabled (not default) * Arch if using `linux-hardened`, if unprivileged user namespaces enabled (not default) * Centos 7 flatpak COPR, if unprivileged user namespaces enabled (not default) This has been fixed in the 0.4.1 release, and all affected users should update.