swagger-api / swagger-api/swagger-codegen
CVE-2021-3765 (High) detected in validator-10.11.0.tgz
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2021-3765 - High Severity Vulnerability
Vulnerable Library - validator-10.11.0.tgz
String validation and sanitization
Library home page: https://registry.npmjs.org/validator/-/validator-10.11.0.tgz
Path to dependency file: /samples/server/petstore/nodejs-google-cloud-functions/package.json
Path to vulnerable library: /samples/server/petstore/nodejs-google-cloud-functions/node_modules/validator/package.json,/samples/server/petstore/nodejs/node_modules/validator/package.json
Dependency Hierarchy:
- swagger-tools-0.10.1.tgz (Root Library)
- z-schema-3.25.1.tgz
- ❌ validator-10.11.0.tgz (Vulnerable Library)
- z-schema-3.25.1.tgz
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branch: master
Vulnerability Details
validator.js is vulnerable to Inefficient Regular Expression Complexity
Publish Date: 2021-11-02
URL: CVE-2021-3765
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
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-qgmg-gppg-76g5
Release Date: 2021-11-02
Fix Resolution: validator - 13.7.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting samples/server/petstore/nodejs-google-cloud-functions/package.json and the related Node.js dependency chain through swagger-tools and z-schema. Update the dependency resolution so validator is at least 13.7.0, then verify both reported node_modules paths no longer contain validator 10.11.0 and rerun the relevant sample dependency checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100