CVE-2014-0482
Last modified
CVE-2014-0482 is a vulnerability of currently unknown severity. The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors related to the REMOTE_USER header.. EPSS estimates a 1.96% chance of exploitation in the next 30 days.
Description
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors related to the REMOTE_USER header.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Opensuse | Opensuse | 12.3 | — |
| Opensuse | Opensuse | 13.1 | — |
| Djangoproject | Django | 1.6 | — |
| Djangoproject | Django | 1.6.1 | — |
| Djangoproject | Django | 1.6.2 | — |
| Djangoproject | Django | 1.6.3 | — |
| Djangoproject | Django | 1.6.4 | — |
| Djangoproject | Django | 1.6.5 | — |
| Djangoproject | Django | <= 1.4.13 | — |
| Djangoproject | Django | 1.4 | — |
| Djangoproject | Django | 1.4.1 | — |
| Djangoproject | Django | 1.4.2 | — |
| Djangoproject | Django | 1.4.4 | — |
| Djangoproject | Django | 1.4.5 | — |
| Djangoproject | Django | 1.4.6 | — |
| Djangoproject | Django | 1.4.7 | — |
| Djangoproject | Django | 1.4.8 | — |
| Djangoproject | Django | 1.4.9 | — |
| Djangoproject | Django | 1.4.10 | — |
| Djangoproject | Django | 1.4.11 | — |
| Djangoproject | Django | 1.4.12 | — |
| Djangoproject | Django | 1.7 | Beta1 |
| Djangoproject | Django | 1.5 | — |
| Djangoproject | Django | 1.5.1 | — |
| Djangoproject | Django | 1.5.2 | — |
| Djangoproject | Django | 1.5.3 | — |
| Djangoproject | Django | 1.5.4 | — |
| Djangoproject | Django | 1.5.5 | — |
| Djangoproject | Django | 1.5.6 | — |
| Djangoproject | Django | 1.5.7 | — |
| Djangoproject | Django | 1.5.8 | — |
References
- https://www.djangoproject.com/weblog/2014/aug/20/security/Vendor Advisory
- https://www.djangoproject.com/weblog/2014/aug/20/security/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2014-0482?
How severe is CVE-2014-0482?
How do I fix CVE-2014-0482?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2014
- CVE-2014-0476The slapper function in chkrootkit before 0.50 does not prop…
- CVE-2014-0477The parse function in Email::Address module before 1.905 for…
- CVE-2014-0478APT before 1.0.4 does not properly validate source packages,…
- CVE-2014-0479reportbug before 6.4.4+deb7u1 and 6.5.x before 6.5.0+nmu1 al…
- CVE-2014-0480The core.urlresolvers.reverse function in Django before 1.4.…
- CVE-2014-0481The default configuration for the file upload handling syste…
- CVE-2014-0483The administrative interface (contrib.admin) in Django befor…
- CVE-2014-0484The Debian acpi-support package before 0.140-5+deb7u3 allows…
- CVE-2014-0485S3QL 1.18.1 and earlier uses the pickle Python module unsafe…
- CVE-2014-0486Knot DNS before 1.5.2 allows remote attackers to cause a den…
- CVE-2014-0487APT before 1.0.9 does not verify downloaded files if they ha…
- CVE-2014-0488APT before 1.0.9 does not "invalidate repository data" when …
Are you affected by CVE-2014-0482?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST