CAPECattack pattern
CAPEC-481 Contradictory Destinations in Traffic Routing Schemes
High
Official page ↗
- Abstraction
- Standard
- Status
- Draft
- Likelihood of attack
- Medium
- Typical severity
- High
- CAPEC version
- 3.9
Description
Adversaries can provide contradictory destinations when sending messages. Traffic is routed in networks using the domain names in various headers available at different levels of the OSI model. In a Content Delivery Network (CDN) multiple domains might be available, and if there are contradictory domain names provided it is possible to route traffic to an inappropriate destination. The technique, called Domain Fronting, involves using different domain names in the SNI field of the TLS header and the Host field of the HTTP header. An alternative technique, called Domainless Fronting, is similar, but the SNI field is left blank.
Prerequisites
• An adversary must be aware that their message will be routed using a CDN, and that both of the contradictory domains are served from that CDN.
• If the purpose of the Domain Fronting is to hide redirected C2 traffic, the C2 server must have been created in the CDN.
Skills required
• [Medium] The adversary must have some knowledge of how messages are routed.
Consequences
• Confidentiality: Read Data, Modify Data
Mitigations
• Monitor connections, checking headers in traffic for contradictory domain names, or empty domain names.
Related
Att&ck technique · MITRE ATT&CK (1)
- T1090.004 Domain Fronting sub-technique
Child of · CAPEC (1)
- CAPEC-161 Infrastructure Manipulation attack pattern
Weakness · CWE (1)
- CWE-923 Improper Restriction of Communication Channel to Intended Endpoints weakness
Referenced by CWE · attack pattern (1)
- CWE-923 Improper Restriction of Communication Channel to Intended Endpoints weakness