Threats Tagged 'cve-2024-1597'

Red Hat has released a security update for its build of Quarkus 2. 13. 9. SP2 addressing three vulnerabilities: CVE-2024-1597, CVE-2024-25710, and CVE-2024-26308. These issues include a SQL injection vulnerability in the PostgreSQL JDBC Driver when using PreferQueryMode=SIMPLE, a denial of service caused by an infinite loop processing corrupted DUMP files, and an OutOfMemoryError triggered by unpacking broken Pack200 files. The update includes fixes for these security flaws alongside other bug fixes and enhancements. Red Hat rates the security impact of this update as Important. Users are advised to apply this update after ensuring all previous errata are applied. No known exploits in the wild have been reported at this time.

Red Hat Integration Camel K 1. 10. 7 includes a security update addressing a vulnerability in the PostgreSQL JDBC Driver (pgjdbc). The vulnerability (CVE-2024-1597) allows an attacker to perform SQL injection when the driver is configured with PreferQueryMode=SIMPLE. This issue has been rated as important by Red Hat Product Security. The update fixes this vulnerability and is recommended to be applied after ensuring all previous relevant errata are installed.

This release of Red Hat Integration - Service Registry 2.5.11 GA includes the following security fixes. Security Fix(es): * commons-compress: Denial of service caused by an infinite loop for a corrupted DUMP file [rhint-serv-2] (CVE-2024-25710) * vert.x: io.vertx/vertx-core: memory leak due to the use of Netty FastThreadLocal data structures in Vertx [rhint-serv-2] (CVE-2024-1023) * vertx-core: io.vertx:vertx-core: memory leak when a TCP server is configured with TLS and SNI support [rhint-serv-2] (CVE-2024-1300) * commons-compress: OutOfMemoryError unpacking broken Pack200 file [rhint-serv-2] (CVE-2024-26308) * netty-codec-http: Allocation of Resources Without Limits or Throttling [rhint-serv-2] (CVE-2024-29025) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.