ASPNuke Comment_Post.ASP Cross-Site Scripting Vulnerability
BID:14226
Info
ASPNuke Comment_Post.ASP Cross-Site Scripting Vulnerability
| Bugtraq ID: | 14226 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 12 2005 12:00AM |
| Updated: | Jul 12 2005 12:00AM |
| Credit: | rUnViRuS is credited with the discovery of this vulnerability. |
| Vulnerable: |
ASPNuke ASPNuke 0.80 |
| Not Vulnerable: | |
Discussion
ASPNuke Comment_Post.ASP Cross-Site Scripting Vulnerability
ASPNuke is prone to a cross-site scripting vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input.
An attacker may leverage this issue to have arbitrary script code executed in the browser of an unsuspecting user in the context of the affected site. This may facilitate the theft of cookie-based authentication credentials as well as other attacks.
ASPNuke is prone to a cross-site scripting vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input.
An attacker may leverage this issue to have arbitrary script code executed in the browser of an unsuspecting user in the context of the affected site. This may facilitate the theft of cookie-based authentication credentials as well as other attacks.
Exploit / POC
ASPNuke Comment_Post.ASP Cross-Site Scripting Vulnerability
No exploit is required.
The following proof of concept URI is available:
http://www.example.com/module/support/task/comment_post.asp?TaskID=<script>JavaScript:alert(document.cookie);</script>
No exploit is required.
The following proof of concept URI is available:
http://www.example.com/module/support/task/comment_post.asp?TaskID=<script>JavaScript:alert(document.cookie);</script>
Solution / Fix
ASPNuke Comment_Post.ASP Cross-Site Scripting Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.