FreshPorts - VuXML

The Django project reports:

These releases address a denial-of-service attack against Django's authentication framework. All users of Django are encouraged to upgrade immediately.

ge 1.5 lt 1.5.4

ge 1.4 lt 1.4.8

ge 1.5 lt 1.5.4

ge 1.4 lt 1.4.8

< 20130922,1

< 20130922,1

Django project reports:

Today the Django team is issuing multiple releases -- Django 1.2.4, Django 1.1.3 and Django 1.3 beta 1 -- to remedy two security issues reported to us. All users of affected versions of Django are urged to upgrade immediately.

Information leakage in Django administrative interface

The Django administrative interface, django.contrib.admin supports filtering of displayed lists of objects by fields on the corresponding models, including across database-level relationships. This is implemented by passing lookup arguments in the querystring portion of the URL, and options on the ModelAdmin class allow developers to specify particular fields or relationships which will generate automatic links for filtering.

Denial-of-service attack in password-reset mechanism

Django's bundled authentication framework, django.contrib.auth, offers views which allow users to reset a forgotten password. The reset mechanism involves generating a one-time token composed from the user's ID, the timestamp of the reset request converted to a base36 integer, and a hash derived from the user's current password hash (which will change once the reset is complete, thus invalidating the token).

gt 1.2 lt 1.2.4

gt 1.1 lt 1.1.3

< 15032,1

The Django Project reports:

These security releases fix four issues: one potential phishing vector, one denial-of-service vector, an information leakage issue, and a range of XML vulnerabilities.

1. Host header poisoning

   an attacker could cause Django to generate and display URLs that link to arbitrary domains. This could be used as part of a phishing attack. These releases fix this problem by introducing a new setting, ALLOWED_HOSTS, which specifies a whitelist of domains your site is known to respond to.

   Important: by default Django 1.3.6 and 1.4.4 set ALLOWED_HOSTS to allow all hosts. This means that to actually fix the security vulnerability you should define this setting yourself immediately after upgrading.

2. Formset denial-of-service

   an attacker can abuse Django's tracking of the number of forms in a formset to cause a denial-of-service attack. This has been fixed by adding a default maximum number of forms of 1,000. You can still manually specify a bigger max_num, if you wish, but 1,000 should be enough for anyone.

3. XML attacks

   Django's serialization framework was vulnerable to attacks via XML entity expansion and external references; this is now fixed. However, if you're parsing arbitrary XML in other parts of your application, we recommend you look into the defusedxml Python packages which remedy this anywhere you parse XML, not just via Django's serialization framework.

4. Data leakage via admin history log

   Django's admin interface could expose supposedly-hidden information via its history log. This has been fixed.

ge 1.3 lt 1.3.6

ge 1.4 lt 1.4.4

Django project reports:

The provided template tag for inserting the CSRF token into forms -- {% csrf_token %} -- explicitly trusts the cookie value, and displays it as-is. Thus, an attacker who is able to tamper with the value of the CSRF cookie can cause arbitrary content to be inserted, unescaped, into the outgoing HTML of the form, enabling cross-site scripting (XSS) attacks.

gt 1.2 lt 1.2.2

< 13698,1

The Django project reports:

These releases address an unexpected code-execution issue, a caching issue which can expose CSRF tokens and a MySQL typecasting issue. While these issues present limited risk and may not affect all Django users, we encourage all users to evaluate their own risk and upgrade as soon as possible.

ge 1.6 lt 1.6.3

ge 1.6 lt 1.6.3

ge 1.6 lt 1.6.3

ge 1.6 lt 1.6.3

ge 1.6 lt 1.6.3

ge 1.6 lt 1.6.3

ge 1.5 lt 1.5.6

ge 1.5 lt 1.5.6

ge 1.5 lt 1.5.6

ge 1.5 lt 1.5.6

ge 1.5 lt 1.5.6

ge 1.5 lt 1.5.6

ge 1.4 lt 1.4.11

ge 1.4 lt 1.4.11

ge 1.4 lt 1.4.11

ge 1.4 lt 1.4.11

ge 1.4 lt 1.4.11

ge 1.4 lt 1.4.11

< 20140423,1

< 20140423,1

Django project reports:

Django's forms library includes field types which perform regular-expression-based validation of email addresses and URLs. Certain addresses/URLs could trigger a pathological performance case in these regular expression, resulting in the server process/thread becoming unresponsive, and consuming excessive CPU over an extended period of time. If deliberately triggered, this could result in an effectively denial-of-service attack.

< 1.1.1

< 11603,1

The Django project reports:

These releases address a directory-traversal vulnerability in one of Django's built-in template tags. While this issue requires some fairly specific factors to be exploitable, we encourage all users of Django to upgrade promptly.

ge 1.5 lt 1.5.3

ge 1.4 lt 1.4.7

ge 1.5 lt 1.5.3

ge 1.4 lt 1.4.7

< 20130912,1

< 20130912,1

Django project reports:

Today the Django team is issuing multiple releases -- Django 1.2.5 and Django 1.1.4 -- to remedy three security issues reported to us. All users of affected versions of Django are urged to upgrade immediately.

gt 1.2 lt 1.2.5

gt 1.1 lt 1.1.4

< 15470,1

The Django project reports:

Please reference CVE/URL list for details

ge 1.3 lt 1.3.1

ge 1.2 lt 1.2.7

< 16758,1

The Django project reports:

Today the Django team is issuing multiple releases -- Django 1.3.2 and Django 1.4.1 -- to remedy security issues reported to us:

• Cross-site scripting in authentication views
• Denial-of-service in image validation
• Denial-of-service via get_image_dimensions()

All users are encouraged to upgrade Django immediately.

ge 1.4 lt 1.4.1

ge 1.3 lt 1.3.2

ge 1.4 lt 1.4.1

ge 1.3 lt 1.3.2

< 20120731,1

< 20120731,1