이름: Reachable Assertion
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
일반 정보
취약점 도입 방식
Implementation적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)이름: C (Sometimes)
이름: Java (Undetermined)
이름: Python (Undetermined)
이름: Rust (Undetermined)
기술
클래스: Not Technology-Specific (Undetermined)일반적인 결과
| 범위 | 영향 | 가능성 |
|---|---|---|
| Availability | DoS: Crash, Exit, or Restart 참고: While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, an attacker can still cause a denial of service if they can trigger an assert statement, and if the scope of the assert() extends beyond the attacker's own session. For example, if a server handles multiple simultaneous connections, if an assert() occurs in one single connection that causes all other connections to be dropped, this could be a significant denial of service. |
관찰된 예시
| 참고 자료 | 설명 |
|---|---|
CVE-2024-8768 | API server for LLM library can crash when provided an empty prompt, which triggers a reachable assertion |
CVE-2023-49286 | Chain: function in web caching proxy does not correctly check a return value (CWE-253) leading to a reachable assertion (CWE-617) |
CVE-2006-6767 | FTP server allows remote attackers to cause a denial of service (daemon abort) via crafted commands which trigger an assertion failure. |
CVE-2006-6811 | Chat client allows remote attackers to cause a denial of service (crash) via a long message string when connecting to a server, which causes an assertion failure. |
CVE-2006-5779 | Product allows remote attackers to cause a denial of service (daemon crash) via LDAP BIND requests with long authcid names, which triggers an assertion failure. |
CVE-2006-4095 | Product allows remote attackers to cause a denial of service (crash) via certain queries, which cause an assertion failure. |
CVE-2006-4574 | Chain: security monitoring product has an off-by-one error that leads to unexpected length values, triggering an assertion. |
CVE-2004-0270 | Anti-virus product has an assertion error when the line length is non-numeric. |
잠재적 완화 방법
Phases : ImplementationIf the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
Phases : Implementation
Consider changing the assertion to some other less "fatal" error. This might not be easy to implement, since other code may be needed to handle the error.
Phases : Implementation
Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)
Phases : Implementation
Perform input validation on user data.
탐지 방법
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
취약점 매핑 메모
근거 : 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.
참고 자료
REF-1541
Secure Coding Guide for PythonOpenSSF.
https://best.openssf.org/Secure-Coding-Guide-for-Python/
제출
| 이름 | 조직 | 날짜 | 출시일 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | Draft 6 |
수정 사항
| 이름 | 조직 | 날짜 | 댓글 |
|---|---|---|---|
| Sean Eidemiller | Cigital | added/updated demonstrative examples | |
| Eric Dalci | Cigital | updated Potential_Mitigations, Time_of_Introduction | |
| CWE Content Team | MITRE | updated Description, Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Common_Consequences, Observed_Examples, Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Potential_Mitigations | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Other_Notes | |
| CWE Content Team | MITRE | updated Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Relationships, Type | |
| CWE Content Team | MITRE | updated Alternate_Terms | |
| CWE Content Team | MITRE | updated Detection_Factors, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Observed_Examples, Relationships | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Common_Consequences, Description, Observed_Examples, Potential_Mitigations, References, Relationships, Taxonomy_Mappings |
