# CVE-2023-46870: Misconfiguration in n/a

> Incorrect file permissions in nRF Sniffer for Bluetooth LE allow attackers to execute arbitrary code via modified scripts.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-q2m4-x7mj-qfqv

## What is CVE-2023-46870?

CVE-2023-46870 is a high-severity vulnerability in n/a, published on 13 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

extcap/nrf_sniffer_ble.py, extcap/nrf_sniffer_ble.sh, extcap/SnifferAPI/*.py in Nordic Semiconductor nRF Sniffer for Bluetooth LE 3.0.0, 3.1.0, 4.0.0, 4.1.0, and 4.1.1 have set incorrect file permission, which allows attackers to do code execution via modified bash and python scripts.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2023-46870 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46870 exists.

Public exploit code:

- https://github.com/Chapoly1305/CVE-2023-46870 (github_poc): https://github.com/Chapoly1305/CVE-2023-46870

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46870 is a high-severity vulnerability in n/a, published on 13 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46870 exists.

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-46870/ (Markdown: https://insights.sbomify.com/CVE-2023-46870/index.md)
```

## Sources

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

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