Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump [email protected] dependency to fix Snyk vulnerability #243

Open
darinspivey opened this issue Aug 16, 2024 · 0 comments
Open

Bump [email protected] dependency to fix Snyk vulnerability #243

darinspivey opened this issue Aug 16, 2024 · 0 comments

Comments

@darinspivey
Copy link

Summary

Snyk is reporting a "Missing Release of Resource after Effective Lifetime" vulnerability in [email protected], which is introduced by its dependency of inflight. [email protected] is the most recent, and the vulnerability has since been removed several versions ago. In fact, inflight is now a deprecated package.

Details

Security information

Factors contributing to the scoring:
Snyk: CVSS v3.1 6.2 - Medium Severity
NVD: NVD only publishes analysis of vulnerabilities which are assigned a CVE ID. This vulnerability currently does not have an assigned CVE ID.
Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview
Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime via the makeres function due to improperly deleting keys from the reqs object after execution of callbacks. This behavior causes the keys to remain in the reqs object, which leads to resource exhaustion.

Exploiting this vulnerability results in crashing the node process or in the application crash.

Note: This library is not maintained, and currently, there is no fix for this issue. To overcome this vulnerability, several dependent packages have eliminated the use of this library.

To trigger the memory leak, an attacker would need to have the ability to execute or influence the asynchronous operations that use the inflight module within the application. This typically requires access to the internal workings of the server or application, which is not commonly exposed to remote users. Therefore, “Attack vector” is marked as “Local”.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant