Products / tensorflow
tensorflow
433 records.
- 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.
- Segfault and OOB write due to incomplete validation in `EditDistance` in TensorFlow Crafted negative indices make EditDistance read or write outside its buffers, causing a crash or memory corruption.
- 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.
- Code injection in `saved_model_cli` in TensorFlow The saved_model_cli input expression is passed to Python eval on an unsafe path, so supplied expressions run arbitrary code; the earlier fix missed this branch.
- 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.
- Heap buffer overflow due to incorrect hash function in TensorFlow The tensor key hash reads raw bytes using a size estimate that does not match the contiguous buffer, causing heap overflows.
- 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.
- Missing validation results in undefined behavior in `QuantizedConv2D` Passing empty minimum and maximum tensors to the quantized convolution op leaves internal references null, so the kernel reads through invalid pointers.
- Missing validation results in undefined behavior in `SparseTensorDenseAdd Mismatched sparse indices and empty values reach a kernel that binds a reference to null, causing undefined behaviour.
- 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.
- Incomplete validation in `SparseSparseMinimum` SparseSparseMinimum accepts invalid sparse tensor triples that are not checked for empty inputs or index-shape consistency, causing out-of-bounds heap writes.
- 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.
- `CHECK`-failures in `TensorByteSize` in Tensorflow A crafted SavedModel causes a tensor size helper to hit internal assertions, aborting the TensorFlow process when the model is loaded.
- `CHECK`-failures during Grappler's `SafeToRemoveIdentity` in Tensorflow A tampered SavedModel causes the Grappler identity-removal check to hit assertion failures, crashing the process when the model is optimized.
- Division by zero in Tensorflow Crafted pooling ratio arguments cause a division by zero in the FractionalMaxPool kernel, crashing the TensorFlow process.
- Null-dereference in Tensorflow A crafted SavedModel with a missing nested signature key makes the loader dereference a null pointer and crash when the model is opened.
- 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.
- Integer overflow in Tensorflow An unchecked multiplication of element count and element size in cost estimation can overflow into an incorrect size.
- `CHECK`-failures in Tensorflow A MapStage call with a non-scalar key tensor hits an assertion in the kernel and aborts the process.
- `CHECK`-failures in binary ops in Tensorflow A tampered SavedModel with mismatched tensor dtypes makes binary ops hit CHECK failures, crashing the process when the model runs.
- 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.
- Integer overflow in Tensorflow Multiplying tensor dimension sizes in the cost estimator can overflow for very large operations, producing a wrong output size.
- Out of bounds read in Tensorflow The Dequantize op does not check the upper bound of the axis argument, so out-of-range values cause heap reads past the end of the dimension array.
- Stack overflow in TensorFlow A SavedModel containing a self-recursive function in its GraphDef causes unbounded recursion during loading or execution, overflowing the stack.