dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-57076

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 lib.post function of ajax-request v1.2.3 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 confidence

A prototype pollution vulnerability in the lib.post function of ajax-request v1.2.3 allows attackers to inject properties into Object.prototype via crafted payloads, causing the application to crash or behave unexpectedly leading to Denial of Service.

MitigationUpgrade ajax-request to the latest version if a patch is available; otherwise, implement input validation and sanitization on all data passed to lib.post to block prototype pollution payloads.

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. Identify ajax-request installation
    Check package.json, package-lock.json, or node_modules/ajax-request/package.json for the ajax-request dependency and its version number
    Affected if ajax-request version 1.2.3 is installed
  2. Verify lib.post usage
    Search codebase for calls to lib.post or ajax.post function from the ajax-request library
    Affected if lib.post is being called in the application code
  3. Inspect data flow to lib.post
    Review the code paths that feed data into lib.post calls and check whether user-supplied input (request parameters, body data, headers) is passed directly without sanitization
    Affected if Unsanitized user input flows directly to lib.post without validation or filtering of special properties like __proto__ and constructor
  4. Check for prototype pollution indicators
    Inspect Object.prototype in the application runtime for unexpected enumerable properties, or check application logs for errors indicating crashes or unexpected behavior during request processing
    Affected if Object.prototype contains unexpected properties or the application exhibits crashes during ajax post operations

You are affected if ajax-request version 1.2.3 is installed, lib.post is used, and unsanitized user input can reach lib.post without filtering of prototype pollution payloads.

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 ajax-request to the latest version if a patch is available; otherwise, implement input validation and sanitization on all data passed to lib.post to block prototype pollution payloads.

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-57076 — 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-57076 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