CVE-2014-6500: High severity oracle solaris and zettabyte file system (zfs) vulnerability

Q: What is the severity of CVE-2014-6500?

CVE-2014-6500 has a high severity rating due to its potential impact on confidentiality, integrity, and availability.

Q: How do I fix CVE-2014-6500?

To fix CVE-2014-6500, upgrade to a version of Oracle MySQL Server that is above 5.5.39 or 5.6.20.

Q: Which software is affected by CVE-2014-6500?

CVE-2014-6500 affects Oracle MySQL Server versions 5.5.39 and earlier, and 5.6.20 and earlier, as well as specific versions of MariaDB and other related software.

Q: What impact can CVE-2014-6500 have if exploited?

Exploitation of CVE-2014-6500 can lead to unauthorized access, data breaches, and service disruptions.

Q: Is there a workaround for CVE-2014-6500?

There are no known workarounds for CVE-2014-6500; upgrading to a patched version is the recommended action.

Published Oct 15, 2014

Updated

Unspecified vulnerability in Oracle MySQL Server 5.5.39 and earlier, and 5.6.20 and earlier, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to SERVER:SSL:yaSSL, a different vulnerability than CVE-2014-6491.

Affected Software

7 affected componentsFixes available

debian/wolfssl

4.6.0+p1-0+deb11u25.5.4-2+deb12u15.7.0-0.3

Oracle Solaris=11.3

Juniper Junos Space<=15.1

MariaDB MariaDB>=5.5.0<5.5.40

MariaDB MariaDB>=10.0.0<10.0.15

ORACLE MySQL>=5.5.0<=5.5.39

ORACLE MySQL>=5.6.0<=5.6.20

Remediation

Patch Available

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

Event History

Oct 15, 2014

CVE Published

via MITRE·10:03 PM

Data Sourced

via MITRE·10:03 PM

Description

Frequently Asked Questions

What is the severity of CVE-2014-6500?

CVE-2014-6500 has a high severity rating due to its potential impact on confidentiality, integrity, and availability.

How do I fix CVE-2014-6500?