Arch Linux 811 Published by

The following updates has been released for Arch Linux:

ASA-201901-6: python-django: content spoofing
ASA-201901-7: python2-django: content spoofing



ASA-201901-6: python-django: content spoofing

Arch Linux Security Advisory ASA-201901-6
=========================================

Severity: Medium
Date : 2019-01-11
CVE-ID : CVE-2019-3498
Package : python-django
Type : content spoofing
Remote : Yes
Link : https://security.archlinux.org/AVG-839

Summary
=======

The package python-django before version 2.1.5-1 is vulnerable to
content spoofing.

Resolution
==========

Upgrade to 2.1.5-1.

# pacman -Syu "python-django>=2.1.5-1"

The problem has been fixed upstream in version 2.1.5.

Workaround
==========

None.

Description
===========

A content spoofing issue has been found in django before 2.1.5 and
1.11.18, where an attacker could craft a malicious URL that could make
spoofed content appear on the default page generated by the
django.views.defaults.page_not_found() view.

Impact
======

A remote attacker can spoof content on the not found page with a
maliciously crafted URL.

References
==========

https://www.djangoproject.com/weblog/2019/jan/04/security-releases/
https://github.com/django/django/commit/64d2396e83aedba3fcc84ca40f23fbd22f0b9b5b
https://github.com/django/django/commit/1cd00fcf52d089ef0fe03beabd05d59df8ea052a
https://security.archlinux.org/CVE-2019-3498


ASA-201901-7: python2-django: content spoofing

Arch Linux Security Advisory ASA-201901-7
=========================================

Severity: Medium
Date : 2019-01-11
CVE-ID : CVE-2019-3498
Package : python2-django
Type : content spoofing
Remote : Yes
Link : https://security.archlinux.org/AVG-838

Summary
=======

The package python2-django before version 1.11.18-1 is vulnerable to
content spoofing.

Resolution
==========

Upgrade to 1.11.18-1.

# pacman -Syu "python2-django>=1.11.18-1"

The problem has been fixed upstream in version 1.11.18.

Workaround
==========

None.

Description
===========

A content spoofing issue has been found in django before 2.1.5 and
1.11.18, where an attacker could craft a malicious URL that could make
spoofed content appear on the default page generated by the
django.views.defaults.page_not_found() view.

Impact
======

A remote attacker can spoof content on the not found page with a
maliciously crafted URL.

References
==========

https://www.djangoproject.com/weblog/2019/jan/04/security-releases/
https://github.com/django/django/commit/64d2396e83aedba3fcc84ca40f23fbd22f0b9b5b
https://github.com/django/django/commit/1cd00fcf52d089ef0fe03beabd05d59df8ea052a
https://security.archlinux.org/CVE-2019-3498