CVE-2015-5246: High severity the foreman vulnerability
larry campbell reports via the foreman bug tracker:
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?
Initial Setup: 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.
Upstream references: http://projects.theforeman.org/issues/11471
Other sources
The LDAP Authentication functionality in Foreman might allow remote attackers with knowledge of old passwords to gain access via vectors involving the password lifetime period in Active Directory.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2015-5246?
CVE-2015-5246 is classified as a medium severity vulnerability.
How do I fix CVE-2015-5246?
To fix CVE-2015-5246, upgrade Foreman to a version higher than 1.9.0 that includes the patch.
What vulnerability does CVE-2015-5246 describe?
CVE-2015-5246 describes an issue where an Active Directory user can log in with both their old and new passwords.
Which version of Foreman is affected by CVE-2015-5246?
Foreman version 1.9.0 is affected by CVE-2015-5246.
Is there a workaround for CVE-2015-5246?
There is no official workaround for CVE-2015-5246; upgrading is recommended.