Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ATutor-Cross-Site Scripting (XSS) #135

Closed
ddddyyy opened this issue Sep 30, 2017 · 3 comments
Closed

ATutor-Cross-Site Scripting (XSS) #135

ddddyyy opened this issue Sep 30, 2017 · 3 comments

Comments

@ddddyyy
Copy link

ddddyyy commented Sep 30, 2017

Product: ATutor
Download: https://github.com/atutor/ATutor
Vunlerable Version: 2.2.2 and probably prior
Tested Version: 2.2.2
Author: ADLab of Venustech

Advisory Details:
Cross-Site Scripting (XSS) were discovered in“ATutor 2.2.2”, which can be exploited to execute arbitrary JS code.

The parameter "url" in the file /ATutor/mods/_standard/rss_feeds/edit_feed.php is unsafe, we can bypass the XSS filter.An attacker could execute arbitrary JS code in a browser in the context of the vulnerable website.
The exploitation examples below use the "alert()" JavaScript function to see a pop-up messagebox:
the poc is : =file%3A%2F%2F%2Fetc%2Fpasswd+%3C%3E%3Cimg+src%3Dxx+onerror%3Dalert%281%29%3E

1111

@atutor
Copy link
Owner

atutor commented Sep 30, 2017

Not able to make your poc work. Can provide a little more details how you used it?

@ddddyyy
Copy link
Author

ddddyyy commented Oct 1, 2017

@atutor
I am providing more details about this vulnerability.
setp1: In the file /ATutor/mods/_standard/rss_feeds/edit_feed.php, while adding a news feed, and the parameter "url" is "file%3A%2F%2F%2Fetc%2Fpasswd+%3C%3E%3Cimg+src%3Dxx+onerror%3Dalert%281%29%3E"
2

setp2: Visiting the url "http://site/ATutor/mods/_standard/rss_feeds/index.php", we will see a pop-up messagebox.

3

@atutor
Copy link
Owner

atutor commented Oct 1, 2017

Issue has now been resolved at:
9292360
Given it is a relatively minor issue, we will release this fix in the next release (2.2.3) rather than posting a patch. Mention its fixed in 2.2.3, or point to the git commit for the fix for earlier versions, in your report.

@atutor atutor closed this as completed Oct 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants