Medium [CVE-2018-0732] Client DoS due to large DH parameter
This medium-severity Red Hat Linux advisory covers CVE-2018-0732 affecting JBoss Core Services Apache HTTP Server 2.4.29 SP2, JBoss Core Services on RHEL 6, JBoss Core Services on RHEL 7.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished.
This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h).
Red Hat severity: Moderate — CVSS 4.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L). Weakness: CWE-325.
Affected Red Hat products: JBoss Core Services Apache HTTP Server 2.4.29 SP2; JBoss Core Services on RHEL 6; JBoss Core Services on RHEL 7; Red Hat Enterprise Linux 7; Red Hat OpenShift Application Runtimes Node.js 10; Red Hat OpenShift Application Runtimes Node.js 8; Red Hat Enterprise Linux 5; Red Hat Enterprise Linux 6; Red Hat JBoss Enterprise Application Platform 5; Red Hat JBoss Enterprise Application Platform 6; Red Hat JBoss Enterprise Web Server 2; Red Hat JBoss Web Server 3.
Red Hat lists Red Hat Enterprise Linux 8 as not affected. Will not fix / out of support: Red Hat Enterprise Linux 5; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat JBoss Enterprise Application Platform 5; Red Hat JBoss Enterprise Application Platform 6; Red Hat JBoss Enterprise Web Server 2.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
- 1.1.0-1
- 1.0.2-1
- openssl
- jbcs-httpd24-httpd-0:2.4.29-40.jbcs.el6
- jbcs-httpd24-openssl-1:1.0.2n-15.jbcs.el6
- jbcs-httpd24-httpd-0:2.4.29-40.jbcs.el7
- jbcs-httpd24-openssl-1:1.0.2n-15.jbcs.el7
- openssl-1:1.0.2k-16.el7
- rhoar-nodejs-1:10.9.0-1.el7
- rhoar-nodejs-1:8.11.4-2.el7
- RHSA-2019:1296
- RHSA-2019:1543
- RHSA-2019:1297
- RHSA-2018:3221
- RHSA-2018:2553
- RHSA-2018:2552
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
Mitigation
Upgrade to a fixed release: 1.1.0-1, 1.0.2-1, openssl, jbcs-httpd24-httpd-0:2.4.29-40.jbcs.el6, jbcs-httpd24-openssl-1:1.0.2n-15.jbcs.el6, jbcs-httpd24-httpd-0:2.4.29-40.jbcs.el7. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 6 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.