# CVE-2023-6691: Code Injection vulnerability in Cambium ePMP Force 300-25

> Attackers can inject code to achieve remote code execution and gain root privileges on Cambium ePMP Force 300-25 devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-x6q7-3r54-hvf2

## What is CVE-2023-6691?

CVE-2023-6691 is a high-severity code injection vulnerability in Cambium  ePMP Force 300-25, published on 18 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cambium ePMP Force 300-25 version 4.7.0.1 is vulnerable to a code injection vulnerability that could allow an attacker to perform remote code execution and gain root privileges.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Cambiumnetworks Epmp Force 300-25 Firmware.

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

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

## Is CVE-2023-6691 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6691 is a high-severity code injection vulnerability in Cambium  ePMP Force 300-25, published on 18 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-6691 in the wild and no public exploit code.

Affected product: Cambium  ePMP Force 300-25. 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-6691/ (Markdown: https://insights.sbomify.com/CVE-2023-6691/index.md)
```

## Sources

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

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