Quick answers
- Is CVE-2017-3320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-3320 being exploited in the wild.
- How severe is CVE-2017-3320?
- Low severity, with a CVSS score of 2.4, published 27 January 2017.
- Which products and versions are affected?
- Oracle MySQL Server 5.7.16 and earlier.
- Is there a fix for CVE-2017-3320?
- A patch was published on 2017-01-17: Oracle January 2017 Critical Patch Update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2017-3320 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-3320?
- Check whether you run Oracle Mysql or Oracle MySQL Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in the Server: Security: Encryption subcomponent of Oracle MySQL Server (specifically version 5.7.16 and earlier) allows a high-privileged attacker with network access via multiple protocols to compromise the server. The vulnerability is classified as 'unspecified' by the vendor but is noted to impact confidentiality. Exploitation is considered easy but requires human interaction from a user other than the attacker (UI:R). Successful attacks result in unauthorized read access to a subset of MySQL Server accessible data. The issue was addressed in the Oracle Critical Patch Update for January 2017.
Affected products
- Oracle MySQL Server 5.7.16 and earlier
Timeline
- 2017-01-27: advisory: Initial NVD publication
- 2017-01-17: patched: Oracle January 2017 Critical Patch Update released