dbcve.org
NgrinderApplication · Naver

CVE-2024-28212

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 uses old version of SnakeYAML, which could allow remote attacker to execute arbitrary code via unsafe 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 includes an outdated SnakeYAML library with unsafe deserialization vulnerabilities. Attackers can exploit this by supplying malicious serialized YAML content, potentially achieving remote code execution on the affected system.

MitigationUpgrade nGrinder to version 3.5.9 or later which contains a patched SnakeYAML library, or update SnakeYAML to a secure version in the dependency chain.

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 version
    Check the nGrinder version by reviewing the application startup logs, the ngrinder.war or ngrinder-core JAR manifest, or the version file in the installation directory. Common locations include the WEB-INF/classes/version.txt within the deployed application or the version displayed in the nGrinder admin UI footer.
    Affected if The installed version is below 3.5.9 (for example, 3.5.8, 3.5.7, or earlier releases).
  2. Locate SnakeYAML library in the deployment
    Inspect the lib or WEB-INF/lib directory of the nGrinder installation for the snakeyaml.jar file. You can also search the classpath for 'org/yaml/snakeyaml' using a find command or by decompiling JARs in the deployment.
    Affected if SnakeYAML library is present and its version cannot be verified as patched against known unsafe deserialization flaws.
  3. Determine if YAML processing is enabled for external input
    Review nGrinder configuration files (such as ngrinder.properties, ngrinder-config.xml, or any custom Spring configuration) for features that accept YAML input. Look for YAML parsers being configured or for script upload/import functionality that processes user-supplied YAML content.
    Affected if The system is configured to accept, parse, or process YAML content from untrusted sources such as user-uploaded test scripts, external API inputs, or configuration imports.
  4. Check for exposed YAML parsing endpoints
    Examine the deployed application's exposed HTTP endpoints, REST controllers, or message consumers that handle YAML data. Use tools like 'grep -r "yaml"' on source or decompiled code, or review the Spring servlet mappings for controllers accepting YAML content types.
    Affected if There are accessible endpoints that accept YAML content (Content-Type: application/x-yaml or similar) without sanitization or security constraints.

You are affected if nGrinder version is below 3.5.9 AND the system processes or accepts YAML input from untrusted sources, allowing unsafe deserialization to be triggered through the outdated SnakeYAML library.

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 which contains a patched SnakeYAML library, or update SnakeYAML to a secure version in the dependency chain.

Recommended fix High confidence

3.5.9

  1. 1. Identify the current nGrinder version currently deployed in your environment
  2. 2. Create a backup of the nGrinder database, configuration files, and any custom scripts or data
  3. 3. Download nGrinder version 3.5.9 or later from the official repository (https://github.com/ngrinder/ngrinder)
  4. 4. Follow the nGrinder upgrade documentation to install the new version, ensuring to preserve your backed-up configuration
  5. 5. After upgrading, verify that the SnakeYAML library has been updated to a safe version by checking the dependency tree
  6. 6. Restart the nGrinder controller and agents
  7. 7. Validate that nGrinder functionality is intact and the vulnerability is resolved

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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