CWE · MITRE source
CWE-617Reachable 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.
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service. For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.
Last updated: 04 July 2026 08:17 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 2 mapping(s) from 1 framework(s): ATT&CK 2 (mostly)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2006-5779 | 8.0 | 7.5 | 0.7537 | 2006-11-07 |
CVE-2018-5740 | 8.0 | 7.5 | 0.5935 | 2019-01-16 |
CVE-2020-8617 | 8.0 | 7.5 | 0.9342 | 2020-05-19 |
CVE-2020-36222 | 8.0 | 7.5 | 0.7774 | 2021-01-26 |
CVE-2021-27212 | 8.0 | 7.5 | 0.6415 | 2021-02-14 |
CVE-2023-28425 | 8.0 | 5.5 | 0.5498 | 2023-03-20 |
CVE-2019-9795 | 7.0 | 9.8 | 0.0170 | 2019-04-26 |
CVE-2020-3615 | 7.0 | 9.8 | 0.0075 | 2020-06-02 |
CVE-2026-27809 | 7.0 | 9.1 | 0.0041 | 2026-02-26 |
CVE-2006-4095 | 6.0 | 7.5 | 0.1255 | 2006-09-06 |
CVE-2016-8864 | 6.0 | 7.5 | 0.3873 | 2016-11-02 |
CVE-2017-7478 | 6.0 | 7.5 | 0.1389 | 2017-05-15 |
CVE-2018-12543 | 6.0 | 7.5 | 0.3601 | 2018-11-15 |
CVE-2017-3136 | 6.0 | 5.9 | 0.1109 | 2019-01-16 |
CVE-2018-5736 | 6.0 | 5.3 | 0.1788 | 2019-01-16 |
CVE-2018-5737 | 6.0 | 5.9 | 0.1036 | 2019-01-16 |
CVE-2011-3596 | 6.0 | 7.5 | 0.1105 | 2019-11-26 |
CVE-2020-36230 | 6.0 | 7.5 | 0.1229 | 2021-01-26 |
CVE-2021-25215 | 6.0 | 7.5 | 0.1130 | 2021-04-29 |
CVE-2022-3488 | 6.0 | 7.5 | 0.1905 | 2023-01-26 |
CVE-2022-3924 | 6.0 | 7.5 | 0.1599 | 2023-01-26 |
CVE-2023-49286 | 6.0 | 8.6 | 0.1035 | 2023-12-04 |
CVE-2006-4574 | 5.5 | 7.5 | 0.0410 | 2006-10-28 |
CVE-2006-6767 | 5.5 | 7.5 | 0.0659 | 2007-01-16 |
CVE-2016-9397 | 5.5 | 7.5 | 0.0359 | 2017-03-23 |