Reino: Encapsulation

La encapsulación consiste en crear límites fuertes. En un explorador web esto puede suponer la seguridad de que tu codificación móvil no se vea comprometido por otro código móvil. En el servidor puede significar la diferenciación entre los datos validados y los que no lo están, entre los datos de un usuario y los de otro, o entre los diferentes usuarios, los datos que pueden ver y los que no.

Insecure Storage: Persistent Named Pasteboard

Objective-C
Swift

Abstract

Un portapapeles con nombre configurado como persistente puede dar lugar a la exposición de información confidencial.

Explanation

Los portapapeles con nombre permiten a los desarrolladores compartir datos con otras partes de una aplicación o con otras aplicaciones que tienen el mismo ID de equipo. Configurar un portapapeles con nombre como persistente es una opción obsoleta que puede conducir a la exposición de datos confidenciales. Cuando un portapapeles se marca como persistente, los datos almacenados en el portapapeles se pueden guardar sin cifrar en el almacenamiento local y persisten al reiniciar las aplicaciones y el dispositivo.
Ejemplo 1: En el siguiente ejemplo, se crea un portapapeles con nombre y se configura como persistente invocando setPersistent:YES .


  ...
  UIPasteboard *pasteboard = [UIPasteboard pasteboardWithName:@"myPasteboard" create:YES];
  [pasteboard setPersistent:YES];
  ...

References

[1] setPersistent: | Apple Developer Documentation Apple

[2] iOS Platform APIs - OWASP Mobile Application Security OWASP

[3] Standards Mapping - Common Weakness Enumeration CWE ID 312, CWE ID 359

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

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

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

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

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

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

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

[11] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.6.3 Look-up Secret Verifier Requirements (L2 L3), 6.1.1 Data Classification (L2 L3), 6.1.2 Data Classification (L2 L3), 6.1.3 Data Classification (L2 L3), 6.2.1 Algorithms (L1 L2 L3), 8.1.6 General Data Protection (L3), 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 M9 Insecure Data Storage

[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 A04 Insecure Design

[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 Software Security Framework 1.0 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective B.2.5 - Terminal Software Design

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective B.2.5 - Terminal Software Design

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.dataflow.objc.insecure_storage_persistent_named_pasteboard

Abstract

Un portapapeles con nombre configurado como persistente puede dar lugar a la exposición de información confidencial.

Explanation


  ...
  let pasteboard = UIPasteboard(name: UIPasteboard.Name(rawValue: "myPasteboard"), create: true)!
  pasteboard.setPersistent(true)
  ...

References

[1] setPersistent(_:) | Apple Developer Documentation Apple