CVE-2013-1502 json
Unspecified vulnerability in Oracle MySQL 5.5.30 and earlier and 5.6.9 and earlier allows local users to affect availability via unknown ve…
published 2013-04-17 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-1538
- cvss
- 1.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle MySQL 5.5.30 and earlier and 5.6.9 and earlier allows local users to affect availability via unknown vectors related to Server Partition.
Patch / fix
- mariadb mariadb 5.5.31, 10.0.3
Vendor 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-1502 updated cvss 1.5
mysql: unspecified DoS related to Server Partition (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
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 1.5 | AV:L/AC:M/Au:S/C:N/I:N/A:P |
Classification
- Technology feeds
References
-
security.gentoo.org
/glsa/glsa-201308-06.xml
vendor-advisory, third-party-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2013:150
vendor-advisory, broken-link
-
oracle.com
/technetwork/topics/security/cpuapr2013-1899555.html
vendor-advisory
-
oracle.com
/technetwork/topics/security/bulletinoct2015-2511968.html
vendor-advisory
-
secunia.com
/advisories/53372
third-party-advisory, not-applicable, permissions-required
Sources
- CVE List CVE-2013-1502
- NVD CVE-2013-1502
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.