Security vulnerability in old version of lodash
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 25.9k
- Forks
- 2.4k
- Avg merge
- 13h 10m
- Merged PRs (30d)
- 4
Description
Describe the bug
The redoc/benchmark/index.html file references an obsolete version of lodash (4.17.4) with a known vulnerability that was fixed in later versions. The latest version is 4.17.21, which seems to have fixed the problem. Could the vulnerable version be replaced with the fixed version? Is the benchmark folder necessary to run redoc?
Expected behavior
I expected redoc to pass muster with the security team at my company, but it was rejected because of the known vulnerability. See attached file.
Redoc ML-vulnerability-report.xlsx
Minimal reproducible OpenAPI snippet(if possible)
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
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 redoc/benchmark/index.html and inspect how its lodash reference is used. Check whether the benchmark folder is still required by the project, then verify the dependency version against the reported vulnerability. Done means the obsolete reference is replaced or its necessity is clarified without leaving the known vulnerable version in use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100