When updates are applied to Redis Enterprise DBMS software, any software components that have been replaced or made unnecessary must be removed.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-251252 | RD6X-00-012400 | SV-251252r961677_rule | CCI-002617 | low |
| Description | ||||
| Previous versions of DBMS components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some DBMSs' installation tools 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 considered in the planning. | ||||
| STIG | Date | |||
| Redis Enterprise 6.x Security Technical Implementation Guide | 2024-09-04 | |||
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)V2R2intersects(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)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-002617
1.00
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
Details
Check Text (C-251252r961677_chk)
When the Redis software is upgraded to a new version, the old version install file remains on the server. The users must remove this manually. To verify if the old install files have been deleted, check the locations below:
/opt/redislabs - Main Installation directory for all Redis Enterprise Software binaries
/opt/redislabs/config - System configuration files
/opt/redislabs/lib - System library files
/var/opt/redislabs - Default storage location for the cluster data, system logs, backups and ephemeral, persisted data
/tmp - Temporary files
The GREP command can be used to search for old Redis files in the above locations.
If software components that have been replaced or made unnecessary are not removed, this is a finding.
Fix Text (F-54641r804945_fix)
When a new update is available and installed, all old install files must be removed from the locations below:
/opt/redislabs - Main Installation directory for all Redis Enterprise Software binaries
/opt/redislabs/config - System configuration files
/opt/redislabs/lib - System library files
/var/opt/redislabs - Default storage location for the cluster data, system logs, backups and ephemeral, persisted data
/tmp - Temporary files
The GREP command can be used to search for old Redis files in the above locations.
If software from a previous/outdated version of Redis Enterprise remains in any of the following locations/directories, run the following to remove it:
rm -r <file_name>