You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /sample/Broadcast/package.json
Path to vulnerable library: /sample/Archiving/node_modules/path-to-regexp/package.json,/sample/Broadcast/node_modules/path-to-regexp/package.json,/sample/HelloWorld/node_modules/path-to-regexp/package.json
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Path to dependency file: /sample/Archiving/package.json
Path to vulnerable library: /sample/Archiving/node_modules/path-to-regexp/package.json,/sample/Broadcast/node_modules/path-to-regexp/package.json,/sample/HelloWorld/node_modules/path-to-regexp/package.json
path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. The regular expression that is vulnerable to backtracking can be generated in the 0.1.x release of path-to-regexp. Upgrade to 0.1.12. This vulnerability exists because of an incomplete fix for CVE-2024-45296.
mend-for-github-combot
changed the title
express-4.21.1.tgz: 1 vulnerabilities (highest severity is: 5.5)
express-4.21.1.tgz: 1 vulnerabilities (highest severity is: 7.5)
Dec 9, 2024
Vulnerable Library - express-4.21.1.tgz
Path to dependency file: /sample/Broadcast/package.json
Path to vulnerable library: /sample/Archiving/node_modules/path-to-regexp/package.json,/sample/Broadcast/node_modules/path-to-regexp/package.json,/sample/HelloWorld/node_modules/path-to-regexp/package.json
Found in HEAD commit: a7f0948738582b190c10062a408e10b28b6ec75d
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-52798
Vulnerable Library - path-to-regexp-0.1.10.tgz
Express style path to RegExp utility
Library home page: https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.10.tgz
Path to dependency file: /sample/Archiving/package.json
Path to vulnerable library: /sample/Archiving/node_modules/path-to-regexp/package.json,/sample/Broadcast/node_modules/path-to-regexp/package.json,/sample/HelloWorld/node_modules/path-to-regexp/package.json
Dependency Hierarchy:
Found in HEAD commit: a7f0948738582b190c10062a408e10b28b6ec75d
Found in base branch: main
Vulnerability Details
path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. The regular expression that is vulnerable to backtracking can be generated in the 0.1.x release of path-to-regexp. Upgrade to 0.1.12. This vulnerability exists because of an incomplete fix for CVE-2024-45296.
Publish Date: 2024-12-05
URL: CVE-2024-52798
Threat Assessment
Exploit Maturity: Not Defined
EPSS: 0.0%
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-rhx6-c78j-4q9w
Release Date: 2024-12-05
Fix Resolution: path-to-regexp - 0.1.12
The text was updated successfully, but these errors were encountered: