Security Digest · Vulnerability record
CVE-2024-28213: nGrinder vulnerable to unsafe Java objects deserialization
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.
CVSS 9.3 Critical EPSS 1.2% · p68
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 1.2%, percentile 68: FIRST’s model estimates a 1.2% chance of exploitation activity in the next 30 days, higher than 68% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
org.ngrinder:ngrinder-core(Maven) < 3.5.9, fixed in 3.5.9. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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 type: CWE-502.
Product: org.ngrinder:ngrinder-core (Maven) · Assigned by: naver · Published: 2024-03-07
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Maven | org.ngrinder:ngrinder-core | < 3.5.9 | 3.5.9 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| NAVER | nGrinder | see vendor advisory |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADP | 3.1 | 9.8 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 1.19% probability of exploitation activity in the next 30 days; percentile 68.
Timeline
- — CVE record published by naver
- — GitHub-reviewed advisory GHSA-j7jm-8gf5-frcm published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-j7jm-8gf5-frcm github.com
- CVE.org record CVE-2024-28213 cve.org
- NVD entry CVE-2024-28213 nvd.nist.gov
Other references from the CVE record and advisory
- NAVER Security Advisory cve.naver.com
- github.com github.com