-
Notifications
You must be signed in to change notification settings - Fork 9.4k
chore: use random_int() in some places #15017
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
Conversation
Hi @DanielRuf. Thank you for your contribution. |
This does not seem to be in 2.2.5; https://github.com/magento/magento2/blob/2.2.5/lib/internal/Magento/Framework/Encryption/Crypt.php#L78 This issue is registered as security vulnerability CVE-2016-6485 so would be great if this can be fixed in the next release. See https://www.cvedetails.com/cve/CVE-2016-6485/ |
It will be in 2.2.6 |
Also this is an older CVE and 5.5/10 is not so critical. |
So this is not a 0day in general. |
Yeah it's old, but still open. Don't know if that makes it better ;) Not a big issue, just nice to have closed. Also for other tools that check if you use projects with known security issues. Nice to have fixed, just expected it in 2.2.5 because of the comment saying it was in 2.2.5 |
Well, the release bot of Magento had the wrong date and so this will be definitely in the next release. So it will be finally fixed in 2.2.6. Not sure who said that it is fixed yet but this is not correct as you can see. |
Never trust a comment, check the code of the tagged release =) |
Description
This PR is for evaluating the possible increased security for generating random numbers in some modules.
Contribution checklist