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

Possible SHA-1 Collision Risk Detected #343

Open
cryptochecktool opened this issue Oct 31, 2024 · 0 comments
Open

Possible SHA-1 Collision Risk Detected #343

cryptochecktool opened this issue Oct 31, 2024 · 0 comments

Comments

@cryptochecktool
Copy link

Hi Team,

I’ve noticed that we’re still using the SHA-1 hashing algorithm in parts of our system. There’s a growing concern in the security community about SHA-1’s vulnerability to collision attacks. This means that two different pieces of data could potentially produce the same hash, which could be exploited.
code:
Action Needed:

We should consider moving away from SHA-1 to a more secure hashing algorithm like SHA-256. It would be good to review where SHA-1 is used and start planning an upgrade.

Thanks, CryptoCheck.

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