# CVE-2023-31826: Command injection in nevado-jms

> Attackers can execute arbitrary commands by sending crafted messages to the Nevado JMS library due to missing security checks.

- **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:** 23 May 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-7gm3-mwjw-j53w

## What is CVE-2023-31826?

CVE-2023-31826 is a high-severity command injection vulnerability in n/a, published on 23 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Skyscreamer Open Source Nevado JMS v1.3.2 does not perform security checks when receiving messages. This allows attackers to execute arbitrary commands via supplying crafted data.

Weakness: CWE-862 (Missing Authorization)

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

2 open source packages ship an affected version, including org.skyscreamer:nevado-jms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.skyscreamer:nevado-jms` | Maven | All versions to 1.3.2 | None |
| `org.skyscreamer:nevado-jms` | Maven | All versions to 1.3.2 | None |

Products: Skyscreamer Nevado Jms.

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

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

## Is CVE-2023-31826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31826 is a high-severity command injection vulnerability in n/a, published on 23 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31826 exists.

Affected packages and fixed versions:
- org.skyscreamer:nevado-jms (Maven): affected all versions up to 1.3.2; no fix listed
- org.skyscreamer:nevado-jms (Maven): affected all versions up to 1.3.2; no fix listed

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

## Sources

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

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