MariaDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-253707	SRG-APP-000224-DB-000384	MADB-10-004900	SV-253707r1043181_rule	2024-12-05	2

Description
Unique session IDs help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. When a user logs out, or when any other session termination event occurs, the DBMS must terminate the user session(s) to minimize the potential for sessions to be hijacked.

Description

Unique session IDs help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. When a user logs out, or when any other session termination event occurs, the DBMS must terminate the user session(s) to minimize the potential for sessions to be hijacked.

ℹ️ Check
Determine if MariaDB is configured to require SSL. MariaDB> SHOW GLOBAL VARIABLES LIKE 'require_secure_transport'; If require_secure_transport is not "ON", this is a finding.

✔️ Fix
Modify the MariaDB configuration file located within /etc/my.cnf.d/ and set the variable require_secure_transport to "ON" under the server section. Restart MariaDB Enterprise Server. Example: [server] require_secure_transport = ON