Axios dependency has several 9+ CVE issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the security issue
Our Snyk security scanning has indicated that the Axios dependency used in the logzio-nodejs package has some critical severity CVEs and is blocking our merge/deployment pipeline.
We are using logzio-nodejs@^2.1.5. This issue is still present in logzio-nodejs as of 2.5.0, however (https://github.com/logzio/logzio-nodejs/blob/8fc36dfc93053f411a06e675fa5bd9c7bcb19ee5/package.json#L53).
I wasn't sure if your team had been made aware of this yet. The vulnerabilities are quite new, and your open PRs show an update to Axios ^1.15.0 (https://github.com/logzio/logzio-nodejs/pull/147), but both CVEs were fixed with Axios 1.15.1.
I'll attach the Snyk reports on them here, for your review.
https://security.snyk.io/vuln/SNYK-JS-AXIOS-16299904
https://security.snyk.io/vuln/SNYK-JS-AXIOS-16298058
Please let me know if I can provide any more information.
### Additional context
_No response_
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
Inspect package.json at the Axios dependency on line 53 and compare the update proposed in pull request 147. Check the Snyk reports linked in the issue and verify that Axios 1.15.1 or later removes the reported CVEs and does not break the package's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100