** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis up to 6.2.7/7.0.5. Affected is the function sigsegvHandler of the file debug.c of the component Crash Report. The manipulation leads to denial of service. The complexity of an attack is rather high. The exploitability is told to be difficult. The real existence of this vulnerability is still doubted at the moment. Upgrading to version 6.2.8 and 7.0.6 is able to address this issue. The patch is identified as 0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this issue. VDB-211962 is the identifier assigned to this vulnerability. NOTE: The vendor claims that this is not a DoS because it applies to the crash logging mechanism which is triggered after a crash has occurred.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:0037 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2022-24834:
    Redis is an in-memory database that persists on disk. A specially crafted Lua script executing in Redis     can trigger a heap overflow in the cjson library, and result with heap corruption and potentially remote     code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6,     and affects only authenticated and authorized users. The problem is fixed in versions 7.0.12, 6.2.13, and     6.0.20.

    CVE-2022-36021:
    Redis is an in-memory database that persists on disk. Authenticated users can use string matching commands     (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis,     causing it to hang and consume 100% CPU time. The problem is fixed in Redis versions 6.0.18, 6.2.11,     7.0.9.

    CVE-2022-3647:
    ** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis. Affected is the     function sigsegvHandler of the file debug.c of the component Crash Report. The manipulation leads to     denial of service. The real existence of this vulnerability is still doubted at the moment. The name of     the patch is 0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this     issue. VDB-211962 is the identifier assigned to this vulnerability. NOTE: The vendor claims that this is     not a DoS because it applies to the crash logging mechanism which is triggered after a crash has occurred.

    CVE-2023-25155:
    Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted     `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a     runtime assertion and termination of the Redis server process. This problem affects all Redis versions.
    Patches were released in Redis version(s) 6.0.18, 6.2.11 and 7.0.9.

    CVE-2023-28856:
    Redis is an open source, in-memory database that persists on disk. Authenticated users can use the     `HINCRBYFLOAT` command to create an invalid hash field that will crash Redis on access in affected     versions. This issue has been addressed in in versions 7.0.11, 6.2.12, and 6.0.19. Users are advised to     upgrade. There are no known workarounds for this issue.

    CVE-2023-36824:
    Redis is an in-memory database that persists on disk. In Redit 7.0 prior to 7.0.12, extracting key names     from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading     random heap memory, heap corruption and potentially remote code execution. Several scenarios that may lead     to authenticated users executing a specially crafted `COMMAND GETKEYS` or `COMMAND GETKEYSANDFLAGS`and     authenticated users who were set with ACL rules that match key names, executing a specially crafted     command that refers to a variadic list of key names. The vulnerability is patched in Redis 7.0.12.



    CVE-2023-41053:
    Redis is an in-memory database that persists on disk. Redis does not correctly identify keys accessed by     `SORT_RO` and as a result may grant users executing this command access to keys that are not explicitly     authorized by the ACL configuration. The problem exists in Redis 7.0 or newer and has been fixed in Redis     7.0.13 and 7.2.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

    CVE-2023-45145:
    Redis is an in-memory database that persists on disk. On startup, Redis begins listening on a Unix socket     before adjusting its permissions to the user-provided configuration. If a permissive umask(2) is used,     this creates a race condition that enables, during a short period of time, another process to establish an     otherwise unauthorized connection. This problem has existed since Redis 2.6.0-RC1. This issue has been     addressed in Redis versions 7.2.2, 7.0.14 and 6.2.14. Users are advised to upgrade. For users unable to     upgrade, it is possible to work around the problem by disabling Unix sockets, starting Redis with a     restrictive umask, or storing the Unix socket file in a protected directory.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - ** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis up to 6.2.7/7.0.5.
    Affected is the function sigsegvHandler of the file debug.c of the component Crash Report. The     manipulation leads to denial of service. The complexity of an attack is rather high. The exploitability is     told to be difficult. The real existence of this vulnerability is still doubted at the moment. Upgrading     to version 6.2.8 and 7.0.6 is able to address this issue. The patch is identified as     0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this issue. VDB-211962     is the identifier assigned to this vulnerability. NOTE: The vendor claims that this is not a DoS because     it applies to the crash logging mechanism which is triggered after a crash has occurred. (CVE-2022-3647)

Note that Nessus relies on the presence of the package as reported by the vendor.

An update of the redis package has been released.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - ** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis up to 6.2.7/7.0.5.
    Affected is the function sigsegvHandler of the file debug.c of the component Crash Report. The
    manipulation leads to denial of service. The complexity of an attack is rather high. The exploitability is
    told to be difficult. The real existence of this vulnerability is still doubted at the moment. Upgrading
    to version 6.2.8 and 7.0.6 is able to address this issue. The patch is identified as
    0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this issue. VDB-211962
    is the identifier assigned to this vulnerability. NOTE: The vendor claims that this is not a DoS because
    it applies to the crash logging mechanism which is triggered after a crash has occurred. (CVE-2022-3647)

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-154 advisory.

    Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted     `SETRANGE` and `SORT(_RO)` commands can trigger an integer overflow, resulting with Redis attempting to     allocate impossible amounts of memory and abort with an out-of-memory (OOM) panic. The problem is fixed in     Redis versions 7.0.8, 6.2.9 and 6.0.17. Users are advised to upgrade. There are no known workarounds for     this vulnerability. (CVE-2022-35977)

    Redis is an in-memory database that persists on disk. Authenticated users can use string matching commands     (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis,     causing it to hang and consume 100% CPU time. The problem is fixed in Redis versions 6.0.18, 6.2.11,     7.0.9. (CVE-2022-36021)

    ** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis. Affected is the     function sigsegvHandler of the file debug.c of the component Crash Report. The manipulation leads to     denial of service. The real existence of this vulnerability is still doubted at the moment. The name of     the patch is 0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this     issue. VDB-211962 is the identifier assigned to this vulnerability. NOTE: The vendor claims that this is     not a DoS because it applies to the crash logging mechanism which is triggered after a crash has occurred.
    (CVE-2022-3647)

    Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted     `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a     runtime assertion and termination of the Redis server process. This problem affects all Redis versions.
    Patches were released in Redis version(s) 6.0.18, 6.2.11 and 7.0.9. (CVE-2023-25155)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2022:4168-1 advisory.

    - CVE-2022-3647: Fixed crash in sigsegvHandler debug function (bsc#1204633).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2022:4169-1 advisory.

    - CVE-2022-3647: Fixed crash in sigsegvHandler debug function (bsc#1204633).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
239773	TencentOS Server 4: redis (TSSA-2024:0037)	Nessus	Tencent Local Security Checks	high
224843	Linux Distros Unpatched Vulnerability : CVE-2022-3647	Nessus	Misc.	low
204157	Photon OS 5.0: Redis PHSA-2023-5.0-0175	Nessus	PhotonOS Local Security Checks	low
203379	Photon OS 4.0: Redis PHSA-2022-4.0-0276	Nessus	PhotonOS Local Security Checks	low
406926	Alpine: multiple redis packages: security update to 7.0.7-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	low
406926	Alpine: multiple redis packages: security update to 7.0.7-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	low
406925	Alpine: multiple redis packages: security update to 7.0.6-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	low
406925	Alpine: multiple redis packages: security update to 7.0.6-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	low
173858	Amazon Linux 2023 : redis6, redis6-devel (ALAS2023-2023-154)	Nessus	Amazon Linux Local Security Checks	medium
168143	SUSE SLES15 / openSUSE 15 Security Update : redis (SUSE-SU-2022:4168-1)	Nessus	SuSE Local Security Checks	low
168142	SUSE SLES15 / openSUSE 15 Security Update : redis (SUSE-SU-2022:4169-1)	Nessus	SuSE Local Security Checks	low

Detections

Analytics

CVE-2022-3647

low

Tenable Plugins

high

low

low

low

low

low

low

low

medium

low

low