Home→Descriptions→SA38513
| Secunia ID | |
| Release Date |
09 Feb 2010 |
| Last Change |
15 Aug 2011 |
| Criticality | |
| Solution Status |
Unpatched |
| Software |
VideoDB 3.x |
| Where | |
| Impact |
Cross-Site ScriptingCross-Site Scripting vulnerabilities allow a third party to manipulate the content or behaviour of a web application in a user's browser, without compromising the underlying system. Different Cross-Site Scripting related vulnerabilities are also classified under this category, including "script insertion" and "cross-site request forgery". Cross-Site Scripting vulnerabilities are often used against specific users of a website to steal their credentials or to conduct spoofing attacks. Exposure of sensitive informationVulnerabilities where documents or credentials are leaked or can be revealed either locally or from remote. Manipulation of dataThis includes vulnerabilities where a user or a remote attacker can manipulate local data on a system, but not necessarily be able to gain escalated privileges or system access. The most frequent type of vulnerabilities with this impact are SQL-injection vulnerabilities, where a malicious user or person can manipulate SQL queries. |
| Description |
A weakness and multiple vulnerabilities have been discovered in VideoDB, which can be exploited by malicious users to disclose potentially sensitive information and to conduct SQL injection attacks and by malicious people to conduct cross-site scripting and SQL injection attacks. 1) Input passed to the "error" parameter in login.php (when "VDBusername" and "VDBpassword" cookies are not set) is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site. 2) Input passed via the "page" parameter to help.php is not properly verified before reading files' contents from local resources. This can be exploited to disclose the content of arbitrary files via directory traversal sequences. NOTE: Successful exploitation requires that the file's content match certain regular expressions for the content to be displayed. 3) Input passed via the "fields[]" parameter to search.php (when the "q" parameter is set) is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. 4) Input passed via the "username" POST parameter to login.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. NOTE: This can further be exploited to bypass the authentication mechanism. 5) Input passed via the "diskid" parameter to borrow.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. The vulnerabilities are confirmed in version 3.1.0. Other versions may also be affected. |
| Solution |
Edit the source code to ensure that input is properly sanitised. |
| Reported by |
1) vr |
| Original Advisory |
Valentin: |