MariaDB up to 10.7 SQL Statement used_tables_and_const_cache_join denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MariaDB up to 10.7. It has been rated as problematic. Affected by this vulnerability is the function Used_tables_and_const_cache::used_tables_and_const_cache_join of the component SQL Statement Handler. This manipulation causes denial of service.
This vulnerability is tracked as CVE-2022-27385. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in MariaDB up to 10.7 (Database Software). It has been declared as problematic. Affected by this vulnerability is the function Used_tables_and_const_cache::used_tables_and_const_cache_join of the component SQL Statement Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability.
The weakness was disclosed 04/13/2022. The advisory is shared at jira.mariadb.org. This vulnerability is known as CVE-2022-27385 since 03/21/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/21/2022 🔍04/13/2022 🔍
04/13/2022 🔍
04/18/2022 🔍
Sources
Advisory: jira.mariadb.orgStatus: Confirmed
CVE: CVE-2022-27385 (🔍)
GCVE (CVE): GCVE-0-2022-27385
GCVE (VulDB): GCVE-100-197197
Entry
Created: 04/13/2022 09:57Updated: 04/18/2022 20:02
Changes: 04/13/2022 09:57 (38), 04/18/2022 20:02 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.