Skip to Main Content

Java Database Connectivity (JDBC)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to fix Ojdbc7- CVE-2016-3506 vulnerability

f8ac0572-c34a-474e-9cfc-4ed19e39be8dApr 1 2020 — edited Apr 2 2020

I was doing the owasp fixes in my application and came across CVE-2016-3506 - Ojdbc7, As per my analysis I could find that there will be a patch update to oracle database that could be a possible fix for this issue(https://www.oracle.com/security-alerts/cpujul2016.html .Does this means that I can continue to use the same ojdbc7 jar? Can an unpatched ojdbc client where the vulnerability exists impact/leverage this vulnerability in a database even if the CPU patch is applied to the database, or are only unpatched databases vulnerable? As I am working on a maven project and the Ojdbc7 jar are kept on a central repo can I continue to use the same ojdbc7 jar or any patch updates are required on ojdbc7 jar also?

Comments
Post Details
Added on Apr 1 2020
2 comments
1,478 views