Loading vulnerability…
CVE-2024-31989 affects Argo CD, a GitOps continuous delivery tool for Kubernetes. The issue arises because an unprivileged pod in a different namespace on the same Kubernetes cluster can connect to Argo CD's Redis service on TCP port 6379 when Redis is not protected by strict access controls. The vulnerable design allows attackers with Redis access to manipulate cached deployment data and related cache entries used by Argo CD. Because Argo CD trusted Redis-backed cache contents without sufficient protection against unauthorized modification, an attacker could poison deployment cache data or manipulate resource-related information. The provided content specifically notes that this condition was observed even where operators believed network policies were in place, because on EKS the VPC CNI plugin requires explicit configuration to enforce network policies. The issue was patched in Argo CD 2.8.19, 2.9.15, and 2.10.10.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides an operational exploit for CVE-2024-31989, a vulnerability in Argo CD where the internal Redis instance is deployed without a password. The exploit is implemented in Go (main.go) and requires the attacker to supply a Redis cache key and a malicious pod manifest (such as the one in pod-example.txt). The exploit connects to the Redis instance (default localhost:6379), retrieves a cached manifest, replaces it with a malicious pod definition that grants host-level privileges and executes a reverse shell, and writes it back to Redis. The pod manifest mounts the host root filesystem and runs a privileged container, enabling full node compromise. The exploit is not part of a framework and is a standalone operational tool. The repository includes a README with usage instructions, a Go module definition, and an example malicious pod manifest. The main attack vector is network access to the Redis instance, and the main fingerprintable endpoints are the Redis TCP address and the host filesystem path used in the pod manifest.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously addressed Argo CD weakness in which Redis lacked password protection, allowing pods inside the cluster to manipulate deployment cache data.
A 2024 Argo CD vulnerability in which Redis had no password, allowing any pod in the cluster to poison the deployment cache.
An Argo CD privilege escalation vulnerability via Redis cache manipulation mentioned as part of vendor security history.
A previously noted Argo CD privilege escalation vulnerability via Redis cache manipulation, mentioned as vendor security history.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.