SUSE update for bluez

1) Heap-based buffer overflow

EUVDB-ID: #VU66639

Risk: Low

CVSSv4.0: 1.3 [CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U/U:Clear]

CVE-ID: CVE-2022-0204

CWE-ID: CWE-122 - Heap-based Buffer Overflow

Exploit availability: No

Description

The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.

The vulnerability exists due to a boundary error. A remote attacker on the local network can pass specially crafted files to the affected system, trigger a heap-based buffer overflow and perform a denial of service (DoS) attack.

Mitigation

Update the affected package bluez to the latest version.

Vulnerable software versions

SUSE Linux Enterprise Storage: 7.1

SUSE Manager Retail Branch Server: 4.2

SUSE Linux Enterprise Workstation Extension: 15-SP3

SUSE Linux Enterprise Desktop: 15-SP3

openSUSE Leap: 15.3

SUSE Manager Server: 4.2

SUSE Manager Proxy: 4.2

SUSE Linux Enterprise Server for SAP Applications: 15-SP3

SUSE Linux Enterprise Server: 15-SP3

SUSE Linux Enterprise High Performance Computing: 15-SP3

SUSE Linux Enterprise Module for Desktop Applications: 15-SP3

SUSE Linux Enterprise Module for Basesystem: 15-SP3

bluez-auto-enable-devices: before 5.55-150300.3.11.1

libbluetooth3-32bit-debuginfo: before 5.55-150300.3.11.1

libbluetooth3-32bit: before 5.55-150300.3.11.1

bluez-devel-32bit: before 5.55-150300.3.11.1

libbluetooth3-debuginfo: before 5.55-150300.3.11.1

libbluetooth3: before 5.55-150300.3.11.1

bluez-test-debuginfo: before 5.55-150300.3.11.1

bluez-test: before 5.55-150300.3.11.1

bluez-devel: before 5.55-150300.3.11.1

bluez-deprecated-debuginfo: before 5.55-150300.3.11.1

bluez-deprecated: before 5.55-150300.3.11.1

bluez-debugsource: before 5.55-150300.3.11.1

bluez-debuginfo: before 5.55-150300.3.11.1

bluez-cups-debuginfo: before 5.55-150300.3.11.1

bluez-cups: before 5.55-150300.3.11.1

bluez: before 5.55-150300.3.11.1

CPE2.3

• cpe:2.3:o:suse:suse_linux_enterprise_storage:7.1:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_manager_retail_branch_server:4.2:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_workstation_extension:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_desktop:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:opensuse_leap:15.3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_manager_server:4.2:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_manager_proxy:4.2:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_server_for_sap_applications:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_server:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_high_performance_computing:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_module_for_desktop_applications:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:suse_linux_enterprise_module_for_basesystem:15-SP3:*:*:*:*:*:*:*
• cpe:2.3:o:suse:bluez-auto-enable-devices:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:libbluetooth3-32bit-debuginfo:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:libbluetooth3-32bit:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-devel-32bit:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:libbluetooth3-debuginfo:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:libbluetooth3:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-test-debuginfo:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-test:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-devel:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-deprecated-debuginfo:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-deprecated:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-debugsource:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-debuginfo:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-cups-debuginfo:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez-cups:*:*:*:*:*:suse_linux:*:*
• cpe:2.3:o:suse:bluez:*:*:*:*:*:suse_linux:*:*

External links

https://www.suse.com/support/update/announcement/2022/suse-su-20222883-1/

Q & A

Can this vulnerability be exploited remotely?

Yes. This vulnerability can be exploited by a remote non-authenticated attacker via the local network (LAN).

Is there known malware, which exploits this vulnerability?

No. We are not aware of malware exploiting this vulnerability.