|
1 | 1 | # Security Policy |
2 | 2 |
|
| 3 | +MySQLTuner is committed to providing a secure and reliable experience for all users. This document outlines our security policies, supported versions, and the process for reporting vulnerabilities. |
| 4 | + |
3 | 5 | ## Supported Versions |
4 | 6 |
|
5 | | -MySQLTuner is committed to providing security updates for the following versions: |
| 7 | +We provide security updates for the following versions of MySQLTuner: |
6 | 8 |
|
7 | | -| Version | Supported | |
8 | | -| ------- | ------------------ | |
9 | | -| 2.x | :white_check_mark: | |
10 | | -| < 2.x | :x: | |
| 9 | +| Version | Status | |
| 10 | +| ------- | --------------------- | |
| 11 | +| v2.x | Supported (v2.8.37) | |
| 12 | +| < v2.x | End of Life | |
11 | 13 |
|
12 | | -We strongly recommend using the latest stable release (currently v2.8.35) available on [GitHub](https://github.com/jmrenouard/MySQLTuner-perl/releases). |
| 14 | +We strongly recommend that all users stay updated with the latest stable release available on [GitHub Releases](https://github.com/jmrenouard/MySQLTuner-perl/releases). |
13 | 15 |
|
14 | 16 | ## Reporting a Vulnerability |
15 | 17 |
|
16 | | -If you discover a security vulnerability within this project, please report it privately to the maintainer. |
| 18 | +If you discover a security vulnerability in MySQLTuner, please do **not** open a public issue. Instead, report it privately to the maintainer: |
| 19 | + |
| 20 | +- **Contact**: Jean-Marie Renouard ([jmrenouard@lightpath.fr](mailto:jmrenouard@lightpath.fr)) |
| 21 | + |
| 22 | +### Reporting Guidelines |
17 | 23 |
|
18 | | -**Contact**: [jmrenouard@lightpath.fr](mailto:jmrenouard@lightpath.fr) |
| 24 | +Please include the following information in your report: |
19 | 25 |
|
20 | | -### What to expect |
| 26 | +- A description of the vulnerability. |
| 27 | +- Steps to reproduce the issue (proof of concept). |
| 28 | +- Potential impact and affected versions. |
21 | 29 |
|
22 | | -- **Acknowledgement**: You can expect an initial response within 48-72 hours. |
23 | | -- **Updates**: We will provide periodic updates on the progress of any reported vulnerability until it is resolved. |
| 30 | +### What to Expect |
| 31 | + |
| 32 | +- **Acknowledgement**: You will receive an initial response within 48-72 hours. |
| 33 | +- **Triage**: We will investigate the report and determine the impact. |
| 34 | +- **Resolution**: We will work on a fix as a priority. |
24 | 35 | - **Disclosure**: We will coordinate with you to determine a mutually agreeable disclosure timeline. |
25 | 36 |
|
| 37 | +## Security Scope |
| 38 | + |
| 39 | +### In-Scope Vulnerabilities |
| 40 | + |
| 41 | +- Local Privilege Escalation through insecure system calls. |
| 42 | +- Credential leaks in the report output (unless explicitly permitted via CLI options). |
| 43 | +- Remote Code Execution (RCE) via malicious database responses. |
| 44 | +- Insecure storage of temporary data. |
| 45 | + |
| 46 | +### Out-of-Scope |
| 47 | + |
| 48 | +- Vulnerabilities in the underlying Percona/MySQL/MariaDB database itself. |
| 49 | +- Issues requiring root access to the host machine to exploit. |
| 50 | +- Denial of Service (DoS) attacks that are inherent to database benchmarking or diagnostics. |
| 51 | + |
26 | 52 | ## Security Philosophy |
27 | 53 |
|
28 | | -- **Production Stability**: Every recommendation provided by MySQLTuner is designed to be safe for production environments. |
29 | | -- **Read-Only**: MySQLTuner is a read-only script. It does not modify your database or system configuration files. |
30 | | -- **CVE Detection**: The script includes features to detect known vulnerabilities (CVEs) based on your MySQL/MariaDB version. |
31 | | -- **Zero-Dependency**: To maintain a secure and portable footprint, we avoid external dependencies and only use Perl Core modules. |
| 54 | +- **Production Stability**: Every recommendation is designed to be safe for production environments. No destructive actions are performed. |
| 55 | +- **Read-Only Architecture**: MySQLTuner is strictly a read-only script. It does not modify database configurations or system files. |
| 56 | +- **Zero-Dependency Portability**: To minimize the attack surface, MySQLTuner only uses Perl Core modules and avoids external dependencies. |
| 57 | +- **CVE Detection**: The script proactively checks for known CVEs based on the detected database version. |
| 58 | +- **Auditability**: As a single-file Perl script, MySQLTuner is easily auditable by security teams before deployment. |
0 commit comments