CVE-2024-57074
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 · uneditedA prototype pollution in the lib.merge function of xe-utils v3.5.31 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 · moderate confidenceA prototype pollution vulnerability in the lib.merge function of xe-utils v3.5.31 allows attackers to inject malicious properties into JavaScript object prototypes via crafted input, leading to Denial of Service. Prototype pollution occurs when the merge function doesn't properly validate or sanitize object keys, allowing an attacker to modify __proto__, constructor, or other 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 checksWork through these to decide whether this CVE applies to you.
-
Identify xe-utils versionRun 'npm list xe-utils' or check package.json for the installed xe-utils version numberAffected if The installed version is 3.5.31 exactly, or falls within a range including 3.5.31 and earlier unpatched versions
-
Locate lib.merge usageSearch codebase for calls to xe.utils.merge, lib.merge, or imports from xe-utils that include the merge function (e.g., 'const { merge } = require("xe-utils")' or similar patterns)Affected if The lib.merge or xe.utils.merge function is being called in your codebase
-
Inspect merge input sourcesReview all code paths that pass data into the merge function; check if input originates from untrusted sources such as user HTTP requests, JSON API responses, file uploads, or external APIsAffected if Untrusted or user-controlled data is passed directly to the merge function without prior sanitization
-
Verify prototype key filteringSearch for input validation logic that explicitly blocks or removes __proto__, constructor, and prototype keys before merge operations; look for code like 'delete obj.__proto__' or validation libraries in the merge call chainAffected if No validation exists to reject or sanitize prototype-related keys (__proto__, constructor, prototype) before merge is called
A user is affected if they are running xe-utils version 3.5.31 or earlier and passing untrusted input to the lib.merge function without filtering prototype-related keys.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of xe-utils that includes proper input validation in the lib.merge function. Until an update is available, validate and sanitize all input passed to merge operations, ensuring that prototype-related keys (__proto__, constructor, prototype) are rejected.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-57074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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