CVE-2014-6500
First published: Wed 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.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/wolfssl | 4.6.0+p1-0+deb11u2 5.5.4-2+deb12u1 5.7.0-0.3 | |
| Oracle Solaris SPARC | =11.3 | |
| Juniper Networks Junos Space | <=15.1 | |
| MariaDB | >=5.5.0<5.5.40 | |
| MariaDB | >=10.0.0<10.0.15 | |
| MySQL | >=5.5.0<=5.5.39 | |
| MySQL | >=5.6.0<=5.6.20 |
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
- http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10698
- http://lists.opensuse.org/opensuse-security-announce/2015-04/msg00016.html
- http://secunia.com/advisories/61579
- http://secunia.com/advisories/62073
- http://security.gentoo.org/glsa/glsa-201411-02.xml
- http://www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html
- http://www.oracle.com/technetwork/topics/security/bulletinoct2015-2511968.html
- http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html
- http://www.securityfocus.com/bid/70478
- https://security-tracker.debian.org/tracker/CVE-2014-6500
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?
To fix CVE-2014-6500, upgrade to a version of Oracle MySQL Server that is above 5.5.39 or 5.6.20.
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.
What impact can CVE-2014-6500 have if exploited?
Exploitation of CVE-2014-6500 can lead to unauthorized access, data breaches, and service disruptions.
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.
- agent/type
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- agent/remedy
- agent/author
- agent/references
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/debian
- vendor/oracle
- canonical/oracle solaris sparc
- version/oracle solaris sparc/11.3
- vendor/juniper
- canonical/juniper networks junos space
- version/juniper networks junos space/15.1
- vendor/mariadb
- canonical/mariadb
- version/mariadb/5.5.0
- version/mariadb/10.0.0
- canonical/mysql
- version/mysql/5.5.0
- version/mysql/5.5.39
- version/mysql/5.6.0
- version/mysql/5.6.20