Most recent entries from all https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:48:10 +0000 bdu:2020-05810 https://cve.radiocsirt.org/vuln/bdu:2020-05810 bdu:2020-05810 https://cve.radiocsirt.org/vuln/bdu:2020-05810 Withdrawn: BELL-CVE-2020-5291 — CVE-2020-5291 does not affect BellSoft software https://cve.radiocsirt.org/vuln/bell-cve-2020-5291 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2020-5291 cnvd-2020-35522 https://cve.radiocsirt.org/vuln/cnvd-2020-35522 cnvd-2020-35522 https://cve.radiocsirt.org/vuln/cnvd-2020-35522 EUVD-2026-36515 https://cve.radiocsirt.org/vuln/euvd-2026-36515 EUVD-2026-36515 https://cve.radiocsirt.org/vuln/euvd-2026-36515 fkie_cve-2020-5291 https://cve.radiocsirt.org/vuln/fkie_cve-2020-5291 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-5291 gsd-2020-5291 https://cve.radiocsirt.org/vuln/gsd-2020-5291 gsd-2020-5291 https://cve.radiocsirt.org/vuln/gsd-2020-5291 msrc_CVE-2020-5291 — Privilege escalation in setuid mode via user namespaces in Bubblewrap https://cve.radiocsirt.org/vuln/msrc_cve-2020-5291 msrc_CVE-2020-5291 https://cve.radiocsirt.org/vuln/msrc_cve-2020-5291 openSUSE-SU-2024:10663-1 — bubblewrap-0.5.0-1.1 on GA media https://cve.radiocsirt.org/vuln/opensuse-su-2024:10663-1 <p>bubblewrap-0.5.0-1.1 on GA media</p> <p>bubblewrap-0.5.0-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10663-1 UBUNTU-CVE-2020-5291 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-5291 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: bubblewrap</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: bubblewrap</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-5291