Django up to 1.7 MySQL Typecast resource management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in Django and classified as problematic. This affects an unknown function of the component MySQL Typecast Handler. Performing a manipulation of the argument FilePathField/GenericIPAddressField/IPAddressField results in resource management. This vulnerability is known as CVE-2014-0474. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Django (Content Management System). It has been classified as problematic. This affects an unknown part of the component MySQL Typecast Handler. The manipulation of the argument FilePathField/GenericIPAddressField/IPAddressField with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on confidentiality. The summary by CVE is:

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

The weakness was published 04/21/2014 by Michael Koziarski with Ruby on Rails Team as Security releases issued as confirmed advisory (Website). The advisory is shared at djangoproject.com. The public release has been coordinated with the project team. This vulnerability is uniquely identified as CVE-2014-0474 since 12/19/2013. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The advisory points out:

The MySQL database is known to "typecast" on certain queries; for example, when querying a table which contains string values, but using a query which filters based on an integer value, MySQL will first silently coerce the strings to integers, and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before querying.

The vulnerability scanner Nessus provides a plugin with the ID 74097 (Debian DSA-2934-1 : python-django - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 123242 (Fedora Security Update for python-django14 (FEDORA-2015-0804)).

Upgrading to version 1.4.11, 1.5.6 or 1.6.3 eliminates this vulnerability. The upgrade is hosted for download at djangoproject.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:

These (...) fields have been updated to convert their arguments to the correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL fragments -- will be advised to ensure they perform appropriate manual type conversions prior to executing queries.

The vulnerability is also documented in the databases at X-Force (92707), Tenable (74097), SecurityFocus (BID 67038†), Secunia (SA58201†) and SecurityTracker (ID 1030149†). Similar entries are available at VDB-10295, VDB-13064, VDB-13063 and VDB-13240. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.6

VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74097
Nessus Name: Debian DSA-2934-1 : python-django - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 702934
OpenVAS Name: Debian Security Advisory DSA 2934-1 (python-django - security update
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Django 1.4.11/1.5.6/1.6.3

Timelineinfo

12/19/2013 🔍
04/21/2014 +123 days 🔍
04/21/2014 +0 days 🔍
04/21/2014 +0 days 🔍
04/23/2014 +2 days 🔍
04/23/2014 +0 days 🔍
04/23/2014 +0 days 🔍
04/23/2014 +0 days 🔍
04/24/2014 +1 days 🔍
04/29/2014 +5 days 🔍
06/17/2021 +2606 days 🔍

Sourcesinfo

Advisory: Security releases issued
Researcher: Michael Koziarski
Organization: Ruby on Rails Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2014-0474 (🔍)
GCVE (CVE): GCVE-0-2014-0474
GCVE (VulDB): GCVE-100-13065

OVAL: 🔍

X-Force: 92707 - Django data injection, High Risk
SecurityFocus: 67038 - Django CVE-2014-0474 Multiple Data Type Injection Vulnerabilities
Secunia: 58201 - Django Security Issue and Multiple Vulnerabilities, Moderately Critical
SecurityTracker: 1030149 - Django Bugs Let Remote Users Execute Arbitrary Code, Modify SQL Queries, and Obtain Potentially Sensitive Information
Vulnerability Center: 44295 - Django Remote Database Read and Write Vulnerability Related to MySQL Typecasting, Critical

See also: 🔍

Entryinfo

Created: 04/23/2014 16:59
Updated: 06/17/2021 16:56
Changes: 04/23/2014 16:59 (89), 05/26/2017 04:03 (6), 06/17/2021 16:56 (3)
Complete: 🔍
Cache ID: 216:3A9:103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!