<span id="7ztzv"></span>
<sub id="7ztzv"></sub>

<span id="7ztzv"></span><form id="7ztzv"></form>

<span id="7ztzv"></span>

        <address id="7ztzv"></address>

            Unsafe Reflection

            ABSTRACT

            攻擊者會創建一個意想不到且貫穿于整個應用程序的控制流路徑,從而逃避潛在的安全檢查。

            EXPLANATION

            若攻擊者可以為應用程序提供確定實例化哪個類或調用哪個方法的參數值,那么就有可能創建一個貫穿于整個應用程序的控制流路徑,而該路徑并非是應用程序開發者最初設計的。這種攻擊途徑可能使攻擊者避開 authentication 或 access control 檢測,或使應用程序以一種意想不到的方式運行。即使狡猾的攻擊者只能控制傳送給指定函數或構造函數的參數,也有可能會成功地發起攻擊。


            例如: 程序員通常使用反射來實現命令發送器。以下示例顯示了一個未使用反射的命令發送器:


            ...
            Dim ctl As String
            Dim ao As New Worker()
            ctl = Request.Form("ctl")
            If (String.Compare(ctl,"Add") = 0) Then
            ao.DoAddCommand(Request)
            Else If (String.Compare(ctl,"Modify") = 0) Then
            ao.DoModifyCommand(Request)
            Else
            App.EventLog("No Action Found", 4)
            End If
            ...


            程序員可能會修改這段代碼,以便按照如下情況使用反射:


            ...
            Dim ctl As String
            Dim ao As New Worker()
            ctl = Request.Form("ctl")
            CallByName(ao, ctl, vbMethod, Request)
            ...


            乍一看,這種修改似乎具有許多優點。代碼的行數比原先少了,if/else 代碼段也完全刪除了,而且還可以在不改變命令發送器的情況下增加新的命令類型。

            然而,進行這樣的修改后,攻擊者就可以調用任意一個實施了 Worker 對象的方法。如果命令發送器對 access control 負責,那么,只要程序員在 Worker 類中創建了新方法,就必須修改發送器的 access control 邏輯。如果 access control 邏輯過期,那么某些 Worker 方法將不具有任何 access control。

            解決 access control 問題的方法是讓 Worker 對象負責執行 access control 檢查。下面是一段重新修改的代碼:


            ...
            Dim ctl As String
            Dim ao As New Worker()
            ctl = Request.Form("ctl")
            If (ao.checkAccessControl(ctl,Request) = True) Then
            CallByName(ao, "Do" & ctl & "Command", vbMethod, Request)
            End If
            ...


            雖然有所改進,但它鼓勵了采用分散化的手段進行 access control,這使程序員在 access control 上更加容易犯錯誤。

            REFERENCES

            [1] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A1 Unvalidated Input

            [2] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A4 Insecure Direct Object Reference

            [3] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A4 Insecure Direct Object References

            [4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3510 CAT I, APP3570 CAT I

            [5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3510 CAT I, APP3570 CAT I

            [6] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 470

            [7] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 6.3.1.1, Requirement 6.5.4

            [8] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.1

            [9] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 6.5.8

            [10] Standards Mapping - FIPS200 - (FISMA) SI


            Copyright 2013 Fortify Software - All rights reserved.
            (Generated from version 2013.1.1.0008 of the Fortify Secure Coding Rulepacks)
            desc.dataflow.dotnet.unsafe_reflection

            <span id="7ztzv"></span>
            <sub id="7ztzv"></sub>

            <span id="7ztzv"></span><form id="7ztzv"></form>

            <span id="7ztzv"></span>

                  <address id="7ztzv"></address>

                      亚洲欧美在线