Fix security vulnerability (lodash)
See original GitHub issueChore summary
yarn add @stoplight/spectral
yarn audit

Tasks Bump lodash version >= 4.17.21
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How to fix Seriate and Lodash vulnerabilities - Stack Overflow
2 Answers 2 · Check the “Path” field for the location of the vulnerability. · On the npm public registry, find the package...
Read more >lodash vulnerabilities | Snyk
version published direct vulnerabilities
4.17.21 20 Feb, 2021 0. C. 0. H. 0. M. 0. L
4.17.20 13 Aug, 2020 0. C. 1. H. 1....
Read more >Lodash : Security vulnerabilities - CVE Details
# CVE ID CWE ID Vulnerability Type(s) Publish Date Update Date Score Gaine...
1 CVE‑2021‑23337 94 2021‑02‑15 2022‑09‑13 6.5 None
2 CVE‑2020‑28500 DoS 2021‑02‑15 2022‑09‑13...
Read more >Security Bulletin: Lodash versions prior to 4.17.21 vulnerability ...
DESCRIPTION: Node.js lodash module is vulnerable to a denial of service, caused by a regular expression denial of service (ReDoS) in the ...
Read more >Lodash: Understanding the recent ... - DEV Community
We can fix it by freezing the Object with the JavaScript ES5 function Object.freeze() or by defining a null Object Object.create(null) . The ......
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 Free
Top 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
Would it make sense for the project to not use an exact version of dependencies, and instead use a version range ?
This would allow to address security vulnerabilities without needing to release new versions of
spectral
🤔i.e. by updating the
package.json
and instead of"lodash": "4.17.21",
, using things like"lodash": "^4.17.21",
-> any4.x
or
"lodash": "~4.17.21",
-> any4.17.x
Looks like #1585 solves this?