RHSA-2019:1543HighCVSS 8.8

Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.29 SP2 security update

Published
June 18, 2019
Last Modified
October 14, 2026

🔗 CVE IDs covered (16)

📋 Description

CVE-2018-0495 — ROHNP: Key Extraction Side Channel in Multiple Crypto Libraries CVE-2018-0732 — openssl: Malicious server can send large prime to client during DH(E) TLS handshake causing the client to hang CVE-2018-14404 — libxml2: NULL pointer dereference in xmlXPathCompOpEval() function in xpath.c CVE-2018-16839 — curl: Integer overflow leading to heap-based buffer overflow in Curl_sasl_create_plain_message() CVE-2018-16840 — curl: Use-after-free when closing "easy" handle in Curl_close() CVE-2018-16842 — curl: Heap-based buffer over-read in the curl tool warning formatting CVE-2018-16890 — curl: NTLM type-2 heap out-of-bounds buffer read CVE-2018-1000005 — curl: Out-of-bounds read in code handling HTTP/2 trailers CVE-2018-1000007 — curl: HTTP authentication leak in redirects CVE-2018-1000120 — curl: FTP path trickery leads to NIL byte out of bounds write CVE-2018-1000121 — curl: LDAP NULL pointer dereference CVE-2018-1000122 — curl: RTSP RTP buffer over-read CVE-2019-0211 — httpd: privilege escalation from modules scripts CVE-2019-3822 — curl: NTLMv2 type-3 header stack buffer overflow CVE-2019-3823 — curl: SMTP end-of-response out-of-bounds read CVE-2019-5436 — curl: TFTP receive heap buffer overflow in tftp_receive_packet() function

🎯 Affected products1

  • JBoss Core Services Apache HTTP Server 2.4.29 SP2

✅ Remediation

The References section of this erratum contains a download link (you must log in to download the update). Before applying the update, back up your existing Red Hat JBoss Core Services installation (including all applications and configuration files). Workaround: Turn off NTLM authentication. Workaround: By default, curl and libcurl will not follow redirect requests. This flaw happens only when curl or libcurl are explicitly requested to follow redirects (option --location in curl, and CURLOPT_FOLLOWLOCATION in libcurl). To mitigate this, it is possible to prevent the automated following of redirects, replacing it by manual redirects (and remove the authentication header), for example. Workaround: Preventing application from using non-default CURLOPT_FTP_FILEMETHOD will avoid triggering the vulnerable code. Workaround: Do not use SMTP authentication with curl

🔗 References (14)