What is the severity of CVE-2014-4274?

CVE-2014-4274 is classified as having the potential to affect confidentiality, integrity, and availability.

How do I fix CVE-2014-4274?

To fix CVE-2014-4274, you should update your Oracle MySQL Server to a version later than 5.5.38 or 5.6.19.

Who is affected by CVE-2014-4274?

CVE-2014-4274 affects local users of Oracle MySQL Server versions 5.5.38 and earlier, as well as 5.6.19 and earlier.

Is MariaDB also affected by CVE-2014-4274?

Yes, MariaDB versions before 5.5.39 and 10.0.13 are also affected by CVE-2014-4274.

What types of databases are impacted by CVE-2014-4274?

CVE-2014-4274 impacts Oracle MySQL Server and certain versions of MariaDB.

Vulnerability/
CVE-2014-4274

medium

4.1

15/10/2014

29/8/2022

CVE-2014-4274

First published: Wed Oct 15 2014(Updated: )

Unspecified vulnerability in Oracle MySQL Server 5.5.38 and earlier and 5.6.19 and earlier allows local users to affect confidentiality, integrity, and availability via vectors related to SERVER:MyISAM.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle Solaris SPARC	=11.3
MySQL	>=5.5.0<=5.5.38
MySQL	>=5.6.0<=5.6.19
Mariadb Mariadb	>=5.5.0<5.5.39
Mariadb Mariadb	>=10.0.0<10.0.13

Remedy

http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-4274?
CVE-2014-4274 is classified as having the potential to affect confidentiality, integrity, and availability.
How do I fix CVE-2014-4274?
To fix CVE-2014-4274, you should update your Oracle MySQL Server to a version later than 5.5.38 or 5.6.19.
Who is affected by CVE-2014-4274?
CVE-2014-4274 affects local users of Oracle MySQL Server versions 5.5.38 and earlier, as well as 5.6.19 and earlier.
Is MariaDB also affected by CVE-2014-4274?
Yes, MariaDB versions before 5.5.39 and 10.0.13 are also affected by CVE-2014-4274.
What types of databases are impacted by CVE-2014-4274?
CVE-2014-4274 impacts Oracle MySQL Server and certain versions of MariaDB.

agent/references
agent/type
agent/last-modified-date
agent/first-publish-date
agent/severity
agent/remedy
agent/author
agent/softwarecombine
agent/tags
agent/description
agent/event
collector/nvd-index
agent/software-canonical-lookup-request
vendor/oracle
canonical/oracle solaris sparc
version/oracle solaris sparc/11.3
canonical/mysql
version/mysql/5.5.0
version/mysql/5.5.38
version/mysql/5.6.0
version/mysql/5.6.19
vendor/mariadb
canonical/mariadb mariadb
version/mariadb mariadb/5.5.0
version/mariadb mariadb/10.0.0

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-2014-4274?
CVE-2014-4274 is classified as having the potential to affect confidentiality, integrity, and availability.
How do I fix CVE-2014-4274?
To fix CVE-2014-4274, you should update your Oracle MySQL Server to a version later than 5.5.38 or 5.6.19.
Who is affected by CVE-2014-4274?
CVE-2014-4274 affects local users of Oracle MySQL Server versions 5.5.38 and earlier, as well as 5.6.19 and earlier.
Is MariaDB also affected by CVE-2014-4274?
Yes, MariaDB versions before 5.5.39 and 10.0.13 are also affected by CVE-2014-4274.
What types of databases are impacted by CVE-2014-4274?
CVE-2014-4274 impacts Oracle MySQL Server and certain versions of MariaDB.