Warnings for vulnerabilities in Ubuntu 20.04
See original GitHub issueThe app works correctly, but at the time of installing it, +22 warnings were presented for vulnerabilities, most of which I solved with --force
in Ubuntu 20.04.
I cloned the project this way:
git clone https://github.com/Rob--W/cors-anywhere.git
With this I get the project updated or should I download it manually from here?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Ubuntu Security Notices
Developers issue an Ubuntu Security Notice when a security issue is fixed in an official Ubuntu package. To report a security vulnerability in...
Read more >Canonical Ubuntu Linux version 20.04 : Security vulnerabilities
# CVE ID CWE ID Vulnerability Type(s) Publish Date Update Date Score
1 CVEβ2022β0492 287 Bypass 2022β03β03 2022β10β19 6.9
2 CVEβ2021β44420 Bypass 2021β12β08 2022β07β12 7.5
3...
Read more >Red Hat, Ubuntu issue warnings over Linux kernel vulnerability
Red Hat and Ubuntu have issued warnings about a serious vulnerability in their Linux distributions. It's described as a heap-based bufferΒ ...
Read more >Ubuntu Security Advisory (AV22-536)
Between 20 and 25 September 2022, Ubuntu published Security Notices to address vulnerabilities in the Linux kernel affecting the followingΒ ...
Read more >Ubuntu Security Advisories - Linuxlookup
USN-5638-1 fixed a vulnerability in Expat. This update provides the corresponding updates for Ubuntu 16.04 ESM, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS,Β ...
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 Free
Top 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
The only non-dev dependency reported by
npm audit
is http-proxy:As mentioned in https://www.npmjs.com/advisories/1486, the server may crash when the
proxyReq.setHeader
method is used. My library doesnβt use this event+method and is therefore not vulnerable.Do not blindly bump dependencies. As mentioned in https://github.com/Rob--W/cors-anywhere/issues/254#issuecomment-659037020, there is only one non-dev dependency. devDependencies are not used when you use CORS Anywhere, only if you develop it and run tests.
CORS Anywhere uses a specific version of http-proxy because it hooks some internals in order to provide the necessary functionality. There is a chance that bumping the http-proxy version would result in broken functionality, so donβt bump it.
This report is a duplicate of #253 by the way, so Iβm going to close this as a duplicate of that other issue. Thanks for contributing useful comments.