# CVE-2023-31465: Command injection in n/a

> Attackers can execute arbitrary Bash commands on FSMLabs TimeKeeper servers by injecting code into URL query parameters.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2023
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-7xq6-44ph-rwqf

## What is CVE-2023-31465?

CVE-2023-31465 is a critical command injection vulnerability in n/a, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in FSMLabs TimeKeeper 8.0.17 through 8.0.28. By intercepting requests from various timekeeper streams, it is possible to find the getsamplebacklog call. Some query parameters are passed directly in the URL and named arg[x], with x an integer starting from 1; it is possible to modify arg[2] to insert Bash code that will be executed directly by the server.

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

It affects 1 product.


Products: Fsmlabs Timekeeper.

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

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

## Is CVE-2023-31465 being exploited?

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

Public exploit code:

- TimeKeeper by FSMLabs - Remote Code Execution (nuclei): http/cves/2023/CVE-2023-31465.yaml

## Other vulnerabilities in n/a

- [CVE-2023-31466](https://insights.sbomify.com/CVE-2023-31466/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31465 is a critical command injection vulnerability in n/a, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31465 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-31465/ (Markdown: https://insights.sbomify.com/CVE-2023-31465/index.md)
```

## Sources

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

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