eazy-logger 4.0.1 lib.Logger prototype pollution

Summaryinfo

A vulnerability, which was classified as problematic, has been found in eazy-logger 4.0.1. This affects the function lib.Logger. Performing a manipulation results in prototype pollution. This vulnerability was named CVE-2024-57075. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic has been found in eazy-logger 4.0.1. This affects the function lib.Logger. The manipulation with an unknown input leads to a prototype pollution vulnerability. CWE is classifying the issue as CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. This is going to have an impact on availability. The summary by CVE is:

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.

The advisory is shared at gist.github.com. This vulnerability is uniquely identified as CVE-2024-57075 since 01/09/2025. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-53518). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Log Management Software

Name

• eazy-logger

Version

• 4.0.1

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion