Reino: Security Features

La seguridad de un software no es un software de seguridad. Nos preocupamos de cuestiones como la autenticación, el control de acceso, la confidencialidad, la criptografía y la gestión de privilegios.

Android Bad Practices: Missing Component Permission

Java/JSP

Abstract

El programa no asigna explícitamente un permiso de acceso a este componente público.

Explanation

Cualquier aplicación puede acceder a componentes públicos a los que no se les haya asignado explícitamente un permiso de acceso en su definición de manifiesto.

El valor predeterminado del atributo exported de los componentes de actividad, receptor y servicio de una aplicación Android depende de la presencia o ausencia de un intent-filter. La presencia de un intent-filter implica que el componente ha sido diseñado para uso externo, por lo que define el atributo exported como verdadero. Este componente es ahora accesible a cualquier otra aplicación de la plataforma Android.

Ejemplo 1: A continuación se muestra un ejemplo de actividad Android con un intent-filter y sin permiso de acceso explícito definido.

 <activity android:name=".AndroidActivity"/>

   <intent-filter android:label="activityName"/>

    <action android:name=".someFunAction"/>

   </intent-filter>

...

 </activity>

Aplicaciones malintencionadas podrían aprovechar esta actividad.

References

[1] Jesse Burns Developing Secure Mobile Applications for Android

[2] The AndroidManifest.xml File

[3] William Enck, Machigar Ongtang, and Patrick McDaniel Understanding Android Security

[4] Security guidelines - Permissions

[5] Standards Mapping - Common Weakness Enumeration CWE ID 265, CWE ID 925, CWE ID 926

[6] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000213, CCI-002165

[7] Standards Mapping - FIPS200 AC

[8] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[9] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-3 Access Enforcement (P1)

[10] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-3 Access Enforcement

[11] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.14.5 Configuration Architectural Requirements (L2 L3), 4.1.3 General Access Control Design (L1 L2 L3), 4.1.5 General Access Control Design (L1 L2 L3), 4.2.1 Operation Level Access Control (L1 L2 L3)

[12] Standards Mapping - OWASP Mobile 2014 M5 Poor Authorization and Authentication

[13] Standards Mapping - OWASP Mobile 2024 M8 Security Misconfiguration

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

[15] Standards Mapping - OWASP Top 10 2004 A2 Broken Access Control

[16] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration

[17] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration

[18] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration

[19] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration

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

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

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 7.1.2

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 7.1.2

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 7.1.2

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 7.1.2

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 7.2.2

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 7.2.2

[28] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control

[31] Standards Mapping - SANS Top 25 2009 Porous Defenses - CWE ID 285

[32] Standards Mapping - SANS Top 25 2010 Porous Defenses - CWE ID 285

[33] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3480.1 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3480.1 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3480.1 CAT I

[36] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3480.1 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3480.1 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3480.1 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3480.1 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[54] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-000460 CAT I, APSC-DV-000470 CAT II

[55] Standards Mapping - Web Application Security Consortium Version 2.00 Insufficient Authorization (WASC-02)

desc.config.java.android_bad_practices_missing_component_permission