Django CMS 1.9/1.10/1.11 Technical 500 Template cross site scripting

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.
5.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Django CMS 1.9/1.10/1.11. It has been declared as problematic. The impacted element is an unknown function of the component Technical 500 Template. Executing a manipulation can lead to cross site scripting. This vulnerability appears as CVE-2017-12794. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Django CMS 1.9/1.10/1.11 (Content Management System) and classified as problematic. This vulnerability affects some unknown processing of the component Technical 500 Template. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity.

The bug was discovered 09/05/2017. The weakness was presented 09/05/2017 as Django security releases issued: 1.11.5 and 1.10.8 as confirmed news (Website). The advisory is shared for download at djangoproject.com. This vulnerability was named CVE-2017-12794 since 08/10/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.

The vulnerability scanner Nessus provides a plugin with the ID 103233 (Fedora 26 : python-django (2017-8614a6e905)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 171064 (OpenSUSE Security Update for python-Django (openSUSE-SU-2018:0826-1)).

Upgrading to version 1.10.8 or 1.11.5 eliminates this vulnerability. It is possible to mitigate the problem by applying the configuration setting DEBUG = False. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability. The news contains the following remark:

This vulnerability shouldn't affect most production sites since you shouldn't run with DEBUG = True (which makes this page accessible) in your production settings.

The vulnerability is also documented in the databases at Tenable (103233), SecurityFocus (BID 100643†) and SecurityTracker (ID 1039264†). See VDB-90143, VDB-92215 and VDB-93264 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.6

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

NVD Base Score: 6.1
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 103233
Nessus Name: Fedora 26 : python-django (2017-8614a6e905)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for python-django FEDORA-2017-8614a6e905
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: CMS 1.10.8/1.11.5
Config: DEBUG = False

Timelineinfo

08/10/2017 🔍
09/05/2017 +26 days 🔍
09/05/2017 +0 days 🔍
09/05/2017 +0 days 🔍
09/05/2017 +0 days 🔍
09/06/2017 +1 days 🔍
09/07/2017 +1 days 🔍
09/07/2017 +0 days 🔍
09/15/2017 +8 days 🔍
01/11/2021 +1214 days 🔍

Sourcesinfo

Advisory: Django security releases issued: 1.11.5 and 1.10.8
Researcher: Charles Bideau
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-12794 (🔍)
GCVE (CVE): GCVE-0-2017-12794
GCVE (VulDB): GCVE-100-106168
SecurityFocus: 100643 - Django CVE-2017-12794 Cross Site Scripting Vulnerability
SecurityTracker: 1039264

See also: 🔍

Entryinfo

Created: 09/07/2017 09:15
Updated: 01/11/2021 07:52
Changes: 09/07/2017 09:15 (75), 11/13/2019 10:47 (11), 01/11/2021 07:47 (2), 01/11/2021 07:52 (1)
Complete: 🔍
Cache ID: 216:371:103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!