CVE-2014-2442 json
Unspecified vulnerability in Oracle MySQL Server 5.6.15 and earlier allows remote authenticated users to affect availability via vectors re…
published 12y ago modified 4mo ago also EUVD-2014-2478
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle MySQL Server 5.6.15 and earlier allows remote authenticated users to affect availability via vectors related to MyISAM.
Is CVE-2014-2442 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-2442 updated cvss 3.5
mysql: unspecified DoS related to MyIASM (CPU April 2014)
-
Red Hat Enterprise Linux 5 mysql55-mysql Red Hat Enterprise Linux 6 mysql, mysql-libs, mysql-test, mysql-bench, mysql-server, mysql-embedded Red Hat Enterprise Linux 7 mariadb, mariadb-libs, mariadb-test, mariadb-bench, mariadb-server, mariadb-embedded Red Hat Software Collections mysql55-mysql, mariadb55-mariadb, mysql55-mysql-libs, mysql55-mysql-test, mysql55-mysql-bench, mysql55-mysql-server, +4 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
Classification
- Technology feeds
References
-
oracle.com
/technetwork/topics/security/cpuapr2014-1972952.html
vendor-advisory
Sources
- CVE List CVE-2014-2442
- NVD CVE-2014-2442
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.