# CVE-2023-2564: OS Command Injection in sbs20/scanservjs

> Attackers can execute arbitrary OS commands via OS Command Injection in scanservjs, requiring an upgrade to mitigate.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 7 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-h5q9-8q57-gqh2

## What is CVE-2023-2564?

CVE-2023-2564 is a critical command injection vulnerability in sbs20/scanservjs, published on 7 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS Command Injection in GitHub repository sbs20/scanservjs prior to v2.27.0.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Scanservjs Project Scanservjs.

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

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

## Is CVE-2023-2564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2564 is a critical command injection vulnerability in sbs20/scanservjs, published on 7 May 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-2564 exists.

Affected product: sbs20/scanservjs. 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-2564/ (Markdown: https://insights.sbomify.com/CVE-2023-2564/index.md)
```

## Sources

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

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