# CVE-2024-0230: Information disclosure in Magic Keyboard Firmware

> An attacker with physical access can extract Bluetooth pairing keys and monitor traffic from the Magic Keyboard.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 12 Jan 2024
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-mmg6-j6rr-w793

## What is CVE-2024-0230?

CVE-2024-0230 is a low-severity vulnerability in Apple Magic Keyboard Firmware, published on 12 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A session management issue was addressed with improved checks. This issue is fixed in Magic Keyboard Firmware Update 2.0.6. An attacker with physical access to the accessory may be able to extract its Bluetooth pairing key and monitor Bluetooth traffic.

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

It affects 1 product.


Products: Apple Magic Keyboard Firmware.

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

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

## Is CVE-2024-0230 being exploited?

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

Public exploit code:

- Helper script to POC of CVE-2024-0230 Bluetooth (github_poc): https://github.com/keldnorman/cve-2024-0230-blue

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0230 is a low-severity vulnerability in Apple Magic Keyboard Firmware, published on 12 Jan 2024. 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-0230 in the wild and no public exploit code.

Affected product: Apple Magic Keyboard Firmware. 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-0230/ (Markdown: https://insights.sbomify.com/CVE-2024-0230/index.md)
```

## Sources

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

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