Serverless Examples – A collection of boilerplates and examples of serverless architectures built with the Serverless Framework on AWS Lambda, Microsoft Azure, Google Cloud Functions, and more.
Path to dependency file: /aws-dotnet-rest-api-with-dynamodb/src/DotNetServerless.Lambda/package.json
Path to vulnerable library: /aws-dotnet-rest-api-with-dynamodb/src/DotNetServerless.Lambda/node_modules/path-to-regexp/package.json,/aws-node-express-api/node_modules/path-to-regexp/package.json,/aws-node-mongodb-atlas/node_modules/path-to-regexp/package.json,/aws-node-typescript-nest/node_modules/express/node_modules/path-to-regexp/package.json,/aws-node-heroku-postgres/node_modules/path-to-regexp/package.json,/aws-node-express-dynamodb-api/node_modules/path-to-regexp/package.json,/aws-node-fullstack/frontend/node_modules/path-to-regexp/package.json,/aws-node-graphql-and-rds/node_modules/path-to-regexp/package.json
Path to dependency file: /aws-node-twilio-send-text-message/package.json
Path to vulnerable library: /aws-node-twilio-send-text-message/node_modules/path-to-regexp/package.json,/aws-node-rest-api-typescript/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. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.
CVE-2024-45296 - High Severity Vulnerability
Vulnerable Libraries - path-to-regexp-2.2.1.tgz, path-to-regexp-0.1.7.tgz, path-to-regexp-1.8.0.tgz
path-to-regexp-2.2.1.tgz
Express style path to RegExp utility
Library home page: https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-2.2.1.tgz
Path to dependency file: /aws-node-typescript-nest/package.json
Path to vulnerable library: /aws-node-typescript-nest/node_modules/path-to-regexp/package.json
Dependency Hierarchy: - core-5.5.0.tgz (Root Library) - :x: **path-to-regexp-2.2.1.tgz** (Vulnerable Library)
path-to-regexp-0.1.7.tgz
Express style path to RegExp utility
Library home page: https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.7.tgz
Path to dependency file: /aws-dotnet-rest-api-with-dynamodb/src/DotNetServerless.Lambda/package.json
Path to vulnerable library: /aws-dotnet-rest-api-with-dynamodb/src/DotNetServerless.Lambda/node_modules/path-to-regexp/package.json,/aws-node-express-api/node_modules/path-to-regexp/package.json,/aws-node-mongodb-atlas/node_modules/path-to-regexp/package.json,/aws-node-typescript-nest/node_modules/express/node_modules/path-to-regexp/package.json,/aws-node-heroku-postgres/node_modules/path-to-regexp/package.json,/aws-node-express-dynamodb-api/node_modules/path-to-regexp/package.json,/aws-node-fullstack/frontend/node_modules/path-to-regexp/package.json,/aws-node-graphql-and-rds/node_modules/path-to-regexp/package.json
Dependency Hierarchy: - graphql-yoga-1.17.4.tgz (Root Library) - express-4.17.1.tgz - :x: **path-to-regexp-0.1.7.tgz** (Vulnerable Library)
path-to-regexp-1.8.0.tgz
Express style path to RegExp utility
Library home page: https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-1.8.0.tgz
Path to dependency file: /aws-node-twilio-send-text-message/package.json
Path to vulnerable library: /aws-node-twilio-send-text-message/node_modules/path-to-regexp/package.json,/aws-node-rest-api-typescript/node_modules/path-to-regexp/package.json
Dependency Hierarchy: - sinon-9.2.4.tgz (Root Library) - nise-4.1.0.tgz - :x: **path-to-regexp-1.8.0.tgz** (Vulnerable Library)
Found in HEAD commit: dcbe4aefe4b3685f4b15493a01db0f19b118a0c4
Found in base branch: master
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. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.
Publish Date: 2024-09-09
URL: CVE-2024-45296
CVSS 3 Score Details (7.5)
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j
Release Date: 2024-09-09
Fix Resolution (path-to-regexp): 8.0.0
Direct dependency fix Resolution (@nestjs/core): 6.0.0
Fix Resolution (path-to-regexp): 8.0.0
Direct dependency fix Resolution (graphql-yoga): 1.18.0
Step up your Open Source Security Game with Mend here