CAPEC-8: Buffer Overflow in an API Call

Detailed Draft 严重程度: High 攻击可能性: High

CAPEC版本: 3.9

更新日期: 2023-01-24

攻击模式描述

This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An adversary who has knowledge of known vulnerable libraries or shared code can easily target software that makes use of these libraries. 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.

执行流程

步骤 1 Explore

[Identify target application] The adversary, with knowledge of vulnerable libraries or shared code modules, identifies a target application or program that makes use of these.

步骤 2 Experiment

[Find injection vector] The adversary attempts to use the API, and if they can they send a large amount of data to see if the buffer overflow attack really does work.

技术:
  • Provide large input to a program or application and observe the behavior. If there is a crash, this means that a buffer overflow attack is possible.
步骤 3 Experiment

[Craft overflow content] The adversary crafts the content to be injected based on their knowledge of the vulnerability and their desired outcome. 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.

技术:
  • Create malicious shellcode that will execute when the program execution is returned to it.
  • Use a NOP-sled in the overflow content to more easily "slide" into the malicious code. This is done so that the exact return address need not be correct, only in the range of all of the NOPs
步骤 4 Exploit

[Overflow the buffer] Using the API as the injection vector, the adversary injects the crafted overflow content into the buffer.

前提条件

  • The target host exposes an API to the user.
  • One or more API functions exposed by the target host has a buffer overflow vulnerability.

所需技能

Low An adversary can simply overflow a buffer by inserting a long string into an adversary-modifiable injection vector. The result can be a DoS.
High Exploiting a buffer overflow to inject malicious code into the stack of a software system or even the heap can require a higher skill level.

后果影响

影响范围: Availability

技术影响: Unreliable Execution

影响范围: Confidentiality Integrity Availability

技术影响: Execute Unauthorized Commands

说明: Run Arbitrary Code

影响范围: Confidentiality

技术影响: Read Data

影响范围: Integrity

技术影响: Modify Data

缓解措施

Use a language or compiler that performs automatic bounds checking.

Use secure functions not vulnerable to buffer overflow.

If you have to use dangerous functions, make sure that you do boundary checking.

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.

Use OS-level preventative functionality. Not a complete solution.

关键信息

CAPEC ID: CAPEC-8

抽象级别: Detailed

状态: Draft

典型严重程度: High

攻击可能性: High

相关攻击模式