Enterpriser16 LB v7.1 - Multiple Web Vulnerabilities
Load Balancer .org have cemented our reputation as market leaders in affordable server load balancing appliances with the ground-breaking release of firmware v7.0 for the Enterprise product family – which includes a slick new web interface design and many additional features which continue to keep us one step ahead of the competition.
(Copy of the Vendor Homepage: http://www.loadbalancer.org )
The Vulnerability Laboratory Research Team discovered multiple web vulnerabilities in Enterpriser16 LoadBalancer v7.1.
2012-12-12: Public or Non-Public Disclosure
Multiple persistent input validation web vulnerabilities are detected in the Enterpriser16 v7.1 Load Balancer Application. The bug allows remote attackers to implement/inject own malicious script code on the application side (persistent) of the service.
The first vulnerabilities are located in the `Edit Configuration` module with the bound vulnerable Label, Virtual Host, Request to send, Email Alerts and Response expected parameters.
The secound vulnerabilities are located in the Create Solution, Access points and New Contract module with the bound vulnerable title, asset name, contract name, name or description parameter requests.
Exploitation requires low user interaction and a low privileged application user account. Successful exploitation of the vulnerability can lead to persistent session hijacking (manager/admin), persistent phishing or persistent module web context manipulation.
Vulnerable Module(s): (Edit Configuration)
[+] Edit Configuration > layer4 > Virtual Servers [+] Edit Configuration > Layer4 > Real Server [+] Edit Configuration > SSL termination > Modify
Vulnerable Parameter(s): [+] [Label] [Virtual Host] [Request to send][Email Alerts][Response expected] [+] [Label] [+] [Label]
Vulnerable Module(s): (Admin/Moderator Back-End)
[+] Solution > Create Solution [+] Assets > It Assets > Access points [+] Contract > New Contract
Vulnerable Parameter(s): [+] [Title] [+] [Asset name] [+] [Contract Name] - [Description] - [Name] - [Support]
The persistent input validation vulnerability can be exploited by remote attackers with low required user interaction & low privileged user account. For demonstration or reproduce ...
Review: Edit Configuration > layer4 > Virtual Servers - [Label] [Virtual Host] [Request to send] [Email Alerts] [Response expected] <pre>
tcp_timeouts(Array) #2 /var/www/html/lbadmin/config/ldirectord.php(627): ldirectord_vip_edit('0', 'ipv4', '10.1.1.5', '80', ' <h1>[PERSISTENT INJECTED SCRIPT CODE!]</h1> ', 'tcp', 'masq', '255.255.255.255', '127.0.0.1', '9081', 'yes', '300', 'wrr', 'none', ' <h1>[PERSISTENT INJECTED SCRIPT CODE!]</h1> <h1>[PERSISTENT INJECTED SCRIPT CODE!]</h1> <h1>[PERSISTENT INJECTED SCRIPT CODE!]</h1> <h1>[PERSISTENT INJECTED SCRIPT CODE!]</h1> </pre>
Review: Edit Configuration > Add New Floating IP <p class="error"> Error: <em> The Floating IP address ' <iframe [PERSISTENT INJECTED SCRIPT CODE!]> <html> <head> <body vlink="#990000" text="#990000" link="#990000" bgcolor="#000000" alink="#999999" dir="ltr"> </html> </iframe> </em> </p>
Review: Edit Configuration > SSL termination > Modify [Label] [Ciphers to use] <pre> execute(): 'cp /usr/local/etc/certs/server.pem /usr/local/etc/certs/ <h1>label</h1> .pem' failed: errno 1, </pre> <p></p> <h3>Trace:</h3> <p></p> <pre>
<h1>[PERSISTENT INJECTED SCRIPT CODE!]</h1> ', 'ipv4', '10.0.0.20', '443', '10.0.0.20', '80', ' <h1> [PERSISTENT INJECTED SCRIPT CODE!] <p></p> </h1> </pre>
Review: Edit Configuration > Physical - Advanced Configuration
<p class="error"> Error: <em> Input field failed the validation. <br> '"> <iframe [PERSISTENT INJECTED SCRIPT CODE!]> ' is not a valid IP address. </em> </p>
The security risk of the persistent input validation vulnerabilities are estimated as medium(+).
Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed (the_storm) [firstname.lastname@example.org] [iel-sayed.blogspot.com]
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: email@example.com - firstname.lastname@example.org - email@example.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 (firstname.lastname@example.org or email@example.com) to get a permission.
Copyright © 2012 | Vulnerability Laboratory
-- VULNERABILITY RESEARCH LABORATORY LABORATORY RESEARCH TEAM CONTACT: firstname.lastname@example.org