CVE-2015-5246 - previous password still allowed to log into foreman with Active Directory backend
This was found on Foreman 1.9.0:
I came across this issue by chance. I was forced to change my Active Directory password today. After doing so, I then (mistakenly) attempted to log onto Foreman with my previous password and was able to successfully log in. The new password also worked. I tried with other browsers and even another workstation that I had never logged onto and all attempts allowed me to log on with my non-valid previous password. Perhaps something on foreman/passenger/ruby/etc is caching my credential and not re-checking?
Have an Active Directory enviornment available for LDAP Authentication. Setup LDAP Authentication Source in Foreman and have a test user account created in Active Directory.
Steps to recreate:
1. Log on to Foreman with the Active Directory user. This should succeed. Log off.
2. Change your Active Directory account's password.
3. Log on to Foreman with the Active Directory user, and use the previous password. This should fail with authentication denied method, however it succeeds.
#3 Updated by Dominic Cleal over 3 years ago
- Status changed from New to Need more information
Thanks to Daniel for passing this onto foreman-security and confirming the problem.
Just searching though, and I see lots of similar reports against other applications that suggest it's a function of Active Directory and/or the domain controller itself, e.g.
Does the login still work an hour later, as that's the claimed timeout of those links?
#4 Updated by Daniel Lobato Garcia over 3 years ago
From my tests, neither the connection to LDAP nor logging in work using the old password after the allowed period in HKLM\System\CurrentControlSet\Control\LSA\OldPasswordAllowedPeriod. (Windows registry). If I set that HKLM\System\CurrentControlSet\Control\LSA\OldPasswordAllowedPeriod to 0, the old password will be disabled right away.
#7 Updated by larry campbell over 3 years ago
I second the observation that the old password failed when we tried it again several hours later. It would make sense this is an AD "feature" as pointed out by Daniel and Dominic, and I support the current method of making users aware through a Foreman Manual notice. Thanks everybody!
#8 Updated by Dominic Cleal over 3 years ago
- Status changed from Feedback to Rejected
Thanks for confirming, and for the report Larry. If you come across across any potential security issue in future, please drop us an e-mail to email@example.com in case we need to embargo it first. Cheers.