Browse / AI Framework and Platform Flaws / Denial of service
Denial of service
377 records in AI Framework and Platform Flaws.
- Null pointer dereference in TensorFlow A crafted raw-op call with an empty min_input tensor makes the quantized max pool kernel bind a reference to a null pointer.
- Division by zero in TFLite A crafted TFLite model makes depthwise convolution padding divide by a value that is not checked to be positive, so it can be zero.
- Multiple `CHECK`-fails in `function.cc` in TensowFlow A tampered SavedModel triggers failed internal assertions in function handling, crashing the Python process.
- Integer overflows in Tensorflow An integer overflow in sparse tensor map shape construction triggers a CHECK failure that aborts the process.
- Reachable Assertion in Tensorflow A protobuf-encoded resource handle with attacker-chosen fields violates a CHECK assertion during decoding, aborting the TensorFlow process.
- Assertion failure based denial of service in Tensorflow Bincount operations lack argument validation for some inputs, so crafted arguments trigger a CHECK failure that crashes the process when output tensors are allocated.
- Null pointer dereference in TensorFlow Building an XLA compilation cache with default GPU settings dereferences a null config pointer, crashing the process.
- Segfault in `simplifyBroadcast` in Tensorflow Calling simplifyBroadcast with all-scalar shapes builds an empty vector that is then indexed, causing a segmentation fault.
- Reachable Assertion in Tensorflow A tensor protobuf with an invalid dtype or shape and zero elements violates a CHECK assertion, crashing the TensorFlow process.
- Undefined behavior in `SparseTensorSliceDataset` Unvalidated sparse tensor inputs lead the dataset op to dereference a null pointer, crashing the process.
- `CHECK`-fails when building invalid tensor shapes in Tensorflow Several TensorFlow operations accept invalid tensor shapes that trip internal CHECK assertions and crash the process.
- Integer overflows in Tensorflow Missing shape validation and an unchecked TensorShape construction let crafted sparse tensor inputs overflow, causing huge allocations or assertion crashes.
- Crash when type cannot be specialized in Tensorflow A failed type specialisation during shape inference hits a debug-only check, so the runtime unwraps an error status and crashes.
- Integer Overflow or Wraparound in TensorFlow A user-controlled tensor shape reaches a CHECK in the Grappler constant folding pass, triggering an assertion failure that crashes the process.
- Integer overflow leading to crash in Tensorflow Integer overflow in SparseCountSparseOutput produces a bad allocation size that crashes the TensorFlow process.
- Abort caused by allocating a vector that is too large in Tensorflow A user-supplied dimension count read from a tensor drives a very large up-front vector reservation during shape inference, which can abort the process.
- Inefficient Regular Expression Complexity in nltk (word_tokenize, sent_tokenize) A long crafted input makes the Punkt-based tokenizers and word_tokenize run regex backtracking that takes super-linear time.
- NLTK Vulnerable to REDoS Regex taggers in NLTK can be driven into catastrophic backtracking by crafted input, stalling the process.
- Overflow/crash in `tf.tile` when tiling tensor is large Oversized tile arguments overflow the output element count, triggering a CHECK failure that aborts the process.
- Null pointer exception when `Exit` node is not preceded by `Enter` op A raw TensorFlow Exit op with no matching Enter causes graph construction to dereference a null parent pointer and crash the process.
- Overflow/crash in `tf.image.resize` when size is large An oversized resize argument overflows the computed output element count and trips a CHECK that aborts the process.
- FPE in convolutions with zero size filters Convolution kernels divide by zero when given empty filter tensors, crashing the process with a floating-point exception.
- Segfault while copying constant resource tensor Constant folding during graph optimisation attempts a deep copy of a resource tensor that should be immutable, and the copy crashes the process.
- FPE in `ParallelConcat` A ParallelConcat call with a zero shape is not validated, so the kernel divides by zero and the process crashes.
- Integer division by 0 in `tf.raw_ops.AllToAll` A zero split_count argument makes AllToAll shape inference divide by zero during tracing, crashing the process.
- Segfault due to negative splits in `SplitV` Negative values in the split size list are not validated, so crafted arguments make the split operation segfault.
- Crash in `tf.math.segment_*` operations Passing a very large segment id to tf.math.segment_* ops overflows a shape calculation, triggering a CHECK failure that aborts the process.
- Incomplete validation in `tf.summary.create_file_writer` Passing non-scalar arguments to the summary file writer constructor trips an assertion and crashes the process.
- Deadlock in mutually recursive `tf.function` objects A non-reentrant lock causes mutually recursive tf.function objects to deadlock when called, hanging any process that loads such a model.
- Crash in `max_pool3d` when size argument is 0 or negative Pooling layers do not check that window sizes are positive, so a zero or negative dimension crashes the process.
- Crashes due to overflow and `CHECK`-fail in ops with large tensor shapes Tensor shape size computations can overflow int64 and hit CHECK failures, so a crafted shape crashes the process instead of returning an error.
- Reference binding to `nullptr` in `tf.ragged.cross` Shape inference for a ragged cross op binds a reference to null, causing undefined behaviour and a crash on crafted input.
- Null pointer exception in `DeserializeSparse` A scalar input to DeserializeSparse makes shape inference dereference a null pointer and crash TensorFlow.
- Overflow/crash in `tf.range` Integer overflow from a double-typed conditional in the range and sparse eye kernels produces a crash with large inputs.
- NLTK Vulnerable to REDoS A regular expression in a corpus reader backtracks catastrophically on crafted input, consuming excessive CPU.
- `CHECK`-fail in `MapStage` An empty key tensor passed to tf.raw_ops.MapStage triggers a CHECK failure that aborts the process because the input is not validated.
- `std::abort` raised from `TensorListReserve` A negative num_elements passed to tf.raw_ops.TensorListReserve makes a std::vector resize to a negative size, aborting the process.
- FPE in `tf.raw_ops.UnravelIndex` A missing check for empty dimension tensors lets a crafted call to an index-unravelling op trigger division by zero and crash serving applications.
- Reference binding to nullptr in `MatrixDiagV*` ops Passing an empty tensor as the k argument to MatrixDiagV ops makes the kernel read the first element of nothing, causing undefined behaviour.
- Null pointer dereference in `UncompressElement` UncompressElement accepts a variant that does not hold a compressed element, so a null pointer is dereferenced during decompression.
- Incomplete validation in `MaxPoolGrad` Missing checks on the orig_input and orig_output tensors in MaxPoolGrad let a crafted call segfault the TensorFlow process.
- NPE in TFLite The TFLite SVDF kernel dereferences a state tensor pointer that may be null, crashing when the variable input lookup fails.
- Integer division by 0 in sparse reshaping A zero-element shape passed to SparseReshape causes an integer division by zero in the reshape functor.
- Division by 0 in most convolution operators A convolution call with zero-sized tensors reaches shape inference, which divides by zero and crashes the process, causing denial of service.
- Null pointer dereference in `SparseTensorSliceDataset` A sparse tensor built with empty indices but non-empty values causes a null pointer dereference during validation, crashing the process.
- Null pointer dereference in `CompressElement` Passing an empty component list to the element compression op dereferences a null buffer before validation, crashing the process.
- Division by zero in TFLite A crafted model file with a zero filter dimension makes a fully connected TFLite kernel divide by zero, crashing the process.
- Division by 0 in `ResourceScatterDiv` A zero update value passed to the scatter-divide op causes a division by zero because the shared binary-op path has no special case for it.
- Division by 0 in inplace operations An empty-input check uses OR instead of AND, so crafted arguments reach a division by zero in the inplace operation and crash it.
- Segfault on strings tensors with mistmatched dimensions, due to Go code A garbage-collection finaliser frees string tensor data whose encoding previously failed, so it dereferences invalid memory and crashes.