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

> Attackers can inject Bash code via the queueUrl parameter to execute arbitrary commands with root privileges on Cassia Gateway devices.

- **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:** 10 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-89ph-wr9x-hcfc

## What is CVE-2023-31446?

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

### Official description

In Cassia Gateway firmware XC1000_2.1.1.2303082218 and XC2000_2.1.1.2303090947, the queueUrl parameter in /bypass/config is not sanitized. This leads to injecting Bash code and executing it with root privileges on device startup.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 2 products.


Products: Cassianetworks Xc1000 Firmware, Cassianetworks Xc2000 Firmware.

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

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

## Is CVE-2023-31446 being exploited?

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

Public exploit code:

- Repository contains description for CVE-2023-31446 (github_poc): https://github.com/Dodge-MPTC/CVE-2023-31446-Remote-Code-Execution
- Cassia Gateway Firmware - Remote Code Execution (nuclei): http/cves/2023/CVE-2023-31446.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31446 is a critical command injection vulnerability in n/a, published on 10 Jan 2024. 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-31446 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-31446/ (Markdown: https://insights.sbomify.com/CVE-2023-31446/index.md)
```

## Sources

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

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