First published: Fri Nov 03 2017(Updated: )
Mahara 1.8 before 1.8.6 and 1.9 before 1.9.4 and 1.10 before 1.10.1 and 15.04 before 15.04.0 are vulnerable to old sessions not being invalidated after a password change.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Mahara Mahara | =1.8-rc1 | |
Mahara Mahara | =1.8-rc2 | |
Mahara Mahara | =1.8.0 | |
Mahara Mahara | =1.8.1 | |
Mahara Mahara | =1.8.2 | |
Mahara Mahara | =1.8.3 | |
Mahara Mahara | =1.8.4 | |
Mahara Mahara | =1.8.5 | |
Mahara Mahara | =1.9-rc1 | |
Mahara Mahara | =1.9.0 | |
Mahara Mahara | =1.9.1 | |
Mahara Mahara | =1.9.2 | |
Mahara Mahara | =1.9.3 | |
Mahara Mahara | =1.10-rc1 | |
Mahara Mahara | =1.10.0 | |
Mahara Mahara | =15.04-rc1 | |
Mahara Mahara | =15.04-rc2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2017-1000136.
Mahara versions 1.8, 1.9, 1.10, and 15.04 are affected.
The severity rating of CVE-2017-1000136 is medium with a score of 6.5.
This vulnerability allows old sessions to remain active even after a password change, potentially allowing unauthorized access.
Yes, upgrading to Mahara versions 1.8.6, 1.9.4, 1.10.1, or 15.04.0 will fix the vulnerability.