CVSS: 5.0EPSS: 0%CPEs: 22EXPL: 0CVE-2011-4138
https://notcve.org/view.php?id=CVE-2011-4138
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. La funcionalidad verify_exists de la implementación URLField en Django antes de su versión v1.2.7 y en v1.3.x antes de v1.3.1 originalmente comprueba la validez de una URL a través de una petición HEAD, pero luego usa una petición GET de la URL en el caso de un redireccionamiento. Esto podría permitir a atacantes remotos para provocar peticiones GET aleatorias con una dirección IP de origen no deseados a través de una cabecera Location especificamente modificada. • http://openwall.com/lists/oss-security/2011/09/11/1 http://openwall.com/lists/oss-security/2011/09/13/2 http://secunia.com/advisories/46614 http://www.debian.org/security/2011/dsa-2332 https://bugzilla.redhat.com/show_bug.cgi?id=737366 https://hermes.opensuse.org/messages/14700881 https://www.djangoproject.com/weblog/2011/sep/09 https://www.djangoproject.com/weblog/2011/sep/10/127 • CWE-20: Improper Input Validation •
CVSS: 5.0EPSS: 1%CPEs: 22EXPL: 0CVE-2011-4139
https://notcve.org/view.php?id=CVE-2011-4139
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. Django v1.2.7 y v1.3.x anterior a v1.3.1 usa la cabecera de una petición HTTP host para la construcción de una dirección URL completa, en determinadas circunstancias, lo que permite a atacantes remotos para realizar ataques de envenenamiento de caché a través de una solicitud manipulada. • http://openwall.com/lists/oss-security/2011/09/11/1 http://openwall.com/lists/oss-security/2011/09/13/2 http://secunia.com/advisories/46614 http://www.debian.org/security/2011/dsa-2332 https://bugzilla.redhat.com/show_bug.cgi?id=737366 https://hermes.opensuse.org/messages/14700881 https://www.djangoproject.com/weblog/2011/sep/09 https://www.djangoproject.com/weblog/2011/sep/10/127 • CWE-20: Improper Input Validation •
CVSS: 6.8EPSS: 0%CPEs: 22EXPL: 0CVE-2011-4140
https://notcve.org/view.php?id=CVE-2011-4140
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code. El mecanismo de protección ante CSRF de Django hasta la versión 1.2.7 y 1.3.x hasta la 1.3.1 no maneja apropiadamente las configuraciones del servidor web que soportan cabeceras HTTP Host arbitrarias, lo que permite a atacantes remotos provocar peticiones falsificadas sin autenticar a través de vectores que involucran un registro DNS CNAME y una página web que contenga código JavaScript. • http://openwall.com/lists/oss-security/2011/09/11/1 http://openwall.com/lists/oss-security/2011/09/13/2 http://secunia.com/advisories/46614 http://www.debian.org/security/2011/dsa-2332 https://bugzilla.redhat.com/show_bug.cgi?id=737366 https://hermes.opensuse.org/messages/14700881 https://www.djangoproject.com/weblog/2011/sep/09 https://www.djangoproject.com/weblog/2011/sep/10/127 • CWE-352: Cross-Site Request Forgery (CSRF) •
CVSS: 4.0EPSS: 0%CPEs: 16EXPL: 3CVE-2010-4534
https://notcve.org/view.php?id=CVE-2010-4534
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. El interfaz de administración de django.contrib.admin de Django en versiones anteriores a 1.1.3, 1.2.x anteriores a 1.2.4, y 1.3.x anteriores a 1.3 beta 1 no restringen apropiadamente el uso de la cadena de consulta para realizar filtrado de objetos. Lo que permite a usuarios autenticados remotos obtener información confidencial a través de peticiones que contengan expresiones regulares, como se ha demostrado con el parámetro created_by__password__regex. • http://archives.neohapsis.com/archives/fulldisclosure/2010-12/0580.html http://code.djangoproject.com/changeset/15031 http://evilpacket.net/2010/dec/22/information-leakage-django-administrative-interfac http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html http://ngenuity-is.com/advisories/2010/dec/22/information-leakage-in-django-administrative-inter http://secunia.com/advisories/42715 http://secunia • CWE-264: Permissions, Privileges, and Access Controls •
CVSS: 5.0EPSS: 13%CPEs: 16EXPL: 0CVE-2010-4535
https://notcve.org/view.php?id=CVE-2010-4535
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. La funcionalidad de restablecimiento de contraseña en django.contrib.auth en Django antes de v1.1.3, v1.2.x antes de v1.2.4, y v1.3.x antes de v1.3 beta 1 no valida la longitud de una cadena que representa una marca de tiempo en base36, que permite a atacantes remotos ausar una denegación de servicio (consumo de recursos) a través de una URL que especifica un gran número entero en base36. • http://code.djangoproject.com/changeset/15032 http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html http://secunia.com/advisories/42715 http://secunia.com/advisories/42827 http://secunia.com/advisories/42913 http://www.djangoproject.com/weblog/2010/dec/22/security http://www.openwall.com/lists/oss-security/2010/12/23/4 http://www.openwall.com/lists/oss-security/2011/01/03 • CWE-20: Improper Input Validation •