界: API Abuse

API 是调用方和被调用方之间的约定。最常见的 API 滥用是由于调用方未能遵守此约定的终止导致的。例如，如果某个程序在调用 chroot() 后未能调用 chdir()，则违反了用于指定如何安全地更改活动根目录的约定。库滥用的另一个典型示例是期望被调用方向调用方返回可信的 DNS 信息。在这种情况下，调用方通过对被调用方行为做出某种假设（返回值可用于身份验证目的）滥用其 API。另一方也可能违反调用方-被调用方约定。例如，如果编码器子类化 SecureRandom 并返回一个非随机值，则将违反此约定。

ASP.NET MVC Bad Practices: Model With Optional and Required Properties

C#/VB.NET/ASP.NET

Abstract

模型类拥有需要的属性和不需要的属性，因此可能容易受重复提交攻击的影响。

Explanation

如果攻击者传送的请求中包含的数据超出预期，使用拥有需要属性（标记为 [Required] 属性）和可选的属性（标记为 [Required] 属性）的模型类可能会导致问题。

ASP.NET MVC 框架将尝试捆绑请求参数到模型属性。

混合的要求而没有明确指出哪个参数为模型绑定可能表明有针对内部使用的模型属性，但是可以由攻击者控制。

以下代码定义了一种可能的模型类，其中有包含 [Required] 的属性和不包含 [Required] 的属性：


public class MyModel
{
    [Required]
    public String UserName { get; set; }

    [Required]
    public String Password { get; set; }

    public Boolean IsAdmin { get; set; }
}

如果有能更改应用程序行为的任何可选参数，那么攻击者可以通过发送一个可选参数请求来真正更改该行为。

References

[1] Input Validation vs. Model Validation in ASP.NET MVC

[2] BindAttribute Class

[3] RequiredAttribute Class

[4] Standards Mapping - CIS Azure Kubernetes Service Benchmark 3

[5] Standards Mapping - CIS Microsoft Azure Foundations Benchmark complete

[6] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 4

[7] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 3

[8] Standards Mapping - CIS Google Kubernetes Engine Benchmark integrity

[9] Standards Mapping - CIS Kubernetes Benchmark partial

[10] Standards Mapping - Common Weakness Enumeration CWE ID 345

[11] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002422

[12] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-8 Transmission Confidentiality and Integrity (P1)

[13] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-8 Transmission Confidentiality and Integrity

[14] Standards Mapping - OWASP Top 10 2004 A1 Unvalidated Input

[15] Standards Mapping - OWASP Top 10 2007 A2 Injection Flaws

[16] Standards Mapping - OWASP Top 10 2010 A1 Injection

[17] Standards Mapping - OWASP Top 10 2013 A1 Injection

[18] Standards Mapping - OWASP Top 10 2017 A1 Injection

[19] Standards Mapping - OWASP Top 10 2021 A03 Injection

[20] Standards Mapping - OWASP API 2023 API3 Broken Object Property Level Authorization

[21] Standards Mapping - OWASP Application Security Verification Standard 4.0 3.5.3 Token-based Session Management (L2 L3), 13.2.6 RESTful Web Service Verification Requirements (L2 L3)

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

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.6

[24] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002470 CAT II

[25] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002470 CAT II

[26] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002470 CAT II

[27] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002470 CAT II

[28] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002470 CAT II

[29] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002470 CAT II

[30] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002470 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002470 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002470 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002470 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002470 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002470 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002470 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002470 CAT II

[38] Standards Mapping - Web Application Security Consortium Version 2.00 Improper Input Handling (WASC-20)

desc.structural.dotnet.aspnet_mvc_bad_practices_mixed_required_model