Execution: Possible Remote Command Execution Detected

This document describes a threat finding type in Security Command Center. Threat findings are generated by threat detectors when they detect a potential threat in your cloud resources. For a full list of available threat findings, see Threat findings index.

Overview

A process was detected spawning common UNIX commands via a network socket, potentially emulating a reverse shell. This behavior suggests an attempt to establish unauthorized remote access to the system, granting the attacker the ability to execute arbitrary commands as if they were directly interacting with the compromised machine. Adversaries frequently utilize reverse shells to bypass firewall restrictions and gain persistent control over a target. The detection of command execution initiated through a socket signifies a significant security risk, as it allows for a wide range of malicious activities, including data exfiltration, lateral movement, and further exploitation, making this a critical finding that demands immediate investigation to identify the source of the connection and the actions performed.

Cloud Run Threat Detection is the source of this finding.

How to respond

To respond to this finding, do the following:

Review finding details

  1. Open the Execution: Possible Remote Command Execution Detected finding as directed in Reviewing findings. Review the details on the Summary and JSON tabs.

  2. On the Summary tab, review the information in the following sections.

    • What was detected, especially the following fields:
      • Program binary: the absolute path of the executed binary
      • Arguments: the arguments passed during binary execution
    • Affected resource, especially the following fields:

  3. On the JSON tab, note the following fields.

    • resource:
      • project_display_name: the name of the project that contains the affected Cloud Run resource
    • finding:
      • processes:
        • binary:
        • path: the full path of the executed binary
      • args: the arguments that were provided when the binary was executed

  4. Identify other findings that occurred at a similar time for the affected container. Related findings might indicate that this activity was malicious, instead of a failure to follow best practices.

  5. Review the settings of the affected container.

  6. Check the logs for the affected container.

Research attack and response methods

  1. Review MITRE ATT&CK framework entries for this finding type: Command and Scripting Interpreter.
  2. To develop a response plan, combine your investigation results with MITRE research.

Implement your response

For response recommendations, see Respond to Cloud Run threat findings.

What's next