Government Security
Network Security Resources

Jump to content

Photo

Pbboard V2.1.4 Cms - Multiple Web Vulnerabilities

pbboard v2.1.4 cms - multiple

  • Please log in to reply
No replies to this topic

#1 remove

remove

    Private First Class

  • Members
  • 51 posts

Posted 15 July 2012 - 03:50 PM

Title:
======
PBBoard v2.1.4 CMS - Multiple Web Vulnerabilities


Date:
=====
2012-06-26


References:
===========
http://www.vulnerabi...tent.php?id=623



VL-ID:
=====
625


Common Vulnerability Scoring System:
====================================
4.5


Introduction:
=============
PBBoard forum is a free and very famous flat-forum bulletin board software.

- LICENSE: http://www.pbboard.c...ual/license.txt
- INSTALL And UPGRADE : http://www.pbboard.c...ual/README.html
- English Style : http://www.pbboard.c...rums/t6478.html
- Languages : http://www.pbboard.c...ges&show=1&id=6
- Converter: http://www.pbboard.c...ges&show=1&id=3
- contact us: http://www.pbboard.c...d&sendmessage=1

(Copy of the Vendor Homepage: http://www.pbboard.com/ )


Abstract:
=========
The Vulnerability Laboratory Research Team discovered multiple Web vulnerabilities in the PBBoard v2.1.4 forum application.



Report-Timeline:
================
2012-06-26: Public Disclosure


Status:
========
Published


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


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


Details:
========
A persistent web vulnerability is detected in the PBBoard v2.1.4 forum application.
The bug allows remote attackers to implement/inject malicious script code on the application side (persistent).
The persistent vulnerability is located in the add poll function when adding a thread. The malicious code can be injected in the `answer field`.
The output listing page with the pool executed the malicious persistent script code (JS/HTML).
Successful exploitation of the vulnerability can lead to stable (persistent) context manipulation.
Exploitation requires low user inter-action.

Vulnerable Module(s):
[+] Add thread > Add poll

Vulnerable Parameter(s):
[+] [Answer]


Proof of Concept:
=================
The persistent input validation vulnerabilities can be exploited by remote attackers with low privileged
user account & required user inter action. For demonstration or reproduce ...

To reproduce the vulnerability, the attacker should add a new thread and the check on the add poll button. After that
the attacker can add his malicious code in the answer field of the poll. Anyone who's viewing that thread will be
exploited by the malicious code. Such attack can result in session hijacking, redirecting or cookie theft. Moreover,
the persistent XSS can be exploited to launch a CSRF attack to the user and to exploit the other CSRF vulnerabilities
in the same product to completely hack the application.

Poll: <iframe src=http://www.vuln-lab.com></iframe> !
</span>
</td>
</tr>
<tr align="center">
<td class="thead" width="95%" colspan="3">
Question :<strong>&<iframe src=http://www.vuln-lab.com></iframe> !</strong>
</td>
</tr> <tr>
<td class="row1" width="50%">
<input type="radio" name="answer" value="0">
<iframe src=http://www.vw.de></iframe></td>
<td class="row1" width="40%">
<img src="look/styles/forum/main/images/bar_right.gif" alt="" width="4" height="11"><img src="look/styles/forum/main/images/bar.gif"
alt="" width="0" height="11"><img src="look/styles/forum/main/images/bar_left.gif" alt="" width="4" height="11">
</td>
<td class="row1" width="12%" align="center">
Voters: 0 </td>
</tr>

<tr>
<td class="row1" width="50%">
<input type="radio" name="answer" value="1">
<[PERSISTENT SCRIPT CODE]></iframe></td>
<td class="row1" width="40%">
<img src="look/styles/forum/main/images/bar_right.gif" alt="" width="4" height="11">
<img src="look/styles/forum/main/images/bar.gif" alt="" width="0" height="11">
<img src="look/styles/forum/main/images/bar_left.gif" alt="" width="4" height="11">
</td>
<td class="row1" width="12%" align="center">


Risk:
=====
The security risk of the persistent input validation vulnerabilities is estimated as medium(+).







Credits:
========
Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed [the StOrM) (storm@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.

Domains: www.vulnerability-lab.com - www.vuln-lab.com
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

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-Lab






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users