Insecure SSL: Android Customized Implementation

ABSTRACT

應用程序可實施一個自定義 SSL 接口。

EXPLANATION

該 SSL 標準提供關于如何在客戶端側進行 SSL 驗證檢查的指導。但是這并非標準的一部分。因此，驗證邏輯的實施留給應用程序開發人員來處理。

研究表明，SSL 標準規范的復雜性和開放性存在多項缺陷，使得獲得無缺陷的自定義 SSL 實施非常困難。采用自定義 SSL 實施的很大比例的 Android 應用程序無法高效地提供安全通信通道，使應用程序易受中間人攻擊。

REFERENCES

[1] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A3 Broken Authentication and Session Management

[2] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A9 Insecure Communications

[3] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A9 Insufficient Transport Layer Protection

[4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3250.1 CAT I, APP3250.2 CAT I, APP3250.3 CAT II, APP3250.4 CAT II

[5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3250.1 CAT I, APP3250.2 CAT I, APP3250.3 CAT II, APP3250.4 CAT II

[6] Standards Mapping - FIPS200 - (FISMA) CM, SC

[7] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 297, CWE ID 296, CWE ID 298, CWE ID 299

[8] Designing for Security Android

[9] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Information Leakage

[10] OWASP Top 10 Mobile Risks OWASP

[11] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 4.1, Requirement 6.3.1.4, Requirement 6.5.9

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

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

[14] S. Fahl, M. Harbach, T. Muders, M. Smith, L. Baumgartner, B. Friesleben Why Eve and Mallory Love Android:An Analysis of Android SSL (In)Security

97av