CVE-2017-3650

Name: CVE-2017-3650
Creator: NVD / NIST
Published: 2017-08-08T15:29:08.663+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.15%

Last modified Jun 17, 2026

CVE-2017-3650 is a vulnerability of currently unknown severity. Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: C API). Supported versions that are affected are 5.7.18 and earlier. EPSS estimates a 2.15% chance of exploitation in the next 30 days.

Description

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: C API). Supported versions that are affected are 5.7.18 and earlier. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.0 Base Score 3.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

Metrics

EPSS Probability

2.15%

79.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Vendor	Product	Versions
Oracle	Mysql	<= 5.7.18

References

http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.htmlPatch, Vendor Advisory
http://www.securityfocus.com/bid/99808Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1038928Third Party Advisory, VDB Entry
https://access.redhat.com/errata/RHSA-2017:2886
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.htmlPatch, Vendor Advisory
http://www.securityfocus.com/bid/99808Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1038928Third Party Advisory, VDB Entry
https://access.redhat.com/errata/RHSA-2017:2886

Timeline

Published: Aug 8, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-3650?

How severe is CVE-2017-3650?

Severity scoring for CVE-2017-3650 is pending analysis. The EPSS model estimates a 2.15% probability of exploitation in the next 30 days.

How do I fix CVE-2017-3650?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-3650?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST