CVE-2017-3320

CVE-2017-3320 is a low-severity vulnerability in Oracle Mysql with a CVSS 3.x base score of 2.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Description

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Security: Encryption). Supported versions that are affected are 5.7.16 and earlier. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS v3.0 Base Score 2.4 (Confidentiality impacts).

Frequently asked questions

What is CVE-2017-3320?
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Security: Encryption). Supported versions that are affected are 5.7.16 and earlier. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS v3.0 Base Score 2.4 (Confidentiality impacts).
How severe is CVE-2017-3320?
CVE-2017-3320 has a CVSS 3.x base score of 2.4, rated low severity. It is exploitable over network with low attack complexity, requires high privileges and user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2017-3320 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-3320?
CVE-2017-3320 affects Oracle Mysql. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-3320?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-3320 published?
CVE-2017-3320 was published on 2017-01-27 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Oracle Mysql

All CVEs affecting Oracle Mysql →

Threat intelligence

Threat-intel indicators referencing this CVE: