界: Security Features

软件安全不是安全软件。此处我们关注的主题包括身份验证、Access Control、机密性、加密和权限管理。

Cookie Security: Overly Permissive SameSite Attribute

Abstract

会话 Cookie 上的 SameSite 属性未设置为 Strict。

Explanation

浏览器会自动将 Cookie 附加到对设置 Cookie 的站点发出的每个 HTTP 请求中。Cookie 可能存储敏感数据，例如会话 ID 和授权令牌，或者在会话期间对同一站点的不同请求之间共享的站点数据。攻击者可以通过从客户机上加载的第三方网站页面生成对已验证站点的请求来执行模拟攻击，因为浏览器会自动将 Cookie 附加到请求中。

SameSite 参数限制了 Cookie 的作用域，因此只有当请求是从第一方或同一站点上下文生成时，才会将 Cookie 附加到请求。这样有助于保护 Cookie 免受 Cross-Site Request Forgery (CSRF) 攻击。SameSite 参数可以有以下三个值：

- Strict：当设置为 Strict 时，Cookie 仅在顶级导航时与请求一起发送。
- Lax：当设置为 Lax 时，Cookie 会在顶级导航时与从第三方站点发送到主机的 GET 请求一起从同一主机发送。例如，假设第三方站点拥有链接到主机站点的 iframe 或 href 标签。如果用户点击链接，请求将包含 Cookie。
- None：Cookie 随对 Cookie 设置的路径和域范围内的站点的所有请求一起发送。因使用 POST 方法提交表单而生成的请求也可以随请求一起发送 Cookie。

示例 1：以下代码将会话 Cookie 的 SameSite 参数设置为 Lax。


...
Cookie cookie = new Cookie('name', 'Foo', path, -1, true, 'Lax');
...

References

[1] HTTP State Management Mechanism Internet Engineering Task Force

[2] SameSite Browser Compatibility Can I Use

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

[4] Standards Mapping - Common Weakness Enumeration Top 25 2019 [9] CWE ID 352

[5] Standards Mapping - Common Weakness Enumeration Top 25 2020 [9] CWE ID 352

[6] Standards Mapping - Common Weakness Enumeration Top 25 2021 [9] CWE ID 352

[7] Standards Mapping - Common Weakness Enumeration Top 25 2022 [9] CWE ID 352

[8] Standards Mapping - Common Weakness Enumeration Top 25 2023 [9] CWE ID 352

[9] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-001310, CCI-001941, CCI-001942

[10] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

[11] Standards Mapping - NIST Special Publication 800-53 Revision 4 IA-2 Identification and Authentication (Organizational Users) (P1), SC-23 Session Authenticity (P1), SI-10 Information Input Validation (P1)

[12] Standards Mapping - NIST Special Publication 800-53 Revision 5 IA-2 Identification and Authentication (Organizational Users), SC-23 Session Authenticity, SI-10 Information Input Validation

[13] Standards Mapping - OWASP Application Security Verification Standard 4.0 3.4.3 Cookie-based Session Management (L1 L2 L3)

[14] Standards Mapping - OWASP Mobile 2014 M5 Poor Authorization and Authentication

[15] Standards Mapping - OWASP Mobile 2024 M3 Insecure Authentication/Authorization

[16] Standards Mapping - OWASP Top 10 2007 A5 Cross Site Request Forgery (CSRF)

[17] Standards Mapping - OWASP Top 10 2010 A5 Cross-Site Request Forgery (CSRF)

[18] Standards Mapping - OWASP Top 10 2013 A8 Cross-Site Request Forgery (CSRF)

[19] Standards Mapping - OWASP Top 10 2021 A01 Broken Access Control

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.5.5

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.9

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.9

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.9

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.9

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.9

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

[27] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[28] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control, Control Objective C.2.3 - Web Software Access Controls

[30] Standards Mapping - SANS Top 25 2009 Insecure Interaction - CWE ID 352

[31] Standards Mapping - SANS Top 25 2010 Insecure Interaction - CWE ID 352

[32] Standards Mapping - SANS Top 25 2011 Insecure Interaction - CWE ID 352

[33] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3585 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3585 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3585 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3585 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3585 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3585 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3585 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-001620 CAT II, APSC-DV-001630 CAT II, APSC-DV-002500 CAT II

[54] Standards Mapping - Web Application Security Consortium Version 2.00 Cross-Site Request Forgery (WASC-09)

[55] Standards Mapping - Web Application Security Consortium 24 + 2 Cross-Site Request Forgery

desc.semantic.apex.cookie_security_overly_permissive_samesite_attribute

Abstract

会话 Cookie 上的 SameSite 属性未设置为 Strict。

Explanation

SameSite 属性保护 Cookie 免受 Cross-Site Request Forgery (CSRF) 等攻击。会话 Cookie 代表用户访问站点，以便用户可以执行授权操作。但是，浏览器会自动将 Cookie 与请求一起发送，因此用户和网站会隐式信任浏览器进行授权。攻击者可以滥用此信任，通过在攻击者控制的第三方网站页面中的 link 和 iframe 等标签的 href 和 src 属性中嵌入链接，代表用户向站点发出请求。如果攻击者能够将一位毫无戒备的用户引诱到他们控制的第三方站点，则攻击者可以发出自动包含用于授权该用户的会话 Cookie 的请求，从而可以使攻击者获取有效授权，就像他们是用户一样。
在会话 Cookie 中将 SameSite 属性的值设置为 Strict。这将限制浏览器仅将 Cookie 附加到顶级导航时的请求或来自同一站点的请求。来自第三方站点的请求（通过 iframe、img 和 form 等各种标签中的链接）不含这些 Cookie，因此能阻止站点采取用户可能未授权的操作。

示例 1：以下代码在会话 Cookie 中将 SameSite 属性的值设置为 Lax。


    ...
    CookieOptions opt = new CookieOptions()
    {
        SameSite = SameSiteMode.Lax;
    };
    context.Response.Cookies.Append("name", "Foo", opt);
    ...