rpm package
suse/pcre2&distro=SUSE Linux Enterprise Module for Basesystem 15 SP4
pkg:rpm/suse/pcre2&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP4
Vulnerabilities (3)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-41409 | — | < 10.39-150400.4.9.1 | 10.39-150400.4.9.1 | Jul 18, 2023 | Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input. | ||
| CVE-2022-1587 | — | < 10.39-150400.4.6.1 | 10.39-150400.4.6.1 | May 16, 2022 | An out-of-bounds read vulnerability was discovered in the PCRE2 library in the get_recurse_data_length() function of the pcre2_jit_compile.c file. This issue affects recursions in JIT-compiled regular expressions caused by duplicate data transfers. | ||
| CVE-2022-1586 | — | < 10.39-150400.4.3.1 | 10.39-150400.4.3.1 | May 16, 2022 | An out-of-bounds read vulnerability was discovered in the PCRE2 library in the compile_xclass_matchingpath() function of the pcre2_jit_compile.c file. This involves a unicode property matching issue in JIT-compiled regular expressions. The issue occurs because the character was n |
- CVE-2022-41409Jul 18, 2023affected < 10.39-150400.4.9.1fixed 10.39-150400.4.9.1
Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
- CVE-2022-1587May 16, 2022affected < 10.39-150400.4.6.1fixed 10.39-150400.4.6.1
An out-of-bounds read vulnerability was discovered in the PCRE2 library in the get_recurse_data_length() function of the pcre2_jit_compile.c file. This issue affects recursions in JIT-compiled regular expressions caused by duplicate data transfers.
- CVE-2022-1586May 16, 2022affected < 10.39-150400.4.3.1fixed 10.39-150400.4.3.1
An out-of-bounds read vulnerability was discovered in the PCRE2 library in the compile_xclass_matchingpath() function of the pcre2_jit_compile.c file. This involves a unicode property matching issue in JIT-compiled regular expressions. The issue occurs because the character was n