[FD] Django CMS v3.3.0 - (Editor Snippet) Persistent Web Vulnerability (CVE-2016-6186)

Document Title: =============== Django CMS v3.3.0 - (Editor Snippet) Persistent Web Vulnerability (CVE-2016-6186) References (Source): ==================== http://ift.tt/2a71N5e Security Release: http://ift.tt/29QeFHQ http://ift.tt/29QE3P0 CVE-ID: ======= CVE-2016-6186 Release Date: ============= 2016-07-19 Vulnerability Laboratory ID (VL-ID): ==================================== 1869 Common Vulnerability Scoring System: ==================================== 3.5 Product & Service Introduction: =============================== django CMS is a modern web publishing platform built with Django, the web application framework for perfectionists with deadlines. django CMS offers out-of-the-box support for the common features you’d expect from a CMS, but can also be easily customised and extended by developers to create a site that is tailored to their precise needs. (Copy of the Homepage: http://ift.tt/29QFBMX ) Abstract Advisory Information: ============================== The vulnerability laboratory core research team discovered an application-side vulnerability (CVE-2016-6186) in the official Django v3.3.0 Content Management System. Vulnerability Disclosure Timeline: ================================== 2016-07-03: Researcher Notification & Coordination (Benjamin Kunz Mejri - Evolution Security GmbH) 2016-07-04 Vendor Notification (Django Security Team) 2016-07-07: Vendor Response/Feedback (Django Security Team) 2016-07-18: Vendor Fix/Patch (Django Service Developer Team) 2016-07-19: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Divio AG Product: Django Framework - Content Management System 3.3.0 Divio AG Product: Django Framework - Content Management System MDB, 1.10, 1.9, 1.8 and 1.7 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ A persistent input validation web vulnerability has been discovered in the official Django v3.3.0 Content Management System. The security vulnerability allows remote attackers or privileged user accounts to inject own malicious script codes to the application-side of the vulnerable modules web context. The persistent web vulnerability is located in the `Name` value of the `Editors - Code Snippet` module POST method request. Remote attackers are able to inject own malicious script code to the snippets name input field to provoke a persistent execution. The injection point is the snippets add module of the editor. The execution point occurs in the `./djangocms_snippet/snippet/` data listing after the add. The data context is not escaped or parsed on add to select and thus results in an execute of any payload inside of the option tag. The attacker vector of the vulnerability is persistent because of the data is stored on add and request method to inject is POST. The vulnerability can be exploited against other privileged user accounts of the django application by interaction with already existing snippets on add. Already added elements become visible for the other user accounts as well on add interaction. The unescaped data is stored in the database of the web-application but when rendered in the frontend or in the edit mode, it's properly escaped. The security risk of the vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.5. Exploitation of the vulnerability requires a low privileged web-application user account and only low user interaction. Successful exploitation of the vulnerability results in session hijacking, persistent phishing attacks, persistent external redirects to malicious source and persistent manipulation of affected or connected application modules. Request Method(s): [+] POST Vulnerable Module(s): [+] Editor - Snippets (Add) Vulnerable Input(s): [+] Name Parameter(s): [+] select Affected Module(s): [+] Snippets Options Listing [./djangocms_snippet/snippet/] - option Proof of Concept (PoC): ======================= The application-side validation web vulnerability can be exploited by low and high privileged web-application user accounts with low user interaction. For security demonstration or to reproduce the application-side web vulnerability follow the provided information and steps below to continue. Manual steps to reproduce the vulnerability ... 1. Login to your django cms website with version 3.3.0 2. Open the structure module 3. Click to edit a page module Note: Now the editor opens with the main default plugins 4. Mark a text passage and click to the code snippets plugin that is configured by default installation 5. Click the plus to add a new snippet of code 6. Inject a script code payload in java-script to the input field of the Name 7. Save the entry iva POST method request 8. Now click the box to choose the vulnerable injected payload 9. The script code payload executes in the box listing without secure parse or filter to encode 10. Successful reproduce of the application-side validation vulnerability in the editors snippet module! Note: Multiple accounts can be exploited by the inject of snippets. When another privileged user account includes a snippet the stable saved categories provoke the execution of the payload. PoC: Snippet Module [./djangocms_snippet/snippet/] (Execution Point) ... Source: Gmail -> IFTTT-> Blogger