LiveActive security incident?Get immediate response
CVE Record

CVE-2022-39176: BlueZ before 5.59 allows physically proximate attackers to obtain sensitive information because profiles/au...

BlueZ before 5.59 allows physically proximate attackers to obtain sensitive information because profiles/audio/avrcp.c does not validate params_len.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects BlueZ, the Linux Bluetooth stack, before version 5.59. A nearby attacker could trigger improper AVRCP parameter handling and potentially access sensitive information. The public record rates it high severity, but the provided sources do not show confirmed active exploitation.

Executive priority

Prioritize remediation where Bluetooth is enabled on business endpoints, Linux appliances, or operational systems. The issue is high severity, proximity-limited, and should be addressed through normal security patch cycles unless critical assets rely on affected Bluetooth functionality.

Technical view

CVE-2022-39176 is a BlueZ AVRCP parsing issue in profiles/audio/avrcp.c where params_len was not validated. The CVSS 3.1 score is 8.8 with adjacent attack vector, low complexity, no privileges, and no user interaction. Public data identifies BlueZ before 5.59 as affected.

Likely exposure

Exposure is most likely on Linux systems, embedded devices, or appliances using BlueZ before 5.59 with Bluetooth enabled or reachable by a physically proximate attacker. NetApp, Ubuntu, and Debian references indicate downstream packaging and product impact should be checked.

Exploitation context

The CVE requires proximity consistent with Bluetooth attack conditions. The source bundle lists KEV as false and provides no cited evidence of active exploitation. Treat exploitation status as unconfirmed, not absent.

Researcher notes

The strongest technical detail in the supplied sources is missing params_len validation in BlueZ AVRCP code. The bundle does not provide a CWE, exploit details, or complete affected CPEs, so validation should focus on package/version evidence and vendor advisories.

Mitigation direction

  • Upgrade BlueZ to version 5.59 or a vendor-fixed package.
  • Apply Ubuntu, Debian, NetApp, or other vendor security updates where applicable.
  • Disable Bluetooth on systems that do not require it.
  • Review vendor advisories for product-specific fixed versions and deployment notes.
  • Prioritize exposed workstations, servers, and appliances with active Bluetooth adapters.

Validation and detection

  • Inventory systems running BlueZ and record package versions.
  • Confirm no in-scope system runs BlueZ before 5.59.
  • Check whether Bluetooth services and adapters are enabled.
  • Compare installed packages against Ubuntu and Debian security notices.
  • For NetApp products, verify applicability against the NetApp advisory.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-39176 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-39176Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.