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

Security Issue: Potential timing attack when using '===' to compare password hashes #1555

Closed
dvicedo opened this issue Mar 23, 2022 · 1 comment

Comments

@dvicedo
Copy link

dvicedo commented Mar 23, 2022

Hi Team,
First of all, thanks for taking the time to read this.
I was looking for timing attacks in public repositories and find a security issue similar to a previous one #1089 but in another code section:

A simple strict equals sign === is used for hash comparison, which is vulnerable to timing attack. I think that hash_equals() could be used instead. It's seems that this portion of code is part of the legacy _password_verify_sha1_legacy function so I don't know if you want to fix it or not, but only want to notice you.

Have a great week, Thanks!

@benedmunds
Copy link
Owner

Great catch, thanks for this! Updated here: f08cd91

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