Nested dependency on a vulnerable package
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Locate the nested [email protected] dependency in the repository's dependency manifests or lockfile and review how it is resolved. Confirm the dependency can be updated to [email protected], then verify that the vulnerable version is no longer present and the two referenced advisories are addressed.
Written by the indexing model from the issue text.
Description
This project has a nested dependency on [email protected], which is vulnerable to CVE-2022-0235 and CVE-2020-15168
This needs to be updated to [email protected]
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
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.
More from loopbackio/loopback-connector-openapi
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in loopbackio/loopback-connector-openapi
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TheOdinProject/curriculum#31423 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
WGBH-MLA/dream-aapb#69 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Mintplex-Labs/anything-llm#6490 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
openlayers/ol-cesium#1364 ·