引入方式
Implementation
適用平台
程式語言
類別: Not Language-Specific (Undetermined)
常見後果
| 範圍 |
影響 |
可能性 |
Integrity Other | Unexpected State, Alter Execution Logic
注意:This weakness can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe or correct, even when it is not. This weakness could place the system in a state that could lead unexpected logic to be executed or other unintended behaviors. | |
觀察到的案例
| 參考資料 |
描述 |
| DNS server returns wrong response code for non-existent AAAA record, which effectively says that the domain is inaccessible. |
| Hardware-specific implementation of system call causes incorrect results from geteuid. |
| Chain: System call returns wrong value (CWE-393), leading to a resultant NULL dereference (CWE-476). |
| Chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -> CWE-561 (Dead Code) -> CWE-295 (Improper Certificate Validation) -> CWE-393 (Return of Wrong Status Code) -> CWE-300 (Channel Accessible by Non-Endpoint). The code's whitespace indentation did not reflect the actual control flow (CWE-1114) and did not explicitly delimit the block (CWE-483), which could have made it more difficult for human code auditors to detect the vulnerability. |
偵測方法
Fuzzing
Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
有效性 : High
漏洞對應備注
理由說明 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
備注
This can be primary or resultant, but it is probably most often primary to other issues.
提交
| 名稱 |
機構 |
日期 |
發布日期 |
Version |
| PLOVER |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
修改記錄
| 名稱 |
機構 |
日期 |
備註 |
| Sean Eidemiller |
Cigital |
2008-07-01 +00:00 |
added/updated demonstrative examples |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Maintenance_Notes, Relationships, Other_Notes, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2008-10-14 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2009-03-10 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2010-02-16 +00:00 |
updated Other_Notes, Relationship_Notes |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2011-06-27 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Common_Consequences, Relationships |
| CWE Content Team |
MITRE |
2014-06-23 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2014-07-30 +00:00 |
updated Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Applicable_Platforms |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2021-03-15 +00:00 |
updated Maintenance_Notes |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Detection_Factors, Relationships, Time_of_Introduction |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2023-10-26 +00:00 |
updated Demonstrative_Examples, Observed_Examples |
| CWE Content Team |
MITRE |
2025-04-03 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Observed_Examples, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Common_Consequences, Description |