High severity vulnerability (axios)
See original GitHub issueAdding browser-sync
as a dependency results in npm audit
warning:
found 1 high severity vulnerability
Further details:
=== npm audit security report ===
┌──────────────────────────────────────────────────────────────────────────────┐
│ Manual Review │
│ Some vulnerabilities require your attention to resolve │
│ │
│ Visit https://go.npm.me/audit-guide for additional guidance │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Server-Side Request Forgery │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ axios │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.21.1 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ browser-sync [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ browser-sync > localtunnel > axios │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1594 │
└───────────────┴──────────────────────────────────────────────────────────────┘
found 1 high severity vulnerability in 212 scanned packages
1 vulnerability requires manual review. See the full report for details.
Steps to reproduce:
mkdir test && cd test
npm init
npm install -D browser-sync
npm audit
It looks like localtunnel
already has a GH issue on this: https://github.com/localtunnel/localtunnel/issues/377
So I guess we need to wait for localtunnel to fix the issue and then bump dependency here?
Ps. in the past a similar issue has happened (https://github.com/BrowserSync/browser-sync/issues/1695)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:20
- Comments:9
Top Results From Across the Web
High severity vulnerability (axios) · Issue #313
Cloning repository reveals: found 1 high severity vulnerability Investigating ... Run npm install axios@0.21.1 to resolve 1 vulnerability ...
Read more >1 high severity vulnerability Incorrect Comparison in axios ...
found 1 high severity vulnerability run npm audit fix to fix them, or npm audit for details. Result on npm audit. High Incorrect...
Read more >axios vulnerabilities
version published direct vulnerabilities
1.2.1 5 Dec, 2022 0. C. 0. H. 0. M. 0. L
1.2.0 22 Nov, 2022 0. C. 0. H. 0....
Read more >Potential security vulnerability found in the axios dependency
Known high severity security vulnerability detected in axios <= 0.18.0 defined in yarn.lock. Since the latest version is 0.18 that is indeed a...
Read more >Axios vulnerable to Server-Side Request Forgery
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) ... Security Bulletin: High severity vulnerabilities in libraries used by IBM ...
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 FreeTop 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
Top GitHub Comments
@thomas-gordon That worked for me. GitHub’s automated security updates couldn’t figure out how to make a PR for me since browser-sync’s version didn’t need to be updated. Uninstalling and re-installing browser-sync updated the localtunnel transitive dependency to 2.0.1 which updated the axios transitive dependency to 0.21.0, resolving the security issue.
Because there’s no need to do anything to browser-sync to resolve this now, this issue should be closed.
To expand on @mattwelke’s comment, the localtunnel dependency was upgraded from
1.9.2
to^2.0.0
back in July; so as soon as2.0.1
(which matches the^2.0.0
version spec) on localtunnel was released with the fix, any new installations of browser-sync will now automatically pick that up. Yay for caret version ranges!