When updates are applied to the MariaDB software, any software components that have been replaced or made unnecessary must be removed.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-253744 | MADB-10-009200 | SV-253744r961677_rule | CCI-002617 | medium |
| Description | ||||
| 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. This should be taken into account in the planning. | ||||
| STIG | Date | |||
| MariaDB Enterprise 10.x Security Technical Implementation Guide | 2026-03-02 | |||
Related Frameworks
1 mapping across 3 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V2R5intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V2R5intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-002617
1.00
- DISA STIG Benchmark (XCCDF)V2R5intersects(normalised)
Details
Check Text (C-253744r961677_chk)
If updating through a repository using yum, apt, etc., all MariaDB packages should be updated/upgraded at the same time.
Use the package manager to verify no outdated packages remain. Example:
$ sudo yum list installed | grep -i mariadb
If older packages remain, this is a finding.
Fix Text (F-57147r841756_fix)
If after the upgrade outdated packages remain, update them if needed or remove. Example:
$ sudo yum remove package_name