|
Description
|
|
A weakness, a security issue, and multiple vulnerabilities have been discovered in Saurus CMS, which can be exploited by malicious users to disclose potentially sensitive information and by malicious people to bypass certain security restrictions and conduct spoofing, cross-site scripting, request forgery, script insertion, and SQL injection attacks.
1) The application allows users to perform certain actions via HTTP requests without making any validity checks to verify the requests. This can be exploited to e.g. change the password of the administrator, empty the trash, modify certain settings, and delete arbitrary forms.
2) Input passed via the "dialog" parameter to admin/fckeditor_dialog_image.php (when "file_id" is set to a valid file ID) is not properly verified before being used to include files. This can be exploited to include arbitrary files from local resources via directory traversal sequences.
3) Input passed via the "id" and "pg" GET parameters to index.php is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
4) Input passed via the "sites" parameter to index.php (when "op" is set to "search") is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
5) Input passed via the "user" parameter to admin/index.php (when "op" is set to "login") is not properly sanitised before being used. This can be exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious data is being viewed.
Successful exploitation of this vulnerability requires the "Enable site log" option to be enabled (enabled by default).
6) Input passed via the "pg" parameter to index.php is not properly sanitised before being used. This can be exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious data is being viewed.
Successful exploitation of this vulnerability requires the "Save PHP and MySQL errors into the database" option to be enabled (enabled by default).
7) Input passed to multiple parameters in 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]/kalender.php?form&vorm&form_field&lahter&month
" target="_blank">http://[host]/kalender.php?form&...field&lahter&month
</a>
<a href="http://[host]/editor/kalender.php?form&vorm&form_field&lahter&month
" target="_blank">http://[host]/editor/kalender.ph...field&lahter&month
</a>
<a href="http://[host]/admin/delete_log.php?tbl
" target="_blank">http://[host]/admin/delete_log.php?tbl
</a>
<a href="http://[host]/admin/edit_adminpage.php?id&op
" target="_blank">http://[host]/admin/edit_adminpage.php?id&op
</a>
<a href="http://[host]/admin/edit_group.php?group_id
" target="_blank">http://[host]/admin/edit_group.php?group_id
</a>
<a href="http://[host]/admin/profile_data.php?profile_id
" target="_blank">http://[host]/admin/profile_data.php?profile_id
</a>
<a href="http://[host]/admin/edit.php?profile_id
" target="_blank">http://[host]/admin/edit.php?profile_id
</a>
<a href="http://[host]/admin/edit_profile.php?pid
" target="_blank">http://[host]/admin/edit_profile.php?pid
</a>
<a href="http://[host]/admin/profiles.php?profile_id&source_table&did
" target="_blank">http://[host]/admin/profiles.php...d&source_table&did
</a>
<a href="http://[host]/admin/sys_alias.php?flt_keel&keel_id
" target="_blank">http://[host]/admin/sys_alias.php?flt_keel&keel_id
</a>
<a href="http://[host]/admin/sys_sonad_loetelu.php?flt_keel
" target="_blank">http://[host]/admin/sys_sonad_loetelu.php?flt_keel
</a>
<a href="http://[host]/admin/permissions.php?selected_group&user_id&group_id&role_id
" target="_blank">http://[host]/admin/permissions....d&group_id&role_id
</a>
<a href="http://[host]/admin/file_source.php?callback
" target="_blank">http://[host]/admin/file_source.php?callback
</a>
<a href="http://[host]/admin/change_config.php?group&flt_keel
" target="_blank">http://[host]/admin/change_config.php?group&flt_keel
</a>
<a href="http://[host]/admin/forms.php?form_id
" target="_blank">http://[host]/admin/forms.php?form_id
</a>
<a href="http://[host]/admin/lang_file.php?flt_keel&keel_id
" target="_blank">http://[host]/admin/lang_file.php?flt_keel&keel_id
</a>
8) Input appended to the URL after /admin/user_management.php and /admin/select_group.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 "url" GET parameter to redirect.php and editor/redirect.php is not properly verified before being used to redirect users. This can be exploited to redirect a user to an arbitrary website e.g. when a user clicks a specially crafted link to the affected script hosted on a trusted domain.
10) The application does not properly verify access permissions when accessing admin/check_requirements.php. This can be exploited to disclose e.g. web server version details.
The vu... (truncated text)
|
