| name | T1601.002_downgrade-system-image |
| description | Adversaries may install an older version of the operating system of a network device to weaken security. |
| category | configuration |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","enterprise","t1601.002","defense-evasion","network-devices","sub-technique"] |
| technique_id | T1601.002 |
| tactic | defense-evasion |
| all_tactics | ["defense-evasion"] |
| platforms | ["Network Devices"] |
| mitre_url | https://attack.mitre.org/techniques/T1601/002 |
| tech_stack | ["network devices"] |
| cwe_ids | ["CWE-693"] |
| chains_with | ["T1601","T1601.001"] |
| prerequisites | ["T1601"] |
| severity_boost | {"T1601":"Chain with T1601 for deeper attack path","T1601.001":"Chain with T1601.001 for deeper attack path"} |
T1601.002 Downgrade System Image
Sub-technique of: T1601
High-Level Description
Adversaries may install an older version of the operating system of a network device to weaken security. Older operating system versions on network devices often have weaker encryption ciphers and, in general, fewer/less updated defensive features.
On embedded devices, downgrading the version typically only requires replacing the operating system file in storage. With most embedded devices, this can be achieved by downloading a copy of the desired version of the operating system file and reconfiguring the device to boot from that file on next system restart. The adversary could then restart the device to implement the change immediately or they could wait until the next time the system restarts.
Downgrading the system image to an older versions may allow an adversary to evade defenses by enabling behaviors such as Weaken Encryption. Downgrading of a system image can be done on its own, or it can be used in conjunction with Patch System Image.
Kill Chain Phase
Platforms: Network Devices
What to Check
How to Test
Manual Testing
-
Identify Attack Surface: Determine if the target environment is susceptible to Downgrade System Image by examining the target platforms (Network Devices).
-
Assess Existing Defenses: Review whether mitigations for T1601.002 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
-
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
Remediation Guide
M1032 Multi-factor Authentication
Use multi-factor authentication for user and privileged accounts. Most embedded network devices support TACACS+ and/or RADIUS. Follow vendor prescribed best practices for hardening access control.