Check: MADB-10-008200
MariaDB Enterprise 10.x STIG:
MADB-10-008200
(in versions v2 r2 through v1 r2)
Title
MariaDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. (Cat II impact)
Discussion
The DOD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, current, DOD-issued Public Key Infrastructure (PKI) certificate, coupled with a Personal Identification Number (PIN) to be entered by the user at the beginning of each session and whenever reauthentication is required. Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the user reauthenticate. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances: (i) When authenticators change; (ii) When roles change; (iii) When security categories of information systems change; (iv) When the execution of privileged functions occurs; (v) After a fixed period of time; or (vi) Periodically. Within the DOD, the minimum circumstances requiring reauthentication are privilege escalation and role changes.
Check Content
Determine all situations where a user must reauthenticate. Check if the mechanisms that handle such situations use the following SQL: To make a single user reauthenticate, an existing connection must be present: To search for a specific user: MariaDB> SELECT * FROM information_schema.PROCESSLIST where user ='<name>' and host like '%'; To review all connections: MariaDB> SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST; Note the ID(s) (processlist_id) of the connection(s) for the user that must reauthenticate. To make a user reauthenticate, run the following for each ID returned above (as they can have multiple connections): MariaDB> KILL CONNECTION processslist_id; If the provided SQL does not force reauthentication, this is a finding.
Fix Text
To force a single user reauthenticate, the user must be currently authenticated to the database server. Find the process ID of the user in question: MariaDB> SELECT id FROM information_schema.processlist WHERE user = 'username'; Use the id to kill the process, which kills the connection and forces the user to reauthenticate: MariaDB> KILL id; To force all users to reauthenticate, run the following as the database administrator: MariaDB> SELECT concat( KILL ,id, ; ) FROM information_schema.processlist INTO OUTFILE /tmp/x.txt; MariaDB> SOURCE /tmp/x.txt;
Additional Identifiers
Rule ID: SV-253735r1018603_rule
Vulnerability ID: V-253735
Group Title: SRG-APP-000389-DB-000372
Expert Comments
CCIs
Number | Definition |
---|---|
CCI-002038 |
The organization requires users to reauthenticate upon organization-defined circumstances or situations requiring reauthentication. |
CCI-004895 |
Permit users to invoke the trusted communications path for communications between the user and the organization-defined security functions, including at a minimum, authentication and re-authentication. |
Controls
Number | Title |
---|---|
IA-11 |
Re-authentication |