Vulnearability: content-type-parser@1.0.2
See original GitHub issueThe react-scripts@1.1.0
introduces a security issue, as properly described by Snky.io.
This is because this versions added (or updated) the dependency content-type-parser@1.0.2
, which leads to a security issue of Regular Expression Denial of Service (ReDoS).
All the information can be found on the links described above.
But, just in case, here is the remediation copied from snyk.io page:
Remediation
There is no fix for content-type-parser
. The package was renamed from content-type-parser
to whatwg-mimetype
, which fixes the issue in version 2.0.0.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
content-type-parser vulnerabilities - Snyk
Learn more about known vulnerabilities in the content-type-parser package. Parse the value of the Content-Type header. ... latest version. 1.0.2 ...
Read more >WS-2017-3757 (Medium) detected in content-type-parser-1.0 ...
all versions prior to 2.0.0 of content-type-parser npm package are vulnerable to ReDoS via the user agent parser. the vulnerability was fixed by...
Read more >Fixed in OpenSSL 1.0.2
In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to...
Read more >content-type-parser - npm
Parse the value of the Content-Type header. Latest version: 1.0.2, last published: 5 years ago. Start using content-type-parser in your ...
Read more >body-parser | Yarn - Package Manager
0 vulnerabilities. Node.js body parsing middleware ... Parse incoming request bodies in a middleware before your handlers, available under the req.body ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t understand how this vulnerability is relevant to what we do.
This package is only used for development (in tests), not for production. How can somebody possibly DDoS your development environment?
Exactly @wtgtybhertgeghgtwtg, I’m still pretty new to the react ecosystem. And the bot snyk.io warning freaked me out.
At least you guys are aware and in next releases, maybe on 2.0.0, i don’t know, it will be fixed.
I shall learn from once for all to setup the webpack myself. hehehe