# CVE-2023-36480: Aerospike Java Client vulnerable to unsafe deserialization of server responses

> Attackers can execute arbitrary code on client machines by tricking them into connecting to a malicious Aerospike server that sends crafted serialized objects.

- **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:** Yes
- **Published:** 4 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-jj95-55cr-9597

## What is CVE-2023-36480?

CVE-2023-36480 is a critical unsafe deserialization vulnerability in aerospike-client-java, published on 4 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Aerospike Java client is a Java application that implements a network protocol to communicate with an Aerospike server. Prior to versions 7.0.0, 6.2.0, 5.2.0, and 4.5.0 some of the messages received from the server contain Java objects that the client deserializes when it encounters them without further validation. Attackers that manage to trick clients into communicating with a malicious server can include especially crafted objects in its responses that, once deserialized by the client, force it to execute arbitrary code. This can be abused to take control of the machine the client is running on. Versions 7.0.0, 6.2.0, 5.2.0, and 4.5.0 contain a patch for this issue.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

6 open source packages ship an affected version, including com.aerospike:aerospike-client. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.aerospike:aerospike-client` | Maven | All versions | 4.5.0 |
| `com.aerospike:aerospike-client` | Maven | All versions | 4.5.0 |
| `com.aerospike:aerospike-client` | Maven | From 5.0.0 | 5.2.0 |
| `com.aerospike:aerospike-client` | Maven | From 5.0.0 | 5.2.0 |
| `com.aerospike:aerospike-client` | Maven | From 6.0.0 | 6.2.0 |
| `com.aerospike:aerospike-client` | Maven | From 6.0.0 | 6.2.0 |

Products: Aerospike Aerospike Java Client.

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

Upgrade com.aerospike:aerospike-client to a fixed version for your release line: 4.5.0, 5.2.0 or 6.2.0.

## Is CVE-2023-36480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36480 is a critical unsafe deserialization vulnerability in aerospike-client-java, published on 4 Aug 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-36480 exists.

Affected packages and fixed versions:
- com.aerospike:aerospike-client (Maven): affected all versions; fixed in 4.5.0
- com.aerospike:aerospike-client (Maven): affected all versions; fixed in 4.5.0
- com.aerospike:aerospike-client (Maven): affected from 5.0.0; fixed in 5.2.0
- com.aerospike:aerospike-client (Maven): affected from 5.0.0; fixed in 5.2.0
- com.aerospike:aerospike-client (Maven): affected from 6.0.0; fixed in 6.2.0
- com.aerospike:aerospike-client (Maven): affected from 6.0.0; fixed in 6.2.0

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

## Sources

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

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