dbcve.org
NgrinderApplication · Naver

CVE-2024-28213

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 3.5.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

nGrinder before version 3.5.9 contains an unsafe deserialization vulnerability where the application accepts serialized Java objects from unauthenticated users without proper validation. This allows remote attackers to send maliciously crafted serialized Java objects that, when deserialized, can lead to arbitrary code execution on the target system.

MitigationUpgrade nGrinder to version 3.5.9 or later to remediate the unsafe deserialization vulnerability. If immediate upgrade is not possible, consider network-level controls to restrict unauthorized access to the affected service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NgrinderApplication
Affected:< 3.5.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify nGrinder installation
    Locate the nGrinder installation directory. Common locations include /opt/ngrinder, /home/ngrinder, or a custom application directory. Check for the ngrinder-core WAR file or extracted directory.
    Affected if nGrinder is not installed on this system - the CVE does not apply
  2. Find the installed version
    Check the nGrinder version file or manifest. Common locations include: version.properties in the installation directory, the MANIFEST.MF file within the ngrinder-core JAR/WAR, or the startup logs that typically print the version on launch. Run: grep -r "version" <installation_dir> or examine startup logs for a version string like 'nGrinder X.X.X'.
    Affected if Unable to determine the version - manual inspection may be required
  3. Compare version to affected range
    Verify the installed version against the affected range. The vulnerability affects all versions before 3.5.9. Compare your detected version number (e.g., 3.5.8, 3.5.7, 3.5.0, 3.4.0) to 3.5.9.
    Affected if Installed version is less than 3.5.9 - the system is affected by CVE-2024-28213
  4. Check network exposure
    Determine if the nGrinder controller service is exposed to unauthenticated/untrusted network access. Review firewall rules, security groups, or network ACLs controlling access to the nGrinder web interface port (typically 8080 or 8443).
    Affected if The service is accessible from untrusted networks without authentication - the deserialization attack surface is exposed

The system is affected if nGrinder is installed and the version is below 3.5.9, especially if the service is network-accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.5.9 or later
Fixed in 3.5.9
Interim mitigation

Upgrade nGrinder to version 3.5.9 or later to remediate the unsafe deserialization vulnerability. If immediate upgrade is not possible, consider network-level controls to restrict unauthorized access to the affected service.

Recommended fix High confidence

nGrinder 3.5.9 or later

  1. 1. Back up your current nGrinder installation including configuration files and any custom scripts or data.
  2. 2. Download nGrinder version 3.5.9 or later from the official nGrinder repository or release page.
  3. 3. Stop the currently running nGrinder service.
  4. 4. Install the new version following the official nGrinder installation documentation for your deployment method (WAR file, Docker, or other).
  5. 5. Restore any custom configurations from the backup, ensuring they are compatible with the new version.
  6. 6. Start the nGrinder service.
  7. 7. Verify the application is running correctly and test essential functionality.
  8. 8. Confirm that deserialization is properly restricted and unauthenticated deserialized objects are no longer accepted.
Caveat Review the 3.5.9 release notes for any configuration or feature changes that may affect your existing setups

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ngrinder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28213 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data