CWE-589: Call to Non-ubiquitous API
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product uses an API function that does not exist on all versions of the target platform. This could cause portability problems or inconsistencies that allow denial of service or other consequences.
扩展描述
Some functions that offer security features supported by the OS are not available on all versions of the OS in common use. Likewise, functions are often deprecated or made obsolete for security reasons and should not be used.
常见后果
影响范围: Other
技术影响: Quality Degradation
潜在缓解措施
阶段: Implementation
描述: Always test your code on any platform on which it is targeted to run on.
阶段: Testing
描述: Test your code on the newest and oldest platform on which it is targeted to run on.
阶段: Testing
描述: Develop a system to test for API functions that are not portable.
检测方法
方法: Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
有效性: High
引入模式
| 阶段 | 说明 |
|---|---|
| Architecture and Design | - |
| Implementation | - |
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| The CERT Oracle Secure Coding Standard for Java (2011) | MET02-J | Do not use deprecated or obsolete classes or methods | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | SER00-J | Maintain serialization compatibility during class evolution | - |
| Software Fault Patterns | SFP3 | Use of an improper API | - |