CAPECattack pattern
CAPEC-121 Exploit Non-Production Interfaces
High
Official page ↗
- Abstraction
- Standard
- Status
- Stable
- Likelihood of attack
- Low
- Typical severity
- High
- CAPEC version
- 3.9
Description
An adversary exploits a sample, demonstration, test, or debug interface that is unintentionally enabled on a production system, with the goal of gleaning information or leveraging functionality that would otherwise be unavailable.
Extended description
Non-production interfaces are insecure by default and should not be resident on production systems, since they may reveal sensitive information or functionality that should not be known to end-users. However, such interfaces may be unintentionally left enabled on a production system due to configuration errors, supply chain mismanagement, or other pre-deployment activities.
Ultimately, failure to properly disable non-production interfaces, in a production environment, may expose a great deal of diagnostic information or functionality to an adversary, which can be utilized to further refine their attack. Moreover, many non-production interfaces do not have adequate security controls or may not have undergone rigorous testing since they were not intended for use in production environments. As such, they may contain many flaws and vulnerabilities that could allow an adversary to severely disrupt a target.
Execution flow
1. [Explore] [Determine Vulnerable Interface] An adversary explores a target system for sample or test interfaces that have not been disabled by a system administrator and which may be exploitable by the adversary.
2. [Exploit] [Leverage Test Interface to Execute Attacks] Once an adversary has discovered a system with a non-production interface, the interface is leveraged to exploit the system and/or conduct various attacks.
Prerequisites
• The target must have configured non-production interfaces and failed to secure or remove them when brought into a production environment.
Skills required
• [High] Exploiting non-production interfaces requires significant skill and knowledge about the potential non-production interfaces left enabled in production.
Consequences
• Confidentiality, Access Control, Authentication: Gain Privileges, Bypass Protection Mechanism
• Confidentiality, Access Control, Authorization: Read Data, Execute Unauthorized Commands
• Access Control, Integrity: Modify Data, Alter Execution Logic
Mitigations
• Ensure that production systems do not contain non-production interfaces and that these interfaces are only used in development environments.
Related
Child of · CAPEC (1)
- CAPEC-113 Interface Manipulation attack pattern
Weakness · CWE (10)
- CWE-1209 Failure to Disable Reserved Bits weakness
- CWE-1259 Improper Restriction of Security Token Assignment weakness
- CWE-1267 Policy Uses Obsolete Encoding weakness
- CWE-1270 Generation of Incorrect Security Tokens weakness
- CWE-1294 Insecure Security Identifier Mechanism weakness
- CWE-1295 Debug Messages Revealing Unnecessary Information weakness
- CWE-1296 Incorrect Chaining or Granularity of Debug Components weakness
- CWE-1302 Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) weakness
- CWE-1313 Hardware Allows Activation of Test or Debug Logic at Runtime weakness
- CWE-489 Active Debug Code weakness
Referenced by CAPEC · child of (1)
- CAPEC-661 Root/Jailbreak Detection Evasion via Debugging attack pattern
Referenced by CWE · attack pattern (10)
- CWE-1209 Failure to Disable Reserved Bits weakness
- CWE-1259 Improper Restriction of Security Token Assignment weakness
- CWE-1267 Policy Uses Obsolete Encoding weakness
- CWE-1270 Generation of Incorrect Security Tokens weakness
- CWE-1294 Insecure Security Identifier Mechanism weakness
- CWE-1295 Debug Messages Revealing Unnecessary Information weakness
- CWE-1296 Incorrect Chaining or Granularity of Debug Components weakness
- CWE-1302 Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) weakness
- CWE-1313 Hardware Allows Activation of Test or Debug Logic at Runtime weakness
- CWE-489 Active Debug Code weakness