ASP 內建 Request("param") 會依序檢查 QueryString、Form、Cookies、ServerVariables。若開發者為求便利使用 id = Request("id"),攻擊者可透過植入 Cookie 繞過針對 QueryString/Form 的防注入檢查,直接注入 SQL 指令。
/1.asp?id=123 使用 Request("id") 取值。javascript:document.cookie="id="+escape("123 and 1=1");123 and 1=2,頁面異常即證明可注入。' 僅接受 QueryString
id = Request.QueryString("id")
' 僅接受 Form
id = Request.Form("id")
Function GetParam(name, source)
Select Case LCase(source)
Case "q": GetParam = Request.QueryString(name)
Case "f": GetParam = Request.Form(name)
Case "c": GetParam = Request.Cookies(name)
Case Else: GetParam = ""
End Select
' 簡易過濾 (實務建議用參數化查詢)
GetParam = Replace(GetParam, "'", "''")
End Function
Set cmd = Server.CreateObject("ADODB.Command")
cmd.ActiveConnection = conn
cmd.CommandText = "SELECT * FROM Products WHERE ID = ?"
cmd.Parameters.Append cmd.CreateParameter("@id", 3, 1, , id) ' adInteger
Set rs = cmd.Execute
Response.Cookies("sessionId").HttpOnly = True
Response.Cookies("sessionId").Secure = True ' 僅 HTTPS
避免使用 Request("...") 捷徑,明確指定參數來源、採用參數化查詢、設定 Cookie 安全屬性,即可有效杜絕 Cookie 注入與大多數 SQL 注入風險。