AWCM Multiple Input Validation Vulnerabilities
BID:43441
Info
AWCM Multiple Input Validation Vulnerabilities
| Bugtraq ID: | 43441 |
| Class: | Input Validation Error |
| CVE: |
CVE-2009-3218 CVE-2009-3219 |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 24 2009 12:00AM |
| Updated: | Jul 24 2009 12:00AM |
| Credit: | SwEET-DeViL and indoushka |
| Vulnerable: |
AWCM CMS AWCM 2.1 AWCM CMS AWCM 2.0 |
| Not Vulnerable: | |
Discussion
AWCM Multiple Input Validation Vulnerabilities
AWCM is prone to multiple input-validation vulnerabilities because it fails to adequately sanitize user-supplied input. These vulnerabilities include local file-include, SQL-injection, and cross-site-scripting issues.
Exploiting these issues can allow an attacker to steal cookie-based authentication credentials, view local files within the context of the webserver, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. Other attacks may also be possible.
AWCM 2.1 is vulnerable; other versions may also be affected.
AWCM is prone to multiple input-validation vulnerabilities because it fails to adequately sanitize user-supplied input. These vulnerabilities include local file-include, SQL-injection, and cross-site-scripting issues.
Exploiting these issues can allow an attacker to steal cookie-based authentication credentials, view local files within the context of the webserver, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. Other attacks may also be possible.
AWCM 2.1 is vulnerable; other versions may also be affected.
Solution / Fix
AWCM Multiple Input Validation Vulnerabilities
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].