Sylwester Lachiewicz

An uncaught exception vulnerability exists in the Apache Thrift Java bindings due to improper handling of exceptional conditions and the allocation of resources without limits or throttling.

Apache Thrift Dart bindings contain an issue involving improper handling of length parameter inconsistency, which can lead to memory allocation with an excessive size value.

An uncaught exception issue exists within the Apache Thrift PHP bindings.

Apache Thrift PHP bindings contain an issue where resources are allocated without limits or throttling, which can lead to resource exhaustion.

Apache Thrift nodejs bindings contain an issue where input quantities are not properly validated, leading to the allocation of resources without limits or throttling. This can result in resource exhaustion.

Uncontrolled recursion occurs within the c glib bindings. Uncontrolled recursion is a condition where a function calls itself without a proper termination condition, potentially leading to a stack overflow and application crash.

The Apache Thrift Python bindings contain an issue involving the improper handling of highly compressed data, which can lead to data amplification. This occurs due to improper validation of the specified quantity in the input and function calls made with incorrectly specified arguments.

Apache Thrift Go bindings contain an issue involving the improper handling of highly compressed data, which can lead to data amplification. Data amplification occurs when a small amount of input data expands into a significantly larger amount of memory during decompression, potentially leading to resource exhaustion.

Apache Thrift PHP bindings contain an issue where resources are allocated without limits or throttling, which can lead to resource exhaustion.

Apache Thrift nodejs bindings contain a prototype pollution issue, which occurs when an attacker can manipulate the prototype of an object, potentially leading to an uncaught exception. This is caused by improper validation of the specified quantity in the input.

An issue exists in the Apache Thrift dart bindings where resources are allocated without limits or throttling. This can lead to excessive resource consumption.

A memory leak occurs in the Apache Thrift C++ bindings due to a missing release of memory after its effective lifetime.

An inefficient algorithmic complexity issue exists within the Lua bindings of Apache Thrift, where resources are allocated without proper limits or throttling.

An issue exists in the Apache Thrift ruby bindings where resources are allocated without limits or throttling. This can lead to excessive resource consumption.

An issue exists in the Apache Thrift JavaME bindings where resources are allocated without limits or throttling. This can lead to resource exhaustion.