Skip to content
This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2022-39177 →
Unrated

Vulnerability in bluez

UBUNTU-CVE-2022-39177 First seen on SecPulse

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 UBUNTU-CVE-2022-39177 has been found in bluez.
Successful exploitation can lead to full system takeover.
What to do: upgrade bluez to 5.48-0ubuntu3.9 or later.
If unsure, ask your IT team or search "bluez UBUNTU-CVE-2022-39177" on the vendor's site.

UBUNTU-CVE-2022-39177 (bluez)
Attack vector: adjacent-network / unauthenticated / no user interaction
Patched: 5.48-0ubuntu3.9 — apply immediately
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 bluez.

Affected scope

Check the vendor advisory for the affected versions of bluez.

Severity

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

How to fix

Update to 5.48-0ubuntu3.9.

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. Run grep -r 'bluez' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposureidentify
    grep -r 'bluez' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で bluez を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade bluez to 5.48-0ubuntu3.9

    ステージング環境で 5.48-0ubuntu3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Ubuntu:Pro:16.04:LTS bluez
All versions
—
Ubuntu:18.04:LTS bluez
< 5.48-0ubuntu3.9
5.48-0ubuntu3.9
Ubuntu:20.04:LTS bluez
< 5.53-0ubuntu3.6
5.53-0ubuntu3.6
Original description The description as published by the source.

BlueZ before 5.59 allows physically proximate attackers to cause a denial of service because malformed and invalid capabilities can be processed in profiles/audio/avdtp.c.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details