CVE-2014-0474
Last modified
CVE-2014-0474 is a vulnerability of currently unknown severity. The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 do not properly perform type conversion, which allows remote attackers to have unspecified impact and vectors, related to "MySQL typecasting.". EPSS estimates a 4.75% chance of exploitation in the next 30 days.
Description
The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 do not properly perform type conversion, which allows remote attackers to have unspecified impact and vectors, related to "MySQL typecasting."
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Canonical | Ubuntu Linux | 10.04 | — |
| Canonical | Ubuntu Linux | 12.04 | — |
| Canonical | Ubuntu Linux | 12.10 | — |
| Canonical | Ubuntu Linux | 13.10 | — |
| Canonical | Ubuntu Linux | 14.04 | — |
| Djangoproject | Django | 1.6 | — |
| Djangoproject | Django | 1.6.1 | — |
| Djangoproject | Django | 1.6.2 | — |
| Djangoproject | Django | <= 1.4.10 | — |
| Djangoproject | Django | 1.4 | — |
| Djangoproject | Django | 1.4.1 | — |
| Djangoproject | Django | 1.4.2 | — |
| Djangoproject | Django | 1.4.3 | — |
| 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.7 | Alpha1 |
| 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 | — |
References
- https://www.djangoproject.com/weblog/2014/apr/21/security/Vendor Advisory
- https://www.djangoproject.com/weblog/2014/apr/21/security/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2014-0474?
How severe is CVE-2014-0474?
How do I fix CVE-2014-0474?
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-0468Vulnerability in fusionforge in the shipped Apache configura…9.8
- CVE-2014-0469Stack-based buffer overflow in a certain Debian patch for xb…
- CVE-2014-0470super.c in Super 3.30.0 does not check the return value of t…
- CVE-2014-0471Directory traversal vulnerability in the unpacking functiona…
- CVE-2014-0472The django.core.urlresolvers.reverse function in Django befo…
- CVE-2014-0473The caching framework in Django before 1.4.11, 1.5.x before …
- CVE-2014-0475Multiple directory traversal vulnerabilities in GNU C Librar…
- 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.…
Are you affected by CVE-2014-0474?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST