| Home > CAPEC List > CAPEC-465: Transparent Proxy Abuse (Version 3.9) |
|
Transparent proxies are often used by enterprises and ISPs. For requests originating at the client transparent proxies need to figure out the final destination of the client's data packet. Two ways are available to do that: either by looking at the layer three (network) IP address or by examining layer seven (application) HTTP header destination. A browser has same origin policy that typically prevents scripts coming from one domain initiating requests to other websites from which they did not come. To circumvent that, however, malicious Flash or an Applet that is executing in the user's browser can attempt to create a cross-domain socket connection from the client to the remote domain. The transparent proxy will examine the HTTP header of the request and direct it to the remote site thereby partially bypassing the browser's same origin policy. This can happen if the transparent proxy uses the HTTP host header information for addressing rather than the IP address information at the network layer. This attack allows malicious scripts inside the victim's browser to issue cross-domain requests to any hosts accessible to the transparent proxy.
Medium
| Nature | Type | ID | Name |
|---|---|---|---|
| ChildOf | Meta Attack PatternMeta Attack Pattern - A meta level attack pattern in CAPEC is a decidedly abstract characterization of a specific methodology or technique used in an attack. A meta attack pattern is often void of a specific technology or implementation and is meant to provide an understanding of a high level approach. A meta level attack pattern is a generalization of related group of standard level attack patterns. Meta level attack patterns are particularly useful for architecture and design level threat modeling exercises. | 554 | Functionality Bypass |
| View Name | Top Level Categories |
|---|---|
| Domains of Attack | Software |
| Mechanisms of Attack | Abuse Existing Functionality |
| CWE-ID | Weakness Name |
|---|---|
| 441 | Unintended Proxy or Intermediary ('Confused Deputy') |
| Entry ID | Entry Name |
|---|---|
| 1090.001 | Proxy: Internal Proxy |
| Submissions | |||
|---|---|---|---|
| Submission Date | Submitter | Organization | |
| 2014年06月23日 (Version 2.6) | CAPEC Content Team | The MITRE Corporation | |
| Modifications | |||
| Modification Date | Modifier | Organization | |
| 2015年12月07日 (Version 2.8) | CAPEC Content Team | The MITRE Corporation | |
| Updated Related_Attack_Patterns | |||
| 2019年09月30日 (Version 3.2) | CAPEC Content Team | The MITRE Corporation | |
| Updated @Abstraction | |||
| 2020年12月17日 (Version 3.4) | CAPEC Content Team | The MITRE Corporation | |
| Updated Mitigations | |||
| 2022年02月22日 (Version 3.7) | CAPEC Content Team | The MITRE Corporation | |
| Updated Description, Extended_Description | |||
| 2022年09月29日 (Version 3.8) | CAPEC Content Team | The MITRE Corporation | |
| Updated Taxonomy_Mappings | |||
| Previous Entry Names | |||
| Change Date | Previous Entry Name | ||
| 2015年12月07日 (Version 2.8) | Socket Capable Browser Plugins Result In Transparent Proxy Abuse | ||
|
Use of the Common Attack Pattern Enumeration and Classification (CAPEC), and the associated references from this website are subject to the Terms of Use. Copyright © 2007–2025, The MITRE Corporation. CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. |
||