# CVE-2024-28213: nGrinder vulnerable to unsafe Java objects deserialization

> Remote attackers can execute arbitrary code by sending malicious serialized Java objects to unauthenticated users of nGrinder.

- **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:** 7 Mar 2024
- **Updated:** 22 Aug 2024
- **Also known as:** GHSA-j7jm-8gf5-frcm

## What is CVE-2024-28213?

CVE-2024-28213 is a critical unsafe deserialization vulnerability in NAVER nGrinder, published on 7 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

nGrinder before 3.5.9 allows to accept serialized Java objects from unauthenticated users, which could allow remote attacker to execute arbitrary code via unsafe Java objects deserialization.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-28213?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.ngrinder:ngrinder-core` | Maven | All versions | 3.5.9 |
| `org.ngrinder:ngrinder-core` | Maven | All versions | 3.5.9 |

Products: Naver Ngrinder.

## How do I fix CVE-2024-28213?

Upgrade org.ngrinder:ngrinder-core to 3.5.9 or later.

## Is CVE-2024-28213 being exploited?

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

## Other vulnerabilities in NAVER nGrinder

- [CVE-2024-28211](https://insights.sbomify.com/CVE-2024-28211/): Deserialization in nGrinder (critical 9.8)
- [CVE-2024-28212](https://insights.sbomify.com/CVE-2024-28212/): Deserialization in nGrinder (critical 9.8)
- [CVE-2024-28215](https://insights.sbomify.com/CVE-2024-28215/): Missing authorization in nGrinder (high 7.5)
- [CVE-2016-5060](https://insights.sbomify.com/CVE-2016-5060/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-28216](https://insights.sbomify.com/CVE-2024-28216/): Missing authorization in nGrinder (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28213 and fix it if it is affected.

What it is: CVE-2024-28213 is a critical unsafe deserialization vulnerability in NAVER nGrinder, published on 7 Mar 2024. 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-2024-28213 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.ngrinder:ngrinder-core (Maven): affected all versions; fixed in 3.5.9
- org.ngrinder:ngrinder-core (Maven): affected all versions; fixed in 3.5.9

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

## Sources

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

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