# CVE-2024-58101: Missing authorization in n/a

> Attackers can pair with Samsung Galaxy Buds by default to hijack audio playback or record microphone input without user consent.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-gwqp-vrqv-c9q6

## What is CVE-2024-58101?

CVE-2024-58101 is a high-severity missing authorization vulnerability in n/a, published on 14 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Samsung Galaxy Buds and Galaxy Buds 2 audio devices are Bluetooth pairable by default without user input nor a way to stop this mode. As a consequence, audio playback takeover or even microphone recording without user consent or notification is achieved. Note: This is considered a low severity vulnerability by the vendor.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-58101?


## How do I fix CVE-2024-58101?

No fix has been published for CVE-2024-58101 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-58101 being exploited?

There is no known exploitation of CVE-2024-58101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58101 and fix it if it is affected.

What it is: CVE-2024-58101 is a high-severity missing authorization vulnerability in n/a, published on 14 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58101 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58101/ (Markdown: https://insights.sbomify.com/CVE-2024-58101/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58101
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58101
- OSV: https://osv.dev/vulnerability/CVE-2024-58101

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58101/
Summaries are generated and may contain mistakes; the official description above is the record.