cyberstrikeus T1546.006 LC_LOAD_DYLIB Addition
Sub-technique of: T1546
High-Level Description
Adversaries may establish persistence by executing malicious content triggered by the execution of tainted binaries. Mach-O binaries have a series of headers that are used to perform certain operations when a binary is loaded. The LC_LOAD_DYLIB header in a Mach-O binary tells macOS and OS X which dynamic libraries (dylibs) to load during execution time. These can be added ad-hoc to the compiled binary as long as adjustments are made to the rest of the fields and dependencies. There are tools available to perform these changes.
Adversaries may modify Mach-O binary headers to load and execute malicious dylibs every time the binary is executed. Although any changes will invalidate digital signatures on binaries because the binary is being modified, this can be remediated by simply removing the LC_CODE_SIGNATURE command from the binary so that the signature isn’t checked at load time.
Kill Chain Phase
- Privilege Escalation (TA0004)
- Persistence (TA0003)
Platforms: macOS
What to Check
- Identify if LC_LOAD_DYLIB Addition technique is applicable to target environment
- Check macOS systems for indicators of LC_LOAD_DYLIB Addition
- Verify mitigations are bypassed or absent (3 known mitigations)
- Assess detection coverage (1 detection strategies)
How to Test
Manual Testing
Identify Attack Surface: Determine if the target environment is susceptible to LC_LOAD_DYLIB Addition by examining the target platforms (macOS).
Assess Existing Defenses: Review whether mitigations for T1546.006 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
M1047 Audit
Binaries can also be baselined for what dynamic libraries they require, and if an app requires a new dynamic library that wasn't included as part of an update, it should be investigated.
M1038 Execution Prevention
Allow applications via known hashes.
M1045 Code Signing
Enforce that all binaries be signed by the correct Apple Developer IDs.
Detection
Detection Strategy for LC_LOAD_DYLIB Modification in Mach-O Binaries on macOS
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| LC_LOAD_DYLIB Addition technique applicable | Low | Privilege Escalation |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-269 | Improper Privilege Management |