Title

Security-relevant software updates to MariaDB must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). (Cat II impact)

Discussion

Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality, will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period utilized must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

Check Content

If new packages are available for MariaDB, they can be reviewed in the package manager appropriate for the server operating system. To list the version of installed MariaDB, run the following Linux commands as the system administrator: MariaDB> SELECT @@version; Check the list of installed packages: $ sudo yum list installed | grep -i mariadb All versions of MariaDB will be listed on: https://mariadb.com/downloads/#mariadb_platform-mariadb_server All security-relevant software updates for MariaDB will be listed on: https://mariadb.com/kb/en/library/security/ If MariaDB is not at the latest version, this is a finding. If MariaDB is not at the latest version and the evaluated version has CVEs (IAVAs), this is a CAT I finding.

Fix Text

Institute and adhere to policies and procedures to ensure that patches are consistently applied to MariaDB within the time allowed.

Additional Identifiers

Rule ID: SV-253745r1001008_rule

Vulnerability ID: V-253745

Group Title: SRG-APP-000456-DB-000390

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.