Incorrect Implementation of Authentication Algorithm in cortezaproject/corteza-server
Reported on
Nov 10th 2021
Description
Hey, when I attempt to change the password after creating an account I noticed that you haven't kept any password boundary. You need to limit password length. Hashing a large amount of data can cause significant resource consumption on behalf of the server and would be an easy target for an Application-level Denial Of Service attack.
#Reproduction steps:
1. Create an account by using any mail (I used temp mail)
2. Login
3. Change password
4. Set New password = Boundless Characters/Special characters/Numbers
5. Done
Vulnerable Area
https://latest.cortezaproject.org/auth/change-password
Impact
Application-Level DoS
This allows for denial-of-service attacks through reworked submission of comprehensive passwords, tying up server resources in the expensive computation of the corresponding hashes.
@7h3h4ckv157 - our system will continue to lightly ping the maintainers to make sure they don't miss your report 👌
Is it conceivable for assigning a CVE? I'm not sure within the case, fair inquiring ...!
We do not assign CVEs to this type of weakness / CWE unfortunately - thanks for the question 👋