Количество 28
Количество 28
CVE-2025-69419
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, caus...
CVE-2025-69419
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, caus...
CVE-2025-69419
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causi
CVE-2025-69419
Issue summary: Calling PKCS12_get_friendlyname() function on a malicio ...
RLSA-2026:4472
Moderate: compat-openssl11 security update
GHSA-x77r-97gw-wh89
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, ca...
ELSA-2026-50131
ELSA-2026-50131: openssl security update (MODERATE)
ELSA-2026-4472
ELSA-2026-4472: compat-openssl11 security update (MODERATE)
ELSA-2026-3042
ELSA-2026-3042: openssl security update (MODERATE)
BDU:2026-01217
Уязвимость функции PKCS12_get_friendlyname() библиотеки OpenSSL, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2026-01219
Уязвимость функции TS_RESP_verify_response() библиотеки OpenSSL, позволяющая нарушителю вызвать отказ в обслуживании
SUSE-SU-2026:0360-1
Security update for openssl-1_1
SUSE-SU-2026:0359-1
Security update for openssl-1_1
SUSE-SU-2026:0358-1
Security update for openssl-1_1
SUSE-SU-2026:0346-1
Security update for openssl-1_1
SUSE-SU-2026:0331-1
Security update for openssl-1_1
SUSE-SU-2026:0312-1
Security update for openssl-3
SUSE-SU-2026:0311-1
Security update for openssl-3
SUSE-SU-2026:0310-1
Security update for openssl-3
SUSE-SU-2026:0309-1
Security update for openssl-3
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-69419 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, caus... | CVSS3: 7.4 | 0% Низкий | около 2 месяцев назад | |
CVE-2025-69419 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, caus... | CVSS3: 7.4 | 0% Низкий | около 2 месяцев назад | |
CVE-2025-69419 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causi | CVSS3: 7.4 | 0% Низкий | около 2 месяцев назад | |
CVE-2025-69419 Issue summary: Calling PKCS12_get_friendlyname() function on a malicio ... | CVSS3: 7.4 | 0% Низкий | около 2 месяцев назад | |
RLSA-2026:4472 Moderate: compat-openssl11 security update | 0% Низкий | 14 дней назад | ||
GHSA-x77r-97gw-wh89 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, ca... | CVSS3: 7.4 | 0% Низкий | около 2 месяцев назад | |
ELSA-2026-50131 ELSA-2026-50131: openssl security update (MODERATE) | 28 дней назад | |||
ELSA-2026-4472 ELSA-2026-4472: compat-openssl11 security update (MODERATE) | 14 дней назад | |||
ELSA-2026-3042 ELSA-2026-3042: openssl security update (MODERATE) | около 1 месяца назад | |||
BDU:2026-01217 Уязвимость функции PKCS12_get_friendlyname() библиотеки OpenSSL, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.4 | 0% Низкий | 3 месяца назад | |
BDU:2026-01219 Уязвимость функции TS_RESP_verify_response() библиотеки OpenSSL, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.5 | 0% Низкий | 3 месяца назад | |
SUSE-SU-2026:0360-1 Security update for openssl-1_1 | около 2 месяцев назад | |||
SUSE-SU-2026:0359-1 Security update for openssl-1_1 | около 2 месяцев назад | |||
SUSE-SU-2026:0358-1 Security update for openssl-1_1 | около 2 месяцев назад | |||
SUSE-SU-2026:0346-1 Security update for openssl-1_1 | около 2 месяцев назад | |||
SUSE-SU-2026:0331-1 Security update for openssl-1_1 | около 2 месяцев назад | |||
SUSE-SU-2026:0312-1 Security update for openssl-3 | около 2 месяцев назад | |||
SUSE-SU-2026:0311-1 Security update for openssl-3 | около 2 месяцев назад | |||
SUSE-SU-2026:0310-1 Security update for openssl-3 | около 2 месяцев назад | |||
SUSE-SU-2026:0309-1 Security update for openssl-3 | около 2 месяцев назад |
Уязвимостей на страницу