Command injection attempt detected

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect Command Injection attempts on web services executing shell commands. Such security activity generally indicates that an attacker is trying to exploit a potential command injection vulnerability and execute malicious code on your server.

Strategy

Monitor command injection attempts (@appsec.security_activity:attack_attempt.command_injection) on routes executing shell commands (@_dd.appsec.enrichment.has_shell:true). Excludes 404 due to excessive noise found during testing. Monitor the presence of errors tied to command execution (@_dd.appsec.enrichment.spans_with_error:system) to detect potential failed exploits.

Generate an Application Security Signal with Medium severity if attacks on routes executing commands are found.
Raise the severity to High if errors were generated on the same trace.

Triage and response

  1. Consider blocking the attacking IP(s) temporarily to prevent them to reach deeper parts of your production systems.
  2. Investigate if the parameters are ending up in shell commands executed without sanitization. If they do, fix the code.
  3. Investigate if the host was compromised.
PREVIEWING: rtrieu/product-analytics-ui-changes