Sungard Banner System XSS

2009-04-21 / 2009-04-22
Credit: gamr
Risk: Low
Local: No
Remote: Yes
CWE: CWE-79


CVSS Base Score: 4.3/10
Impact Subscore: 2.9/10
Exploitability Subscore: 8.6/10
Exploit range: Remote
Attack complexity: Medium
Authentication: No required
Confidentiality impact: None
Integrity impact: Partial
Availability impact: None

_| _| _|_|_| _|_|_| _| _| _| _| _| _|_| _|_| By: gamr _| _| _| _| _| _| _|_|_| _|_|_| # Header # Product - Banner Student System by SunGard Specific Page - http://www.EXAMPLE.com/PATH/twbkwbis.P_SecurityQuestion (Change Security Question) Version - 7.4 / earlier versions could be effected also Product URL - http://www.sungardhe.com/Products/Product.aspx?id=1024 Bug Type - Cross Site Scripting (XSS) Discovery Date - 04/06/2009 Notification Date - 04/06/2009 # Contact # Author - gmar Website - yougotxssed.com # Bug in a nut shell # Students that use this system could inject malicious code into the "New Question: " field (NAME="question"). When saving the changes, the system does not strip out HTML entities. # Bug scenario # Jim does not like his teacher / administrator at his school. He changes his forgotten pin security question. He puts in a specially crafted piece of code in the field to call a remote javascript file. He emails his teacher administrator and tells them he has forgotten his password and wonders if they could walk him through out to retrieve it. He tells them that he can not get it to work and asks them if the could try to retrieve his password. They enter in his username and hit the "forget password?" button. The next screen comes up and the script is launched. Jim could steal the session of the teacher / administrator, he could fake a login page and wait for his teacher /administrator to authenticate, or he could just do malicious things to their browser. # Bug PoC # Enter ANY html into the "New Question" field and hit submit. Logout and then go to the login screen again. Enter in your username and hit forget password. # Fix # Sanitize the user input in all fields to make sure there is no unwanted characters ( html entities ). You could encode them on POST.

References:

http://www.securityfocus.com/bid/34620
http://www.securityfocus.com/archive/1/archive/1/502810/100/0/threaded


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top