swagger-api / swagger-api/swagger-codegen
CVE-2017-16138 (High) detected in mime-1.3.4.tgz
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2017-16138 - High Severity Vulnerability
Vulnerable Library - mime-1.3.4.tgz
A comprehensive library for mime-type mapping
Library home page: https://registry.npmjs.org/mime/-/mime-1.3.4.tgz
Path to dependency file: /samples/dynamic-html/package.json
Path to vulnerable library: /samples/dynamic-html/node_modules/mime/package.json,/samples/server/petstore/nodejs-google-cloud-functions/node_modules/superagent/node_modules/mime/package.json,/samples/server/petstore/nodejs/node_modules/superagent/node_modules/mime/package.json
Dependency Hierarchy:
- express-3.21.2.tgz (Root Library)
- send-0.13.0.tgz
- ❌ mime-1.3.4.tgz (Vulnerable Library)
- send-0.13.0.tgz
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branches: 3.0.0, master
Vulnerability Details
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.
Publish Date: 2018-06-07
URL: CVE-2017-16138
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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138
Release Date: 2018-06-07
Fix Resolution (mime): 1.4.1
Direct dependency fix Resolution (express): 4.0.0
- Check this box to open an automated fix PR
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 with /samples/dynamic-html/package.json and inspect how express resolves mime-1.3.4; also check the listed superagent dependency paths under the petstore samples. Update the dependency resolution to a fixed mime release or the stated express resolution, then verify that the vulnerable mime package is no longer present in these paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, node.js
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100