First published: Mon Apr 24 2017(Updated: )
An unspecified vulnerability in Oracle MySQL related to the Connectors Connector/J component could allow an authenticated attacker to cause high confidentiality impact, high integrity impact, and high availability impact.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Connector\/j | <=5.1.40 | |
IBM Data Virtualization on Cloud Pak for Data | <=3.0 | |
IBM Watson Query with Cloud Pak for Data as a Service | <=2.2 | |
IBM Watson Query with Cloud Pak for Data as a Service | <=2.1 | |
IBM Watson Query with Cloud Pak for Data as a Service | <=2.0 | |
IBM Data Virtualization on Cloud Pak for Data | <=1.8 | |
IBM Data Virtualization on Cloud Pak for Data | <=1.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2017-3523 is classified as high for confidentiality, integrity, and availability impacts.
To fix CVE-2017-3523, ensure you upgrade to a version of Oracle Connector/J newer than 5.1.40.
CVE-2017-3523 affects users of Oracle Connector/J and specific IBM products including Data Virtualization and Watson Query on Cloud Pak for Data.
CVE-2017-3523 is an unspecified vulnerability that may allow authenticated attackers to compromise confidentiality, integrity, and availability.
Yes, exploitation of CVE-2017-3523 requires the attacker to be authenticated.