Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect security advisory on npmjs.com #383

Closed
FreekVR opened this issue May 7, 2021 · 6 comments
Closed

Incorrect security advisory on npmjs.com #383

FreekVR opened this issue May 7, 2021 · 6 comments

Comments

@FreekVR
Copy link

FreekVR commented May 7, 2021

Hi,

I sent this issue to npm support but they referred me back here :)

In a recent advisory on npmjs a vulnerability was disclosed: https://www.npmjs.com/advisories/1500/versions

It doesn't report 5.0.1 as unaffected while it DOES include 5.0.0-security.0 as unafffected -- and this is additionally inconsistent with the Snyk report here: https://snyk.io/vuln/SNYK-JS-YARGSPARSER-560381

Is it possible to get this remedied? Sorry if this is the wrong place to ask, but NPM support wasn't getting my anywhere so far :)

@mvangeest
Copy link

npm audit etc. no longer report 5.0.1 as affected, probably since npm audit switched to the GitHub Advisory Database; they list 5.0.1 as patched.

@bcoe bcoe closed this as completed Nov 8, 2021
@bcoe
Copy link
Member

bcoe commented Nov 8, 2021

@mvangeest thanks for confirmation this is fixed 👍

@FreekVR let me know if you continue to bump into any issues.

@jeran-urban
Copy link

jeran-urban commented Nov 15, 2022

@bcoe just wanted to verify, this fix was backported to 5.0.1 in commit 1c417bd, 5.0.1 is safe from vulnerability CVE-2020-7608
, and github advisory and Snyk are correct, but other sources are not correct? please confirm and I will put in a request for the other agencies to update and report the correct version to avoid this in future

@bcoe
Copy link
Member

bcoe commented Nov 17, 2022

v5.0.1 is patched:

#363

@jeran-urban
Copy link

jeran-urban commented Nov 18, 2022

Thank you for the verification, I have submitted to NVD and they have corrected the entry, still waiting on the CVE from Mitre and the OSS INDEX from Sonatype to update per the requests as well.

@jeran-urban
Copy link

OSS INDEX has been updated and reflects no issues as well. The last one is the CVE which will take awhile, with these two changes, security scans should not show it as an issue as these dbs are normally prioritized over the root cve finding. Thank you again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants