Vulnerability in Blueman is a GTK+ Bluetooth Manager. In Blu… (CVE-2020-15238)

Summary

Vulnerability in Blueman is a GTK+ Bluetooth Manager. In Blueman (CVE-2020-15238). Successful exploitation can lead to full system takeover. Exploitable via org.blueman.dhcp.client.

Original description

The description as published by the source.

Blueman is a GTK+ Bluetooth Manager. In Blueman before 2.1.4, the DhcpClient method of the D-Bus interface to blueman-mechanism is prone to an argument injection vulnerability. The impact highly depends on the system configuration. If Polkit-1 is disabled and for versions lower than 2.0.6, any local user can possibly exploit this. If Polkit-1 is enabled for version 2.0.6 and later, a possible attacker needs to be allowed to use the org.blueman.dhcp.client action. That is limited to users in the wheel group in the shipped rules file that do have the privileges anyway. On systems with ISC DHCP client (dhclient), attackers can pass arguments to ip link with the interface name that can e.g. be used to bring down an interface or add an arbitrary XDP/BPF program. On systems with dhcpcd and without ISC DHCP client, attackers can even run arbitrary scripts by passing -c/path/to/script as an interface name. Patches are included in 2.1.4 and master that change the DhcpClient D-Bus method(s) to accept BlueZ network object paths instead of network interface names. A backport to 2.0(.8) is also available. As a workaround, make sure that Polkit-1-support is enabled and limit privileges for the org.blueman.dhcp.client action to users that are able to run arbitrary commands as root anyway in /usr/share/polkit-1/rules.d/blueman.rules.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-15238 has been found in Blueman is a GTK+ Bluetooth Manager. In Blueman.
Attackers can target a specific entry point like org.blueman.dhcp.client over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Blueman is a GTK+ Bluetooth Manager. In Blueman CVE-2020-15238" on the vendor's site.

CVE-2020-15238 (Blueman is a GTK+ Bluetooth Manager. In Blueman)
Attack vector: local / no user interaction
Attack surface: org.blueman.dhcp.client
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Blueman is a GTK+ Bluetooth Manager. In Blueman. Attackers reach the vulnerable code path via org.blueman.dhcp.client.

📍 Affected scope

Check the vendor advisory for the affected versions of Blueman is a GTK+ Bluetooth Manager. In Blueman. Attack surface: org.blueman.dhcp.client.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Blueman is a GTK+ Bluetooth Manager. In Blueman を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Summary

Original description

Auto-generated summary

Response actions

References