Reino: Security Features

Segurança de software não é o mesmo que software de segurança. Aqui, estamos interessados em tópicos como autenticação, controle de acesso, confidencialidade, criptografia e gestão de privilégios.

Android Bad Practices: Provider Permission Defined

Java/JSP

Abstract

O programa declara um provedor de conteúdo com a permission de acesso combinado de leitura e gravação.

Explanation

Um provedor de conteúdo declarado com a permission combinada de leitura e gravação estará acessível para as entidades que solicitam acesso de leitura ou gravação ao provedor. No entanto, em muitos casos, assim como no caso de arquivos em um sistema de arquivos, as entidades que precisam de acesso de leitura aos dados armazenados pelo provedor não devem ter permissão para modificar os dados. Configurar o atributo permission não permite distinguir entre usuários de dados e interações que afetam a integridade dos dados.

Exemplo 1: Veja a seguir um exemplo de um provedor de conteúdo declarado com o atributo permission de acesso combinado de leitura e gravação.

 <provider android:name=".ContentProvider" android:permission="content.permission.READ_AND_WRITE_CONTENT"/>

References

[1] Provider Element

[2] Path Permission Element

[3] Security tips - Use permissions

[4] Jesse Burns Developing Secure Mobile Applications for Android

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

[6] Standards Mapping - CIS Azure Kubernetes Service Benchmark 2

[7] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

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

[9] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 1

[10] Standards Mapping - CIS Google Kubernetes Engine Benchmark normal

[11] Standards Mapping - Common Weakness Enumeration CWE ID 265

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

[13] Standards Mapping - FIPS200 AC

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

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

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

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

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

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

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

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

[22] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.14.5 Configuration Architectural Requirements (L2 L3)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[38] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3480.2 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3480.2 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3480.2 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3480.2 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3480.2 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3480.2 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3480.2 CAT II

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.config.java.android_bad_practices_provider_permission_defined