Marc Schönefeld

**Name of the Vulnerable Software and Affected Versions** Node.js versions v16, v18, and v20 **Description** The issue is related to insufficient input validation in the crypto.X509Certificate() function. When an invalid public key is used to create an x509 certificate, a non-expected termination occurs, making it susceptible to DoS attacks. This happens because the process terminates when accessing public key information from user code, causing the current user context to be lost and leading to a DoS scenario. The vulnerability can be exploited by a remote attacker to cause a denial of service. **Recommendations** For Node.js versions v16, v18, and v20, update to a version that includes a fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** OpenSSL (affected versions not specified) **Description** An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the `d2i PKCS7()`, `d2i PKCS7 bio()`, or `d2i PKCS7 fp()` functions. The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function; however, third-party applications might call these functions on untrusted data. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** OpenSSL (affected versions not specified) **Description** The function PEM read bio ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the `name out`, `header` and `data` arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM read bio ex() will return a failure code but will populate the `header` argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM read bio() and PEM read() are simple wrappers around PEM read bio ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM X509 INFO read bio ex() and SSL CTX use serverinfo file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the `header` argument if PEM read bio ex() returns a failure code. These locations include the PEM read bio TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** libgimpprint versions (affected versions not specified) libgimpprint-devel versions (affected versions not specified) libgimpprint-debuginfo versions (affected versions not specified) **Description** The issue is related to the exploitation of a vulnerability in the libgimpprint package, which can lead to a disruption of confidentiality, integrity, and availability of protected information. This vulnerability can be exploited remotely. Additionally, there are multiple integer underflows in the icmLut allocate function in the International Color Consortium (ICC) Format library, which can cause a denial of service and possibly execute arbitrary code via crafted PostScript or PDF files with embedded images. **Recommendations** For libgimpprint, consider disabling the vulnerable package until a patch is available. For libgimpprint-devel, restrict access to the vulnerable package to minimize the risk of exploitation. For libgimpprint-debuginfo, avoid using the package until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.