CVE-2016-5630
MEDIUMCVSS 4.9/10EPSS 2.02%
Last modified
CVE-2016-5630 is a medium-severity vulnerability rated 4.9/10 on the CVSS scale. Unspecified vulnerability in Oracle MySQL 5.6.31 and earlier and 5.7.13 and earlier allows remote administrators to affect availability via vectors related to Server: InnoDB.. EPSS estimates a 2.02% chance of exploitation in the next 30 days.
Description
Unspecified vulnerability in Oracle MySQL 5.6.31 and earlier and 5.7.13 and earlier allows remote administrators to affect availability via vectors related to Server: InnoDB.
Metrics
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Oracle | Mysql | >= 5.6.0, <= 5.6.31 |
| Oracle | Mysql | >= 5.7.0, <= 5.7.13 |
| Mariadb | Mariadb | >= 10.0.0, < 10.0.27 |
References
- http://rhn.redhat.com/errata/RHSA-2016-1601.htmlThird Party Advisory
- http://rhn.redhat.com/errata/RHSA-2016-2927.htmlThird Party Advisory
- http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/93674Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037050Broken Link, Third Party Advisory, VDB Entry
- https://security.gentoo.org/glsa/201701-01Third Party Advisory, VDB Entry
- http://rhn.redhat.com/errata/RHSA-2016-1601.htmlThird Party Advisory
- http://rhn.redhat.com/errata/RHSA-2016-2927.htmlThird Party Advisory
- http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/93674Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037050Broken Link, Third Party Advisory, VDB Entry
- https://security.gentoo.org/glsa/201701-01Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-5630?
Unspecified vulnerability in Oracle MySQL 5.6.31 and earlier and 5.7.13 and earlier allows remote administrators to affect availability via vectors related to Server: InnoDB.
How severe is CVE-2016-5630?
CVE-2016-5630 has a CVSS score of 4.9/10 (MEDIUM severity). The EPSS model estimates a 2.02% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5630?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-5624Unspecified vulnerability in Oracle MySQL 5.5.51 and earlier…6.5
- CVE-2016-5625Unspecified vulnerability in Oracle MySQL 5.7.14 and earlier…7
- CVE-2016-5626Unspecified vulnerability in Oracle MySQL 5.5.51 and earlier…6.5
- CVE-2016-5627Unspecified vulnerability in Oracle MySQL 5.6.31 and earlier…6.5
- CVE-2016-5628Unspecified vulnerability in Oracle MySQL 5.7.13 and earlier…4.9
- CVE-2016-5629Unspecified vulnerability in Oracle MySQL 5.5.51 and earlier…4.9
- CVE-2016-5631Unspecified vulnerability in Oracle MySQL 5.7.13 and earlier…4.9
- CVE-2016-5632Unspecified vulnerability in Oracle MySQL 5.7.14 and earlier…4.9
- CVE-2016-5633Unspecified vulnerability in Oracle MySQL 5.7.13 and earlier…4.9
- CVE-2016-5634Unspecified vulnerability in Oracle MySQL 5.7.13 and earlier…4.9
- CVE-2016-5635Unspecified vulnerability in Oracle MySQL 5.7.13 and earlier…4.9
- CVE-2016-5636Integer overflow in the get_data function in zipimport.c in …
Are you affected by CVE-2016-5630?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST