dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-57085

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A prototype pollution in the function deepMerge of @stryker-mutator/util v8.6.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.

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

This is a prototype pollution vulnerability in the deepMerge function of @stryker-mutator/util v8.6.0. Attackers can exploit this by supplying a crafted payload that manipulates JavaScript object prototypes, leading to denial of service.

MitigationUpgrade @stryker-mutator/util to a version beyond v8.6.0 that patches the prototype pollution vulnerability in deepMerge, or implement property validation in the deepMerge function to reject __proto__, constructor, and prototype properties.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if @stryker-mutator/util is installed
    Run 'npm list @stryker-mutator/util' or inspect your package.json dependencies section
    Affected if The package appears in your dependency tree
  2. Determine the installed version of @stryker-mutator/util
    Run 'npm list @stryker-mutator/util' and note the version number displayed, or check the version field in package.json
    Affected if The installed version is exactly v8.6.0
  3. Verify deepMerge is being used
    Search your codebase for imports of deepMerge from @stryker-mutator/util (e.g., 'import { deepMerge } from "@stryker-mutator/util"' or require statements)
    Affected if Your code imports and calls the deepMerge function
  4. Confirm external input reaches deepMerge
    Review the code paths where deepMerge is called and identify whether untrusted user data or external payloads are passed as arguments to this function
    Affected if Data from untrusted sources flows into deepMerge without prior sanitization

You are affected if @stryker-mutator/util version v8.6.0 is installed AND your application uses the deepMerge function with external input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade @stryker-mutator/util to a version beyond v8.6.0 that patches the prototype pollution vulnerability in deepMerge, or implement property validation in the deepMerge function to reject __proto__, constructor, and prototype properties.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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