dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-57075

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.Logger function of eazy-logger v4.0.1 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

Prototype pollution vulnerability in the lib.Logger function of the eazy-logger npm package v4.0.1 allows attackers to inject malicious properties into JavaScript prototype objects via crafted payload input, leading to application denial of service.

MitigationUpgrade to a patched version of eazy-logger if available; otherwise remove or replace the library. Implement strict input validation on any data reaching the Logger function and consider freezing Object.prototype to block prototype modifications.

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 if eazy-logger is installed
    Search for 'eazy-logger' in package.json dependencies, or check node_modules/eazy-logger/package.json for the package
    Affected if The package is listed as a dependency
  2. Determine installed version of eazy-logger
    Check the version field in node_modules/eazy-logger/package.json or the version entry in package-lock.json for eazy-logger
    Affected if Version is 4.0.1 or falls within the v4.x range without a patch applied
  3. Find code using the Logger function
    Search codebase for require('eazy-logger').Logger or import { Logger } from 'eazy-logger' and identify all call sites
    Affected if The Logger function is imported and invoked in the codebase
  4. Check if Logger receives untrusted input
    Review each Logger call site to determine whether the argument values originate from user request data, query parameters, body input, HTTP headers, or other external sources
    Affected if User-controlled or external data is passed directly to the Logger function without sanitization

You are affected if eazy-logger v4.0.1 is installed and external input reaches the Logger function without validation.

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 to a patched version of eazy-logger if available; otherwise remove or replace the library. Implement strict input validation on any data reaching the Logger function and consider freezing Object.prototype to block prototype modifications.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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