CVE-2013-2395 json
Unspecified vulnerability in Oracle MySQL 5.6.10 and earlier allows remote authenticated users to affect availability via unknown vectors r…
published 13y ago modified 4mo ago also EUVD-2013-2341
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle MySQL 5.6.10 and earlier allows remote authenticated users to affect availability via unknown vectors related to Data Manipulation Language, a different vulnerability than CVE-2013-1567.
Is CVE-2013-2395 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-2013-2395 updated cvss 4.0
mysql: unspecified DoS related to Data Manipulation Language (CPU April 2013)
-
Red Hat Enterprise Linux 5 mysql Red Hat Enterprise Linux 6 mysql, mysql-libs, mysql-test, mysql-bench, mysql-server, mysql-embeddednot 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
2.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:L/Au:S/C:N/I:N/A:C |
Classification
- Technology feeds
References
-
security.gentoo.org
/glsa/glsa-201308-06.xml
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2013:150
vendor-advisory
-
oracle.com
/technetwork/topics/security/cpuapr2013-1899555.html
vendor-advisory
-
secunia.com
/advisories/53372
third-party-advisory
Sources
- CVE List CVE-2013-2395
- NVD CVE-2013-2395
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.