An update for rubygem-yajl-ruby is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3 and openEuler-22.03-LTS Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2022-1752 Final 1.0 1.0 2022-07-15 Initial 2022-07-15 2022-07-15 openEuler SA Tool V1.0 2022-07-15 rubygem-yajl-ruby security update An update for rubygem-yajl-ruby is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3 and openEuler-22.03-LTS. 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) An update for rubygem-yajl-ruby is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3 and openEuler-22.03-LTS. openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. High rubygem-yajl-ruby https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1752 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2022-24795 https://nvd.nist.gov/vuln/detail/CVE-2022-24795 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-22.03-LTS rubygem-yajl-ruby-debugsource-1.4.3-1.oe1.aarch64.rpm rubygem-yajl-ruby-1.4.3-1.oe1.aarch64.rpm rubygem-yajl-ruby-debuginfo-1.4.3-1.oe1.aarch64.rpm rubygem-yajl-ruby-1.4.3-1.oe1.aarch64.rpm rubygem-yajl-ruby-debuginfo-1.4.3-1.oe1.aarch64.rpm rubygem-yajl-ruby-debugsource-1.4.3-1.oe1.aarch64.rpm rubygem-yajl-ruby-1.4.3-1.oe2203.aarch64.rpm rubygem-yajl-ruby-debuginfo-1.4.3-1.oe2203.aarch64.rpm rubygem-yajl-ruby-debugsource-1.4.3-1.oe2203.aarch64.rpm rubygem-yajl-ruby-help-1.4.3-1.oe1.noarch.rpm rubygem-yajl-ruby-help-1.4.3-1.oe1.noarch.rpm rubygem-yajl-ruby-help-1.4.3-1.oe2203.noarch.rpm rubygem-yajl-ruby-1.4.3-1.oe1.src.rpm rubygem-yajl-ruby-1.4.3-1.oe1.src.rpm rubygem-yajl-ruby-1.4.3-1.oe2203.src.rpm rubygem-yajl-ruby-debuginfo-1.4.3-1.oe1.x86_64.rpm rubygem-yajl-ruby-debugsource-1.4.3-1.oe1.x86_64.rpm rubygem-yajl-ruby-1.4.3-1.oe1.x86_64.rpm rubygem-yajl-ruby-debugsource-1.4.3-1.oe1.x86_64.rpm rubygem-yajl-ruby-1.4.3-1.oe1.x86_64.rpm rubygem-yajl-ruby-debuginfo-1.4.3-1.oe1.x86_64.rpm rubygem-yajl-ruby-debugsource-1.4.3-1.oe2203.x86_64.rpm rubygem-yajl-ruby-1.4.3-1.oe2203.x86_64.rpm rubygem-yajl-ruby-debuginfo-1.4.3-1.oe2203.x86_64.rpm 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. 2022-07-15 CVE-2022-24795 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-22.03-LTS High 7.5 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H rubygem-yajl-ruby security update 2022-07-15 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1752