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

Backported fix for CVE-2021-23440 to 2.0.1 #47

Open
noren95 opened this issue Apr 2, 2023 · 1 comment
Open

Backported fix for CVE-2021-23440 to 2.0.1 #47

noren95 opened this issue Apr 2, 2023 · 1 comment

Comments

@noren95
Copy link

noren95 commented Apr 2, 2023

Hi,

According to some public reports (i.e GHSA-4jqc-8m5r-9rpr, https://www.cve.org/CVERecord?id=CVE-2021-23440)
,CVE-2021-23440 is fixed in 4.0.1 along with a backport to 2.0.1.

As is understand, this is the fix for 4.0.1: 383b72d
That was reached via 4.0.0...4.0.1.

However, when inspecting the changelog between 2.0.0 and 2.0.1 (2.0.0...2.0.1), it seems the fix for CVE-2021-23440 does not exist. This commit cb12f14 seems to be the fix for CVE-2019-10747, while CVE-2021-23440 states that CVE-2019-10747 is bypassed.

When inspecting it even furtherly, there is a pull request for fixing 2.0.1 #38, but it was not merged neither in the GH repo nor the NPM package itself.

Can you confirm the vulnerable range and the fix here (CVE-2021-23440)? It raises some confusion and I would like to make sure 2.0.1 is safe.

Thanks in advance!

@noren95
Copy link
Author

noren95 commented May 3, 2023

Hi!

Do you have any updates?

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

1 participant