summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended/bash/bash/bash-CVE-2019-18276.patch
AgeCommit message (Collapse)Author
2020-12-18bash: Rename patch namezangrc
Because the name of CVE patch is wrong, cve-check-tool cannot get the correct CVE result. Rename the patch name. (From OE-Core rev: 422f9af7d0f7de7a2e933154853e7a281f98ab93) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-09-24bash: fix CVE-2019-18276De Huo
An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected. Get the patch from [1] to fix the issue. [1] https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=951bdaa (From OE-Core rev: 6f01acae9c279e0a580f46d1ba4c015caa3f8c2c) Signed-off-by: De Huo <De.Huo@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>