CVE-2017-3318: Medium severity Oracle MySQL vulnerability

Published Jan 18, 2017
·
Updated

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Error Handling ). Supported versions that are affected are 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes 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 access to critical data or complete access to all MySQL Server accessible data.

External References:

http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL

Other sources

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Error Handling). Supported versions that are affected are 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes 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 access to critical data or complete access to all MySQL Server accessible data. CVSS v3.0 Base Score 4.0 (Confidentiality impacts).

MITRE

Affected Software

25 affected componentsFixes available
redhat/mysql<5.5.54
5.5.54
redhat/mysql<5.6.35
5.6.35
redhat/mysql<5.7.17
5.7.17
redhat/mariadb<5.5.54
5.5.54
redhat/mariadb<10.1.21
10.1.21
redhat/mariadb<10.0.29
10.0.29
Oracle MySQL>=5.5.0<=5.5.53
Oracle MySQL>=5.6.0<=5.6.34
Oracle MySQL>=5.7.0<=5.7.16
Debian Debian Linux=8.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Eus=7.4
redhat Enterprise Linux Eus=7.5
redhat Enterprise Linux Eus=7.6
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Workstation=7.0
MariaDB MariaDB>=5.5.0<5.5.54
MariaDB MariaDB>=10.0.0<10.0.29
MariaDB MariaDB>=10.1.0<10.1.21

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/mysql to a version that resolves this vulnerability.

    Fixed in 5.5.54
  2. Upgrade

    Upgrade redhat/mysql to a version that resolves this vulnerability.

    Fixed in 5.6.35
  3. Upgrade

    Upgrade redhat/mysql to a version that resolves this vulnerability.

    Fixed in 5.7.17
  4. Upgrade

    Upgrade redhat/mariadb to a version that resolves this vulnerability.

    Fixed in 5.5.54
  5. Upgrade

    Upgrade redhat/mariadb to a version that resolves this vulnerability.

    Fixed in 10.1.21
  6. Upgrade

    Upgrade redhat/mariadb to a version that resolves this vulnerability.

    Fixed in 10.0.29
  7. Upgrade

    Upgrade Oracle MySQL Server (Server: Error Handling) to a version that resolves this vulnerability.

    Fixed in 5.5.53 and earlier
  8. Upgrade

    Upgrade Oracle MySQL Server (Server: Error Handling) to a version that resolves this vulnerability.

    Fixed in 5.6.34 and earlier
  9. Upgrade

    Upgrade Oracle MySQL Server (Server: Error Handling) to a version that resolves this vulnerability.

    Fixed in 5.7.16 and earlier

Event History

Jan 27, 2017
CVE Published
via MITRE·10:01 PM
Data Sourced
via MITRE·10:01 PM
DescriptionWeakness
Data Sourced
via NVD·10:59 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-3318?

CVE-2017-3318 is classified as a low complexity vulnerability that is difficult to exploit.

2

How do I fix CVE-2017-3318?

To remediate CVE-2017-3318, upgrade MySQL to versions 5.5.54, 5.6.35, or 5.7.17, or apply the appropriate patches for affected versions.

3

Which versions of MySQL are vulnerable to CVE-2017-3318?

MySQL versions 5.5.53 and earlier, 5.6.34 and earlier, and 5.7.16 and earlier are affected by CVE-2017-3318.

4

Can MariaDB be affected by CVE-2017-3318?

Yes, certain versions of MariaDB are affected, specifically 5.5.54, 10.1.21, and 10.0.29.

5

Who is primarily impacted by CVE-2017-3318?

CVE-2017-3318 poses a risk primarily to high privileged users who have logon access to the MySQL Server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203