Feedback
Did this article resolve your question/issue?

   

Article

Are the JDBC drivers effected by FREAK, POODLE, other security vulnerabilities?

Information

 
TitleAre the JDBC drivers effected by FREAK, POODLE, other security vulnerabilities?
URL NameAre-the-JDBC-drivers-effected-by-FREAK-POODLE-other-security-vulnerabilities
Article Number000110871
EnvironmentProduct: Connect for JDBC
Version: All supported versions
OS: Java
Database: All supported databases.
Application: All supported applications
Question/Problem Description
Are the Connect for JDBC drivers effected by FREAK, POODLE, SLOTH or other Security vulnerabilities?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Connect for JDBC drivers are not directly affected by these security vulnerabilities.

JDBC drivers use a JRE/JDK . If the driver uses a version of JRE or JDK that is affected by a security vulnerability, the application will be affected by the vulnerability.

It is always recommended to use the very latest JRE/JDK release to stay current with all Java security updates. 

For example, an upgrade to Java runtime Environment (JRE) 7 or higher is needed to deny the small diffie-hellman keys.

For additional information on what JRE/JDK releases effected by security vulnerabilities, refer the Java provider's web site.
Workaround
Notes
Last Modified Date4/9/2018 5:31 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.