sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, group_comments in sqlparse/engine/grouping.py repeatedly rescans comment-only statements before the MAX_GROUPING_TOKENS guard, causing quadratic CPU consumption through sqlparse.parse() and sqlparse.format(sql, strip_comments=True). This issue is fixed in version 0.6.0.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | RedHat | python3.12-sqlparse-0:0.6.0-1.el8ap | * |
| Red Hat Ansible Automation Platform 2.5 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9ap | * |
| Red Hat Ansible Automation Platform 2.6 for RHEL 10 | RedHat | python-sqlparse-0:0.6.0-1.el10ap | * |
| Red Hat Ansible Automation Platform 2.6 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9ap | * |
| Red Hat Ansible Automation Platform 2.7 for RHEL 10 | RedHat | python-sqlparse-0:0.6.0-1.el10ap | * |
| Red Hat Ansible Automation Platform 2.7 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9ap | * |
| Red Hat Satellite 6.18 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9pc | * |
| Red Hat Satellite 6.18 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9pc | * |
| Red Hat Satellite 6.19 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9pc | * |
| Red Hat Satellite 6.19 for RHEL 9 | RedHat | python3.12-sqlparse-0:0.6.0-1.el9pc | * |
| Red Hat Ansible Automation Platform 2.5 | RedHat | ansible-automation-platform-25/gateway-rhel8:1789605572 | * |
| Red Hat Ansible Automation Platform 2.5 | RedHat | ansible-automation-platform-25/hub-rhel8:1789606395 | * |
| Red Hat Ansible Automation Platform 2.5 | RedHat | ansible-automation-platform-25/lightspeed-rhel8:1789685837 | * |
| Red Hat Ansible Automation Platform 2.6 | RedHat | ansible-automation-platform-26/eda-controller-rhel9:1789653608 | * |
| Red Hat Ansible Automation Platform 2.6 | RedHat | ansible-automation-platform-26/gateway-rhel9:1789666472 | * |
| Red Hat Ansible Automation Platform 2.6 | RedHat | ansible-automation-platform-26/hub-rhel9:1789611274 | * |
| Red Hat Ansible Automation Platform 2.6 | RedHat | ansible-automation-platform-26/lightspeed-rhel9:1789656884 | * |
| Red Hat Ansible Automation Platform 2.6 | RedHat | ansible-automation-platform-tech-preview/metrics-service-rhel9:1789654558 | * |
| Red Hat Ansible Automation Platform 2.7 | RedHat | ansible-automation-platform-27/eda-controller-rhel9:1788917355 | * |
| Red Hat Ansible Automation Platform 2.7 | RedHat | ansible-automation-platform-27/gateway-rhel9:1788918510 | * |
| Red Hat Ansible Automation Platform 2.7 | RedHat | ansible-automation-platform-27/lightspeed-rhel9:1788916677 | * |
| Red Hat Ansible Automation Platform 2.7 | RedHat | ansible-automation-platform-27/metrics-service-rhel9:1788917058 | * |
| Red Hat Ansible Automation Platform 2.7 | RedHat | ansible-automation-platform-27/hub-rhel9:1789572632 | * |
| Red Hat Discovery 2 | RedHat | discovery/discovery-server-rhel9:1788205779 | * |
| Red Hat Discovery 2 | RedHat | discovery/discovery-server-rhel9:1789675186 | * |
| Red Hat OpenShift AI 3.5 | RedHat | rhoai/odh-training-cuda128-torch29-py312-rhel9:1789529851 | * |
| Red Hat Satellite 6.18 | RedHat | satellite/iop-advisor-backend-rhel9:1789666499 | * |
| Red Hat Satellite 6.19 | RedHat | satellite/iop-advisor-backend-rhel9:1789666498 | * |
| Sqlparse | Ubuntu | devel | * |
| Sqlparse | Ubuntu | esm-infra-legacy/xenial | * |
| Sqlparse | Ubuntu | esm-infra/bionic | * |
| Sqlparse | Ubuntu | esm-infra/focal | * |
| Sqlparse | Ubuntu | jammy | * |
| Sqlparse | Ubuntu | noble | * |
| Sqlparse | Ubuntu | resolute | * |
| Sqlparse | Ubuntu | upstream | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.