계: Security Features

소프트웨어 보안은 보안 소프트웨어가 아닙니다. 여기서는 인증, 액세스 제어, 기밀성, 암호화, 권한 관리 등의 항목에 대해 설명합니다.

Privacy Violation: Sensitive Data Accessible From iTunes

Objective-C
Swift

Abstract

식별된 메서드는 먼저 민감한 데이터를 적절하게 마스킹하지 않고 공개 Documents 디렉터리에 씁니다.

Explanation

Documents 디렉터리의 용도는 응용 프로그램이 오프라인 모드로 실행할 수 있도록 로컬 정보 또는 사용자 생성 콘텐트와 같은 일시적이지 않은 응용 프로그램 데이터를 저장하기 위한 것입니다. 응용 프로그램의 Info.plist 파일에서 UIFileSharingEnabled가 설정된 경우 iTunes를 통해 이러한 파일에 액세스할 수 있습니다. 민감한 데이터를 Documents 디렉터리에 쓸 경우 암호화되지 않은 백업에서 또는 iTunes 인터페이스를 통해 데이터가 노출될 수 있습니다.

예제 1: 다음 코드 조각에서는 사용자 암호를 Documents 디렉터리 내에 일반 텍스트로 씁니다.


    ...
    NSString *docsDirectory = [NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) objectAtIndex:0];
    NSString *passwd_path = [docsDirectory stringByAppendingPathComponent:@"passwords.txt"];

    NSString *password = [user password];
    [password writeToFile:passwd_path atomically:YES encoding:NSUTF8StringEncoding error:nil];
    ...

References

[1] David Thiel iOS Application Security: The Definitive Guide for Hackers and Developers No Starch Press

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

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

[4] Standards Mapping - Common Weakness Enumeration Top 25 2020 [7] CWE ID 200

[5] Standards Mapping - Common Weakness Enumeration Top 25 2021 [20] CWE ID 200

[6] Standards Mapping - Common Weakness Enumeration Top 25 2024 [17] CWE ID 200

[7] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002475

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

[9] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-4 Information Flow Enforcement (P1), SC-28 Protection of Information at Rest (P1)

[10] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-4 Information Flow Enforcement, SC-28 Protection of Information at Rest

[11] Standards Mapping - OWASP Application Security Verification Standard 4.0 8.2.2 Client-side Data Protection (L1 L2 L3), 8.3.4 Sensitive Private Data (L1 L2 L3), 10.2.1 Malicious Code Search (L2 L3)

[12] Standards Mapping - OWASP Mobile 2014 M2 Insecure Data Storage

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

[14] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-STORAGE-1

[15] Standards Mapping - OWASP Top 10 2004 A8 Insecure Storage

[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.2, Requirement 3.4, Requirement 4.2, Requirement 8.4

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.6, Requirement 8.4

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.4

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 3.3.1, Requirement 3.5.1, Requirement 4.2.2, Requirement 6.2.4, Requirement 8.3.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 3.3.1, Requirement 3.3.2, Requirement 3.3.3, Requirement 3.5.1, Requirement 4.2.2, Requirement 6.2.4, Requirement 8.3.1

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 3.3 - Sensitive Data Retention, Control Objective 3.6 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 3.3 - Sensitive Data Retention, Control Objective 3.6 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 3.3 - Sensitive Data Retention, Control Objective 3.6 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[32] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3210.1 CAT II, APP3310 CAT I, APP3340 CAT I

[33] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3210.1 CAT II, APP3340 CAT I

[34] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3210.1 CAT II, APP3340 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3210.1 CAT II, APP3340 CAT I

[36] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3210.1 CAT II, APP3340 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3210.1 CAT II, APP3340 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3210.1 CAT II, APP3340 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002340 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002340 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002340 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002340 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002340 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002340 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002340 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002340 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002340 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002340 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002340 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002340 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002340 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002340 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002340 CAT II

[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.dataflow.objc.privacy_violation_sensitive_data_accessible_from_itunes

Abstract

식별된 메서드는 먼저 민감한 데이터를 적절하게 마스킹하지 않고 공개 Documents 디렉터리에 씁니다.

Explanation


    let documents = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true)[0] as String
    let passwd_path = NSURL(fileURLWithPath: documents).URLByAppendingPathComponent("secret.txt")
    let password = getUserPassword()
    try password.writeToURL(passwd_path, atomically:true, encoding: NSUTF8StringEncoding)