Document Title: =============== Gwibber v2.29.1 & v3.x - Persistent Software Vulnerability References (Source): ==================== http://www.vulnerability-lab.com/get_content.php?id=365 Release Date: ============= 2011-12-21 Vulnerability Laboratory ID (VL-ID): ==================================== 365 Common Vulnerability Scoring System: ==================================== 2.5 Product & Service Introduction: =============================== Gwibber is a microblogging client for the GNOME desktop environment. It was created by Ryan Paul, a writer for Ars Technica. Gwibber is distributed under the GNU GPL license.It supports Linux and is written in Python using the PyGTK library. It is included by default in Ubuntu 10.04 and above. (Copy of the Vendor Homepage: http://en.wikipedia.org/wiki/Gwibber ) Abstract Advisory Information: ============================== A Vulnerability Laboratory researcher discovered a persistent software vulnerability on the Gwibber social client software. Vulnerability Disclosure Timeline: ================================== 2011-11-21: Vendor Notification 2011-12-22: Public or Non-Public Disclosure Discovery Status: ================= Published Affected Product(s): ==================== Exploitation Technique: ======================= Remote Severity Level: =============== Low Technical Details & Description: ================================ A persistent input validation vulnerability is detected on the linux version of Gwibber. The bug is located in the search bar module of the index. The vulnerability allows an local attacker to implement persistent malicious script codes on a Gwibber software main module. The successfully exploitation can lead to redirects, client side exploitation, session hijacking, malicious downloads & request manipulation over the vulnerable software main module. Vulnerable Module(s): [+] Search Option Picture(s): ../1.png ../2.png ../3.png Security Risk: ============== The security risk of the persistent software vulnerability is estimated as medium. Credits & Authors: ================== Vulnerability Research Laboratory - Ucha Gobejishvili (longrifle0x) 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 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