CAPECattack pattern

CAPEC-81 Web Server Logs Tampering

High Official page ↗
Abstraction
Detailed
Status
Draft
Likelihood of attack
Medium
Typical severity
High
CAPEC version
3.9

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.

Execution flow

1. [Explore] [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. [Experiment] [Determine Injectable Content] The attacker launches various logged actions with malicious data to determine what sort of log injection is possible. 3. [Exploit] [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.

Prerequisites

• Target server software must be a HTTP server that performs web logging.

Skills required

• [Low] To input faked entries into Web logs

Consequences

• Integrity: Modify Data

Mitigations

• Design: Use input validation before writing to web log • Design: Validate all log data before it is output

Related

Child of · CAPEC (1)

  • CAPEC-268 Audit Log Manipulation attack pattern

Weakness · CWE (10)

  • CWE-116 Improper Encoding or Escaping of Output weakness
  • CWE-117 Improper Output Neutralization for Logs weakness
  • CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences weakness
  • CWE-20 Improper Input Validation weakness
  • CWE-221 Information Loss or Omission weakness
  • CWE-276 Incorrect Default Permissions weakness
  • CWE-279 Incorrect Execution-Assigned Permissions weakness
  • CWE-75 Failure to Sanitize Special Elements into a Different Plane weakness
  • CWE-93 Improper Neutralization of CRLF Sequences weakness
  • CWE-96 Improper Neutralization of Directives in Statically Saved Code weakness

Referenced by CWE · attack pattern (10)

  • CWE-116 Improper Encoding or Escaping of Output weakness
  • CWE-117 Improper Output Neutralization for Logs weakness
  • CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences weakness
  • CWE-20 Improper Input Validation weakness
  • CWE-221 Information Loss or Omission weakness
  • CWE-276 Incorrect Default Permissions weakness
  • CWE-279 Incorrect Execution-Assigned Permissions weakness
  • CWE-75 Failure to Sanitize Special Elements into a Different Plane weakness
  • CWE-93 Improper Neutralization of CRLF Sequences weakness
  • CWE-96 Improper Neutralization of Directives in Statically Saved Code weakness