CVE-2017-12419: Infoleak
If, after successful installation of MantisBT through 2.5.2 on MySQL/MariaDB, the administrator does not remove the 'admin' directory (as recommended in the "Post-installation and upgrade tasks" section of the MantisBT Admin Guide), and the MySQL client has a localinfile setting enabled (in php.ini mysqli.allowlocalinfile, or the MySQL client config file, depending on the PHP setup), an attacker may take advantage of MySQL's "connect file read" feature to remotely access files on the MantisBT server.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-12419?
CVE-2017-12419 has a medium severity level due to the potential unauthorized access if the 'admin' directory is not removed after installation.
How do I fix CVE-2017-12419?
To fix CVE-2017-12419, remove the 'admin' directory as recommended in the MantisBT Admin Guide.
What versions are affected by CVE-2017-12419?
CVE-2017-12419 affects MantisBT version 2.5.2.
What could happen if CVE-2017-12419 is exploited?
If exploited, CVE-2017-12419 could allow attackers to access sensitive administrative features of the MantisBT application.
Is the local_infile setting related to CVE-2017-12419?
Yes, the local_infile setting being enabled in the MySQL client can contribute to the risk associated with CVE-2017-12419.