Yuval Avrahami

توجد مشكلة تتعلق برفع مستوى الامتيازات في حاويات Microsoft Azure Confidential Computing. وهذا يسمح بالوصول والتحكم غير المصرح بهما داخل بيئة الحاوية.

قد يسمح تعبير منتظم متساهل في Azure Compute Gallery لمهاجم مخول برفع مستوى الامتيازات محليًّا.

توجد ثغرة أمنية تتعلق بحقن الأوامر في Azure Compute Gallery قد تسمح لمهاجم محلي مصرح له برفع مستوى امتيازاته. تنجم هذه الثغرة الأمنية عن عدم معالجة العناصر الخاصة المستخدمة في أحد الأوامر بشكل صحيح. وهناك ثغرة أمنية ذات صلة في Microsoft ACI Confidential Containers تتعلق بوجود خلل في عملية تنقية البيانات على مستوى الإدارة، مما يتيح للمهاجم رفع مستوى امتيازاته.

The issue is related to a lack of access control in the deployment and management of confidential containers in Azure Kubernetes Service, which can be exploited by a remote attacker to elevate their privileges. This could potentially allow unauthenticated attackers to gain full control of Azure Kubernetes clusters, including stealing credentials.

The issue is related to insufficient access controls in the deployment and management of confidential containers in Azure Kubernetes Service. Exploitation of this issue may allow a remote attacker to elevate their privileges.

The issue is related to insufficient input validation in the deployment and management software of Azure Kubernetes Service Confidential Containers. This can be exploited by a remote attacker to execute arbitrary code.

The issue is related to insufficient access controls in the deployment and management of confidential containers in Microsoft Azure Kubernetes Service. It may allow a remote attacker to elevate their privileges.

A bug in the Kubernetes API server allows bypassing validation of node proxying addresses. This could enable an attacker to send authenticated requests to the API server's private network, potentially granting access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. The issue is related to the node proxying feature, which allows clients to access Kubelet endpoints, establish connections to Pods, and retrieve container logs.

The issue is related to insufficient validation in the floating IP feature, which may allow a privileged attacker to set a floating IP annotation to a pod even if the feature is not enabled. This could enable the attacker to intercept and reroute traffic to their compromised pod.

A security issue in the Kubelet and kube-proxy components allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. This means that services thought to be reachable only by other processes on the same host could be accessed by other hosts on the same LAN or by containers on the same node. For instance, a TCP service running on a node and listening on 127.0.0.1:1234 could be potentially reachable by other hosts or containers, posing a risk if the service does not require additional authentication. IPv6-only services on localhost are not affected by this issue.

A potential denial of service flaw was found in the virtio-fs shared file system daemon implementation. This issue occurs when a guest opens the maximum number of file descriptors under the shared directory, allowing a guest user or process to cause a denial of service on the host. Virtio-fs is designed to share a host file system directory with a guest via a virtio-fs device.

The issue allows a malicious client with the `clients.write` authority or scope to bypass restrictions and create clients with arbitrary scopes that the creator does not possess. This can lead to privilege escalation.

The issue concerns improper escaping in certain endpoints, allowing an authenticated malicious user with basic read privileges for one identity zone to extend those privileges to all other identity zones. This enables the malicious user to obtain private information on users, clients, and groups in all other identity zones.