Overview
This week we discuss new kernel memory hardening and security development
proposals from Ubuntu Security Alumnus Kees Cook, plus we look at details
of security updates for WebKitGTK, libsndfile, GnuTLS, exiv2 and more.
This week in Ubuntu Security Updates
[USN-5024-1] WebKitGTK vulnerabilities [00:57]
13 CVEs addressed in Bionic (18.04 LTS), Focal (20.04 LTS), Hirsute (21.04)CVE-2021-30799 CVE-2021-30797 CVE-2021-30795 CVE-2021-30758 CVE-2021-30749 CVE-2021-30744 CVE-2021-30734 CVE-2021-30720 CVE-2021-30689 CVE-2021-30665 CVE-2021-30663 CVE-2021-21779 CVE-2021-21775 Every 5-10 weeks so time for another oneUsual web / js engine issues - XSS, DoS, RCE etc[USN-4944-2] MariaDB regression [01:30]
Affecting Focal (20.04 LTS)Update announced back in Episode 115 - MariaDB intends to be compatiblewith MySQL but failed to include the caching_sha2_password.so module
which is the standard module used to authenticate in MySQL - as such
clients would not be able to connect since they expect to use this method
to authenticate by default. Upstream MariaDB fixed this in newer versions
and this update backports that fix to the version in Ubuntu 20.04
[USN-5025-1, USN-5025-2] libsndfile vulnerability [02:25]
1 CVEs addressed in Trusty ESM (14.04 ESM), Xenial ESM (16.04 ESM), Bionic (18.04 LTS), Focal (20.04 LTS), Hirsute (21.04)CVE-2021-3246 Heap buffer overflow in wav decoder - possible RCE / DoS - found byOSSFuzz
[USN-5026-1, USN-5026-2] QPDF vulnerabilities [02:58]
2 CVEs addressed in Xenial ESM (16.04 ESM), Bionic (18.04 LTS), Focal (20.04 LTS)CVE-2021-36978 CVE-2018-18020 DoS due to recursive parsing in the face of errors - fixed to insteadbail out if encounters too many successive errors as PDF is damaged in
this case anyway
Heap buffer overflow from crafted PDF - also found by OSSFuzz[USN-5027-1, USN-5027-2] PEAR vulnerability [03:50]
1 CVEs addressed in Xenial ESM (16.04 ESM), Bionic (18.04 LTS), Focal (20.04 LTS), Hirsute (21.04)CVE-2021-32610 Symlink path traversal in handling of tar archives in the Archive_Tarmodule - since PEAR uses this directly when handling archives, it was
also vulnerable so could be made to overwrite arbitrary local files on
archive extraction and hence get code execution
[USN-5029-1] GnuTLS vulnerabilities [04:22]
2 CVEs addressed in Focal (20.04 LTS)CVE-2021-20232 CVE-2021-20231 2 possible UAF in certain scenarious - hard to exploit as need to be ableto predict the behaviour of glibc’s memory allocator as well as GnuTLS’s
own internal allocator but could possibly be used for RCE
[USN-5028-1] Exiv2 vulnerability [04:57]
1 CVEs addressed in Xenial ESM (16.04 ESM), Bionic (18.04 LTS), Focal (20.04 LTS), Hirsute (21.04)CVE-2021-31291 More exiv2 (last seen in Episode 115 and Episode 117)Heap buffer overflow in handling of jpeg image metadata - DoS / RCE[USN-5030-1] Perl DBI module vulnerabilities [05:24]
2 CVEs addressed in Bionic (18.04 LTS), Focal (20.04 LTS)CVE-2020-14393 CVE-2014-10402 Incomplete fix for previous Perl DBI CVE-2014-10401 - would allow accessto files outside the original data source directory - was still
potentially vulnerable - fixed to parse attributes more strictly to avoid
this
Possible stack buffer overflow if using a really long perl package nameas a database driver - unlikely to actually be triggered in practice -
used a fixed size stack buffer and memcpy()’d into it without checking
bounds - fixed to allocate the buffer on the heap to the exact required
size
Goings on in Ubuntu Security Community
Upstream kernel memcpy() hardening [06:31]
https://lwn.net/Articles/864521/Ubuntu Security Alumnus Kees CookAiming to make memcpy() within the kernel detect whenoverwriting following structure members
Current kernel memcpy() is able to already detect when writing outsidethe bounds of a given structure (when the structure size can be known at
either compile or run-time) - but can’t handle detecting overwriting of
extra members within a structure
Uses the built-in features of GCC plus some C macro smarts to actuallyallow this to be done in certain circumstances without triggering
warnigns - ie in some cases want to actually overwrite following
structure members like when handling network packets etc
Most cases are only able to be detected at runtime and since it is noteasy to statically determine all these call sites, for now this proposal
is warn-only - but in the future the hope is to make it enforcing so it
can actually stop possible buffer overflows
Also had this been present it would have detected the 11 previously knownmemcpy() overflows so shows likely real-world promise as an extra
defensive measure
Linux kernel security done right [09:29]
https://security.googleblog.com/2021/08/linux-kernel-security-done-right.htmlMore from KeesMakes a strong case for having vendors track either latest releasedkernel or one of the stable trees - instead of each manually backporting
patches etc - duplicated work
Then could devote engineers to working more upstream on testing,hardening etc - which benefit everyone - ie by working upstream on a
common platform this reduces duplicated efforts and gains many
efficiencies
Hiring [11:50]
Linux Cryptography and Security Engineer
https://canonical.com/careers/2612092/linux-cryptography-and-security-engineer-remoteSecurity Engineer - Ubuntu
https://canonical.com/careers/2925180/security-engineer-ubuntu-remoteSecurity - Product Manager
https://canonical.com/careers/2278145/security-product-manager-remoteGet in contact
#ubuntu-security on the Libera.Chat IRC networkubuntu-hardened mailing listSecurity section on discourse.ubuntu.com@ubuntu_sec on twitter