<dd id="sga4y"><optgroup id="sga4y"></optgroup></dd>
<nav id="sga4y"><code id="sga4y"></code></nav>
  • <optgroup id="sga4y"></optgroup>

    Android Bad Practices: Provider permission Defined

    ABSTRACT

    程序聲明內容提供者具有讀取和寫入 permission

    EXPLANATION

    聲明為具有讀取和寫入 permission 的內容提供者可供請求對此提供者進行讀取或寫入訪問的實體訪問。但在許多情況下,與讀取 file system 中的文件一樣,這些需要讀取由內容提供者存儲的數據的實體不能修改數據。設置 permission 屬性不允許區分數據用戶與影響數據完整性的交互。

    例 1:下面是聲明為具有讀取和寫入 permission 的內容提供者示例。

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

    REFERENCES

    [1] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A2 Broken Access Control

    [2] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A6 Security Misconfiguration

    [3] Standards Mapping - FIPS200 - (FISMA) AC

    [4] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 265

    [5] Jesse Burns Developing Secure Mobile Applications for Android

    [6] Standards Mapping - SANS Top 25 2009 - (SANS 2009) Improper Access Control - CWE ID 285

    [7] Path Permission Element

    [8] Provider Element

    [9] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.10

    [10] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 7.1.1

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

    [12] William Enck and Patrick McDaniel Understanding Android's Security Framework

    [13] Using Permissions


    Copyright 2013 Fortify Software - All rights reserved.
    (Generated from version 2013.1.1.0008 of the Fortify Secure Coding Rulepacks)
    desc.config.java.android_bad_practices_provider_permission_defined

    97av