T1474.001 Compromise Software Dependencies and Development Tools
Sub-technique of: T1474
High-Level Description
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise. Applications often depend on external software to function properly. Popular open source projects that are used as dependencies in many applications may be targeted as a means to add malicious code to users of the dependency.
Kill Chain Phase
- Initial Access (TA0027)
Platforms: Android, iOS
What to Check
- Identify if Compromise Software Dependencies and Development Tools technique is applicable to target mobile environment
- Check Android devices for indicators of Compromise Software Dependencies and Development Tools
- Check iOS devices for indicators of Compromise Software Dependencies and Development Tools
- Verify mitigations are bypassed or absent (1 known mitigations)
- Assess detection coverage (1 detection strategies)
How to Test
Identify Attack Surface
Determine if the target mobile environment is susceptible to Compromise Software Dependencies and Development Tools by examining the target platforms (Android, iOS).
Assess Existing Defenses
Review whether mitigations for T1474.001 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Remediation Guide
M1013 Application Developer Guidance
Application developers should be cautious when selecting third-party libraries to integrate into their application.
Detection
Detection of Compromise Software Dependencies and Development Tools
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| Compromise Software Dependencies and Development Tools technique applicable | Low | Initial Access |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-20 | Improper Input Validation |