CAPEC-81: Web Server Logs Tampering
CAPEC版本: 3.9
更新日期: 2023-01-24
攻击模式描述
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.
执行流程
步骤 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.
- 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.
步骤 2 Experiment
[Determine Injectable Content] The attacker launches various logged actions with malicious data to determine what sort of log injection is possible.
- Attacker triggers logged actions with maliciously crafted data as inputs, parameters, arguments, etc.
步骤 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.
- Directly through log file or database manipulation, modify existing log entries.
前提条件
- Target server software must be a HTTP server that performs web logging.
所需技能
所需资源
- Ability to send specially formatted HTTP request to web server
后果影响
影响范围: Integrity
技术影响: Modify Data
缓解措施
Design: Use input validation before writing to web log
Design: Validate all log data before it is output
示例实例
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.