# CVE-2023-48887: Jupiter allows attackers to execute arbitrary commands via sending a crafted RPC request

> Attackers can execute arbitrary commands by sending crafted RPC requests to the Jupiter library due to unsafe deserialization.

- **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:** 1 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6pqx-v9g4-5hc8

## What is CVE-2023-48887?

CVE-2023-48887 is a critical unsafe deserialization vulnerability in n/a, published on 1 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A deserialization vulnerability in Jupiter v1.3.1 allows attackers to execute arbitrary commands via sending a crafted RPC request.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

2 open source packages ship an affected version, including org.jupiter-rpc:jupiter-rpc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jupiter-rpc:jupiter-rpc` | Maven | All versions to 1.3.1 | None |
| `org.jupiter-rpc:jupiter-rpc` | Maven | All versions to 1.3.1 | None |

Products: Fengjiachun Jupiter.

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

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

## Is CVE-2023-48887 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-48887 is a critical unsafe deserialization vulnerability in n/a, published on 1 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-48887 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jupiter-rpc:jupiter-rpc (Maven): affected all versions up to 1.3.1; no fix listed
- org.jupiter-rpc:jupiter-rpc (Maven): affected all versions up to 1.3.1; 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-48887/ (Markdown: https://insights.sbomify.com/CVE-2023-48887/index.md)
```

## Sources

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

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