CVE-2014-0474: SQL Injection

Published Apr 23, 2014
·
Updated

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."

Affected Software

31 affected componentsFixes available
pip/Django>=1.6<1.6.3
1.6.3
pip/Django>=1.5<1.5.6
1.5.6
pip/django<1.4.11
1.4.11
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.7-alpha2
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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 1.6.3
  2. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 1.5.6
  3. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 1.4.11
  4. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 1.4.11
  5. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 1.5.6
  6. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 1.6.3
  7. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 1.7 beta 2

Event History

Apr 23, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·03:55 PM
DescriptionSeverityWeaknessAffected Software
May 17, 2022
Advisory Published
via GitHub·03:07 AM
Jan 14, 58316
Event
via GitHub·04:22 PM

Frequently Asked Questions

1

What is the severity of CVE-2014-0474?

CVE-2014-0474 has a medium severity level due to improper type conversion vulnerabilities.

2

How do I fix CVE-2014-0474?

To fix CVE-2014-0474, upgrade Django to version 1.4.11, 1.5.6, 1.6.3, or later.

3

What versions of Django are affected by CVE-2014-0474?

CVE-2014-0474 affects Django versions prior to 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7 beta 2.

4

Can remote attackers exploit CVE-2014-0474?

Yes, remote attackers could exploit CVE-2014-0474 due to insufficient type conversion.

5

What fields are affected by CVE-2014-0474 in Django?

The affected fields in Django for CVE-2014-0474 are FilePathField, GenericIPAddressField, and IPAddressField.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203