CAPEC-75: Manipulating Writeable Configuration Files
Description
Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.
- Likelihood of attack
- High
- Typical severity
- Very High
- Abstraction
- StandardA specific methodology or technique used in an attack.
Mechanism of attack: Manipulate System Resources
Prerequisites
- Configuration files must be modifiable by the attacker
Skills required
- MediumTo identify vulnerable configuration files, and understand how to manipulate servers and erase forensic evidence
Consequences
- ConfidentialityAccess ControlAuthorization
Gain Privileges
Mitigations
- Design: Enforce principle of least privilege
- Design: Backup copies of all configuration files
- Implementation: Integrity monitoring for configuration files
- Implementation: Enforce audit logging on code and configuration promotion procedures.
- Implementation: Load configuration from separate process and memory space, for example a separate physical device like a CD
Related weaknesses (CWE)
- CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection')
- CWE-99Improper Control of Resource Identifiers ('Resource Injection')
- CWE-346Origin Validation Error
- CWE-349Acceptance of Extraneous Untrusted Data With Trusted Data
- CWE-353Missing Support for Integrity Check
- CWE-354Improper Validation of Integrity Check Value