Document Title: =============== Def Blog CMS v1.0.2 - Multiple Web Vulnerabilities References (Source): ==================== http://www.vulnerability-lab.com/get_content.php?id=576 Release Date: ============= 2012-05-19 Vulnerability Laboratory ID (VL-ID): ==================================== 576 Common Vulnerability Scoring System: ==================================== 8.5 Product & Service Introduction: =============================== Blog tres simple d utilisation installable sur un serveur en moins de 10 minutes capable de gerer Des articles avec commentaires Une fiche perso avec vos informations Vos contacts avec diverses informations les concernant Vos creations avec possibilte pour les utilisateurs de les telecharger et d en donner une note Le tout parametrable via un panel direct et possibilite de gerer les articles ou autres directement dessus Possibilite de changer de template et gestion d un BBcode en Francais plus les smileys FONCTIONNE SOUS IE ET MOZILLA (Copy of the Vendor Homepage: http://www.def-blog.com ) Abstract Advisory Information: ============================== The Vulnerability Laboratory Research Team discovered multiple Web Vulnerabilities in Def-Blog v1.0.2 CMS. Vulnerability Disclosure Timeline: ================================== 2012-05-20: Public or Non-Public Disclosure Discovery Status: ================= Published Exploitation Technique: ======================= Remote Severity Level: =============== High Technical Details & Description: ================================ 1.1 Multiple SQL Injection vulnerabilities are detected in Def-Blog v1.0.2 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): [+] comlook.php [+] comaddok.php [+] modif.php [+] vue.php [+] redir.php [+] comlook.php [+] modifok.php [+] sup.php 1.2 Multiple persistent input validation vulnerabilities are detected in Def-Blog v1.0.2 Content Management System. The bugs allow remote attackers to implement/inject malicious script code on the application-side (persistent). Successful exploitation of the vulnerability can lead to session hijacking (manager/admin) or stable (persistent) context manipulation. Exploitation requires low user inter action or low privileged appliance user account. Vulnerable Module(s): [+]imprt.php [+]modifok.php Proof of Concept (PoC): ======================= 1.1 The sql injection vulnerabilities can be exploited by remote attackers without user inter action. For demonstration or reproduce ... PoC: http://127.0.0.1/defblog/comaddok.php?article=[ SQL Injection ] http://127.0.0.1/defblog/modif.php?type=article&id=[ SQL Injection ] http://127.0.0.1/defblog/modif.php?type=creas&id=[ SQL Injection ] http://127.0.0.1/defblog/vue.php?id=[ SQL Injection ] http://127.0.0.1/defblog/redir.php?id=[ SQL Injection ] Solution - Fix & Patch: ======================= 1.1 In file: comaddok.php In line: 19: $Tout = addslashes($_GET[`article`]); 20: $Tout = htmlentities($Tout); In file: comlook.php In file: 21: $Tout = addslashes($_GET[`article`]); 22: $Tout = htmlentities($Tout); In file: modif.php In file: 29: $Tout = addslashes($_GET[`id`]); 30: $Tout = htmlentities($Tout); In file: modifok.php In file: 27: $Tout = addslashes($_GET[`id`]); 28: $Tout = htmlentities($Tout); In file: sup.php In file: 29: $Tout = addslashes($_GET[`id`]); 30: $Tout = htmlentities($Tout); We must add in each of these files into the lines of: $Tout = (int)$Tout ; In file: imprt.php In file: 19: if (isset($_GET[`id`])) { $id = addslashes($_GET[`id`]); } In file: redir.php In file: 17: if (isset($_GET[`id`])) { $id = addslashes($_GET[`id`]); } In file: vue.php In file: 17: if (isset($_GET[`id`])) { $id = addslashes($_GET[`id`]); } We must add in each of these files into the lines of: $id = (int)$id; 1.2 In file: imprt.php In file: 26: $pseudo = addslashes($_POST[`pseudo`]); 28: $TheTexte = addslashes($_POST[`TheTexte`]); 92: $pseudo = addslashes($_POST[`pseudo`]); 117: if($_POST[`prenom`]!=``) { $prenom=addslashes($_POST[`prenom`]); } else { $prenom=`Aucun`; } 128: if($_POST[`prenom`]!=``) { $prenom=addslashes($_POST[`prenom`]); } else { $prenom=`Aucun`; } 119: if($_POST[`loc`]!=``) { $localisation=addslashes($_POST[`loc`]); } else { $localisation=`Aucune`; } 120: if($_POST[`loisirs`]!=``) { $loisirs=addslashes($_POST[`loisirs`]); } else { $loisirs=`Aucun`; } 121: if($_POST[`emploi`]!=``) { $emploi=addslashes($_POST[`emploi`]); } else { $emploi=`Aucun`; } 122: if($_POST[`citation`]!=``) { $citation=addslashes($_POST[`citation`]); } else { $citation=`Aucune`; } 123: if($_POST[`mail`]!=``) { $mail=addslashes($_POST[`mail`]); } else { $mail=`Aucune`; } 124: if($_POST[`msn`]!=``) { $msn=addslashes($_POST[`msn`]); } else { $msn=`Aucune`; } 125: if($_POST[`yahoo`]!=``) { $yahoo=addslashes($_POST[`yahoo`]); } else { $yahoo=`Aucune`; } 126: if($_POST[`icq`]!=``) { $icq=addslashes($_POST[`icq`]); } else { $icq=`Aucune`; } 127: if($_POST[`aim`]!=``) { $aim=addslashes($_POST[`aim`]); } else { $aim=`Aucune`; } 129: $web=addslashes($_POST[`web`]); 157: $pseudo = addslashes($_POST[`pseudo`]); 203: if($_POST[`TheTexte`]!=``) { $TheTexte=addslashes($_POST[`TheTexte`]); } else { $TheTexte=`Aucun`; } 231: $pseudo = addslashes($_POST[`pseudo`]); 260: if($_POST[`prenom`]!=``) { $prenom=addslashes($_POST[`prenom`]); } else { $prenom=`Aucun`; } 263: if($_POST[`msn`]!=``) { $msn=addslashes($_POST[`msn`]); } else { $msn=`Aucun`; } In file: modifok.php In file: 131: if($_POST[`msn`]!=``) { $msn=addslashes($_POST[`msn`]); } else { $msn=`Aucun`; } 208: if($_POST[`TheTexte`]!=``) { $TheTexte=addslashes($_POST[`TheTexte`]); } else { $TheTexte=`Aucun`; } We need to change these lines: In file: imprt.php In file: 26: $pseudo = addslashes($_POST[`pseudo`])); 28: $TheTexte = addslashes($_POST[`TheTexte`])); 92: $pseudo = addslashes($_POST[`pseudo`])); 117: if($_POST[`prenom`]!=``) { $prenom=htmlspecialchars(strip_tags($_POST[`prenom`])); } else { $prenom=`Aucun`; } 128: if($_POST[`prenom`]!=``) { $prenom=htmlspecialchars(strip_tags($_POST[`prenom`])); } else { $prenom=`Aucun`; } 119: if($_POST[`loc`]!=``) { $localisation=htmlspecialchars(strip_tags($_POST[`loc`])); } else { $localisation=`Aucune`; } 120: if($_POST[`loisirs`]!=``) { $loisirs=htmlspecialchars(strip_tags($_POST[`loisirs`])); } else { $loisirs=`Aucun`; } 121: if($_POST[`emploi`]!=``) { $emploi=htmlspecialchars(strip_tags($_POST[`emploi`])); } else { $emploi=`Aucun`; } 122: if($_POST[`citation`]!=``) { $citation=htmlspecialchars(strip_tags($_POST[`citation`])); } else { $citation=`Aucune`; } 123: if($_POST[`mail`]!=``) { $mail=htmlspecialchars(strip_tags($_POST[`mail`])); } else { $mail=`Aucune`; } 124: if($_POST[`msn`]!=``) { $msn=htmlspecialchars(strip_tags($_POST[`msn`])); } else { $msn=`Aucune`; } 125: if($_POST[`yahoo`]!=``) { $yahoo=htmlspecialchars(strip_tags($_POST[`yahoo`])); } else { $yahoo=`Aucune`; } 126: if($_POST[`icq`]!=``) { $icq=htmlspecialchars(strip_tags($_POST[`icq`])); } else { $icq=`Aucune`; } 127: if($_POST[`aim`]!=``) { $aim=htmlspecialchars(strip_tags($_POST[`aim`])); } else { $aim=`Aucune`; } 129: $web=htmlspecialchars(strip_tags($_POST[`web`])); 157: $pseudo = htmlspecialchars(strip_tags($_POST[`pseudo`])); 203: if($_POST[`TheTexte`]!=``) { $TheTexte=htmlspecialchars(strip_tags($_POST[`TheTexte`])); } else { $TheTexte=`Aucun`; } 231: $pseudo = htmlspecialchars(strip_tags($_POST[`pseudo`])); 260: if($_POST[`prenom`]!=``) { $prenom=htmlspecialchars(strip_tags($_POST[`prenom`])); } else { $prenom=`Aucun`; } 263: if($_POST[`msn`]!=``) { $msn=htmlspecialchars(strip_tags($_POST[`msn`])); } else { $msn=`Aucun`; } In file: modifok.php In file: 131: if($_POST[`msn`]!=``) { $msn=htmlspecialchars(strip_tags($_POST[`msn`])); } else { $msn=`Aucun`; } 208: if($_POST[`TheTexte`]!=``) { $TheTexte=htmlspecialchars(strip_tags($_POST[`TheTexte`])); } else { $TheTexte=`Aucun`; } Security Risk: ============== 1.1 The security risk of the sql injection vulnerabilities are estimated as critical. 1.2 The security risk of the persistent input validation vulnerabilities are estimated as medium(+). Credits & Authors: ================== Vulnerability Laboratory [Research Team] - snup (snup@vulnerability-lab.com) [ http://snup1.blogspot.com ] 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