eFront Educational 3.6.11 Cross Site Scripting

2012.09.05
Risk: Low
Local: No
Remote: Yes
CVE: N/A
CWE: CWE-79

Title: ====== eFront Educational v3.6.11 - Multiple Web Vulnerabilities Date: ===== 2012-08-03 References: =========== http://www.vulnerability-lab.com/get_content.php?id=666 VL-ID: ===== 666 Common Vulnerability Scoring System: ==================================== 3.5 Introduction: ============= Tailored with larger organizations in mind, eFront Educational offers solutions for the management of companies most valued asset - the people. Based on a coherent approach to human capital management which keeps the workforce actively engaged, the eFront Educational platform offers the means of aligning learning programs with business goals to cultivate employee skills and knowledge associated with business performance. eFront Enterprise builds on top of eFront Educational. (Copy of the Vendor Homepage: http://efrontlearning.net/product/ ) Abstract: ========= A Vulnerability Laboratory Researcher of the Vulnerability Laboratory Team discovered multiple web vulnerabilties in eFront v3.6.11 Educational. Report-Timeline: ================ 2011-08-03: Public Disclosure Status: ======== Published Affected Products: ================== eFront Product: Educational v3.6.11 Exploitation-Technique: ======================= Remote Severity: ========= High Details: ======== Multiple persistent input validation vulnerabilities are detected in the eFront Educational v3.6.11 Content Management System. The vulnerabilities allow remote attackers to implement/inject malicious script code on the application side (persistent). The first vulnerability is located in the profile module with the bound vulnerable firstname & lastname parameters. The bug allows a low privileged student account to exploit higher privileged trainer or administrator user accounts via registration. Exploitation of the first vulnerability requires low privileged student elearning application user account. The secound vulnerability is located in the Messages - New Folder Name module with the bound vulnerable folder listing. Exploitation of the secound vulnerability requires low privileged student user account & is only local exploitable. Successful exploitation of the vulnerabilities can lead to persistent session hijacking (manager/admin) or stable (persistent) context manipulation. Vulnerable Module(s): [+] Profile - User (Administrator User Listing) [+] Messages Vulnerable Parameters(s): [+] Firstname & Lastname [+] Foldername Proof of Concept: ================= The persistent input validation vulnerabilities can be exploited by remote attacker with a privileged student account. For demonstration or reproduce ... Review: Administrator - User Listing (Firstname & Lastname) <tr id="row_student" class="oddRowColor "> <td><a href="http://efront.127.0.0.1:137/educational/www/administrator.php?ctg=personal&user=student" class="editLink"><span id="column_student">"><iframe src="administrator.php-[PERSISTENT INJECTED SCRIPT CODE!])' <="" d.="" (student)<="" span=""></a></td> Affected URL(s): http://efront.127.0.0.1:137/educational/www/student.php?ctg=personal&user=student&op=profile http://efront.127.0.0.1:137/educational/www/administrator.php?ctg=users http://efront.127.0.0.1:137/educational/www/administrator.php?ctg=personal&user=student&op=profile Review: Messages - Add New Folder Name - Listing <td> <span class="counter">4.</span> <a href="http://efront.127.0.0.1:137/educational/www/student.php?ctg=messages& folder=10">"><iframe src="student-[PERSISTENT INJECTED SCRIPT CODE!])' < (0="" messages,="" 0kb)<="" a=""> </td> <td> Risk: ===== The security risk of the persistent web vulnerabilities are estimated as high(-). Credits: ======== Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@vulnerability-lab.com) Disclaimer: =========== 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.vulnerability-lab.com/register Contact: admin@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com Section: video.vulnerability-lab.com - forum.vulnerability-lab.com - news.vulnerability-lab.com 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 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, sourcecode, 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@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission. Copyright 2012 | Vulnerability Laboratory

References:

http://www.vulnerability-lab.com/get_content.php?id=666


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top