| name | T1222_file-and-directory-permissions-modification |
| description | Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files. |
| category | configuration |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","enterprise","t1222","defense-evasion","esxi","linux","macos","windows"] |
| technique_id | T1222 |
| tactic | defense-evasion |
| all_tactics | ["defense-evasion"] |
| platforms | ["ESXi","Linux","macOS","Windows"] |
| mitre_url | https://attack.mitre.org/techniques/T1222 |
| tech_stack | ["esxi","linux","macos","windows"] |
| cwe_ids | ["CWE-693"] |
| chains_with | ["T1222.001","T1222.002"] |
| prerequisites | [] |
| severity_boost | {"T1222.001":"Chain with T1222.001 for deeper attack path","T1222.002":"Chain with T1222.002 for deeper attack path"} |
T1222 File and Directory Permissions Modification
High-Level Description
Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files. File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.).
Modifications may include changing specific access rights, which may require taking ownership of a file or directory and/or elevated permissions depending on the file or directory’s existing permissions. This may enable malicious activity such as modifying, replacing, or deleting specific files or directories. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via Accessibility Features, Boot or Logon Initialization Scripts, Unix Shell Configuration Modification, or tainting/hijacking other instrumental binary/configuration files via Hijack Execution Flow.
Adversaries may also change permissions of symbolic links. For example, malware (particularly ransomware) may modify symbolic links and associated settings to enable access to files from local shortcuts with remote paths.
Kill Chain Phase
Platforms: ESXi, Linux, macOS, Windows
What to Check
How to Test
Atomic Red Team Tests
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
Atomic Test 1: Enable Local and Remote Symbolic Links via fsutil
Use fsutil to enable both ‘remote to local’ and ‘remote to remote’ symbolic links. This allows access to files from local shortcuts with local or remote paths.
