Vulnerability Laboratory ID (VL-ID):
====================================
2241
Common Vulnerability Scoring System:
====================================
5.2
Vulnerability Class:
====================
Cross Site Scripting - Persistent
Current Estimated Price:
========================
1.000€ - 2.000€
Product & Service Introduction:
===============================
Froxlor Server Management Panel, the lightweight server management
software for your needs. Developed by experienced server
administrators, this open source (GPL) panel simplifies the effort of
managing your hosting. Manage reseller ressources and
limit what the customers may use in the dedicated customerpanel. MySQL
management, Directory protection & settings management.
(Copy of the Homepage: https://froxlor.org/index.php &
https://froxlor.org/download/ )
Abstract Advisory Information:
==============================
The vulnerability laboratory core research team discovered a persistent
cross site vulnerability in the Froxlor Server Management Panel v0.10.16.
User Interaction:
=================
Low User Interaction
Disclosure Type:
================
Full Disclosure
Technical Details & Description:
================================
A persistent input validation web vulnerability has been discovered in
the Froxlor Server Management Panel v0.10.16 web-application.
The vulnerability allows remote attackers to inject own malicious script
codes with persistent attack vector to compromise browser
to web-application requests from the application-side.
The persistent cross site web vulnerability is located in the
`username`, `name` and `firstname` input fields of the customer
add or registration module. Remote attackers are able to add customers
with malicious script code as firstname or name to
manipulate in the backend the `admin_customers.php` and `customers.php`
files. The injection point is the registration
or customer add/edit module and the execution occurs on preview of the
traffic module in the admin backend. The request
method to inject is POST and the attack vector is persistent located on
the application-side. In a valid attack case the
remote attacker uses a customer or reseller account to inject the
payload as name to provoke an execute in the insecure
backend module.
Successful exploitation of the vulnerability results in session
hijacking, persistent phishing attacks, persistent external
redirects to malicious source and persistent manipulation of affected
application modules.
Request Method(s):
[+] POST
Vulnerable Input(s):
[+] Username
[+] Name
[+] Firstname
Vulnerable Module(s):
[+] Customers
Vulnerable Parameter(s):
[+] name
[+] firstname
Affected File(s):
[+] admin_customers.php
Proof of Concept (PoC):
=======================
The persistent input validation vulnerability can be exploited by remote
attackers with low privilege user account and with low user interaction.
For security demonstration or to reproduce the security web
vulnerability follow the provided information and steps below to continue.
Manual steps to reproduce the vulnerability ...
1. Register or login with a low privilege user account
2. Open the profile account section
3. Change the name and firstname or include in the registration process
Note: Inject test payload to vulnerable marked input fields
4. Save or submit the input via form
5. Wait until an admin or higher privileged user role opens the traffic
stats to execute
6. Successful reproduce of the persistent input validation web
vulnerability!
Solution - Fix & Patch:
=======================
The vulnerability can be patched by follwing the next steps ...
1. Validate and escape the content of the vulnerable username, name and
firstname input fields
2. Restrict the input fields and disallow specialchars on inputs to filter
3. Parse the two output location and escape or secure encode the content
4. Encode in the edit formular the results on check
Security Risk:
==============
The security risk of the persistent validation web vulnerability in the
web-application is estimated as medium.
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 licenses, policies,
deface websites, hack into databases or trade with stolen data.
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, modify, use or
edit our material contact (admin@ or research@) to get a ask permission.