界: Environment

本節包括原始程式碼之外的所有內容，但對於建立中產品的安全性仍至關重要。由於此領域所涵蓋的問題與原始程式碼沒有直接關係，因此我們將其與其他領域分開。

HTML5: MIME Sniffing

Abstract

方法 Application_BeginRequest 為空，或不包括將 X-Content-Type-Options 設定為 nosniff 的函數呼叫，或嘗試移除該表頭。

Explanation

MIME 攔截，是檢查位元組資料流內容的作法，可嘗試推算其內資料的檔案格式。

如果不明確停用 MIME 攔截，則某些瀏覽器可能會遭受操縱，從而以非預期的方式解譯資料，導致出現 Cross-site scripting 攻擊。

對於可能包含使用者可控內容的每個頁面，您應該使用 HTTP 表頭 X-Content-Type-Options: nosniff。

References

[1] Reducing MIME type security risks

[2] ASP.NET Configuration Files

[3] Global.asax Syntax

[4] IE8 Security Part V: Comprehensive Protection

[5] Custom HttpModule Example

[6] HttpResponse Class

[7] MIME types and stylesheets

[8] Standards Mapping - Common Weakness Enumeration CWE ID 554

[9] Standards Mapping - Common Weakness Enumeration Top 25 2019 [3] CWE ID 020

[10] Standards Mapping - Common Weakness Enumeration Top 25 2020 [3] CWE ID 020

[11] Standards Mapping - Common Weakness Enumeration Top 25 2021 [4] CWE ID 020

[12] Standards Mapping - Common Weakness Enumeration Top 25 2022 [4] CWE ID 020

[13] Standards Mapping - Common Weakness Enumeration Top 25 2023 [6] CWE ID 020

[14] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002754

[15] Standards Mapping - FIPS200 CM

[16] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[17] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[18] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[19] Standards Mapping - OWASP Application Security Verification Standard 4.0 5.1.3 Input Validation Requirements (L1 L2 L3), 5.1.4 Input Validation Requirements (L1 L2 L3), 14.1.3 Build (L2 L3)

[20] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls

[21] Standards Mapping - OWASP Mobile 2024 M8 Security Misconfiguration

[22] Standards Mapping - OWASP Top 10 2004 A10 Insecure Configuration Management

[23] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration

[24] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration

[25] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration

[26] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.10

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.1

[29] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.1

[30] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.1

[31] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.1

[32] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.1

[33] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.1

[34] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[35] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[36] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection

[37] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection

[38] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002560 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002560 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002560 CAT I

[48] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002560 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002560 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002560 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002560 CAT I

[52] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002560 CAT I

[53] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002560 CAT I

[54] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002560 CAT I

[55] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002560 CAT I

[56] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002560 CAT I

[57] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002560 CAT I

[58] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002560 CAT I

[59] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002560 CAT I

[60] Standards Mapping - Web Application Security Consortium Version 2.00 Application Misconfiguration (WASC-15)

desc.structural.dotnet.html5_mime_sniffing

Abstract

應用程式套用 MIME 攔截演算法，或未將 X-Content-Type-Options 設定為 nosniff。

Explanation

MIME 攔截是檢查位元組串流內容的做法，可嘗試推算其中所包含資料的檔案格式。

如果不明確停用 MIME 攔截，則某些瀏覽器可能會遭受操縱，從而以非預期的方式解譯資料，導致出現 Cross-Site Scripting 攻擊。
撰寫 Web 應用程式時，請將 HTTP 標頭 X-Content-Type-Options: nosniff 用於可能含有使用者可控制內容的每個頁面中。
撰寫用戶端應用程式時，不得使用 MIME 攔截演算法確定伺服器的回應 Content-Type。

範例：下列程式碼使用 net.http.DetectContentType() 確定資源 Content-Type：


    ...
    resp, err := http.Get("http://example.com/")
    if err != nil {
        // handle error
    }
    defer resp.Body.Close()
    body, err := ioutil.ReadAll(resp.Body)

    content_type := DetectContentType(body)
    ...

References

[1] OWASP OWASP Secure Headers Project

[2] WHATWG MIME Sniffing

[3] Standards Mapping - Common Weakness Enumeration CWE ID 554

[4] Standards Mapping - Common Weakness Enumeration Top 25 2019 [3] CWE ID 020

[5] Standards Mapping - Common Weakness Enumeration Top 25 2020 [3] CWE ID 020

[6] Standards Mapping - Common Weakness Enumeration Top 25 2021 [4] CWE ID 020

[7] Standards Mapping - Common Weakness Enumeration Top 25 2022 [4] CWE ID 020

[8] Standards Mapping - Common Weakness Enumeration Top 25 2023 [6] CWE ID 020

[9] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002754

[10] Standards Mapping - FIPS200 CM

[11] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[12] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[13] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[14] Standards Mapping - OWASP Application Security Verification Standard 4.0 5.1.3 Input Validation Requirements (L1 L2 L3), 5.1.4 Input Validation Requirements (L1 L2 L3), 14.1.3 Build (L2 L3)

[15] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls

[16] Standards Mapping - OWASP Mobile 2024 M8 Security Misconfiguration

[17] Standards Mapping - OWASP Top 10 2004 A10 Insecure Configuration Management

[18] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration

[19] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration

[20] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration

[21] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.10

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.1

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.1

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.1

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.1

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.1

[29] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection

[32] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection

[33] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I

[34] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I

[36] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002560 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002560 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002560 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002560 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002560 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002560 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002560 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002560 CAT I

[48] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002560 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002560 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002560 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002560 CAT I

[52] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002560 CAT I

[53] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002560 CAT I

[54] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002560 CAT I

[55] Standards Mapping - Web Application Security Consortium Version 2.00 Application Misconfiguration (WASC-15)

desc.dataflow.golang.html5_mime_sniffing

Abstract

應用程式不會將 X-Content-Type-Options 設定為 nosniff，或明確停用此安全性標頭。

Explanation

MIME 攔截是檢查位元組串流內容的做法，可推算其中所包含資料的檔案格式。

如果未明確停用 MIME 攔截，攻擊者可以操縱某些瀏覽器以非預期的方式解譯資料，進行導致出現 Cross-Site Scripting 攻擊。對於可能包含使用者可控內容的每個頁面，您應該使用 HTTP 標頭 X-Content-Type-Options: nosniff。

範例：以下程式碼會將受 Spring Security 保護的應用程式設定為停用 MIME 攔截保護：


	<http auto-config="true">
        ...
        <headers>
            ...
            <content-type-options disabled="true"/>
        </headers>
	</http>

References

[1] OWASP OWASP Secure Headers Project

[2] Standards Mapping - Common Weakness Enumeration CWE ID 554

[3] Standards Mapping - Common Weakness Enumeration Top 25 2019 [3] CWE ID 020

[4] Standards Mapping - Common Weakness Enumeration Top 25 2020 [3] CWE ID 020

[5] Standards Mapping - Common Weakness Enumeration Top 25 2021 [4] CWE ID 020

[6] Standards Mapping - Common Weakness Enumeration Top 25 2022 [4] CWE ID 020

[7] Standards Mapping - Common Weakness Enumeration Top 25 2023 [6] CWE ID 020

[8] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002754

[9] Standards Mapping - FIPS200 CM

[10] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[11] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[12] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[13] Standards Mapping - OWASP Application Security Verification Standard 4.0 5.1.3 Input Validation Requirements (L1 L2 L3), 5.1.4 Input Validation Requirements (L1 L2 L3), 14.1.3 Build (L2 L3)

[14] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls

[15] Standards Mapping - OWASP Mobile 2024 M8 Security Misconfiguration

[16] Standards Mapping - OWASP Top 10 2004 A10 Insecure Configuration Management

[17] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration

[18] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration

[19] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration

[20] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.10

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.1

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.1

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.1

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.1

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.1

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection

[32] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I

[33] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I

[34] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I

[36] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002560 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002560 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002560 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002560 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002560 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002560 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002560 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002560 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002560 CAT I

[48] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002560 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002560 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002560 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002560 CAT I

[52] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002560 CAT I

[53] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002560 CAT I

[54] Standards Mapping - Web Application Security Consortium Version 2.00 Application Misconfiguration (WASC-15)

desc.config.java.html5_mime_sniffing

Abstract

Node.js 應用程式不會將 X-Content-Type-Options 設定為 nosniff，或明確停用此安全性標頭。

Explanation

MIME 攔截是檢查位元組串流內容的做法，可嘗試推算其中所包含資料的檔案格式。

如果不明確停用 MIME 攔截，則某些瀏覽器可能會遭受操縱，從而以非預期的方式解譯資料，導致出現 Cross-site scripting 攻擊。

對於可能包含使用者可控內容的每個頁面，您應該使用 HTTP 表頭 X-Content-Type-Options: nosniff。

References

[1] Node.js Security Checklist

[2] OWASP OWASP Secure Headers Project