Security Vulnerabilities (CVE) Fixed in Oracle MySQL That Did Not Exist in MariaDB
Reference list of security vulnerabilities (CVEs) found in Oracle MySQL that do not affect MariaDB, helping administrators distinguish relevant threats.
About
CVE® stands for Common Vulnerabilities and Exposures. It is a publicly available and free-to-use database of known software vulnerabilities maintained at https://cve.mitre.org/.
CPU stands for Critical Patch Update. Oracle publishes Critical Patch Update Advisories four times a year, on the Tuesday closest to the 17th day of January, April, July and October. MySQL vulnerabilities are included in these CPU Advisories.
Some vulnerabilities found in MySQL apply to MariaDB as well, they are listed on the Security page.
Other vulnerabilities found in MySQL do not apply to MariaDB.
This page lists all CVEs that were fixed in MySQL and mentioned in Oracle CPU Advisories, but that — to the best of our knowledge — were never present in MariaDB.
Full List of CVEs Fixed in Oracle MySQL That Never Existed in MariaDB
October 2020
CVE-2020-14672 2f35c37bacf0
CVE-2020-14769 6a0e79b462e1
CVE-2020-14793 9bb243a3fa25
CVE-2020-14867 7e730bd604e1
This page is licensed: CC BY-SA / Gnu FDL
Last updated
Was this helpful?