CVE-2007-0405: Medium severity Django Project Django vulnerability
Published Jan 23, 2007
·Updated
The LazyUser class in the AuthenticationMiddleware for Django 0.95 does not properly cache the user name across requests, which allows remote authenticated users to gain the privileges of a different user.
Affected Software
2 affected componentsFixes available
pip/Django=0.95
1.0
Django Project Django=0.95
Remediation
Patch Available
Event History
Jan 23, 2007
CVE Published
12:28 AM
CVE Published
via MITRE·05:00 AM
Data Sourced
via MITRE·05:00 AM
Description
May 1, 2022
Advisory Published
via GitHub·05:44 PM
Frequently Asked Questions
1
What is the severity of CVE-2007-0405?
CVE-2007-0405 is classified as a medium severity vulnerability.
2
How do I fix CVE-2007-0405?
To fix CVE-2007-0405, upgrade Django to version 1.0 or later.
3
What does CVE-2007-0405 affect?
CVE-2007-0405 affects Django version 0.95 specifically.
4
What type of vulnerability is CVE-2007-0405?
CVE-2007-0405 is a privilege escalation vulnerability.
5
Who can exploit CVE-2007-0405?
Remote authenticated users can exploit CVE-2007-0405 to gain privileges of a different user.