Products / tensorflow
tensorflow
433 records.
- Heap buffer overflow in Tensorflow A double-indexed reverse map in the sparse fill gradient can point past the end of the gradient values buffer, writing outside a heap allocation.
- Memory leak in Tensorflow Passing a list of strings to dlpack conversion leaks allocated memory because the error status from validation is never checked.
- Denial of Service in Tensorflow Incomplete shape validation of one gradient argument lets a crafted tensor trigger an assertion failure in a serving process.
- Out of bounds access in tensorflow-lite A crafted TFLite model uses the -1 optional-tensor marker on operators that require real tensors, so the runtime reads and writes outside heap arrays.
- Data leak in Tensorflow Unvalidated split offsets passed to an n-gram op cause out-of-bounds heap reads that return adjacent process memory.
- Integer truncation in Shard API usage Shard callers pass lambdas taking 32-bit integers where 64-bit is expected, so large workloads truncate indices and write outside heap buffers.
- 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.
- Out of bounds access in tensorflow-lite A crafted negative segment id in a TFLite segment sum kernel makes the write index fall outside a heap buffer.
- Heap buffer overflow in Tensorflow Sparse count inputs with mismatched indices and values shapes cause out-of-bounds heap reads and writes.
- Data corruption in tensorflow-lite A no-op debug check in the Lite interpreter lets a crafted model with mismatched tensor dimensions cause out-of-bounds reads and writes.
- Out of bounds write in tensorflow-lite A Lite model whose segment ids are unsorted causes the segment sum kernel to size the output too small, then write past its end.
- Heap buffer overflow in Tensorflow RaggedCountSparseOutput does not check that splits form a valid partition of values, so a crafted input drives a read past a heap buffer.
- Heap buffer overflow in Tensorflow Sparse and ragged count ops do not check that weights match the data shape, so they read past the end of the weights heap buffer.
- Segfault and data corruption in tensorflow-lite Negative axis values are converted to indices with a validity check that only runs in debug builds, so release builds read out of bounds.
- 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.
- Undefined behavior in Tensorflow Invalid input to dlpack.to_dlpack leaves pointers null, and the unchecked error status lets code bind references to null, causing undefined behaviour.
- 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.
- Null pointer dereference in tensorflow-lite A crafted TFLite model remaps a buffer index so a read-only tensor becomes read-write with an unset buffer, causing a null pointer crash.
- Memory corruption in Tensorflow dlpack.to_dlpack accepts non-tensor Python objects and reads uninitialized memory, corrupting process memory.
- Denial of Service in Tensorflow Altering required key names in a SavedModel protobuf causes segfaults and corrupted loads when the model is loaded for serving.
- 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.
- Segfault in Tensorflow Splits values that do not start at zero cause an out-of-range access to an uninitialised map entry, crashing the process.
- Segmentation fault in tensorflow-lite A TFLite model reusing one tensor as both operator input and output is not rejected at load, causing memory corruption when the operator runs.
- 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.
- Out-of-bounds read in TensorFlow possibly causing disclosure of the contents of process memory. An integer overflow in the BMP decoder causes an out-of-bounds read that can expose process memory.
- 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.
- Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow Truncating 64-bit size values to 32-bit in a segment-sum kernel yields negative indices that write past a heap buffer.
- NULL Pointer Dereference in Google TensorFlow A malformed GIF file triggers a null pointer dereference in TensorFlow's decoder, crashing the process.
- Integer Overflow or Wraparound in Google TensorFlow A crafted checkpoint metadata file carries a huge block size that overflows an integer, leading the loader to read memory out of bounds.
- Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow A crafted configuration file triggers a heap buffer overflow in the XLA compiler, causing crashes or reads of other process memory.
- Improper Input Validation in Google TensorFlow Overlapping source and destination buffers in a bundled Snappy memcpy call cause out-of-bounds reads that can crash the process or expose nearby memory.
- Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow A malformed TFLite model file passed to the TOCO converter overflows a memory buffer during parsing, which can lead to code execution.
- 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.