依靠 CDN 向用戶直接提供必須的代碼會導致執行惡意代碼。
使用 CDN 來提供應用程序所依賴的 JavaScript 與通過應用程序自身的服務器提供 JavaScript 相比有許多優勢。其中包括提高了性能,以及減少了應用程序所有者的代碼維護工作。但是,應用程序假定 CDN 會將安全內容發送至瀏覽器。如果攻擊者攻擊 CDN,CDN 會將惡意代碼發送至用戶瀏覽器。因此,用戶的瀏覽器會執行應用程序無法控制或檢測出有惡意的代碼。
例 1:下列 ASPX 代碼通過引用 Microsoft CDN 包含 Microsoft 的 jQuery 代碼:
...
<script src="http://ajax.microsoft.com/ajax/jquery/jquery-1.4.2.min.js" type="text/javascript"></script>
...
...
<asp:ScriptManager
ID="ScriptManager1"
EnableCdn="true"
Runat="Server" />
...
[1] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A1 Injection
[2] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A1 Unvalidated Input
[3] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A3 Malicious File Execution
[4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3510 CAT I, APP3600 CAT II
[5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3510 CAT I, APP3600 CAT II
[6] Content Deliver Network and its Regulation The Journal of China Universities of Posts and Telecommunications
[7] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 94, CWE ID 98
[8] Managed Content Security Delivery radware
[9] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 6.3.1.1, Requirement 6.5.3
[10] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.1
[11] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 6.5.8
[12] Standards Mapping - SANS Top 25 2009 - (SANS 2009) Risky Resource Management - CWE ID 094
[13] Standards Mapping - SANS Top 25 2010 - (SANS 2010) Risky Resource Management - CWE ID 098
[14] Standards Mapping - FIPS200 - (FISMA) SI