First published: Wed Jan 18 2017(Updated: )
Multiple cases of insecure use of chmod and chown were found in the MySQL init script: - In database directory initialization code: <a href="https://github.com/mysql/mysql-server/blob/mysql-5.6.34/packaging/rpm-oel/mysql.init#L97">https://github.com/mysql/mysql-server/blob/mysql-5.6.34/packaging/rpm-oel/mysql.init#L97</a> - In code handling error log file creation and permission setting: <a href="https://github.com/mysql/mysql-server/blob/mysql-5.6.34/packaging/rpm-oel/mysql.init#L73">https://github.com/mysql/mysql-server/blob/mysql-5.6.34/packaging/rpm-oel/mysql.init#L73</a> The mysql OS user could use these flaws to escalate privileges to root. Note that the second issue is only exploitable in configurations where log file is stored in a directory writable to the mysql OS user. If log file is stored in the /var/log directory, mysql user is not able to replace it with a link to some other file. This issue was fixed in MySQL versions 5.5.54, 5.6.35, and 5.7.17. The following related entry can be found in the release notes: Initialization scripts create the error log file only if the base directory is /var/log or /var/lib. <a href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-54.html">http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-54.html</a> <a href="http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-35.html">http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-35.html</a> <a href="http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html">http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html</a> MySQL upstream commit: <a href="https://github.com/mysql/mysql-server/commit/53230ba274a37fa13d65e802c6ef3766cd0c6d91#diff-5fccc3d0e109e8f9ad0653728bd1d975">https://github.com/mysql/mysql-server/commit/53230ba274a37fa13d65e802c6ef3766cd0c6d91#diff-5fccc3d0e109e8f9ad0653728bd1d975</a>
Affected Software | Affected Version | How to fix |
---|---|---|
MySQL (MySQL-common) | <5.5.54<5.6.35<5.7.17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1414423 is moderate due to insecure permissions that can lead to potential unauthorized access.
To fix REDHAT-BUG-1414423, update your MySQL installation to a version above 5.6.35 or apply patches that address the insecure use of chmod and chown.
REDHAT-BUG-1414423 affects MySQL versions up to 5.5.54, 5.6.35 and 5.7.17.
REDHAT-BUG-1414423 introduces vulnerabilities related to improper file permissions which could allow unauthorized users to access sensitive data.
A workaround for REDHAT-BUG-1414423 includes manually adjusting the file permissions in the database directory after installation.