Mariadb: Use After Free
CVE-2022-27383 is a high-severity use after free vulnerability in Mariadb, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 10.2.44, 10.3.35, 10.4.25 as the first without the flaw, so updating Mariadb to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.13% chance of exploitation within 30 days, higher than 82% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Mariadb to 10.2.44 or 10.3.35 or 10.4.25 or 10.5.16, whichever matches your release line, or a later version.
- Read the advisory on jira.mariadb.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MariaDB | Mariadb | 10.2.0 up to, but not including, 10.2.44; 10.3.0 up to, but not including, 10.3.35; 10.4.0 up to, but not including, 10.4.25; 10.5.0 up to, but not including, 10.5.16; 10.6.0 up to, but not including, 10.6.8; 10.7.0 up to, but not including, 10.7.4; 10.8.0 up to, but not including, 10.8.3 | 10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4 |
| Debian | Debian Linux | 10.0 | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
MariaDB Server v10.6 and below was discovered to contain an use-after-free in the component my_strcasecmp_8bit, which is exploited via specially crafted SQL statements.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- jira.mariadb.org/browse/MDEV-26323Exploit, Issue Tracking
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2022/09/msg00023.htmlMailing List, Third Party Advisory
- security.netapp.com/advisory/ntap-20220519-0006/Third Party Advisory
Other vulnerabilities in Mariadb
- 8.8 High severity
- 9.9 Critical severity
- 7.7 High severity
- 9.9 Critical severity
- 9.9 Critical severity
- 7.2 High severity
Recent Use After Free vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.0 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.