In MariaDB server version through 11.8.5, when server audit plugin is enabled with server_audit_events variable configured with QUERY_DCL, QUERY_DDL, or QUERY_DML filtering, if an authenticated database user invokes a SQL statement prefixed with double-hyphen (—) or hash (#) style comments, the statement is not logged.
Weakness
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mariadb | Mariadb | * | 10.6.24 (including) |
| Mariadb | Mariadb | 10.7.0 (including) | 10.11.15 (including) |
| Mariadb | Mariadb | 11.0.0 (including) | 11.4.9 (including) |
| Mariadb | Mariadb | 11.5.0 (including) | 11.8.5 (including) |
Extended Description
When security-critical events are not logged properly, such as a failed login attempt, this can make malicious behavior more difficult to detect and may hinder forensic analysis after an attack succeeds. As organizations adopt cloud storage resources, these technologies often require configuration changes to enable detailed logging information, since detailed logging can incur additional costs. This could lead to telemetry gaps in critical audit logs. For example, in Azure, the default value for logging is disabled.