CVE-2024-57081
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.fromQuery function of underscore-contrib v0.3.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 · moderate confidenceA prototype pollution vulnerability exists in the lib.fromQuery function of underscore-contrib v0.3.0, allowing attackers to manipulate JavaScript object prototypes via crafted input parameters. This can cause a Denial of Service by corrupting object behavior or causing unexpected application crashes.
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.
-
Locate underscore-contrib in your dependenciesSearch your package.json, package-lock.json, or node_modules directory for 'underscore-contrib'. In Node.js, run: grep -r 'underscore-contrib' node_modules/../package*.json 2>/dev/null or inspect package.json dependencies manually.Affected if underscore-contrib appears in your project's dependencies
-
Identify the installed versionCheck the version number in package-lock.json under underscore-contrib, or run: npm list underscore-contrib. Compare the version to v0.3.0 specifically.Affected if The installed version is exactly v0.3.0 or falls within the v0.3.0 release line
-
Verify the fromQuery function is accessibleSearch your codebase for imports or requires of 'underscore-contrib' and usage of 'fromQuery' (e.g., grep -r 'fromQuery' your source files). Check if the library is loaded server-side where attacker-controlled input can reach it.Affected if Your code imports underscore-contrib and calls the fromQuery function
-
Determine if fromQuery receives untrusted inputInspect how fromQuery is invoked. Look for query strings, URL parameters, request bodies, or user-controlled data passed to fromQuery without prior sanitization. Search for patterns like fromQuery(req.query) or similar.Affected if Data from HTTP request parameters, query strings, or other untrusted sources flows directly into fromQuery without validation
You are affected if underscore-contrib v0.3.0 is installed AND your application uses the fromQuery function with input that originates from untrusted sources such as HTTP request parameters or query strings.
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 underscore-contrib if available, or implement input validation/sanitization on the fromQuery function to reject prototype-polluting payloads. Consider using Object.freeze(Object.prototype) as a defense-in-depth measure.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57081 — 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-57081 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