Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-617 (可达断言) — Vulnerability Class 234

234 vulnerabilities classified as CWE-617 (可达断言). AI Chinese analysis included.

CWE-617 represents a software weakness where an assertion statement, intended for debugging or internal logic validation, remains enabled in production code and can be triggered by external input. This flaw typically leads to a denial of service, as the application abruptly terminates or crashes when the assertion fails, rather than handling the error gracefully. Attackers exploit this by crafting specific inputs that violate the assumed invariants, forcing the program to exit unexpectedly. To mitigate this risk, developers must ensure that assertions are strictly disabled in production environments or replace them with robust error-handling mechanisms. By validating inputs and managing exceptions without relying on fatal assertions, teams can maintain application availability and prevent attackers from leveraging these logic checks for disruptive service interruptions.

MITRE CWE Description
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.
Common Consequences (1)
AvailabilityDoS: Crash, Exit, or Restart
An attacker that can trigger an assert statement can still lead to a denial of service if the relevant code can be triggered by an attacker, and if the scope of the assert() extends beyond the attacker's own session.
Mitigations (2)
ImplementationMake sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
ImplementationPerform input validation on user data.
Examples (1)
In the excerpt below, an AssertionError (an unchecked exception) is thrown if the user hasn't entered an email address in an HTML form.
String email = request.getParameter("email_address"); assert email != null;
Bad · Java
CVE IDTitleCVSSSeverityPublished
CVE-2022-35992 `CHECK` fail in `TensorListFromTensor` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35991 `CHECK` fail in `TensorListScatter` and `TensorListScatterV2` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35999 `CHECK` fail in `Conv2DBackpropInput` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35998 `CHECK` fail in `EmptyTensorList` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35997 `CHECK` fail in `tf.sparse.cross` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35995 `CHECK` fail in `AudioSummaryV2` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36016 `CHECK`-fail in `tensorflow::full_type::SubstituteFromAttrs` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36005 `CHECK` fail in `FakeQuantWithMinMaxVarsGradient` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36004 `CHECK` fail in `tf.random.gamma` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36003 `CHECK` fail in `RandomPoissonV2` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36002 `CHECK` fail in `Unbatch` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36001 `CHECK` fail in `DrawBoundingBoxes` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36026 `CHECK` fail in `QuantizeAndDequantizeV3` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36018 `CHECK` fail in `RaggedTensorToVariant` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-36019 `CHECK` fail in `FakeQuantWithMinMaxVarsPerChannel` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35990 `CHECK` fail in `FakeQuantWithMinMaxVarsPerChannelGradient` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35987 `CHECK` fail in `DenseBincount` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35985 `CHECK` fail in `LRNGrad` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35984 `CHECK` fail in `ParameterizedTruncatedNormal` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35983 `CHECK` fail in `Save` and `SaveSlices` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35989 `CHECK` fail in `MaxPool` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35988 `CHECK` fail in `tf.linalg.matrix_rank` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35981 `CHECK` fail in `FractionalMaxPoolGrad` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35971 `CHECK` fail in `FakeQuantWithMinMaxVars` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35969 `CHECK` fail in `Conv2DBackpropInput` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35968 `CHECK` fail in `AvgPoolGrad` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35963 `CHECK` failures in `FractionalAvgPoolGrad` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35960 `CHECK` failure in `TensorListReserve` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35959 `CHECK` failures in `AvgPool3DGrad` in TensorFlow — tensorflow 5.9 Medium2022-09-16
CVE-2022-35952 `CHECK` failures in `UnbatchGradOp` in TensorFlow — tensorflow 5.9 Medium2022-09-16

Vulnerabilities classified as CWE-617 (可达断言) represent 234 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.