STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 3 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to MariaDB Enterprise Server Security Technical Implementation Guide

V-286227

CAT II (Medium)

When updates are applied to the MariaDB software, any software components that have been replaced or made unnecessary must be removed.

Rule ID

SV-286227r1292251_rule

STIG

MariaDB Enterprise Server Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-002617

Discussion

Previous versions of MariaDB components that are not removed from the information system after updates have been installed may be exploited by adversaries. MariaDB may remove older versions of software automatically from the information system. In other cases, manual review and removal will be required. In planning installations and upgrades, organizations must include steps (automated, manual, or both) to identify and remove the outdated modules. A transition period may be necessary when both the old and the new software are required.

Check Content

As a DBA, review installed MariaDB packages on the host operating system.

For RPM-based Linux distributions (e.g., RHEL, CentOS, Fedora), run:

rpm -qa | grep -i mariadb

For DEB-based Linux distributions (e.g., Debian, Ubuntu), run:

dpkg -l | grep -i mariadb

Review the output and verify that only the currently required MariaDB packages and versions are installed.

Confirm that the following have been removed following the upgrade:
- Outdated MariaDB packages.
- Superseded MariaDB versions.
- Unused MariaDB client libraries or components.

If any obsolete, superseded, or unnecessary MariaDB components remain installed on the system, this is a finding.

Fix Text

Remove any unnecessary packages using the OS package manager for each outdated, deprecated, or unused component. Examples:

For RPM-based systems, run:

sudo yum remove <component_name>

For DEB-based systems, run:

sudo apt-get remove <package_name>