Advisory Published
Updated

REDHAT-BUG-1414423

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 SoftwareAffected VersionHow to fix
MySQL (MySQL-common)<5.5.54<5.6.35<5.7.17

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of REDHAT-BUG-1414423?

    The severity of REDHAT-BUG-1414423 is moderate due to insecure permissions that can lead to potential unauthorized access.

  • How do I fix REDHAT-BUG-1414423?

    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.

  • Who is affected by REDHAT-BUG-1414423?

    REDHAT-BUG-1414423 affects MySQL versions up to 5.5.54, 5.6.35 and 5.7.17.

  • What vulnerabilities does REDHAT-BUG-1414423 introduce?

    REDHAT-BUG-1414423 introduces vulnerabilities related to improper file permissions which could allow unauthorized users to access sensitive data.

  • Is there a workaround for REDHAT-BUG-1414423?

    A workaround for REDHAT-BUG-1414423 includes manually adjusting the file permissions in the database directory after installation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203