|
Description
|
|
Multiple vulnerabilities have been discovered in ClipBucket, which can be exploited by malicious people to conduct cross-site scripting, cross-site request forgery, and SQL injection attacks and compromise a vulnerable system.
1) Input passed via multiple parameters to multiple scripts 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.
List of affected scripts and parameters:
<a href="http://[host]/channels.php?cat
" target="_blank">http://[host]/channels.php?cat
</a>
<a href="http://[host]/collections.php?cat
" target="_blank">http://[host]/collections.php?cat
</a>
<a href="http://[host]/groups.php?cat
" target="_blank">http://[host]/groups.php?cat
</a>
<a href="http://[host]/videos.php?cat
" target="_blank">http://[host]/videos.php?cat
</a>
2) Input passed via the "type" parameter to e.g. view_collection.php, view_channel.php, or view_item.php 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.
3) Input passed via the "time" parameter to videos.php or channels.php is not properly sanitised in the "update_counter()" function in includes/functions.php before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
4) Input passed via the "collection" parameter to view_item.php (when "type" is set to e.g. "photos") is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
5) The application allows users to perform certain actions via HTTP requests without performing proper validity checks to verify the requests. This can be exploited to e.g. add an administrative user when a logged-in administrative user visits a specially crafted web page.
6) Input passed via the "forgot_username" parameter to forgot.php (when "reset" is set to "Reset") is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
7) Input passed via the "type" parameter to search_result.php 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.
8) Input passed via the "username" POST parameter to signup.php 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.
9) Input passed via the "sort", "page", and "seo_cat_name" parameters to channels.php and videos.php, "sort", "page", "seo_cat_name", and "time" to "collections.php" and "groups.php", and "cat", "sort", "page", "seo_cat_name" and "time" params to photos.php 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.
10) Input passed via the "ci_id" POST parameter to ajax.php (while "mode" is set to "get_item" and "type" is set to "photos" or "videos") is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
11) Input passed via the "id" POST parameter to ajax.php (while "mode" is set to "rating", "rating" is set to "1", and "type" is set to "video", "photo", "collection", or "user", and "mode" is set to "add_to_fav" and "type" is set to "video", "photo", or "collection" ) is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
12) Input passed via the "cid" POST parameter to ajax.php (while "mode" is set to "get_item", "add_new_item", or "remove_collection_item" and "type" is set to "photos" or "videos") is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
13) Input passed via the "query" GET paramete to search_result.php 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.
This vulnerability is confirmed in version 2.6-r738 and 2.6-r738-security-fixed-p2. Prior versions may also be affected.
14) The application bundles a vulnerable version of Open Flash Chart.
For more information:
SA37903
The vulnerabilities #1 through #12 and #14 are confirmed in version 2.6-r738 and 2.6-r738-security-fixed-p3. Other versions may also be affected.
15) Input passed via the "email" POST parameter to signup.php (when "agree" is set to "yes" and "username", "password", "cpassword", "country", "gender", "dob", "category", and "signup" are 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.
This vulnerability is confirmed in version 2.6-r738-security-fixed-p3. Other versions may also be affected.
|
