CVE-2017-3331: Medium severity ORACLE MySQL vulnerability

Published Apr 19, 2017
·
Updated

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DML). The supported version that is affected is 5.7.11 to 5.7.17. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.

External References:

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL

Other sources

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DML). The supported version that is affected is 5.7.11 to 5.7.17. Easily "exploitable" vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.0 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

MITRE

Affected Software

8 affected componentsFixes available
redhat/mysql<5.7.18
5.7.18
ORACLE MySQL=5.7.11
ORACLE MySQL=5.7.12
ORACLE MySQL=5.7.13
ORACLE MySQL=5.7.14
ORACLE MySQL=5.7.15
ORACLE MySQL=5.7.16
ORACLE MySQL=5.7.17

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.7.18
  2. Upgrade

    Upgrade oracle/mysql/server to a version that resolves this vulnerability.

    Fixed in 5.7.18

Event History

Apr 24, 2017
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionWeakness
Data Sourced
via NVD·07:59 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-3331?

CVE-2017-3331 has been rated as an easily exploitable vulnerability, allowing low privileged attackers to compromise MySQL Server.

2

How do I fix CVE-2017-3331?

To fix CVE-2017-3331, upgrade MySQL Server to version 5.7.18 or later.

3

Which versions of MySQL are affected by CVE-2017-3331?

MySQL versions 5.7.11 through 5.7.17 are affected by CVE-2017-3331.

4

What are the potential impacts of CVE-2017-3331?

The impact of CVE-2017-3331 includes potential unauthorized access and compromise of the MySQL Server.

5

Who is at risk for CVE-2017-3331?

Organizations using MySQL versions 5.7.11 to 5.7.17 are at risk for CVE-2017-3331.

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