界: Security Features

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

Privacy Violation: Shoulder Surfing

Abstract

收集敏感信息的一些 API 可能会在用户在输入提示符处输入敏感信息时将其返回给用户，从而对其进行错误处理。

Explanation

某些收集敏感信息的 API 可能会错误地处理该信息，将其返回给用户。

示例 1： 以下代码演示 ASP.NET 中的模型，该模型具有密码属性，但未将 DataType 指定为密码，这表示在显示时，系统会默认显示该属性：


public class User
{
  [Required]
  public int ID { get; set; }
  
  public string Title { get; set; }
  
  [DataType(DataType.Date)]
  [DisplayFormat(DataFormatString = "{0:yyyy-MM-dd}", ApplyFormatInEditMode = true)]
  public DateTime DateOfEmployment { get; set; }
  
  [DataType(DataType.Currency)]
  public decimal Salary { get; set; }
  
  [Required]
  public string Username { get; set; }
  
  [Required]
  public string Password { get; set; }
  
  ...
}

由于Example 1 中的 Password 属性未指定 [DataType(DataType.Password)] 属性，因此默认情况下在 UI 中显示不会隐藏它。

References

[1] Standards Mapping - Common Weakness Enumeration CWE ID 549

[2] Standards Mapping - Common Weakness Enumeration Top 25 2019 [13] CWE ID 287

[3] Standards Mapping - Common Weakness Enumeration Top 25 2020 [14] CWE ID 287, [18] CWE ID 522

[4] Standards Mapping - Common Weakness Enumeration Top 25 2021 [14] CWE ID 287, [21] CWE ID 522

[5] Standards Mapping - Common Weakness Enumeration Top 25 2022 [14] CWE ID 287

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

[7] Standards Mapping - Common Weakness Enumeration Top 25 2024 [14] CWE ID 287

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

[9] Standards Mapping - General Data Protection Regulation (GDPR) Privacy Violation

[10] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-4 Information Flow Enforcement (P1), IA-6 Authenticator Feedback (P2)

[11] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-4 Information Flow Enforcement, IA-6 Authentication Feedback

[12] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.7.1 Out of Band Verifier Requirements (L1 L2 L3), 2.7.2 Out of Band Verifier Requirements (L1 L2 L3), 2.7.3 Out of Band Verifier Requirements (L1 L2 L3), 2.8.4 Single or Multi Factor One Time Verifier Requirements (L2 L3), 2.8.5 Single or Multi Factor One Time Verifier Requirements (L2 L3), 2.10.2 Service Authentication Requirements (L2 L3), 2.10.3 Service Authentication Requirements (L2 L3), 3.7.1 Defenses Against Session Management Exploits (L1 L2 L3), 9.2.3 Server Communications Security Requirements (L2 L3)

[13] Standards Mapping - OWASP Mobile 2014 M4 Unintended Data Leakage

[14] Standards Mapping - OWASP Mobile 2024 M6 Inadequate Privacy Controls

[15] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-PLATFORM-3, MASVS-STORAGE-2

[16] Standards Mapping - OWASP Top 10 2007 A6 Information Leakage and Improper Error Handling

[17] Standards Mapping - OWASP Top 10 2013 A6 Sensitive Data Exposure

[18] Standards Mapping - OWASP Top 10 2017 A3 Sensitive Data Exposure

[19] Standards Mapping - OWASP Top 10 2021 A02 Cryptographic Failures

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 3.3

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 3.3

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 3.3

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 3.3

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 3.3

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 3.3

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 3.3

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 3.4.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 3.4.1

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective A.2.2 - Cardholder Data Protection

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective A.2.2 - Cardholder Data Protection

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective A.2.2 - Cardholder Data Protection

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[54] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)

[55] Standards Mapping - Web Application Security Consortium 24 + 2 Information Leakage

desc.structural.dotnet.privacy_violation_shoulder_surfing

Abstract

收集敏感信息的一些 API 可能会在用户在输入提示符处输入敏感信息时将其返回给用户，从而对其进行错误处理。

Explanation

收集敏感信息的一些 API 可能会将敏感信息返回给用户，从而对其进行错误处理。

示例 1：以下代码演示的 TextField 小组件在用户在输入提示符处输入密码时不会对用户密码进行模糊处理：


class SelectionContainerDisabledExampleApp extends StatelessWidget {
  const SelectionContainerDisabledExampleApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Column(
            children: <Widget>[
              TextField(
                decoration: InputDecoration(
                  hintText: "Please enter your password",
                ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

由于Example 1 中的 TextField 小组件是在 obscureText 属性设置为 true 的情况下进行实例化的，因此，当用户在“请输入您的密码:”提示符处输入密码时，该密码不会进行模糊显示。