[SECURITY] [DLA 2827-1] bluez security update
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- -------------------------------------------------------------------------
Debian LTS Advisory DLA-2827-1 debian-lts@lists.debian.org
https://www.debian.org/lts/security/ Sylvain Beucler
November 27, 2021 https://wiki.debian.org/LTS
- -------------------------------------------------------------------------
Package : bluez
Version : 5.43-2+deb9u5
CVE ID : CVE-2019-8921 CVE-2019-8922 CVE-2021-41229
Debian Bug : 1000262
Several vulnerabilities were discovered in BlueZ, the Linux Bluetooth
protocol stack. An attacker could cause a denial-of-service (DoS) or
leak information.
CVE-2019-8921
SDP infoleak; the vulnerability lies in the handling of a
SVC_ATTR_REQ by the SDP implementation of BlueZ. By crafting a
malicious CSTATE, it is possible to trick the server into
returning more bytes than the buffer actually holds, resulting in
leaking arbitrary heap data.
CVE-2019-8922
SDP Heap Overflow; this vulnerability lies in the SDP protocol
handling of attribute requests as well. By requesting a huge
number of attributes at the same time, an attacker can overflow
the static buffer provided to hold the response.
CVE-2021-41229
sdp_cstate_alloc_buf allocates memory which will always be hung in
the singly linked list of cstates and will not be freed. This will
cause a memory leak over time. The data can be a very large
object, which can be caused by an attacker continuously sending
sdp packets and this may cause the service of the target device to
crash.
For Debian 9 stretch, these problems have been fixed in version
5.43-2+deb9u5.
We recommend that you upgrade your bluez packages.
For the detailed security status of bluez please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/bluez
Further information about Debian LTS security advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://wiki.debian.org/LTS
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE1vEOfV7HXWKqBieIDTl9HeUlXjAFAmGiEh0ACgkQDTl9HeUl
XjCqVQ/9HDvMcYwdegi6hxeBdzaBghIHveFKGx9HxOSEVHjtFabZbURMWT+nlg1a
TvhzC2YPKGyvqV6DJz3d1Nvc01bHcqRr/0ZUywn7bgjsCyjhNGTQCJgCL4lGdRkb
i9fsgDRVAb94PACw9O4o5FvpAexAIpNlhEi8+jyPmUa/dgPXS6UwD9SG1jbvAY/L
NK4uilj6y0rcLuJLNS5DlXsSKSaQ/OauzPcZgh3r99C4SU51Ix90GbhBL/+C7aox
hP8s85bjfMMpqrkxqu+210Pf+J/fQc/h/LGBGryQqgaOdQ2Feu8YOLTSG64M42UJ
Bm0Xw3MXbxOl4Rk2eg86g0zf/s/ONBGZZcIdHwJDDeWvWRtoJ+b/FceWdJvlgxBA
0gwzWsdvlaporMIabqhgVVRebpsK9sSJ3MLVo6ADZV3UZvfNdPQYmh5psvzBgYXX
O01V+kB5Gxd+MegV8QfOb+pKE+jNTrwhzWOx5z2J9T6nTBo6ABq9PgBHKqJnO2Ov
K1rwRF1EMPjnM+en1plSjfNRIxATBTDXAISryK00NL+X35QgetA5YcVWH0bHbLZr
kXE2pk/56UzC64Fw+wkTJKwxNP7TykFAY6JZAwtDb58jssXOXHa8j5wzQ4IZ8Kcd
t7QY1Xt77yyFlVLWszbkQtFsWX7hETVnEC90tNHrIYXe34dELso=
=fTkb
-----END PGP SIGNATURE-----
Reply to: