dbcve.org
NgrinderApplication · Naver

CVE-2024-28216

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 3.5.9 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 an attacker to obtain the results of webhook requests due to lack of access control, which could be the cause of information disclosure and limited Server-Side Request Forgery.

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 · moderate confidence

nGrinder before version 3.5.9 lacks proper access control on webhook endpoints, allowing unauthenticated attackers to retrieve the results of webhook requests. This enables information disclosure of webhook response data and limited Server-Side Request Forgery (SSRF) where attackers can potentially trigger and capture responses from internal webhook callbacks.

MitigationUpgrade nGrinder to version 3.5.9 or later which includes proper access control enforcement on webhook endpoints. If upgrading is not immediately possible, restrict network access to webhook-related paths and monitor for unauthorized access patterns.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installed nGrinder version
    Locate the nGrinder installation and check its version number. Common locations include the admin UI header, about page, or version file in the installation directory. Compare the version to the affected range: any version before 3.5.9 is vulnerable.
    Affected if Installed version is before 3.5.9
  2. Confirm webhook functionality is in use
    Inspect the nGrinder configuration to determine if webhooks have been configured or enabled. Look for webhook-related settings in the admin interface or configuration files.
    Affected if Webhooks are configured or enabled on the system
  3. Test webhook endpoint accessibility
    Attempt to access webhook-related endpoints (typically under /webhook/ paths) without providing authentication credentials. Use a tool like curl to send a request to common webhook paths.
    Affected if Webhook endpoints respond to unauthenticated requests with valid HTTP responses instead of requiring login or returning 401/403 errors
  4. Check for exposed webhook response data
    If webhook endpoints are accessible, examine whether response data from webhook callbacks can be retrieved without authentication. Look for endpoints that return webhook execution results or response content.
    Affected if Webhook endpoints return sensitive response data to unauthenticated users

You are affected if nGrinder version is below 3.5.9 AND webhook functionality is enabled AND webhook endpoints are accessible without authentication.

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 includes proper access control enforcement on webhook endpoints. If upgrading is not immediately possible, restrict network access to webhook-related paths and monitor for unauthorized access patterns.

Recommended fix High confidence

3.5.9

  1. Backup your current nGrinder installation and configuration
  2. Stop the nGrinder service
  3. Download nGrinder version 3.5.9 or later from the official source (https://github.com/naver/ngrinder)
  4. Install or upgrade to the downloaded version
  5. Start the nGrinder service
  6. Verify the upgrade was successful and the webhooks function correctly

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

Fix this in Ngrinder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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