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

CVE-2021-46743 - Insecure Encryption Vulnerability #226

Closed
KieranMellorNBS opened this issue May 19, 2022 · 2 comments
Closed

CVE-2021-46743 - Insecure Encryption Vulnerability #226

KieranMellorNBS opened this issue May 19, 2022 · 2 comments

Comments

@KieranMellorNBS
Copy link

This project uses firebase/php-jwt@5.X.X which has an insecure encryption vulnerability as detailed below:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46743

This vulnerability is remedied in firebase/php-jwt@6.X.X so can hopefully be fixed by upgrading to that version and making the required changed.

For reference:
firebase/php-jwt#351

@mxr576
Copy link
Contributor

mxr576 commented May 23, 2022

I was wondering why our always running security scanners (like via Local PHP Security Checker
did not raise this concern way sooner.

  1. Possibility of Reintroducing HS256/RSA256 Type Confusion (CVE-2021-46743) firebase/php-jwt#351 (comment) This comment says using >= 5.5.0 should be fine and as of today, nothing prevents installing that version or above from the 5x branch
  2. In addition, it looks like at the first sight only JWT::decode() had this vulnerability (this is what changes in the related PR confirms also), as of today this library only uses JWT::encode()

If I am right then adding firebase/php-jwt 6x support is nice to have.

@KieranMellorNBS
Copy link
Author

Thanks for looking into this Dezső - agree with your findings that this is a false alarm. Closing the issue now.

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

2 participants