界: API Abuse

API 就像是呼叫者與被呼叫者之間簽訂的規定。最常見的 API 濫用形式是由呼叫者這一當事方未能遵守此規定所造成的。例如，如果程式在呼叫 chroot() 後無法呼叫 chdir()，即違反規範如何以安全方式變更使用中根目錄的規定。程式庫濫用的另一個好例子是期待被呼叫者向呼叫者傳回值得信賴的 DNS 資訊。在這種情況下，呼叫者是透過對其行為做出某些假設 (傳回值可用於驗證目的) 來濫用被呼叫者 API。另一方也可能違反呼叫者與被呼叫者間的規定。例如，如果編碼器衍生出子類別 SecureRandom 並傳回一個非隨機值，則違反了規定。

Code Correctness: Call to System.gc()

Java/JSP

Abstract

明確的垃圾回收機制的要求，可以預示效能可能出現的問題。

Explanation

幾乎每個 Java 開發人員都會遇到這樣的情況，有時候一個看上去十分蹊蹺、不能理解且無法除錯的問題，似乎只能把原因歸咎於垃圾回收機制上。特別是當問題與 Time and State 相關的時候，可以根據經驗事實的推斷來支持此理論：有時候在程式中插入 System.gc() 呼叫，問題似乎就解決了。

在大部分我們所遇過的情況下，呼叫 System.gc() 是錯誤的行為。事實上，過於頻繁的呼叫 System.gc() 會帶來效能問題。

References

[1] D. H. Hovermeyer FindBugs User Manual

[2] Standards Mapping - Common Weakness Enumeration CWE ID 730

[3] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-001094

[4] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-5 Denial of Service Protection (P1)

[5] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-5 Denial of Service Protection

[6] Standards Mapping - OWASP Top 10 2004 A9 Application Denial of Service

[7] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.9

[8] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP6080 CAT II

[9] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP6080 CAT II

[10] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP6080 CAT II

[11] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP6080 CAT II

[12] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP6080 CAT II

[13] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP6080 CAT II

[14] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP6080 CAT II

[15] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002400 CAT II

[16] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002400 CAT II

[17] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002400 CAT II

[18] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002400 CAT II

[19] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002400 CAT II

[20] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002400 CAT II

[21] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002400 CAT II

[22] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002400 CAT II

[23] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002400 CAT II

[24] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002400 CAT II

[25] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002400 CAT II

[26] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002400 CAT II

[27] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002400 CAT II

[28] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002400 CAT II

[29] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002400 CAT II

[30] Standards Mapping - Web Application Security Consortium Version 2.00 Denial of Service (WASC-10)

[31] Standards Mapping - Web Application Security Consortium 24 + 2 Denial of Service

desc.structural.java.code_correctness_call_to_system_gc