dbcve.org
NgrinderApplication · Naver

CVE-2024-28211

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 connection to malicious JMX/RMI server by default, which could be the cause of executing arbitrary code via RMI registry by remote attacker.

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 has a dangerous default behavior where it connects to user-specified JMX/RMI servers without proper validation. A remote attacker can set up a malicious RMI registry that returns malicious serialized Java objects to the client, leading to arbitrary code execution via deserialization attack.

MitigationUpgrade to nGrinder 3.5.9 or later which disables automatic connection to untrusted JMX/RMI servers. If immediate upgrade is not possible, disable JMX/RMI agent functionality or restrict network access to only trusted JMX endpoints.

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. Check nGrinder version
    Locate the nGrinder installation directory and check the version file or startup banner. Common locations include the WAR file version, the controller's about page, or the ngrinder-runtime JAR version embedded in the installation.
    Affected if The installed version is earlier than 3.5.9 (for example, 3.5.8, 3.5.7, 3.5.6, or any version before 3.5.9).
  2. Identify JMX/RMI agent configuration
    Search the nGrinder installation for configuration files that specify JMX/RMI server addresses. Look for properties files or XML configuration files containing keys like 'jmx', 'rmi', 'agent', or 'monitor' that point to remote hostnames or IP addresses.
    Affected if JMX/RMI agent connections are configured to point to remote, untrusted servers.
  3. Verify JMX/RMI monitor functionality is enabled
    Check the nGrinder controller or agent configuration for monitor/JMX enable flags. Look for properties such as 'monitor.enabled', 'jmx.monitor.enabled', or similar boolean settings in the configuration.
    Affected if The JMX/RMI monitor functionality is turned on and the system connects to user-specified RMI registries automatically.
  4. Inspect network connections to RMI registries
    Review any scripts, configuration files, or database entries that define target RMI registry URLs. Examine how agents or the controller resolve and connect to RMI services during operation.
    Affected if The system is configured to dynamically connect to RMI registries specified by users without validation.

You are affected if nGrinder version is earlier than 3.5.9 AND JMX/RMI agent functionality is enabled, as this allows automatic connections to untrusted RMI servers that could deliver malicious deserialized objects.

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 to nGrinder 3.5.9 or later which disables automatic connection to untrusted JMX/RMI servers. If immediate upgrade is not possible, disable JMX/RMI agent functionality or restrict network access to only trusted JMX endpoints.

Recommended fix High confidence

3.5.9

  1. Identify all nGrinder installations running versions prior to 3.5.9
  2. Schedule upgrade during a maintenance window
  3. Backup existing nGrinder configuration and data
  4. Download nGrinder version 3.5.9 or later from the official source (github.com/naver/ngrinder)
  5. Stop the nGrinder service
  6. Install the upgraded version (3.5.9 or later)
  7. Verify the version upgrade was successful by checking the version number in the UI or logs
  8. Restart the nGrinder service

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

Fix this in Ngrinder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28211 — 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-28211 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