486 lines
32 KiB
JSON
486 lines
32 KiB
JSON
{
|
||
"Definition": [
|
||
{
|
||
"ID": "oval:org.altlinux.errata:def:20234109",
|
||
"Version": "oval:org.altlinux.errata:def:20234109",
|
||
"Class": "patch",
|
||
"Metadata": {
|
||
"Title": "ALT-PU-2023-4109: package `redis` update to version 6.2.8-alt1",
|
||
"AffectedList": [
|
||
{
|
||
"Family": "unix",
|
||
"Platforms": [
|
||
"ALT Linux branch c9f2"
|
||
],
|
||
"Products": [
|
||
"ALT SPWorkstation",
|
||
"ALT SPServer"
|
||
]
|
||
}
|
||
],
|
||
"References": [
|
||
{
|
||
"RefID": "ALT-PU-2023-4109",
|
||
"RefURL": "https://errata.altlinux.org/ALT-PU-2023-4109",
|
||
"Source": "ALTPU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-00559",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-00559",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-04030",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-04030",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-04962",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-04962",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-04966",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-04966",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-04969",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-04969",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-05031",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-05031",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-05037",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-05037",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-02940",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-02940",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-02945",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-02945",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2023-02181",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2023-02181",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2023-02305",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2023-02305",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2023-02353",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2023-02353",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2023-02451",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2023-02451",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2023-03483",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2023-03483",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "CVE-2015-8080",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2015-8080",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2020-14147",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2020-14147",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-21309",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-21309",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32626",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32626",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32627",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32627",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32628",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32628",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32672",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32672",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32675",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32675",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32687",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32687",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32761",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32761",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32762",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32762",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-3470",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-3470",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-41099",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-41099",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-24735",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-24735",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2022-24736",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2022-24736",
|
||
"Source": "CVE"
|
||
}
|
||
],
|
||
"Description": "This update upgrades redis to version 6.2.8-alt1. \nSecurity Fix(es):\n\n * BDU:2021-00559: Уязвимость реализации функции getnum() резидентной системы управления базами данных класса NoSQL Redis, позволяющая нарушителю вызвать отказ в обслуживании или выполнить произвольный код\n\n * BDU:2021-04030: Уязвимость параметра конфигурации proto-max-bulk-len системы управления базами данных (СУБД) Redis, позволяющая нарушителю выполнить произвольный код\n\n * BDU:2021-04962: Уязвимость сервера системы управления базами данных (СУБД) Redis, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2021-04966: Уязвимость параметров конфигурации proto-max-bulk-len и client-query-buffer-limit системы управления базами данных (СУБД) Redis, позволяющая нарушителю выполнить произвольный код\n\n * BDU:2021-04969: Уязвимость структуры данных ziplist системы управления базами данных (СУБД) Redis, позволяющая нарушителю выполнить произвольный код\n\n * BDU:2021-05031: Уязвимость интерпретатора скриптов Lua системы управления базами данных Redis. позволяющая нарушителю выполнить произвольный код\n\n * BDU:2021-05037: Уязвимость параметра конфигурации set-max-intset-entries системы управления базами данных (СУБД) Redis, позволяющая нарушителю выполнить произвольный код\n\n * BDU:2022-02940: Уязвимость системы управления базами данных Redis, связанная с ошибками разыменования указателей, позволяющая нарушителю вызвать отказ в обслуживании\n\n * BDU:2022-02945: Уязвимость системы управления базами данных Redis, позволяющая нарушителю выполнить произвольный код\n\n * BDU:2023-02181: Уязвимость системы управления базами данных NoSQL Redis, связанная с целочисленным переполнением, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании\n\n * BDU:2023-02305: Уязвимость библиотеки hiredis системы управления базами данных NoSQL Redis, связанная с целочисленным переполнением, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании\n\n * BDU:2023-02353: Уязвимость системы управления базами данных NoSQL Redis, связанная с целочисленным переполнением, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании\n\n * BDU:2023-02451: Уязвимость системы управления базами данных NoSQL Redis, связанная с чтением за границами буфера, позволяющая нарушителю получить доступ к конфиденциальным данным\n\n * BDU:2023-03483: Уязвимость функции maloc системы управления базами данных (СУБД) Redis, позволяющая нарушителю вызвать отказ в обслуживании\n\n * CVE-2015-8080: Integer overflow in the getnum function in lua_struct.c in Redis 2.8.x before 2.8.24 and 3.0.x before 3.0.6 allows context-dependent attackers with permission to run Lua code in a Redis session to cause a denial of service (memory corruption and application crash) or possibly bypass intended sandbox restrictions via a large number, which triggers a stack-based buffer overflow.\n\n * CVE-2020-14147: An integer overflow in the getnum function in lua_struct.c in Redis before 6.0.3 allows context-dependent attackers with permission to run Lua code in a Redis session to cause a denial of service (memory corruption and application crash) or possibly bypass intended sandbox restrictions via a large number, which triggers a stack-based buffer overflow. NOTE: this issue exists because of a CVE-2015-8080 regression.\n\n * CVE-2021-21309: Redis is an open-source, in-memory database that persists on disk. In affected versions of Redis an integer overflow bug in 32-bit Redis version 4.0 or newer could be exploited to corrupt the heap and potentially result with remote code execution. Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. We believe this could in certain conditions be exploited for remote code execution. By default, authenticated Redis users have access to all configuration parameters and can therefore use the “CONFIG SET proto-max-bulk-len” to change the safe default, making the system vulnerable. **This problem only affects 32-bit Redis (on a 32-bit system, or as a 32-bit executable running on a 64-bit system).** The problem is fixed in version 6.2, and the fix is back ported to 6.0.11 and 5.0.11. Make sure you use one of these versions if you are running 32-bit Redis. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent clients from directly executing `CONFIG SET`: Using Redis 6.0 or newer, ACL configuration can be used to block the command. Using older versions, the `rename-command` configuration directive can be used to rename the command to a random string unknown to users, rendering it inaccessible. Please note that this workaround may have an additional impact on users or operational systems that expect `CONFIG SET` to behave in certain ways.\n\n * CVE-2021-32626: Redis is an open source, in-memory database that persists on disk. In affected versions specially crafted Lua scripts executing in Redis can cause the heap-based Lua stack to be overflowed, due to incomplete checks for this condition. This can result with heap corruption and potentially remote code execution. This problem exists in all versions of Redis with Lua scripting support, starting from 2.6. The problem is fixed in versions 6.2.6, 6.0.16 and 5.0.14. For users unable to update an additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.\n\n * CVE-2021-32627: Redis is an open source, in-memory database that persists on disk. In affected versions an integer overflow bug in Redis can be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves changing the default proto-max-bulk-len and client-query-buffer-limit configuration parameters to very large values and constructing specially crafted very large stream elements. The problem is fixed in Redis 6.2.6, 6.0.16 and 5.0.14. For users unable to upgrade an additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the proto-max-bulk-len configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.\n\n * CVE-2021-32628: Redis is an open source, in-memory database that persists on disk. An integer overflow bug in the ziplist data structure used by all versions of Redis can be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves modifying the default ziplist configuration parameters (hash-max-ziplist-entries, hash-max-ziplist-value, zset-max-ziplist-entries or zset-max-ziplist-value) to a very large value, and then constructing specially crafted commands to create very large ziplists. The problem is fixed in Redis versions 6.2.6, 6.0.16, 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the above configuration parameters. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.\n\n * CVE-2021-32672: Redis is an open source, in-memory database that persists on disk. When using the Redis Lua Debugger, users can send malformed requests that cause the debugger’s protocol parser to read data beyond the actual buffer. This issue affects all versions of Redis with Lua debugging support (3.2 or newer). The problem is fixed in versions 6.2.6, 6.0.16 and 5.0.14.\n\n * CVE-2021-32675: Redis is an open source, in-memory database that persists on disk. When parsing an incoming Redis Standard Protocol (RESP) request, Redis allocates memory according to user-specified values which determine the number of elements (in the multi-bulk header) and size of each element (in the bulk header). An attacker delivering specially crafted requests over multiple connections can cause the server to allocate significant amount of memory. Because the same parsing mechanism is used to handle authentication requests, this vulnerability can also be exploited by unauthenticated users. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate this problem without patching the redis-server executable is to block access to prevent unauthenticated users from connecting to Redis. This can be done in different ways: Using network access control tools like firewalls, iptables, security groups, etc. or Enabling TLS and requiring users to authenticate using client side certificates.\n\n * CVE-2021-32687: Redis is an open source, in-memory database that persists on disk. An integer overflow bug affecting all versions of Redis can be exploited to corrupt the heap and potentially be used to leak arbitrary contents of the heap or trigger remote code execution. The vulnerability involves changing the default set-max-intset-entries configuration parameter to a very large value and constructing specially crafted commands to manipulate sets. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the set-max-intset-entries configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.\n\n * CVE-2021-32761: Redis is an in-memory database that persists on disk. A vulnerability involving out-of-bounds read and integer overflow to buffer overflow exists starting with version 2.2 and prior to versions 5.0.13, 6.0.15, and 6.2.5. On 32-bit systems, Redis `*BIT*` command are vulnerable to integer overflow that can potentially be exploited to corrupt the heap, leak arbitrary heap contents or trigger remote code execution. The vulnerability involves changing the default `proto-max-bulk-len` configuration parameter to a very large value and constructing specially crafted commands bit commands. This problem only affects Redis on 32-bit platforms, or compiled as a 32-bit binary. Redis versions 5.0.`3m 6.0.15, and 6.2.5 contain patches for this issue. An additional workaround to mitigate the problem without patching the `redis-server` executable is to prevent users from modifying the `proto-max-bulk-len` configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.\n\n * CVE-2021-32762: Redis is an open source, in-memory database that persists on disk. The redis-cli command line tool and redis-sentinel service may be vulnerable to integer overflow when parsing specially crafted large multi-bulk network replies. This is a result of a vulnerability in the underlying hiredis library which does not perform an overflow check before calling the calloc() heap allocation function. This issue only impacts systems with heap allocators that do not perform their own overflow checks. Most modern systems do and are therefore not likely to be affected. Furthermore, by default redis-sentinel uses the jemalloc allocator which is also not vulnerable. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14.\n\n * CVE-2021-3470: A heap overflow issue was found in Redis in versions before 5.0.10, before 6.0.9 and before 6.2.0 when using a heap allocator other than jemalloc or glibc's malloc, leading to potential out of bound write or process crash. Effectively this flaw does not affect the vast majority of users, who use jemalloc or glibc malloc.\n\n * CVE-2021-41099: Redis is an open source, in-memory database that persists on disk. An integer overflow bug in the underlying string library can be used to corrupt the heap and potentially result with denial of service or remote code execution. The vulnerability involves changing the default proto-max-bulk-len configuration parameter to a very large value and constructing specially crafted network payloads or commands. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from modifying the proto-max-bulk-len configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.\n\n * CVE-2022-24735: Redis is an in-memory database that persists on disk. By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis prior to version 7.0.0 or 6.2.7 can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. The Lua script execution environment in Redis provides some measures that prevent a script from creating side effects that persist and can affect the execution of the same, or different script, at a later time. Several weaknesses of these measures have been publicly known for a long time, but they had no security impact as the Redis security model did not endorse the concept of users or privileges. With the introduction of ACLs in Redis 6.0, these weaknesses can be exploited by a less privileged users to inject Lua code that will execute at a later time, when a privileged user executes a Lua script. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.\n\n * CVE-2022-24736: Redis is an in-memory database that persists on disk. Prior to versions 6.2.7 and 7.0.0, an attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result with a crash of the redis-server process. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.\n\n * #40279: Прошу собрать версию 6.2.4",
|
||
"Advisory": {
|
||
"From": "errata.altlinux.org",
|
||
"Severity": "High",
|
||
"Rights": "Copyright 2024 BaseALT Ltd.",
|
||
"Issued": {
|
||
"Date": "2023-07-07"
|
||
},
|
||
"Updated": {
|
||
"Date": "2023-07-07"
|
||
},
|
||
"BDUs": [
|
||
{
|
||
"ID": "BDU:2021-00559",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:N/I:N/A:C",
|
||
"CVSS3": "AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-00559",
|
||
"Impact": "High",
|
||
"Public": "20200719"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-04030",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-125, CWE-190, CWE-680",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-04030",
|
||
"Impact": "High",
|
||
"Public": "20210721"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-04962",
|
||
"CVSS": "AV:N/AC:L/Au:N/C:N/I:N/A:C",
|
||
"CVSS3": "AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
|
||
"CWE": "CWE-770",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-04962",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-04966",
|
||
"CVSS": "AV:N/AC:H/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190, CWE-680",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-04966",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-04969",
|
||
"CVSS": "AV:N/AC:H/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190, CWE-680",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-04969",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-05031",
|
||
"CVSS": "AV:N/AC:H/Au:N/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-122, CWE-787",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-05031",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-05037",
|
||
"CVSS": "AV:N/AC:H/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190, CWE-680",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-05037",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2022-02940",
|
||
"CVSS": "AV:L/AC:L/Au:S/C:N/I:N/A:P",
|
||
"CVSS3": "AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
|
||
"CWE": "CWE-476",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-02940",
|
||
"Impact": "Low",
|
||
"Public": "20220427"
|
||
},
|
||
{
|
||
"ID": "BDU:2022-02945",
|
||
"CVSS": "AV:L/AC:L/Au:S/C:P/I:P/A:N",
|
||
"CVSS3": "AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N",
|
||
"CWE": "CWE-74, CWE-94",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-02945",
|
||
"Impact": "Low",
|
||
"Public": "20220210"
|
||
},
|
||
{
|
||
"ID": "BDU:2023-02181",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://bdu.fstec.ru/vul/2023-02181",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2023-02305",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://bdu.fstec.ru/vul/2023-02305",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2023-02353",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://bdu.fstec.ru/vul/2023-02353",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2023-02451",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:P/I:N/A:N",
|
||
"CVSS3": "AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
|
||
"CWE": "CWE-125",
|
||
"Href": "https://bdu.fstec.ru/vul/2023-02451",
|
||
"Impact": "Low",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2023-03483",
|
||
"CVSS": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
|
||
"CVSS3": "AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
|
||
"CWE": "CWE-119",
|
||
"Href": "https://bdu.fstec.ru/vul/2023-03483",
|
||
"Impact": "Low",
|
||
"Public": "20210331"
|
||
}
|
||
],
|
||
"CVEs": [
|
||
{
|
||
"ID": "CVE-2015-8080",
|
||
"CVSS": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2015-8080",
|
||
"Impact": "High",
|
||
"Public": "20160413"
|
||
},
|
||
{
|
||
"ID": "CVE-2020-14147",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
|
||
"CWE": "CWE-787",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2020-14147",
|
||
"Impact": "High",
|
||
"Public": "20200615"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-21309",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-21309",
|
||
"Impact": "High",
|
||
"Public": "20210226"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32626",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-787",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32626",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32627",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32627",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32628",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32628",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32672",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:P/I:N/A:N",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
|
||
"CWE": "CWE-125",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32672",
|
||
"Impact": "Low",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32675",
|
||
"CVSS": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
|
||
"CWE": "CWE-770",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32675",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32687",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32687",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32761",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-125",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32761",
|
||
"Impact": "High",
|
||
"Public": "20210721"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32762",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32762",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-3470",
|
||
"CVSS": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
|
||
"CWE": "CWE-787",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-3470",
|
||
"Impact": "Low",
|
||
"Public": "20210331"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-41099",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-190",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-41099",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2022-24735",
|
||
"CVSS": "AV:N/AC:M/Au:N/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-94",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-24735",
|
||
"Impact": "High",
|
||
"Public": "20220427"
|
||
},
|
||
{
|
||
"ID": "CVE-2022-24736",
|
||
"CVSS": "AV:L/AC:L/Au:N/C:N/I:N/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
||
"CWE": "CWE-476",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2022-24736",
|
||
"Impact": "Low",
|
||
"Public": "20220427"
|
||
}
|
||
],
|
||
"Bugzilla": [
|
||
{
|
||
"ID": "40279",
|
||
"Href": "https://bugzilla.altlinux.org/40279",
|
||
"Data": "Прошу собрать версию 6.2.4"
|
||
}
|
||
],
|
||
"AffectedCPEs": {
|
||
"CPEs": [
|
||
"cpe:/o:alt:spworkstation:8.4",
|
||
"cpe:/o:alt:spserver:8.4"
|
||
]
|
||
}
|
||
}
|
||
},
|
||
"Criteria": {
|
||
"Operator": "AND",
|
||
"Criterions": [
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:3001",
|
||
"Comment": "ALT Linux must be installed"
|
||
}
|
||
],
|
||
"Criterias": [
|
||
{
|
||
"Operator": "OR",
|
||
"Criterions": [
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20234109001",
|
||
"Comment": "redis is earlier than 0:6.2.8-alt1"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
}
|
||
]
|
||
} |