Often Misused: Android Permission Check

ABSTRACT

應慎重使用 checkCallingOrSelfPermission() 或 checkCallingOrSelfUriPermission() 函數，因為它允許沒有所需或任何權限的調用程序利用您應用程序的權限來繞過權限檢查。

EXPLANATION

函數 checkCallingOrSelfPermission() 或 checkCallingOrSelfUriPermission() 用來判定調用程序是否具備訪問某個服務或給定 URI 所需的權限。但是，由于此類函數可允許缺乏相應權限的惡意應用程序利用您應用程序的權限進行訪問，因而應慎重使用。

這意味著沒有相應權限的惡意應用程序可以利用您應用程序的權限來避開它的權限檢查，以獲得對本應拒絕其訪問的資源的訪問。這可能導致所稱的混淆代理人攻擊。

REFERENCES

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

[2] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A4 Insecure Direct Object Reference

[3] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A4 Insecure Direct Object References

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

[5] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3510 CAT I

[6] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3510 CAT I

[7] Context:Android Developers Android

[8] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 275

[9] Designing for Security Android

[10] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Insufficient Authorization

[11] Standards Mapping - SANS Top 25 2011 - (SANS Top 25 2011) Porous Defenses - CWE ID 863

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

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

[14] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 6.5.8

97av