CVE-2018-1002105

CMPT733-Group110x90 CVE-2018-1002105 الأعضاء : Abhishek Rungta, Shubham Saini, Siddhant Sood إعداد البيئة جهاز افتراضي بنظام لينكس مثل 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 تشغيل الاستغلال لقد وفرنا صور...

CVE-2024-31989

CVE-2024-31989 CVE-Exploit para Argo CD Este repositório contém um exploit para CVE-2024-31989 que tem como alvo uma instância Redis sem senha no Argo CD. Descrição O Argo CD é uma ferramenta declarativa de entrega contínua baseada em GitOps para Kubernetes. Este exploit aproveita uma...

kubetcd

Kubetcd Wrapper di https://github.com/jpbetz/auger. Automatizza il deployment dei pod scrivendo direttamente in etcd. Include diverse funzioni per la post-esplorazione di etcd compromessi. Avvertenza !WARNING Questa è una PoC, non utilizzarla in un ambiente di produzione. Scrivere direttamente in...

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...