Vulnerability in pm2@5.3.0 CVE-2023-29017
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
- Synk caught a vulnerability in
vm2 < 3.9.15https://www.cve.org/CVERecord?id=CVE-2023-29017 - This packaged is used by
pm2@5.3.0 › @pm2/agent@2.0.1 › proxy-agent@5.0.0 › pac-proxy-agent@5.0.0 › pac-resolver@5.0.1 › degenerator@3.0.2 › vm2@3.9.14
How could we reproduce this issue?
Supporting information
- Solution would be to update vm2 dependency to > 3.9.15. Fixed by https://github.com/patriksimek/vm2/issues/515
$ pm2 report
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
Trace the reported chain from pm2@5.3.0 through @pm2/agent, proxy-agent, pac-proxy-agent, pac-resolver, and degenerator to vm2@3.9.14. Review the CVE-2023-29017 advisory and the linked vm2 fix; done means the packaged dependency resolves to a version newer than 3.9.15 and the vulnerability is no longer reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100