CVE-2018-1002105

CMPT733-Group110x90 CVE-2018-1002105 成员 : Abhishek Rungta, Shubham Saini, Siddhant Sood 环境搭建 一台 Linux 虚拟机（例如 Ubuntu 20.04） Minikube 用于本地部署 Kubernetes 以下任一旧版本（1.0.x—1.9.x, 1.10.0—1.10.10, 1.11.0—1.11.4, 1.12.0—1.12.2） 运行漏洞利用 我们提供了一个 VirtualBox 镜像文件（.ova 文件） 下载它并从中创建一个虚拟机。 提供的 ova 已预配置了 docker v18....

CVE-2024-31989

CVE-2024-31989 Argo CD 的 CVE 漏洞利用 该仓库包含针对 CVE-2024-31989 的漏洞利用代码，攻击目标为 Argo CD 中未设置密码的 Redis 实例。 描述 Argo CD 是一款 Kubernetes 的声明式 GitOps 持续交付工具。此漏洞利用利用的是 Argo CD 中 Redis 实例部署时未设置密码的缺陷。 安装 1. 克隆仓库： root@kitploit: git clone https://github.com/vt0x78/CVE-2024-31989.git cd CVE-2024-31989 go build -o 或直...

kubetcd

Kubetcd https://github.com/jpbetz/auger 的封装。 它通过直接写入 etcd 来自动化 Pod 部署，并包含多项用于对已失陷 etcd 进行后渗透利用的功能。 免责声明 !WARNING 这是一个 PoC，请勿在生产环境中使用。直接写入 etcd 可能导致数据不一致或损坏，进而使kube-apiserver 逻辑无法从 etcd 检索或操作数据。可使用 KIND 部署多节点测试环境 为什么？ 主仓库 auger 提供了对 etcd 中 protobuf 序列化条目进行序列化和反序列化的主要功能。Kubetcd 是一个 PoC，它封装了这些功能，使...

CVE-2026-45760

Apache Camel K (CVE-2026-45760) contains a cross-namespace build execution vulnerability: authorized users in a Kubernetes namespace can create a Build resource that controls Pod generation in a target namespace, including the operator namespace, via externally controlled resource references and ...

CVE-2026-45760 Apache Camel K: Camel K Cross-Namespace Build Deputy Attack

Externally Controlled Reference to a Resource in Another Sphere, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel K. Authorized users in a Kubernetes namespace can create a Build resource, controlling the Pod generation in a namespace of their choice, including the...

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed.

...

SUSE CVE-2022-0811

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deploy...

CRI-O: Arbitrary code execution in cri-o via abusing “kernel.core_pattern” kernel parameter

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deploy...

AZL-37070 CVE-2022-0811 affecting package cri-o for versions less than 1.22.3-1

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deploy...

CVE-2022-0811

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deploy...

CVE-2022-0811

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deploy...

CVE-2022-0811

CVE-2022-0811 affects CRI-O and allows a pod-deployer with Kubernetes permissions to escape container boundaries and execute code as root on the cluster node. The root cause is a flaw in how CRI-O sets kernel options for a pod (notably kernel.core_pattern). Documented impact is arbitrary code exe...

CRI-O: Arbitrary code execution in cri-o via abusing “kernel.core_pattern” kernel parameter

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deploy...