LogMethods A2Z.JSP Cross-Site Scripting Vulnerability
BID:17675
Info
LogMethods A2Z.JSP Cross-Site Scripting Vulnerability
| Bugtraq ID: | 17675 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Apr 24 2006 12:00AM |
| Updated: | Apr 24 2006 09:36PM |
| Credit: | r0t is credited with the discovery of this vulnerability. |
| Vulnerable: |
David Zhong logMethods 0.9 |
| Not Vulnerable: | |
Discussion
LogMethods A2Z.JSP Cross-Site Scripting Vulnerability
LogMethods 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 help the attacker steal cookie-based authentication credentials and launch other attacks.
LogMethods versions 0.9 and prior are vulnerable to this issue; other versions may also be affected.
LogMethods 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 help the attacker steal cookie-based authentication credentials and launch other attacks.
LogMethods versions 0.9 and prior are vulnerable to this issue; other versions may also be affected.
Exploit / POC
LogMethods A2Z.JSP Cross-Site Scripting Vulnerability
This issue can be exploited through a web client.
This issue can be exploited through a web client.
Solution / Fix
LogMethods A2Z.JSP 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]:[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]:[email protected]