Critical Vulnerability in MariaDB: Unauthorized Access Risk Due to MySQL Server Flaw

mariadb Updated 02 Oct 2025

Summary

27/01/2017
N/A
Yes i
Medium
4.7

ALPINE-CVE-2017-3313: Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: MyISAM). Affects mariadb versions < 10.1.22-r0. Fixed in 10.1.22-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

MariaDB is an open-source relational database management system that is widely used for web applications and data storage. It is a fork of MySQL and offers enhanced features and performance improvements. The package is known for its robustness, scalability, and compatibility with MySQL. However, it is susceptible to vulnerabilities that can compromise the integrity and confidentiality of the data it manages.

Vulnerability Detail

The vulnerability identified as CVE-2017-3313 affects the MySQL Server component of Oracle MySQL, specifically in the MyISAM subcomponent. It impacts supported versions of MySQL Server, including 5.5.53 and earlier, 5.6.34 and earlier, and 5.7.16 and earlier. This vulnerability allows a low-privileged attacker with access to the infrastructure where MySQL Server runs to exploit the flaw, potentially leading to unauthorized access to critical data or complete access to all MySQL Server accessible data. The CVSS v3.0 Base Score for this vulnerability is 4.7, indicating a moderate risk to confidentiality.

How To Fix

Minimum fixed version

10.1.22-r0

This is the first release that contains the fix.

sudo apk add --upgrade mariadb

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate patching is not feasible, consider restricting access to the MySQL Server by implementing stricter firewall rules or limiting user permissions to mitigate the risk of exploitation until the patch can be applied.

Conclusion

CVE-2017-3313 represents a significant vulnerability in the MariaDB package that can lead to unauthorized access to sensitive data. It is crucial to update to the patched version 10.1.22-r0 to mitigate this risk. Additionally, utilizing tools like Vulert can help monitor and alert for open-source vulnerabilities in your software.

See every vulnerability recorded for mariadb →

Share this vulnerability

FAQ

CVE-2017-3313 is a vulnerability in the MySQL Server component of Oracle MySQL that allows unauthorized access to data due to a flaw in the MyISAM subcomponent.

The vulnerability affects MariaDB versions that are based on MySQL versions 5.5.53 and earlier, 5.6.34 and earlier, and 5.7.16 and earlier.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Update your MariaDB package to the fixed version 10.1.22-r0 and consider implementing stricter access controls and firewall rules as a temporary measure.

The CVSS v3.0 Base Score for CVE-2017-3313 is 4.7, indicating a moderate risk to confidentiality.

Related vulnerabilities

Recent vulnerabilities recorded for mariadb.

How To Fix

Minimum fixed version

10.1.22-r0

This is the first release that contains the fix.

sudo apk add --upgrade mariadb

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback