MITRE ATT&CK CAPEC CDF

The web format of this guide reflects the most current release.  Guides for older iterations are available in PDF format.  

This integration can be installed in the My Integration section of your ThreatQ instance. See the Adding an Integration topic for more details.

MITRE ATT&CK CAPEC

The MITRE ATT&CK CAPEC CDF for ThreatQuotient enables the automatic ingestion of Common Attack Pattern Enumerations and Classifications, distributed by MITRE. In addition, the feed brings in any related MITRE ATT&CK Patterns, related MITRE ATT&CK CWEs, and more.

GET https://raw.githubusercontent.com/mitre/cti/master/capec/2.1/stix-capec.json

Sample Response:

{
    "objects": [
        {
            "definition_type": "statement",
            "id": "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d",
            "definition": {
                "statement": "CAPEC is sponsored by US-CERT in the office of Cybersecurity and Communications at the U.S. Department of Homeland Security. Copyright \u00a9 2007 - 2021, The MITRE Corporation. CAPEC and the CAPEC logo are trademarks of The MITRE Corporation."
            },
            "type": "marking-definition",
            "created": "2021-01-08T19:55:06.45963Z"
        },
        {
            "name": "The MITRE Corporation",
            "identity_class": "organization",
            "id": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd",
            "object_marking_refs": [
                "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d"
            ],
            "type": "identity",
            "created": "2021-01-08T19:55:06.461Z",
            "modified": "2021-01-08T19:55:06.461Z"
        },
        {
            "id": "attack-pattern--92cdcd3d-d734-4442-afc3-4599f261498b",
            "name": "Accessing Functionality Not Properly Constrained by ACLs",
            "description": "In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.",
            "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd",
            "object_marking_refs": [
                "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d"
            ],
            "created": "2014-06-23T00:00:00.000Z",
            "modified": "2020-12-17T00:00:00.000Z",
            "external_references": [
                {
                    "source_name": "capec",
                    "url": "https://capec.mitre.org/data/definitions/1.html",
                    "external_id": "CAPEC-1"
                },
                {
                    "source_name": "cwe",
                    "url": "http://cwe.mitre.org/data/definitions/276.html",
                    "external_id": "CWE-276"
                },
                {
                    "source_name": "ATTACK",
                    "description": "Hijack Execution Flow: ServicesFile Permissions Weakness",
                    "url": "https://attack.mitre.org/wiki/Technique/T1574/010",
                    "external_id": "T1574.010"
                }
            ],
            "x_capec_likelihood_of_attack": "High",
            "x_capec_typical_severity": "High",
            "x_capec_prerequisites": [
                "The application must be navigable in a manner that associates elements (subsections) of the application with ACLs.",
                "The various resources, or individual URLs, must be somehow discoverable by the attacker",
                "The administrator must have forgotten to associate an ACL or has associated an inappropriately permissive ACL with a particular navigable resource."
            ],
            "x_capec_skills_required": {
                "Low": "In order to discover unrestricted resources, the attacker does not need special tools or skills. They only have to observe the resources or access mechanisms invoked as each action is performed and then try and access those access mechanisms directly."
            },
            "x_capec_resources_required": [
                "None: No specialized resources are required to execute this type of attack."
            ],
            "x_capec_consequences": {
                "Confidentiality": [
                    "Gain Privileges"
                ],
                "Access_Control": [
                    "Gain Privileges"
                ],
                "Authorization": [
                    "Gain Privileges"
                ]
            },
            "x_capec_abstraction": "Standard",
            "x_capec_example_instances": [
                "\n               <xhtml:p>Implementing the Model-View-Controller (MVC) within Java EE's Servlet paradigm using a \"Single front controller\" pattern that demands that brokered HTTP requests be authenticated before hand-offs to other Action Servlets.</xhtml:p>\n               <xhtml:p>If no security-constraint is placed on those Action Servlets, such that positively no one can access them, the front controller can be subverted.</xhtml:p>\n            "
            ],
            "x_capec_execution_flow": "<h2> Execution Flow </h2><div><h3>Explore</h3><ol><li> <p> <b>Survey: </b>The attacker surveys the target application, possibly as a valid and authenticated user</p></li><table><tbody><tr><th>Techniques</th></tr><tr><td>Spidering web sites for all available links</td></tr><tr><td>Brute force guessing of resource names</td></tr><tr><td>Brute force guessing of user names / credentials</td></tr><tr><td>Brute force guessing of function names / actions</td></tr></tbody></table><li> <p> <b>Identify Functionality: </b>At each step, the attacker notes the resource or functionality access mechanism invoked upon performing specific actions</p></li><table><tbody><tr><th>Techniques</th></tr><tr><td>Use the web inventory of all forms and inputs and apply attack data to those inputs.</td></tr><tr><td>Use a packet sniffer to capture and record network traffic</td></tr><tr><td>Execute the software in a debugger and record API calls into the operating system or important libraries. This might occur in an environment other than a production environment, in order to find weaknesses that can be exploited in a production environment.</td></tr></tbody></table></ol></div><div><h3>Experiment</h3><ol><li> <p> <b>Iterate over access capabilities: </b>Possibly as a valid user, the attacker then tries to access each of the noted access mechanisms directly in order to perform functions not constrained by the ACLs.</p></li><table><tbody><tr><th>Techniques</th></tr><tr><td>Fuzzing of API parameters (URL parameters, OS API parameters, protocol parameters)</td></tr></tbody></table></ol></div>",
            "x_capec_status": "Draft",
            "x_capec_version": "3.4",
            "type": "attack-pattern"
        }
    ]
}

ThreatQuotient provides the following default mapping for this feed:

Get CWE HTML (Supplemental)

The Get CWE HTML Supplemental feed fetches the HTML page corresponding to the CWE ID in question. The CWE value/name is parsed out of the HTML response.

GET http://cwe.mitre.org/data/definitions/{{cwe_id}}.html

PDF Guides