What is the severity of CVE-2018-2573?

CVE-2018-2573 has been classified as an easily exploitable low severity vulnerability in MySQL Server.

How do I fix CVE-2018-2573?

To mitigate CVE-2018-2573, upgrade MySQL Server to version 5.6.39 or later for the 5.6 series, and to version 5.7.21 or later for the 5.7 series.

What versions of MySQL are affected by CVE-2018-2573?

The affected versions of MySQL for CVE-2018-2573 are 5.6.38 and prior, as well as 5.7.20 and prior.

Who can exploit CVE-2018-2573?

CVE-2018-2573 can be exploited by low privileged attackers with network access via multiple protocols.

Is there a patch available for CVE-2018-2573?

Yes, patches are available in MySQL Server versions 5.6.39 and 5.7.21, which address the vulnerability.

Vulnerability/
CVE-2018-2573

medium

6.8

17/1/2018

18/1/2018

3/10/2024

CVE-2018-2573

First published: Wed Jan 17 2018(Updated: )

Last updated 24 July 2024

Credit: secalert_us@oracle.com secalert_us@oracle.com

Affected Software	Affected Version	How to fix
redhat/mysql	<5.6.39	5.6.39
redhat/mysql	<5.7.21	5.7.21
debian/mysql-5.5
debian/mysql-5.7
MySQL	>=5.6.0<=5.6.38
MySQL	>=5.7.0<=5.7.20

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-2573?
CVE-2018-2573 has been classified as an easily exploitable low severity vulnerability in MySQL Server.
How do I fix CVE-2018-2573?
To mitigate CVE-2018-2573, upgrade MySQL Server to version 5.6.39 or later for the 5.6 series, and to version 5.7.21 or later for the 5.7 series.
What versions of MySQL are affected by CVE-2018-2573?
The affected versions of MySQL for CVE-2018-2573 are 5.6.38 and prior, as well as 5.7.20 and prior.
Who can exploit CVE-2018-2573?
CVE-2018-2573 can be exploited by low privileged attackers with network access via multiple protocols.
Is there a patch available for CVE-2018-2573?
Yes, patches are available in MySQL Server versions 5.6.39 and 5.7.21, which address the vulnerability.

agent/author
agent/type
agent/severity
agent/remedy
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2018-2573
agent/software-canonical-lookup
collector/launchpad-cve
source/Launchpad
collector/security-tracker-debian
source/Debian
collector/usn-cve
source/Ubuntu
agent/references
agent/softwarecombine
agent/description
agent/first-publish-date
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/trending
agent/source
agent/tags
collector/nvd-cve
source/NVD
agent/software-canonical-lookup-request
collector/nvd-index
package-manager/redhat
package-manager/debian
vendor/oracle
canonical/mysql
version/mysql/5.6.0
version/mysql/5.6.38
version/mysql/5.7.0
version/mysql/5.7.20

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2018-2573?
CVE-2018-2573 has been classified as an easily exploitable low severity vulnerability in MySQL Server.
How do I fix CVE-2018-2573?
To mitigate CVE-2018-2573, upgrade MySQL Server to version 5.6.39 or later for the 5.6 series, and to version 5.7.21 or later for the 5.7 series.
What versions of MySQL are affected by CVE-2018-2573?
The affected versions of MySQL for CVE-2018-2573 are 5.6.38 and prior, as well as 5.7.20 and prior.
Who can exploit CVE-2018-2573?
CVE-2018-2573 can be exploited by low privileged attackers with network access via multiple protocols.
Is there a patch available for CVE-2018-2573?
Yes, patches are available in MySQL Server versions 5.6.39 and 5.7.21, which address the vulnerability.