SB2011011001 - Multiple vulnerabilities in Django

CSH
CYBERSECURITY HELP
Sign In REGISTER

Main Vulnerability Database SB2011011001

SB2011011001 - Multiple vulnerabilities in Django

Published: January 10, 2011 Updated: February 2, 2022

Security Bulletin ID SB2011011001
Severity
Medium
Patch available
YES
Number of vulnerabilities 7
Exploitation vector Remote access
Highest impact Data manipulation

Breakdown by Severity

Medium 86% Low 14%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 7 secuirty vulnerabilities.


1) Resource management error (CVE-ID: CVE-2011-4137)

The vulnerability allows a remote non-authenticated attacker to perform service disruption.

The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.


2) Input validation error (CVE-ID: CVE-2011-4138)

The vulnerability allows a remote non-authenticated attacker to gain access to sensitive information.

The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.


3) Input validation error (CVE-ID: CVE-2011-4139)

The vulnerability allows a remote non-authenticated attacker to manipulate data.

Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's HTTP Host header to construct a full URL in certain circumstances, which allows remote attackers to conduct cache poisoning attacks via a crafted request.


4) Cross-site request forgery (CVE-ID: CVE-2011-4140)

The vulnerability allows a remote attacker to perform cross-site request forgery attacks.

The vulnerability exists due to insufficient validation of the HTTP request origin. A remote attacker can trick the victim to visit a specially crafted web page and perform arbitrary actions on behalf of the victim on the vulnerable website.


5) Input validation error (CVE-ID: CVE-2011-4136)

The vulnerability allows a remote non-authenticated attacker to manipulate or delete data.

django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.


6) Permissions, Privileges, and Access Controls (CVE-ID: CVE-2010-4534)

The vulnerability allows a remote #AU# to gain access to sensitive information.

The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter.


7) Input validation error (CVE-ID: CVE-2010-4535)

The vulnerability allows a remote non-authenticated attacker to perform service disruption.

The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.


Remediation

Install update from vendor's website.

References