Threats Tagged 'cwe-789'

imagecli's `scale <ratio>` pipeline operation (Scale::apply() in src/image_ops.rs) computes output width/height as (dimension as f32 * ratio) as u32 with no upper-bound validation on the CLI-supplied ratio, which is parsed via nom::number::complete::float with no range check. A large ratio (e.g. 100000) causes an attempted allocation of hundreds of terabytes, aborting the process. Any application embedding imagecli as a library and accepting user-controlled pipeline strings is remotely crashable with a single request.

** UNSUPPORTED WHEN ASSIGNED ** Memory Allocation with Excessive Size Value vulnerability in Apache Lucy. This issue affects Apache Lucy: all versions. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid ProtonJ2: through 1.1.0. Users are recommended to upgrade to version 1.2.0, which fixes the issue.

pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid Proton-Dotnet: through 1.0.0. Users are recommended to upgrade to version 1.1.0, which fixes the issue.

A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid Proton-J: through 0.34.1. Users are recommended to upgrade to version 0.35.0, which fixes the issue.

A vulnerability in Veeam Service Provider Console allowing an unauthenticated attacker to exhaust host memory and cause adenial of service.

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Jaeyoung Jang for reporting this issue.

Bouncy Castle for Java versions before 1.85 have an unbounded HSS public-key level count, which can lead to excessive memory allocation during verification. This vulnerability also affects Bouncy Castle for Java LTS versions before 2.73.12 and Bouncy Castle for Java FIPS versions before 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

Bouncy Castle for Java versions prior to 1.85 and certain LTS and FIPS versions contain a vulnerability that may cause an out-of-memory (OOM) condition due to unbounded memory allocation during a definite-length read operation. This issue affects multiple Bouncy Castle Java variants including LTS before 2.73.12, BC-FJA before 1.0.2.7, 2.0.2, and 2.1.3, and bctls-fips before 1.0.24. The vulnerability is classified under CWE-789 (Uncontrolled Memory Allocation).

Bouncy Castle for Java versions before 1.85 contain a vulnerability in the MLS wire decoder where it allocates memory based on an attacker-controlled opaque length before performing bounds checking. This flaw can lead to resource exhaustion or denial of service. No patch information is currently provided.