Loading vulnerability…
CVE-2022-23648 is an information disclosure vulnerability in containerd’s CRI implementation on Linux affecting versions prior to 1.4.13, 1.5.10, and 1.6.1. When a container is launched from a specially crafted image configuration, the CRI plugin can incorrectly handle image-defined volumes and allow the container to obtain read-only copies of arbitrary files and directories from the host filesystem. Because the flaw occurs during container setup by the runtime, it can bypass policy-based controls applied to container configuration, including Kubernetes Pod Security Policy, and expose host data that should not be accessible from within the container.
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 a proof-of-concept (PoC) exploit for CVE-2022-23648, a vulnerability in containerd that allows containers to mount arbitrary host paths, potentially exposing sensitive files. The repository contains YAML manifests for deploying a pod and a daemonset in a Kubernetes cluster, as well as a Containerfile for building the exploit image. The main exploit capability is to mount host directories (such as /var/lib/kubelet/pki) into a container, allowing the attacker to access secrets like kubelet.key. The daemonset automates the search for Kubernetes service account tokens with cluster-admin privileges and prints them to the pod logs, enabling privilege escalation. The exploit is demonstrated using KinD with a vulnerable image. The repository is structured with configuration files for GitHub Actions (for building and pushing the container image), the Containerfile, and Kubernetes manifests for deploying the exploit. No custom binary code is present; the exploit relies on container configuration and bash scripting.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.