계: Input Validation and Representation

입력 검증 및 표현 문제는 메타 문자, 대체 인코딩 및 숫자 표현 때문에 발생합니다. 보안 문제는 입력을 신뢰하기 때문에 발생합니다. 문제로는 "Buffer Overflows", "Cross-Site Scripting" 공격, "SQL Injection", 그 외 여러 가지가 있습니다.

Path Manipulation: Base Path Overwriting

C#/VB.NET/ASP.NET

Abstract

사용자 입력이 파일 시스템 작업에 사용되는 경로를 제어하는 것을 허용하면 그렇지 않을 때 보호할 수 있는 시스템 리소스에 공격자가 액세스하거나 수정할 수 있습니다.

Explanation

Path.Combine은 여러 파일 경로를 인수로 사용합니다. 일반적으로 파일에 대한 read() 또는 write() 호출 후에 여러 파일 경로를 연결하여 하나의 전체 경로를 가져옵니다. 첫 번째 또는 나머지 매개 변수가 절대 경로인지 여부에 따라 서로 다른 여러 시나리오가 설명서에 설명되어 있습니다. 두 번째 또는 나머지 매개 변수가 절대 경로인 경우 Path.Combine()은 해당 절대 경로를 반환합니다. 이전 매개 변수는 무시됩니다. 이 경우 다음 예제와 유사한 코드가 있는 응용 프로그램에서 심각한 영향이 발생합니다.

예제 1: 다음 코드는 사용자가 제어하는 경로 요소가 있는 파일을 안전하지 않게 로드합니다.


  // Called with user-controlled data
  public static bytes[] getFile(String filename) 
  {
    String imageDir = "\\FILESHARE\images\";
    filepath = Path.Combine(imageDir, filename);
    return File.ReadAllBytes(filepath);
  }

공격자는 절대 경로(예: C:\\inetpub\wwwroot\web.config)를 제공하여 응용 프로그램이 반환하는 파일을 제어할 수 있습니다.

References

[1] Editorial Team Path.Combine Security Issues in ASP.NET Applications

[2] Microsoft Path.Combine Method

[3] Standards Mapping - Common Weakness Enumeration CWE ID 22, CWE ID 73

[4] Standards Mapping - Common Weakness Enumeration Top 25 2019 [10] CWE ID 022

[5] Standards Mapping - Common Weakness Enumeration Top 25 2020 [12] CWE ID 022

[6] Standards Mapping - Common Weakness Enumeration Top 25 2021 [8] CWE ID 022

[7] Standards Mapping - Common Weakness Enumeration Top 25 2022 [8] CWE ID 022

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

[9] Standards Mapping - Common Weakness Enumeration Top 25 2024 [5] CWE ID 022, [12] CWE ID 020

[10] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000345, CCI-002754

[11] Standards Mapping - FIPS200 SI

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

[13] Standards Mapping - Motor Industry Software Reliability Association (MISRA) C Guidelines 2012 Rule 1.3

[14] Standards Mapping - Motor Industry Software Reliability Association (MISRA) C++ Guidelines 2008 Rule 0-3-1

[15] Standards Mapping - Motor Industry Software Reliability Association (MISRA) C++ Guidelines 2023 Rule 4.1.3

[16] Standards Mapping - NIST Special Publication 800-53 Revision 4 CM-5 Access Restrictions for Change (P1), SI-10 Information Input Validation (P1)

[17] Standards Mapping - NIST Special Publication 800-53 Revision 5 CM-5 Access Restrictions for Change, SI-10 Information Input Validation

[18] Standards Mapping - OWASP Application Security Verification Standard 4.0 12.3.1 File Execution Requirements (L1 L2 L3), 12.3.2 File Execution Requirements (L1 L2 L3)

[19] Standards Mapping - OWASP Mobile 2014 M8 Security Decisions Via Untrusted Inputs

[20] Standards Mapping - OWASP Mobile 2024 M4 Insufficient Input/Output Validation

[21] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-CODE-4

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

[23] Standards Mapping - OWASP Top 10 2007 A4 Insecure Direct Object Reference

[24] Standards Mapping - OWASP Top 10 2010 A4 Insecure Direct Object References

[25] Standards Mapping - OWASP Top 10 2013 A4 Insecure Direct Object References

[26] Standards Mapping - OWASP Top 10 2017 A5 Broken Access Control

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

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

[29] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.1, Requirement 6.5.4

[30] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.8

[31] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.8

[32] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.8

[33] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.8

[34] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.8

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

[36] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4

[37] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection, Control Objective 5.4 - Authentication and Access Control

[38] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection, Control Objective 5.4 - Authentication and Access Control, Control Objective B.3.1 - Terminal Software Attack Mitigation, Control Objective B.3.1.1 - Terminal Software Attack Mitigation

[39] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection, Control Objective 5.4 - Authentication and Access Control, Control Objective B.3.1 - Terminal Software Attack Mitigation, Control Objective B.3.1.1 - Terminal Software Attack Mitigation, Control Objective C.2.3 - Web Software Access Controls, Control Objective C.3.2 - Web Software Attack Mitigation

[40] Standards Mapping - SANS Top 25 2009 Risky Resource Management - CWE ID 426

[41] Standards Mapping - SANS Top 25 2010 Risky Resource Management - CWE ID 022

[42] Standards Mapping - SANS Top 25 2011 Risky Resource Management - CWE ID 022

[43] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I, APP3600 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I, APP3600 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I, APP3600 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I, APP3600 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I, APP3600 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I, APP3600 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I, APP3600 CAT II

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

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

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

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

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

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

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

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

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

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

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

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

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

[63] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002530 CAT II, APSC-DV-002560 CAT I, APSC-DV-002960 CAT II

[64] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002530 CAT II, APSC-DV-002560 CAT I, APSC-DV-002960 CAT II

[65] Standards Mapping - Web Application Security Consortium Version 2.00 Path Traversal (WASC-33)

[66] Standards Mapping - Web Application Security Consortium 24 + 2 Path Traversal

desc.dataflow.dotnet.path_manipulation_base_path_overwriting