Most recent entries from all

ALSA-2022:7524 — Moderate: yajl security update

Affected: AlmaLinux:8: yajl, AlmaLinux:8: yajl-devel

Yet Another JSON Library (YAJL) is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.

Security Fix(es):

* yajl: heap-based buffer overflow when handling large inputs due to an integer overflow (CVE-2022-24795)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Additional Changes:

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

bdu:2023-07630

BREW-yajl-CVE-2022-24795 — Buffer Overflow and Integer Overflow in yajl-ruby

Affected: Homebrew: yajl

yajl-ruby is a C binding to the YAJL JSON parsing and generation library. The 1.x branch and the 2.x branch of `yajl` contain an integer overflow which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. The reallocation logic at `yajl_buf.c#L64` may result in the `need` 32bit integer wrapping to 0 when `need` approaches a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation of buf->alloc into a small heap chunk. These integers are declared as `size_t` in the 2.x branch of `yajl`, which practically prevents the issue from triggering on 64bit platforms, however this does not preclude this issue triggering on 32bit builds on which `size_t` is a 32bit integer. Subsequent population of this under-allocated heap chunk is based on the original buffer size, leading to heap memory corruption. This vulnerability mostly impacts process availability. Maintainers believe exploitation for arbitrary code execution is unlikely. A patch is available and anticipated to be part of yajl-ruby version 1.4.2. As a workaround, avoid passing large inputs to YAJL.

certfr-2025-avi-0003 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…

certfr-2025-avi-0003

EUVD-2026-232776

fkie_cve-2022-24795

GHSA-jj47-x69x-mxrm — Buffer Overflow in yajl-ruby

Affected: RubyGems: yajl-ruby

_NOTE: A previous patch, 1.4.2, fixed the heap memory issue, but could still lead to a DoS infinite loop. Please update to version 1.4.3_

The 1.x branch and the 2.x branch of [yajl](https://github.com/lloyd/yajl) contain an integer overflow which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs.

### Details

The [reallocation logic at yajl_buf.c#L64](https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64) may result in the `need` 32bit integer wrapping to 0 when `need` approaches a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation of buf->alloc into a small heap chunk.

These integers are declared as `size_t` in the 2.x branch of `yajl`, which practically prevents the issue from triggering on 64bit platforms, however this does not preclude this issue triggering on 32bit builds on which `size_t` is a 32bit integer.

Subsequent population of this under-allocated heap chunk is based on the original buffer size, leading to heap memory corruption.

### Impact

We rate this as a moderate severity vulnerability which mostly impacts process availability as we believe exploitation for arbitrary code execution to be unlikely.

### Patches

Patched in yajl-ruby 1.4.3

### Workarounds

Avoid passing large inputs to YAJL

### References https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64

### For more information If you…

gsd-2022-24795

msrc_CVE-2022-24795 — Buffer Overflow and Integer Overflow in yajl-ruby

msrc_CVE-2022-24795

OESA-2022-1752 — rubygem-yajl-ruby security update

Affected: openEuler:20.03-LTS-SP1: rubygem-yajl-ruby, openEuler:20.03-LTS-SP3: rubygem-yajl-ruby, openEuler:22.03-LTS: rubygem-yajl-ruby

Ruby C bindings to the excellent Yajl JSON stream-based parser library. Security Fix(es): yajl-ruby is a C binding to the YAJL JSON parsing and generation library. The 1.x branch and the 2.x branch of `yajl` contain an integer overflow which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. The reallocation logic at `yajl_buf.c#L64` may result in the `need` 32bit integer wrapping to 0 when `need` approaches a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation of buf->alloc into a small heap chunk. These integers are declared as `size_t` in the 2.x branch of `yajl`, which practically prevents the issue from triggering on 64bit platforms, however this does not preclude this issue triggering on 32bit builds on which `size_t` is a 32bit integer. Subsequent population of this under-allocated heap chunk is based on the original buffer size, leading to heap memory corruption. This vulnerability mostly impacts process availability. Maintainers believe exploitation for arbitrary code execution is unlikely. A patch is available and anticipated to be part of yajl-ruby version 1.4.2. As a workaround, avoid passing large inputs to YAJL.(CVE-2022-24795)

openSUSE-SU-2024:12258-1 — libyajl-devel-2.1.0-6.1 on GA media

libyajl-devel-2.1.0-6.1 on GA media

RHSA-2024:2063 — Red Hat Security Advisory: yajl security update

yajl: heap-based buffer overflow when handling large inputs due to an integer overflow yajl: Memory leak in yajl_tree_parse function

SUSE-SU-2022:1746-1 — Security update for libyajl

Security update for libyajl

UBUNTU-CVE-2022-24795

Affected: Ubuntu:Pro:14.04:LTS: yajl, Ubuntu:Pro:16.04:LTS: yajl, Ubuntu:16.04:LTS: argyll, Ubuntu:16.04:LTS: burp, Ubuntu:16.04:LTS: collada2gltf, Ubuntu:16.04:LTS: icinga2, Ubuntu:Pro:16.04:LTS: libbson, Ubuntu:16.04:LTS: lnav, Ubuntu:16.04:LTS: php-mongodb, Ubuntu:16.04:LTS: r-cran-jsonlite and 53 more

WID-SEC-W-2025-0001 — IBM DB2: Mehrere Schwachstellen

Ein entfernter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 on Cloud Pak for Data ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder einen Denial-of-Service-Zustand zu erzeugen.