dbcve.org
NgrinderApplication · Naver

CVE-2024-28215

HIGH · 7.5 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 3.5.9 or later.
See remediation →
84/100
Remediation priority · High
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 an attacker to create or update webhook configuration 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 configuration endpoints, allowing unauthenticated or unauthorized attackers to create or modify webhooks. This vulnerability can lead to information disclosure through webhook data exfiltration and limited Server-Side Request Forgery (SSRF) by manipulating webhook URLs to internal services.

MitigationUpgrade nGrinder to version 3.5.9 or later. If immediate patching is not possible, restrict network access to webhook configuration endpoints and audit existing webhook configurations for unauthorized changes.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
    Check the nGrinder version by inspecting the about page in the web UI, or check the version file in the nGrinder installation directory if accessible.
    Affected if The installed version is before 3.5.9
  2. Review existing webhook configurations
    Navigate to the webhook configuration section in the nGrinder admin or settings panel. Inspect all configured webhooks for unexpected URLs, especially those pointing to internal services, cloud metadata endpoints, or unfamiliar external domains.
    Affected if Webhooks exist with URLs pointing to internal infrastructure (127.0.0.1, localhost, 169.254.169.254, or private IP ranges) or to unknown external destinations
  3. Audit webhook creation and modification logs
    Review nGrinder server access logs and audit logs for POST, PUT, orPATCH requests to webhook-related endpoints (typically under /webhook or /admin/webhook paths). Look for requests originating from unexpected IP addresses or during unusual time periods.
    Affected if Webhook configuration changes are present in logs that were not initiated by authorized administrators
  4. Check for unauthorized webhook data exfiltration
    Inspect the content of configured webhooks to see if they include sensitive data patterns (API keys, tokens, authentication headers) that could be exfiltrated, or check webhook delivery history for outbound requests to unexpected destinations.
    Affected if Webhook payloads contain sensitive nGrinder data or webhook deliveries have been made to unknown external URLs

A system is affected if it runs nGrinder version before 3.5.9 AND has webhook configuration endpoints exposed or shows signs of unauthorized webhook modifications or suspicious outbound webhook requests.

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. If immediate patching is not possible, restrict network access to webhook configuration endpoints and audit existing webhook configurations for unauthorized changes.

Recommended fix High confidence

nGrinder 3.5.9

  1. 1. Back up your current nGrinder configuration, scripts, and database data
  2. 2. Download nGrinder version 3.5.9 or later from the official repository (https://github.com/naver/ngrinder)
  3. 3. Stop the running nGrinder service
  4. 4. Install the new version (3.5.9+) following the standard installation process for your deployment method (WAR file or Docker)
  5. 5. Restore your configuration and data from the backup
  6. 6. Start the nGrinder service
  7. 7. Verify the webhook functionality works correctly and that unauthorized users cannot modify webhook configurations

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

Fix this in Ngrinder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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