Browse / AI Framework and Platform Flaws / Denial of service
Denial of service
377 records in AI Framework and Platform Flaws.
- TensorFlow vulnerable to `CHECK` fail in `Unbatch` A non-scalar id passed to TensorFlow's Unbatch op fails an internal CHECK, crashing the process.
- TensorFlow vulnerable to `CHECK` fail in `tf.random.gamma` Large shape and rate inputs to tf.random.gamma trigger an assertion failure that crashes the process.
- TensorFlow vulnerable to `CHECK` fail in `ParameterizedTruncatedNormal` Passing an int64 shape to the truncated normal op hits a type-mismatch check that aborts the process, so a crafted call crashes it.
- TensorFlow vulnerable to `CHECK` fail in `tf.sparse.cross` A non-scalar separator passed to tf.sparse.cross triggers a failed internal CHECK, crashing the process with a single call.
- TensorFlow vulnerable to `CHECK` fail in `Conv2DBackpropInput` Passing a Conv2DBackpropInput call with a non-4-dimensional input_sizes tensor triggers a CHECK failure that crashes the process.
- TensorFlow vulnerable to floating point exception in `Conv2D` Passing an empty input tensor to Conv2D with valid filter and padding causes a division by zero that raises a floating point exception and crashes the process.
- TensorFlow vulnerable to segfault in `LowerBound` and `UpperBound` Empty sorted-input tensors passed to LowerBound and UpperBound cause a null pointer dereference that crashes the process when invoked through raw ops.
- TensorFlow vulnerable to `CHECK` fail in `FakeQuantWithMinMaxVarsGradient` Passing a non-scalar min or max to the fake-quant gradient op triggers an internal CHECK failure that aborts the process.
- TensorFlow vulnerable to integer overflow in math ops Range arguments that overflow int64 are not fully checked in RangeSize, so the operation crashes.
- TensorFlow vulnerable to `CHECK` failure in `TensorListReserve` via missing validation Passing a multi-element tensor as num_elements to TensorListReserve trips an internal assertion that aborts the process.
- TensorFlow vulnerable to segfault in `QuantizedAdd` Passing non-scalar min and max range tensors to QuantizedAdd causes a segmentation fault that crashes the process.
- TensorFlow vulnerable to segfault in `QuantizedRelu` and `QuantizedRelu6` Passing non-scalar min or max feature range tensors to QuantizedRelu or QuantizedRelu6 causes a segmentation fault that crashes the process.
- TensorFlow vulnerable to segfault in `QuantizeDownAndShrinkRange` Passing non-scalar minimum or maximum tensors to the quantization op makes it read invalid data and crash the process.
- TensorFlow vulnerable to `CHECK` fail in `TensorListScatter` and `TensorListScatterV2` A tensor list scatter op given an element shape of rank above one hits an internal check failure that aborts the process.
- TensorFlow vulnerable to `CHECK` fail in `FractionalMaxPoolGrad` Invalid input sizes to a pooling gradient op hit a CHECK assertion instead of returning an error, crashing the process.
- TensorFlow vulnerable to `CHECK` fail in `DenseBincount` Passing a weights tensor whose shape differs from the input triggers a CHECK failure that aborts the process.
- TensorFlow vulnerable to `CHECK` fail in `SetSize` Passing a non-1D set_shape to the SetSize op triggers a CHECK failure that aborts the TensorFlow process.
- TensorFlow vulnerable to segfault in `Requantize` Requantize given range tensors of nonzero rank causes a segmentation fault in TensorFlow.
- TensorFlow vulnerable to `CHECK` failures in `AvgPool3DGrad` An oversized shape value in AvgPool3DGrad overflows a size calculation and triggers a CHECK failure that crashes the operation.
- TensorFlow vulnerable to Int overflow in `RaggedRangeOp` A very large float limit overflows during int64 conversion in RaggedRange, producing an abort that crashes the process.
- TensorFlow vulnerable to `CHECK` fail in `EmptyTensorList` Passing a multi-dimensional element_shape to EmptyTensorList triggers a CHECK failure that aborts the process.
- TensorFlow vulnerable to segfault in `RaggedBincount` An empty splits tensor passed to RaggedBincount causes a segmentation fault in TensorFlow.
- `CHECK` failure in depthwise ops via overflows Overflowing the element count in depthwise filter backprop computation triggers an assertion failure that crashes TensorFlow.
- Missing validation causes `TensorSummaryV2` to crash Metadata with unexpected shape reaches an unvalidated CHECK in the summary op, aborting the process.
- Missing validation causes denial of service via `LSTMBlockCell` Inputs with unvalidated ranks reach LSTMBlockCell, where element access triggers a CHECK failure that crashes the process.
- Segfault due to missing support for quantized types Calling compat.v1 ops with quantized dtypes passes a null kernel pointer that is later dereferenced, crashing the process.
- Incomplete validation in signal ops leads to crashes in TensorFlow Missing argument validation in the rfft2d and rfft3d signal ops lets certain inputs trigger CHECK failures that crash the process.
- Missing validation causes denial of service via `Conv3DBackpropFilterV2` A raw Conv3DBackpropFilterV2 call with a non-vector filter_sizes argument hits an unchecked CHECK and crashes the process.
- Undefined behavior when users supply invalid resource handles Passing an empty resource handle to several eager-mode TensorFlow ops binds a reference to a null pointer, causing undefined behaviour and likely crashes.
- Core dump when loading TFLite models with quantization in TensorFlow A converter-produced quantised model has a scale above one, which trips a sub-unit assertion in the quantisation helper and aborts the interpreter.
- Denial of service in `tf.ragged.constant` due to lack of validation The ragged constructor does not validate ragged_rank, so an oversized value makes it allocate memory until the process exhausts all available memory.
- Type confusion leading to `CHECK`-failure based denial of service in TensorFlow Mixed signed and unsigned comparisons in TensorFlow assertion macros trigger CHECK failures that crash the process.
- Missing validation causes denial of service via `GetSessionTensor` A non-scalar handle passed to GetSessionTensor hits an unvalidated scalar assumption, triggering a CHECK failure that aborts the process.
- Missing validation crashes `QuantizeAndDequantizeV4Grad` Missing shape validation in QuantizeAndDequantizeV4Grad triggers a CHECK failure that crashes the process.
- Missing validation causes denial of service via `StagePeek` A missing scalar check on an index input to a TensorFlow op triggers a CHECK failure that crashes the process.
- Missing validation causes denial of service via `DeleteSessionTensor` A non-scalar handle passed to DeleteSessionTensor triggers a CHECK failure in TensorFlow that crashes the process.
- Missing validation causes denial of service via `UnsortedSegmentJoin` A missing check on the segment count input lets a zero-valued tensor trigger a CHECK failure that aborts the TensorFlow process.
- Missing validation causes denial of service via `Conv3DBackpropFilterV2` A negative segment count passed to a string segment-join op is not validated before allocation, tripping an assertion that crashes TensorFlow.
- Integer overflow in `SpaceToBatchND` An integer overflow in the SpaceToBatchND output size calculation yields a negative value, which trips an assertion and crashes the process.
- Missing validation causes denial of service via `SparseTensorToCSRSparseMatrix` Malformed sparse tensor inputs to SparseTensorToCSRSparseMatrix fail an internal CHECK, crashing the TensorFlow process.
- Missing validation causes denial of service via `LoadAndRemapMatrix` A tensor op receives a malformed remapping argument that is not validated, triggering a CHECK failure that crashes the process.
- Segfault if `tf.histogram_fixed_width` is called with NaN values in TensorFlow NaN values reach a float-to-integer cast in the CPU histogram kernel, causing a crash.
- Overflow and uncaught divide by zero in Tensorflow Integer overflow in an index operation produces a division by zero that crashes the process on crafted input.
- Division by zero in Tensorflow Crafted pooling ratio arguments cause a division by zero in the FractionalMaxPool kernel, crashing the TensorFlow process.
- Memory leak in Tensorflow An invalid graph node sends executor initialisation down an error path that overwrites a kernel pointer with null without freeing it, leaking memory on each attempt.
- Memory exhaustion in Tensorflow A negative padding width overflows an integer in StringNGrams, leading to a huge allocation and memory exhaustion.
- Memory exhaustion in Tensorflow The thread pool handle accepts an unbounded thread count, so a single call can allocate enormous memory and exhaust the host.
- `CHECK`-failures in Tensorflow A MapStage call with a non-scalar key tensor hits an assertion in the kernel and aborts the process.
- Type confusion leading to segfault in Tensorflow A very large axis value is compared against a 32-bit limit during shape inference, causing a type confusion that segfaults the process.
- Division by zero in Tensorflow A zero stride passed to AvgPoolGrad causes a division by zero in TensorFlow's cost estimator, crashing the process.