[Debian] High CVE: CVE-2017-16516/CVE-2022-24795/CVE-2023-33460 yajl: multiple CVEs

Bug #2038882 reported by Yue Tao
256
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Triaged
High
Unassigned

Bug Description

CVE-2017-16516: https://nvd.nist.gov/vuln/detail/CVE-2017-16516

In the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON file is supplied to Yajl::Parser.new.parse, the whole ruby process crashes with a SIGABRT in the yajl_string_decode function in yajl_encode.c. This results in the whole ruby process terminating and potentially a denial of service.

CVE-2022-24795: https://nvd.nist.gov/vuln/detail/CVE-2022-24795

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-2023-33460: https://nvd.nist.gov/vuln/detail/CVE-2023-33460

There's a memory leak in yajl 2.1.0 with use of yajl_tree_parse function. which will cause out-of-memory in server and cause crash.

Base Score: High

Reference:

['yajl-tools_2.1.0-3_amd64.deb===>yajl-tools_2.1.0-3+deb11u2_amd64.deb', 'libyajl-dev_2.1.0-3_amd64.deb===>libyajl-dev_2.1.0-3+deb11u2_amd64.deb', 'libyajl2_2.1.0-3_amd64.deb===>libyajl2_2.1.0-3+deb11u2_amd64.deb']

To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.