-
Notifications
You must be signed in to change notification settings - Fork 6k
SEC-3187: LdapUserDetailsManager password change with LDAP operation (RFC 3062) #3392
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
Comments
This is a security issue, not just an improvement. By doing a direct modify on the userPassword attribute, the security configuration for userPassword is bypassed. |
I have noticed some clear password stored in my test LDAP database because of that. Any update on this? We use a bcrypt module on the Ldap and the BCryptPasswordEncoder hash is not compatible with the bcrypt hash. Only the SSHA password and weak password encryption are available. It's clearly a security issue. |
Hi, Is there any update on this? |
+1 |
1 similar comment
+1 |
@monowai, |
+1 |
This is raised when analyzing code through vulnerability analysis tools like Snyk: |
Yeah, we're getting it in our snyk.io reports as well! Could we have an update on this, please? |
+1. This needs to be fixed. |
Is there any update on this? It's been around for a while now and it's causing our snyk.io checks to fail, (which is, of course the least of our concerns, given the seriousness of the issue). Could we get some sort of update, please? |
LdapUserDetailsManager can be configured to either use direct attribute modification or the LDAP Password Modify Extended Operation to change a user's password. Fixes: spring-projectsgh-3392
LdapUserDetailsManager can be configured to either use direct attribute modification or the LDAP Password Modify Extended Operation to change a user's password. Fixes: gh-3392
LdapUserDetailsManager can be configured to either use direct attribute modification or the LDAP Password Modify Extended Operation to change a user's password. Fixes: gh-3392
Thanks for fixing this @jzheaux ! In which version do you think this will be released and any idea when that will be? :) |
@carlspring Looks like I failed to add the milestone earlier. It's available in 4.2.9, 5.0.9, and 5.1.1, which are in Maven Central now. |
Is there any plan to get a CVE for this issue? |
@ddillard No. This was not a feature that was supported, so users would have been expected to hash it themselves. |
Mark Janssen (Migrated from SEC-3187) said:
Currently the LdapUserDetailsManager changePassword method modifies the password attribute directly. It would be better to (optionally) use the LDAP Password Modify Extended Operation as described in RFC 3062. This way, any associated attributes (e.g. Samba NTLM hashed passwords) will also be updated by the LDAP server.
The text was updated successfully, but these errors were encountered: