rpm package
opensuse/openssl-3&distro=openSUSE Leap 15.6
pkg:rpm/opensuse/openssl-3&distro=openSUSE%20Leap%2015.6
Vulnerabilities (22)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-31790 | Hig | 7.5 | < 3.1.4-150600.5.45.1 | 3.1.4-150600.5.45.1 | Apr 7, 2026 | Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the appli | |
| CVE-2026-31789 | Cri | 9.8 | < 3.1.4-150600.5.45.1 | 3.1.4-150600.5.45.1 | Apr 7, 2026 | Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior | |
| CVE-2026-28389 | Hig | 7.5 | < 3.1.4-150600.5.45.1 | 3.1.4-150600.5.45.1 | Apr 7, 2026 | Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resu | |
| CVE-2026-28388 | Hig | 7.5 | < 3.1.4-150600.5.45.1 | 3.1.4-150600.5.45.1 | Apr 7, 2026 | Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service f | |
| CVE-2026-28387 | Hig | 8.1 | < 3.1.4-150600.5.45.1 | 3.1.4-150600.5.45.1 | Apr 7, 2026 | Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of po | |
| CVE-2026-22796 | Med | 5.3 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data. Impact su | |
| CVE-2026-22795 | Med | 5.5 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file. Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denia | |
| CVE-2025-69421 | Hig | 7.5 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files. T | |
| CVE-2025-69420 | Hig | 7.5 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Imp | |
| CVE-2025-69419 | Hig | 7.4 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | 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 cau | |
| CVE-2025-69418 | Med | 4.0 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: When using the low-level OCB API directly with AES-NI orother hardware-accelerated code paths, inputs whose length is not a multipleof 16 bytes can leave the final partial block unencrypted and unauthenticated.Impact summary: The trailing 1-15 bytes | |
| CVE-2025-68160 | Med | 4.7 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of-bounds write can cause memory corruption which typically results in | |
| CVE-2025-15467 | Hig | 8.8 | < 3.1.4-150600.5.42.1 | 3.1.4-150600.5.42.1 | Jan 27, 2026 | Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When | |
| CVE-2025-9230 | Hig | 7.5 | < 3.1.4-150600.5.39.1 | 3.1.4-150600.5.39.1 | Sep 30, 2025 | Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds | |
| CVE-2025-27587 | Med | 5.3 | < 3.1.4-150600.5.27.1 | 3.1.4-150600.5.27.1 | Jun 16, 2025 | OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based | |
| CVE-2024-13176 | Med | 4.1 | < 3.1.4-150600.5.24.1 | 3.1.4-150600.5.24.1 | Jan 20, 2025 | Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measurin | |
| CVE-2024-4741 | Hig | 7.5 | < 3.1.4-150600.5.7.1 | 3.1.4-150600.5.7.1 | Nov 13, 2024 | Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of | |
| CVE-2024-6119 | Hig | 7.5 | < 3.1.4-150600.5.15.1 | 3.1.4-150600.5.15.1 | Sep 3, 2024 | Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process. Impact summary: Abnormal termination of an application can | |
| CVE-2024-41996 | Hig | 7.5 | < 3.1.4-150600.5.18.1 | 3.1.4-150600.5.18.1 | Aug 26, 2024 | Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause a | |
| CVE-2024-5535 | Cri | 9.1 | < 3.1.4-150600.5.10.1 | 3.1.4-150600.5.10.1 | Jun 27, 2024 | Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected appl |
- affected < 3.1.4-150600.5.45.1fixed 3.1.4-150600.5.45.1
Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the appli
- affected < 3.1.4-150600.5.45.1fixed 3.1.4-150600.5.45.1
Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior
- affected < 3.1.4-150600.5.45.1fixed 3.1.4-150600.5.45.1
Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resu
- affected < 3.1.4-150600.5.45.1fixed 3.1.4-150600.5.45.1
Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service f
- affected < 3.1.4-150600.5.45.1fixed 3.1.4-150600.5.45.1
Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of po
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data. Impact su
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file. Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denia
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files. T
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Imp
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
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 cau
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: When using the low-level OCB API directly with AES-NI orother hardware-accelerated code paths, inputs whose length is not a multipleof 16 bytes can leave the final partial block unencrypted and unauthenticated.Impact summary: The trailing 1-15 bytes
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of-bounds write can cause memory corruption which typically results in
- affected < 3.1.4-150600.5.42.1fixed 3.1.4-150600.5.42.1
Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When
- affected < 3.1.4-150600.5.39.1fixed 3.1.4-150600.5.39.1
Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds
- affected < 3.1.4-150600.5.27.1fixed 3.1.4-150600.5.27.1
OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based
- affected < 3.1.4-150600.5.24.1fixed 3.1.4-150600.5.24.1
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measurin
- affected < 3.1.4-150600.5.7.1fixed 3.1.4-150600.5.7.1
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of
- affected < 3.1.4-150600.5.15.1fixed 3.1.4-150600.5.15.1
Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process. Impact summary: Abnormal termination of an application can
- affected < 3.1.4-150600.5.18.1fixed 3.1.4-150600.5.18.1
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause a
- affected < 3.1.4-150600.5.10.1fixed 3.1.4-150600.5.10.1
Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected appl
Page 1 of 2