Isovalent Runtime Security - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/isovalent-runtime-security/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 12 Oct 2026 17:36:38 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDetection of Insecure Curl Execution in Kubernetes Clustershttps://feed.craftedsignal.io/briefs/2026-10-curl-insecure-flags/Mon, 12 Oct 2026 17:36:38 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-curl-insecure-flags/Threat actors may leverage curl with insecure flags within Kubernetes environments to bypass TLS certificate verification, facilitating man-in-the-middle attacks and unauthorized tool ingress.Monitoring of Kubernetes environments reveals that curl commands are frequently executed with insecure flags, such as -k or --insecure, to circumvent SSL/TLS verification during file transfers. This activity is often associated with the ingress of unauthorized tools or payloads into containerized environments. Within the Cisco Isovalent platform, defenders can monitor process execution logs to identify these commands. This behavior is notable because bypassing certificate validation exposes the infrastructure to man-in-the-middle attacks, potentially leading to sensitive data interception, service disruption, or unauthorized access to the cluster. SOC teams should investigate such executions to determine if they originate from legitimate administrative scripts or indicate malicious activity.

Attack Chain

  1. Attacker gains initial access to a Kubernetes pod, possibly via compromised container applications.
  2. Attacker attempts to download external malicious tools or configuration files using curl.
  3. The target server uses self-signed or invalid certificates, preventing standard curl requests.
  4. Attacker executes curl with the -k or --insecure flag to force the connection despite certificate validation errors.
  5. The insecure connection is established, potentially allowing an interceptor to perform a man-in-the-middle attack.
  6. The attacker successfully pulls the secondary stage payload or configuration into the container.
  7. The attacker executes the downloaded payload to conduct further malicious actions, such as lateral movement or data exfiltration.

Impact

Successful exploitation allows attackers to bypass infrastructure security controls, leading to the ingress of unauthorized payloads, potential interception of sensitive communications, and unauthorized access to the Kubernetes control plane or pod secrets. This impacts security posture by weakening the transport layer security required for cloud-native workloads.

Recommendation

  • Deploy detection logic to monitor process execution logs within the Cisco Isovalent environment for curl commands containing insecure flags.
  • Audit administrative scripts and container entrypoints that utilize curl to ensure certificate verification is enforced where feasible.
  • Use the provided Sigma rule to detect these command-line arguments in process monitoring telemetry.
  • Investigate triggered alerts by cross-referencing with pod activity and established cron jobs to reduce noise from legitimate administrative tasks.
]]>mediumadvisorykubernetescloud-securityprocess-monitoring