Out-of-bounds Write Affecting rsyslog package, versions <0:8.2102.0-7.el8_6.1
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-RSYSLOG-2809075
- published 6 May 2022
- disclosed 5 May 2022
Introduced: 5 May 2022
CVE-2022-24903 Open this link in a new tabHow to fix?
Upgrade Centos:8 rsyslog to version 0:8.2102.0-7.el8_6.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream rsyslog package and not the rsyslog package as distributed by Centos.
See How to fix? for Centos:8 relevant fixed versions and status.
Rsyslog is a rocket-fast system for log processing. Modules for TCP syslog reception have a potential heap buffer overflow when octet-counted framing is used. This can result in a segfault or some other malfunction. As of our understanding, this vulnerability can not be used for remote code execution. But there may still be a slight chance for experts to do that. The bug occurs when the octet count is read. While there is a check for the maximum number of octets, digits are written to a heap buffer even when the octet count is over the maximum, This can be used to overrun the memory buffer. However, once the sequence of digits stop, no additional characters can be added to the buffer. In our opinion, this makes remote exploits impossible or at least highly complex. Octet-counted framing is one of two potential framing modes. It is relatively uncommon, but enabled by default on receivers. Modules imtcp, imptcp, imgssapi, and imhttp are used for regular syslog message reception. It is best practice not to directly expose them to the public. When this practice is followed, the risk is considerably lower. Module imdiag is a diagnostics module primarily intended for testbench runs. We do not expect it to be present on any production installation. Octet-counted framing is not very common. Usually, it needs to be specifically enabled at senders. If users do not need it, they can turn it off for the most important modules. This will mitigate the vulnerability.
References
- https://access.redhat.com/security/cve/CVE-2022-24903
- https://access.redhat.com/errata/RHSA-2022:4799
- https://github.com/rsyslog/rsyslog/commit/f211042ecbb472f9d8beb4678a65d272b6f07705
- https://github.com/rsyslog/rsyslog/security/advisories/GHSA-ggw7-xr6h-mmr8
- https://lists.debian.org/debian-lts-announce/2022/05/msg00028.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMNNXLCU2UORRVSZO24HL4KMVPK5PHVW/
- https://security.netapp.com/advisory/ntap-20221111-0002/
- https://www.debian.org/security/2022/dsa-5150
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GMNNXLCU2UORRVSZO24HL4KMVPK5PHVW/