Document Title: =============== JPM Article Script 6 - SQL Injection Vulnerability References (Source): ==================== http://www.vulnerability-lab.comget_content.phpid=473 Release Date: ============= 2012-03-14 Vulnerability Laboratory ID (VL-ID): ==================================== 473 Product & Service Introduction: =============================== A PHP and MySQL light-weight article web application. (Copy of the Vendor Homepage httpwww.jpmalloy.comblogindex.php ) Abstract Advisory Information: ============================== A Vulnerability Laboratory Researchers discovered a SQL Injection Vulnerability on JPMs Article Script 6 Web Application. Vulnerability Disclosure Timeline: ================================== 2012-03-15: Public or Non-Public Disclosure Discovery Status: ================= Published Exploitation Technique: ======================= Remote Severity Level: =============== High Technical Details & Description: ================================ A remote SQL Injection vulnerability is detected on on JPMs Article Script 6 Web Application. The vulnerability allows an attacker (remote) or local low privileged user account to injectexecute own sql commands on the affected application dbms. Successful exploitation of the vulnerability results in dbms & application compromise. Vulnerable Module(s) [+] page2= [INDEX] --- Exception Logs --- You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near \'-12, 6\' at line 1 Affected Version(s) [+] JPM Article Script 6 Proof of Concept (PoC): ======================= The vulnerability can be exploited by remote attacker without required user inter action. For demonstration or reproduce ... PoC http://www.jpmalloy.com/blogindex.php?page2=-1%27[SQL-INJECTION!]&cid=0 Security Risk: ============== The security risk of the SQL Injection Vulnerability is estimated as high(+). Credits & Authors: ================== Vulnerability Research Laboratory - the_storm 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