Bug 1915502
| Summary: | Segfault and possible DoS with a crafted query | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | t_j80 | |
| Component: | mysql | Assignee: | Michal Schorm <mschorm> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jakub Heger <jheger> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.0 | CC: | databases-maint, hhorak, jkejda, ljavorsk, mschorm | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | 8.5 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Rebase: Bug Fixes Only | ||
| Doc Text: |
Rebase package(s) to version:
8.0.22
Important bug fixes:
Crash on a specific SQL query. See comment #1 for more info.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1996699 (view as bug list) | Environment: | ||
| Last Closed: | 2021-09-27 13:24:22 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1944766 | |||
| Bug Blocks: | 1996699 | |||
|
Description
t_j80
2021-01-12 18:35:12 UTC
Hello, Thank you for the report. I can confirm the issue exists. I minimised your reproducer to the following form: ----- DROP DATABASE IF EXISTS test; CREATE DATABASE test; USE test; CREATE TABLE `test` ( `ip` varchar(10) DEFAULT NULL, `dt` int DEFAULT '0' KEY ) ENGINE=Innodb; INSERT INTO `test` VALUES (NULL,0); SELECT MIN(dt) AS dt, COUNT( DISTINCT ip ) AS v2 FROM test GROUP BY MONTH(CONVERT_TZ(FROM_UNIXTIME(dt), @@session.time_zone, '+00:00')); ----- It appears, the issue is with using "COUNT( DISTINCT )" as well as "CONVERT_TZ". If either is removed / changed; the command will pass. I can also confirm that the 8.0.22 release of community MySQL solves the issue for both above reproducers. I went through the MySQL 8.0.22 release notes in hope to spot a fixed issue which would correspond with this reproducer, but nothing there caught my eye. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-22.html I agree this issue deserves fixing.
The MySQL components in Red Hat products are *usually* updated about once a year or more often because of medium and high priority CVEs discovered by upstream in their product.
However the planning and decision making are not purely engineering driven, so I can't promise any dates nor confirm any plans.
Thank you for taking the time to report this issue to us.
You can watch Oracle quarterly announcements, which can provide some idea about the current priority of the update:
https://www.oracle.com/security-alerts/
That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
https://access.redhat.com/support
Pushed in the rpms (stream-8.0-rhel-8.5.0 branch), modules (8.0-rhel-8.5.0 branch) |