First published: Wed Sep 26 2012(Updated: )
It was found that the fix for <a href="https://access.redhat.com/security/cve/CVE-2009-4030">CVE-2009-4030</a> was removed from the MySQL packages as provided with RHSA-2012:0127 when it was updated to version 5.0.95. Upstream claimed to have corrected this in version 5.0.88, so the patch was removed when it did not apply. As a result, MySQL version 5.0.95-1.el5_7.1 became vulnerable to <a href="https://access.redhat.com/security/cve/CVE-2009-4030">CVE-2009-4030</a> again. For most default or typical configurations, this flaw has no impact. Please see <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - CVE-2009-4030 mysql: Incomplete fix for CVE-2008-2079 / CVE-2008-4098" href="show_bug.cgi?id=543653#c4">https://bugzilla.redhat.com/show_bug.cgi?id=543653#c4</a> for further discussion on the possible scenarios where this flaw can be triggered. If the basedir and datadir directives are unchanged in MySQL's configuration or command-line arguments, this flaw has no impact.
Affected Software | Affected Version | How to fix |
---|---|---|
MySQL Server |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-860808 is considered high due to the potential for exploitation.
To fix REDHAT-BUG-860808, upgrade to a version of MySQL that includes the necessary security patches.
REDHAT-BUG-860808 affects MySQL version prior to the fixes implemented after upstream correction.
Yes, there is an official patch available in later versions of MySQL to address REDHAT-BUG-860808.
If REDHAT-BUG-860808 is not addressed, it may leave the system vulnerable to potential SQL injection attacks.