swagger-api / swagger-api/swagger-codegen
CVE-2022-24434 (High) detected in dicer-0.2.5.tgz
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2022-24434 - High Severity Vulnerability
Vulnerable Library - dicer-0.2.5.tgz
A very fast streaming multipart parser for node.js
Library home page: https://registry.npmjs.org/dicer/-/dicer-0.2.5.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/dicer/package.json,/samples/server/petstore/nodejs/node_modules/dicer/package.json
Dependency Hierarchy:
- swagger-tools-0.10.1.tgz (Root Library)
- multer-1.4.2.tgz
- busboy-0.2.14.tgz
- ❌ dicer-0.2.5.tgz (Vulnerable Library)
- busboy-0.2.14.tgz
- multer-1.4.2.tgz
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branches: 3.0.0, master
Vulnerability Details
This affects all versions of package dicer. A malicious attacker can send a modified form to server, and crash the nodejs service. An attacker could sent the payload again and again so that the service continuously crashes.
Publish Date: 2022-05-20
URL: CVE-2022-24434
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
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 dependency path through swagger-tools, multer, and busboy; compare it with the nodejs sample path mentioned in the report. Confirm how dicer-0.2.5 is introduced and use the CVE details to determine the required dependency remediation. Done means the affected sample dependencies no longer resolve to the vulnerable dicer package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100