Document Title:
===============
Jaow CMS v2.3 - Multiple Web Vulnerabilities
References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=568
Release Date:
=============
2012-05-13
Vulnerability Laboratory ID (VL-ID):
====================================
568
Common Vulnerability Scoring System:
====================================
7.2
Product & Service Introduction:
===============================
Jaow is a CMS that can manage sites of small sizes, thanks to its simple, commented code you
can easily create templates and / or create modules to suit your needs. Jaow is the solution for
small sites, blogs or portfolio. Here is the list of features currently available:
* Category Manager
* Section Manager (using TinyMCE)
* Manager menu (adding links)
* Manager template (using Vtemplate)
* File Manager (using Elfinder)
* Manager of partners
* User Manager (Administration access)
* Contact Form
* General Configuration via Back-Office
* Manager Comments
* Maintenance Manager Site
* Backing up the database
* Page Manager
* Statistics Tool
* Notation articles
* Share with social networks (twitter, Facebook)
* Customize error 404
* Generating RSS feeds
(Copy of the Vendor Homepage: http://fr.wikipedia.org/wiki/Jaow_CMS )
Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered multiple Web Vulnerabilities in Jaow v2.3 Content Management System.
Vulnerability Disclosure Timeline:
==================================
2012-05-13: Public or Non-Public Disclosure
Discovery Status:
=================
Published
Exploitation Technique:
=======================
Remote
Severity Level:
===============
High
Technical Details & Description:
================================
Multiple SQL Injection vulnerabilities are detected in in Jaow v2.3 Content Management System.
The vulnerability allows an attacker (remote) or local low privileged user account to inject/execute own sql commands
on the affected application dbms. Successful exploitation of the vulnerability results in dbms & application compromise.
Vulnerable Module(s):
[+] articles.php?modifier_articles=2&page
[+] articles.php?modifier_articles
[+] categories.php?modifier_categories=1&page
[+] categories.php?modifier_categories
[+] pages.php?modifier_pages=1&page
[+] pages.php?modifier_pages
[+] menu.php?modifier_menus=6&page
[+] menu.php?modifier_menus
[+] liens.php?modifier_liens=1&page
[+] liens.php?modifier_liens
Picture(s):
../1.png
../2.png
../3.png
Proof of Concept (PoC):
=======================
The sql injection vulnerabilities can be exploited by privileged user accounts. For demonstration or reproduce ...
PoC:
articles.php?modifier_articles=2&page=-1'[ SQL Injection ]
articles.php?modifier_articles=-1'[ SQL Injection ]
categories.php?modifier_categories=1&page=-1'[ SQL Injection ]
categories.php?modifier_categories=-1'[ SQL Injection ]
pages.php?modifier_pages=1&page=-1'[ SQL Injection ]
pages.php?modifier_pages=-1'[ SQL Injection ]
menu.php?modifier_menus=6&page=-1'[ SQL Injection ]
menu.php?modifier_menus=-1'[ SQL Injection ]
liens.php?modifier_liens=1&page=-1'[ SQL Injection ]
liens.php?modifier_liens=-1'[ SQL Injection ]
Solution - Fix & Patch:
=======================
In file: administration/pages.php
In line 49:
$Id_selection = $_GET[`modifier_pages`];
we edit:
$Id_selection = (int)$_GET[`modifier_pages`];
In file: administration/menu.php
In line 48:
$Id_selection = $_GET[`modifier_menus`];
we edit:
$Id_selection = (int)$_GET[`modifier_menus`];
In file: administration/liens.php
In line 49:
$Id_selection = $_GET[`modifier_liens`];
we edit:
$Id_selection = (int)$_GET[`modifier_liens`];
In file: administration/categories.php
In line 50:
$Id_selection = $_GET[`id`];
we edit:
$Id_selection = (int)$_GET[`id`];
In file: administration/articles.php
In line 48:
$Id_selection = $_GET[`modifier_articles`];
we edit:
$Id_selection = (int)$_GET[`modifier_articles`];
In file: administration/articles.php
In line 137:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: administration/categories.php
In line 115:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: administration/liens.php
In line 105:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: administration/menu.php
In line 103:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: administration/pages.php
In line 100:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: administration/statistiques.php
In line 184:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: administration/utilisateur.php
In line 66:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: archives.php
In line 65:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: articles.php
In line 48:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: articles_categories.php
In line 86:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
In file: liens.php
In line 68:
$start_pages = ($courant - 1) * $nb_results_p_page;
we edit:
$start_pages = ($courant - 1) * $nb_results_p_page;
$start_pages = (int)$start_pages;
if($start_pages<0) $start_pages = 0;
XSS:
In file: modules/Commentaires/mod_commentaires.php
49:
$Pseudo = addslashes($_POST[`Pseudo`]);
we edit:
$Pseudo = htmlentities(addslashes($_POST[`Pseudo`]));
In file: administration/articles.php
In line 105:
$Titre = addslashes($_POST[`titre`]);
we edit:
$Titre = htmlentities(addslashes($_POST[`titre`]));
In line 107:
$Sommaire = addslashes($_POST[`sommaire`]);
we edit:
$Sommaire = htmlentities(addslashes($_POST[`sommaire`]));
In line 108:
$Contenu = addslashes($_POST[`contenu`]);
we edit:
$Contenu = htmlentities(addslashes($_POST[`contenu`]));
In file: administration/categories.php
In line 85:
$Titre = addslashes($_POST[`titre`]);
we edit:
$Titre = htmlentities(addslashes($_POST[`titre`]));
In file: administration/pages.php
In line 71:
$Titre = addslashes($_POST[`titre`]);
we edit:
$Titre = htmlentities(addslashes($_POST[`titre`]));
In file: administration/pages.php
In line 72:
$Contenu = addslashes($_POST[`contenu`]);
we edit:
$Contenu = htmlentities(addslashes($_POST[`contenu`]));
In file: administration/configuration.php
In line 180:
$Titre = addslashes($_POST[`Titre`]);
we edit:
$Titre = htmlentities(addslashes($_POST[`Titre`]));
In line 185:
$Footer = addslashes($_POST[`Footer`]);
we edit:
$Footer = htmlentities(addslashes($_POST[`Footer`]));
In file: administration/utilisateur.php
In line 57:
$Pseudo = stripAccents($_POST[`Pseudo`]);
we edit:
$Pseudo = htmlentities(stripAccents($_POST[`Pseudo`]));
Security Risk:
==============
1.1
The security risk of the sql injection vulnerability is estimated as medium(+).
1.2
The security risk of the persistent input validation vulnerability is estimated as medium(-).
Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - snup ([email protected])
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: [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
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation