界: Security Features

軟體安全性並非安全性軟體。我們關注驗證、Access Control、保密性、加密以及權限管理之類的主題。

Privacy Violation: iOS Property List

Objective-C

Abstract

已儲存但未加保護的私人資訊，例如純文字檔案中的密碼，會危及系統安全。

Explanation

當私人使用者資訊儲存於未加保護的位置時，就會發生Privacy Violation。
範例 1：以下 XML 包含 plist 檔案中使用者的私人資訊。在其他儲存的值中，MyCreditCard 金鑰會儲存與帳戶相關且由使用者提供的純文字信用卡卡號。



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>password</key>
  <string>BASICSECRET</string>
  <key>credentials</key>
  <dict>
          <key>pin</key>
          <string>2345</string>
          <key>MyCreditCard</key>
          <string>1111 11 2321 1112</string>
          <key>MysSn</key>
          <string>1111-22-3333</string>
          <key>ssn</key>
          <string>2345-22-3345</string>
          <key>userid</key>
          <string>12345</string>
  </dict>
</dict>
</plist>

Example 1 中的程式碼在裝置上未加保護的 plist 檔案中儲存來自行動裝置的私人使用者資訊。雖然許多開發者信任 plist 檔案是任何及所有資料的安全儲存位置，但不應對其絕對信賴，特別是關係到隱私問題時，因為 plist 檔案可由擁有裝置的任何人讀取。

隱私資料可以透過多種方式進入到程式中：

- 直接來自於使用者的密碼或個人資訊。

- 應用程式從資料庫或其他資料存放區存取。

- 間接地來自於合作者或者其他第三方。

- 從行動資料儲存區擷取的項目包含：通訊錄、快照、地理位置、組態設定檔案 (包括 plist)、封存 SMS 訊息等。

有時候，未標示為隱私的資料仍有可能在不同的內容中有隱私含意。例如，學生的學號通常不會視為隱私資訊，因為學號中沒有明確和公開的資訊以對應於個別學生的個人資訊。不過，如果學校以學生的身份證字號來產生學號，則此學號應視為隱私資訊。

安全性和隱私似乎時常互相矛盾。從安全的觀點來看，您應該要記錄所有重要的操作，以便於日後辨別所有的異常活動。不過，當其中包含了私人資料時，此種作法將會造成其他風險。

雖然有多種情況會發生隱私資料處理不安全，但常見的風險多是來自盲目的信賴。程式設計師通常會信賴程式執行的作業環境，所以相信將隱私資訊儲存在檔案系統、登錄、plist 內或是其他局部控制的資源中是可以接受的。不過，即使存取特定資源是受限制的，亦不保證應予信賴可以存取該資料的個體。例如，在 2004 年時一位無恥的 AOL 員工將大約 9 千 2 百萬名客戶的私人電子郵件地址賣給了一個透過發送垃圾郵件進行行銷的賭博網站 [1]。

為了應對此類受矚目的資料攻擊事件，隱私資料的收集和管理正日益規範。要求各組織根據其位置、所管理的業務類型，以及其所處理的隱私資訊性質，遵守以下一個或多個聯邦和州的規定：

- Safe Harbor Privacy Framework [3]

- Gramm-Leach Bliley Act (GLBA) [4]

- Health Insurance Portability and Accountability Act (HIPAA) [5]

- California SB-1386 [6]

雖已制訂規範，但隱私違反的情況仍持續發生。

References

[1] J. Oates AOL man pleads guilty to selling 92m email addies The Register

[2] Privacy Initiatives U.S. Federal Trade Commission

[3] Safe Harbor Privacy Framework U.S. Department of Commerce

[4] Financial Privacy: The Gramm-Leach Bliley Act (GLBA) Federal Trade Commission

[5] Health Insurance Portability and Accountability Act (HIPAA) U.S. Department of Human Services

[6] California SB-1386 Government of the State of California

[7] M. Howard, D. LeBlanc Writing Secure Code, Second Edition Microsoft Press

[8] Standards Mapping - Common Weakness Enumeration CWE ID 359

[9] Standards Mapping - Common Weakness Enumeration Top 25 2019 [4] CWE ID 200

[10] Standards Mapping - Common Weakness Enumeration Top 25 2020 [7] CWE ID 200

[11] Standards Mapping - Common Weakness Enumeration Top 25 2021 [20] CWE ID 200

[12] Standards Mapping - Common Weakness Enumeration Top 25 2024 [17] CWE ID 200

[13] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000196, CCI-004062

[14] Standards Mapping - General Data Protection Regulation (GDPR) Privacy Violation

[15] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-4 Information Flow Enforcement (P1), IA-5 Authenticator Management (P1)

[16] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-4 Information Flow Enforcement, IA-5 Authenticator Management

[17] Standards Mapping - OWASP Application Security Verification Standard 4.0 8.2.2 Client-side Data Protection (L1 L2 L3), 8.3.4 Sensitive Private Data (L1 L2 L3), 10.2.1 Malicious Code Search (L2 L3)

[18] Standards Mapping - OWASP Mobile 2014 M2 Insecure Data Storage

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

[20] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-STORAGE-1

[21] Standards Mapping - OWASP Top 10 2007 A6 Information Leakage and Improper Error Handling

[22] Standards Mapping - OWASP Top 10 2013 A6 Sensitive Data Exposure

[23] Standards Mapping - OWASP Top 10 2017 A3 Sensitive Data Exposure

[24] Standards Mapping - OWASP Top 10 2021 A02 Cryptographic Failures

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 8.4

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.6, Requirement 8.4

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.4

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 8.2.1

[29] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 8.2.1

[30] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 8.2.1

[31] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 8.2.1

[32] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 3.3.1, Requirement 3.5.1, Requirement 4.2.2, Requirement 8.3.1

[33] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 3.3.1, Requirement 3.3.2, Requirement 3.3.3, Requirement 3.5.1, Requirement 4.2.2, Requirement 8.3.1

[34] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[35] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[36] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection, Control Objective 7 - Use of Cryptography

[37] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3210.1 CAT II, APP3310 CAT I, APP3340 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3210.1 CAT II, APP3340 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3210.1 CAT II, APP3340 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3210.1 CAT II, APP3340 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3210.1 CAT II, APP3340 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3210.1 CAT II, APP3340 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3210.1 CAT II, APP3340 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-001740 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-001740 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-001740 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-001740 CAT I

[48] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-001740 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-001740 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-001740 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-001740 CAT I

[52] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-001740 CAT I

[53] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-001740 CAT I

[54] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-001740 CAT I

[55] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-001740 CAT I

[56] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-001740 CAT I

[57] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-001740 CAT I

[58] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-001740 CAT I

[59] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)

[60] Standards Mapping - Web Application Security Consortium 24 + 2 Information Leakage

desc.config.objc.privacy_violation_ios_property_list