Security Resilience

CVE-2024-28213

RCE in Naver Ngrinder ≤ 3.5.9

Published
07 March 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.012 67th percentile
Risk Priority 79 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-28213 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Naver Ngrinder. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

nGrinder versions prior to 3.5.9 contain a deserialization flaw (CWE-502) that accepts serialized Java objects from remote, unauthenticated sources. The affected component is the application's network-facing object-handling logic, which performs unsafe deserialization without authentication or type validation, resulting in a CVSS 3.1 score of 9.8.

An unauthenticated attacker can send a crafted serialized object over the network to trigger arbitrary code execution. Successful exploitation grants the attacker full control over the confidentiality, integrity, and availability of the nGrinder instance, as indicated by the high impact metrics across all three categories.

The EPSS score has remained flat at 0.0812 with no material increase after disclosure. The version string in the CVE record indicates that upgrading to nGrinder 3.5.9 or later addresses the issue by eliminating acceptance of unauthenticated serialized objects.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-28212Same product: Naver Ngrinder
CVE-2024-28211Same product: Naver Ngrinder
CVE-2024-28216Same product: Naver Ngrinder
CVE-2024-28215Same product: Naver Ngrinder
CVE-2024-28214Same product: Naver Ngrinder
CVE-2026-4266Shared CWE-502
CVE-2025-60234Shared CWE-502
CVE-2026-109237Shared CWE-502
CVE-2019-10068Shared CWE-502
CVE-2026-22471Shared CWE-502

Affected Assets

naver
ngrinder
≤ 3.5.9

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 none match
blocks

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
removes
removes
removes
removes

References