Service interruption via unsafe configuration merge
Published Feb 5, 2025 · Updated Mar 13, 2025
Prototype pollution in eazy-logger 4.0.1 and earlier allows attackers to interrupt service through a crafted Logger configuration. Logger passes attacker-controlled configuration to lodash merge without first excluding prototype-related keys, allowing properties such as proto to modify Object.prototype. Exploitation requires a consuming application to pass attacker-controlled configuration into Logger; polluted global prototype properties can then disrupt its Node.js process.
Summary
What happened
Prototype pollution in eazy-logger 4.0.1 and earlier allows attackers to interrupt service through a crafted Logger configuration. Logger passes attacker-controlled configuration to lodash merge without first excluding prototype-related keys, allowing properties such as proto to modify Object.prototype. Exploitation requires a consuming application to pass attacker-controlled configuration into Logger; polluted global prototype properties can then disrupt its Node.js process.
The record
- CVE
- CVE-2024-57075
- Published
- Feb 5, 2025
- Updated
- Mar 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, CWE-1321, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2025CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Logger prototype-pollution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo