CVE-2017-3730: Bad (EC)DHE parameters cause a client crash
Published May 4, 2017
·Updated
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash. This could be exploited in a Denial of Service attack.
Affected Software
18 affected components
OpenSSL OpenSSL=1.1.0
OpenSSL OpenSSL=1.1.0a
OpenSSL OpenSSL=1.1.0b
OpenSSL OpenSSL=1.1.0c
Oracle Agile Engineering Data Management=6.1.3
Oracle Agile Engineering Data Management=6.2.0
Oracle Communications Application Session Controller=3.7.1
Oracle Communications Application Session Controller=3.8.0
Oracle Communications Eagle Lnp Application Processor=10.0
Oracle Communications Eagle Lnp Application Processor=10.1
Oracle Communications Eagle Lnp Application Processor=10.2
Oracle Communications Operations Monitor=3.4
Oracle Communications Operations Monitor=4.0
ORACLE JD Edwards EnterpriseOne Tools=9.2
Oracle Jd Edwards World Security=a9.1
Oracle Jd Edwards World Security=a9.2
Oracle Jd Edwards World Security=a9.3
Oracle Jd Edwards World Security=a9.4
Remediation
Patch Available
Event History
May 4, 2017
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2017-3730?
The severity of CVE-2017-3730 is classified as high due to its potential to cause Denial of Service attacks.
2
How do I fix CVE-2017-3730?
To fix CVE-2017-3730, upgrade OpenSSL to version 1.1.0d or later.
3
What types of attacks can be executed using CVE-2017-3730?
CVE-2017-3730 can be exploited to perform Denial of Service attacks by causing a client to crash.
4
Which versions of OpenSSL are affected by CVE-2017-3730?
OpenSSL versions 1.1.0, 1.1.0a, 1.1.0b, and 1.1.0c are affected by CVE-2017-3730.
5
Is CVE-2017-3730 relevant for Oracle products?
Yes, CVE-2017-3730 affects several Oracle products that rely on vulnerable versions of OpenSSL.