Browse / AI Framework and Platform Flaws / Denial of service
Denial of service
377 records in AI Framework and Platform Flaws.
- Division by 0 in `DenseCountSparseOutput` Empty batch dimensions in the values tensor cause a division by zero in the count kernel, crashing the process.
- Stack overflow in `ParseAttrValue` with nested tensors Deeply nested tensor attribute input recurses without limit in the parser, overflowing the stack and crashing the process.
- Division by 0 in `FusedBatchNorm` A zero last dimension in FusedBatchNorm inputs causes a division by zero that crashes the process.
- Division by 0 in `Conv2DBackpropFilter` A zero-sized input to a convolution gradient op makes the kernel take a modulus by a caller-controlled zero, crashing the process.
- Null pointer dereference in `SparseFillEmptyRows` A sparse tensor with an empty dense shape reaches an unchecked dereference because validation was left as a TODO, crashing the process.
- Segfault in `CTCBeamSearchDecoder` The CTC beam search decoder does not detect empty input tensors, so it reads from a null buffer and crashes.
- Segfault in `tf.raw_ops.SparseCountSparseOutput` Invalid arguments to SparseCountSparseOutput cause a segmentation fault in TensorFlow.
- Division by 0 in `QuantizedConv2D` A zero-sized filter in QuantizedConv2D causes a division by zero that crashes TensorFlow.
- Division by 0 in `QuantizedAdd` A zero-sized input shape makes a modulo operation divide by zero, crashing the quantized add op.
- Undefined behavior and `CHECK`-fail in `FractionalMaxPoolGrad` Empty or mismatched input tensors passed to the raw gradient op trigger undefined behaviour and a CHECK failure that aborts the whole process.
- Invalid validation in `SparseMatrixSparseCholesky` An empty permutation argument passes validation that checks only the dtype, leading to a null pointer dereference and process crash.
- Division by 0 in `Conv2DBackpropInput` Empty filter and gradient tensors make the op divide by a caller-controlled zero quantity, crashing the process.
- Null pointer dereference in `StringNGrams` Missing validation of data_splits lets crafted input yield a null output buffer that is later written, crashing the process.
- Crash in `tf.transpose` with complex inputs Passing a complex value together with conjugate=True to the transpose operation triggers a crash.
- CHECK-fail due to integer overflow Integer overflow when building a dense shape in the sparse split op triggers a CHECK failure that crashes the process.
- Division by 0 in `SparseMatMul` An empty input matrix causes a division by zero inside the sparse matrix multiplication kernel, raising a runtime error.
- CHECK-fail in LSTM with zero-length input in TensorFlow An LSTM or GRU layer receiving zero-length input triggers a CHECK failure that crashes the process on the CUDA backend.
- Segfault in Tensorflow The eager runtime iterates over a null output tensor for one branch of the Switch op, crashing the process when that branch is taken.
- Denial of Service in Tensorflow Incomplete shape validation of one gradient argument lets a crafted tensor trigger an assertion failure in a serving process.
- Denial of service in tensorflow-lite A crafted segment ID value in a TensorFlow Lite model causes the segment sum kernel to make an enormous allocation, exhausting memory.
- Segfault in Tensorflow In eager mode the session state is never set, so the session handle ops dereference a null pointer and crash the process.
- Denial of Service in Tensorflow A sparse-count input whose indices tensor has the wrong rank triggers an assertion failure that crashes the serving process.
- Denial of Service in Tensorflow Passing an empty or single-element splits tensor to a ragged count op reaches an unchecked null path that aborts the process.
- Denial of Service in Tensorflow The fill argument is spliced into a printf format string, so attacker-chosen characters alter the formatting and can corrupt the operation's output.
- Segmentation faultin TensorFlow when converting a Python string to `tf.float16` Passing a Python string where a float16 is expected crashes the process in eager mode, because the type check only runs in graph mode.
- NULL Pointer Dereference in Google TensorFlow A malformed GIF file triggers a null pointer dereference in TensorFlow's decoder, crashing the process.
- Null pointer dereference in TensorFlow leads to exploitation A null pointer is dereferenced in TensorFlow 1.x releases, so crafted inputs can crash the process.