[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Jease CMS v2.11 - Persistent UI Web Vulnerability
Jease CMS v2.11 - Persistent UI Web Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
Jease is an Open Source Content-Management-System which is driven by the power of Java. Jease means `Java with Ease`,
so Jease promises to keep simple things simple and the hard things (j)easy. Content-Management with Jease. Jease is built
on top of the most advanced open-source technologies existing in the Java-community. Jease glues these technologies together
to provide an outstanding productive development experience by combining the safety and ide-/compiler-support of Java with
the turn-around-times of scripting languages.
(Copy of the Vendor Homepage: http://www.jease.org/ )
Abstract Advisory Information:
The independent Vulnerability Laboratory Researcher (Manideep K.) discovered a persistent input validation web vulnerability in the Jease 2.11 CMS.
Vulnerability Disclosure Timeline:
2014-12-12: Public Disclosure (Vulnerability Laboratory)
Product: Jease - Content Management System 2.11
Technical Details & Description:
An application-side input validation web vulnerability has been discovered in the official Jease v2.11 Content Management System.
The vulnerability allows an attacker to inject own script code as payload to the application-side of the vulnerable service function.
The vulnerability is located in the content values of the create function. Local attackers with low privileged application user accounts
are able to manipulate the content input values by usage of the create functions. The execution of the persistent script code occurs in
the view browser module of the content management system. The attack vector is persistent on the application-side and the request method
to inject is POST. The issue allows to transfer persistent malicious script codes to the frontend service.
The security risk of the application-side web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.7.
Exploitation of the application-side web vulnerability requires a low privileged web-application user account and low user interaction.
Successful exploitation of the vulnerability results in persistent phishing mails, session hijacking, persistent external redirect to malicious
sources and application-side manipulation of affected or connected module context.
[+] View - Browser Service
Proof of Concept (PoC):
The persistent input validation web vulnerability can be exploited by remote attackers without privileged application user account
and with low user interaction. For security demonstration or to reproduce the security vulnerability follow the provided information
and steps below to continue.
Manual steps to reproduce:
1. Install the Content Management System
2. Open online service to interact (link - http://jease.127.0.0.1:8080/login?file&auth
3. Click to include on any entry (Alternatively, you can create one and reproduce) and enter the following parameters in the Content section
Note: (Select the plaintext option present at the end of the content box)
4. Enter “ <script>alert(document.cookie)</script> ” or “ <script>alert(document.cookie)</script> ” in the box and press view in browser option
Note: the request got saved and is now persistent included to the browser module service
5. Successful reproduce of the vulnerability!
The security risk of the persistent input validation web vulnerability in the Jease CMS is estimated as medium. (CVSS 3.7)
Credits & Authors:
Manideep K. - Information Security Researcher [https://in.linkedin.com/in/manideepk]
Disclaimer & Information:
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed
or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable
in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab
or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses,
policies, deface websites, hack into databases or trade with fraud/stolen material.
Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.evolution-sec.com
Contact: admin@xxxxxxxxxxxxxxxxxxxxx - research@xxxxxxxxxxxxxxxxxxxxx - admin@xxxxxxxxxxxxxxxxx
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.php - evolution-sec.com/contact
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/
Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
(admin@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a permission.
Copyright © 2014 | Vulnerability Laboratory - [Evolution Security GmbH]™
VULNERABILITY LABORATORY - RESEARCH TEAM
PGP KEY: http://www.vulnerability-lab.com/keys/admin@xxxxxxxxxxxxxxxxxxxxx%280x198E9928%29.txt