CVE-2018-3203
First published: Wed Oct 17 2018(Updated: )
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer). Supported versions that are affected are 8.0.12 and prior. 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).
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle MySQL | >=8.0.0<=8.0.12 | |
| NetApp OnCommand Insight | ||
| Netapp Oncommand Unified Manager Vsphere | >=7.3<=9.5 | |
| Netapp Oncommand Unified Manager Windows | >=7.3<=9.5 | |
| NetApp OnCommand Workflow Automation | ||
| Netapp Snapcenter | ||
| Netapp Storage Automation Store |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-3203?
The severity of CVE-2018-3203 is considered medium (6.5).
What is the affected software for CVE-2018-3203?
The affected software for CVE-2018-3203 includes Oracle MySQL versions 8.0.12 and prior, NetApp OnCommand Insight, NetApp OnCommand Unified Manager (versions 7.3 to 9.5), Apple macOS High Sierra, Apple tvOS, NetApp OnCommand Workflow Automation, Netapp Snapcenter, and Netapp Storage Automation Store.
How can a low privileged attacker exploit CVE-2018-3203?
A low privileged attacker with network access via multiple protocols can exploit CVE-2018-3203 to compromise MySQL Server.
Where can I find more information about CVE-2018-3203?
More information about CVE-2018-3203 can be found on the Oracle website and security advisories, as well as other references such as SecurityFocus and SecurityTracker.
How can I fix CVE-2018-3203?
To fix CVE-2018-3203, Oracle MySQL users should update to version 8.0.13 or later, and follow any additional recommendations from the vendor or security advisories.
- agent/severity
- agent/references
- agent/author
- agent/description
- agent/type
- agent/event
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/remedy
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/oracle
- canonical/oracle mysql
- version/oracle mysql/8.0.0
- version/oracle mysql/8.0.12
- vendor/netapp
- canonical/netapp oncommand insight
- canonical/netapp oncommand unified manager vsphere
- version/netapp oncommand unified manager vsphere/7.3
- version/netapp oncommand unified manager vsphere/9.5
- canonical/netapp oncommand unified manager windows
- version/netapp oncommand unified manager windows/7.3
- version/netapp oncommand unified manager windows/9.5
- canonical/netapp oncommand workflow automation
- canonical/netapp snapcenter
- canonical/netapp storage automation store