# CVE-2023-49914: Denial of service in n/a

> Remote attackers can disrupt meditation tracking accuracy by injecting false brain wave signals via RF, misleading the companion app.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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:** 2 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-gqph-3889-qrcx

## What is CVE-2023-49914?

CVE-2023-49914 is a medium-severity denial of service vulnerability in n/a, published on 2 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

InteraXon Muse 2 devices allow remote attackers to cause a denial of service (incorrect Muse App report of an outstanding, calm meditation state) via a 480 MHz RF carrier that is modulated by a "false" brain wave, aka a Brain-Hack attack. For example, the Muse App does not display the reception of a strong RF carrier, and alert the user that a report may be misleading if this carrier has been modulated by a low-frequency signal.

## Which versions are affected by CVE-2023-49914?

It affects 1 product.


Products: Choosemuse Muse 2 Firmware.

## How do I fix CVE-2023-49914?

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

## Is CVE-2023-49914 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49914 and fix it if it is affected.

What it is: CVE-2023-49914 is a medium-severity denial of service vulnerability in n/a, published on 2 Dec 2023. 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-2023-49914 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-2023-49914/ (Markdown: https://insights.sbomify.com/CVE-2023-49914/index.md)
```

## Sources

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

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