Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2023-46254— Service accounts can see namespaces of other tenants in capsule-proxy

Quick assessment

Affected
projectcapsule capsule-proxy
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

capsule-proxy是允许克服 Kubernetes API Server 在列出拥有的集群范围资源方面的限制，例如 Namespace、Ingress 和 Storage Classes、Nodes 以及 Capsule 涵盖的其他资源。 capsule-proxy存在信息泄露漏洞。攻击者利用该漏洞可以获取敏感信息。

CVSS 4.3 · Medium EPSS 0.41% · P33
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2023-46254

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Service accounts can see namespaces of other tenants in capsule-proxy
Source: CVE Program / CVE List V5
Vulnerability Description
capsule-proxy is a reverse proxy for Capsule kubernetes multi-tenancy framework. A bug in the RoleBinding reflector used by `capsule-proxy` gives ServiceAccount tenant owners the right to list Namespaces of other tenants backed by the same owner kind and name. For example consider two tenants `solar` and `wind`. Tenant `solar`, owned by a ServiceAccount named `tenant-owner` in the Namespace `solar`. Tenant `wind`, owned by a ServiceAccount named `tenant-owner` in the Namespace `wind`. The Tenant owner `solar` would be able to list the namespaces of the Tenant `wind` and vice-versa, although this is not correct. The bug introduces an exfiltration vulnerability since allows the listing of Namespace resources of other Tenants, although just in some specific conditions: 1. `capsule-proxy` runs with the `--disable-caching=false` (default value: `false`) and 2. Tenant owners are ServiceAccount, with the same resource name, but in different Namespaces. This vulnerability doesn't allow any privilege escalation on the outer tenant Namespace-scoped resources, since the Kubernetes RBAC is enforcing this. This issue has been addressed in version 0.4.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
信息暴露
Source: CVE Program / CVE List V5
Vulnerability Title
capsule-proxy 信息泄露漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
capsule-proxy是允许克服 Kubernetes API Server 在列出拥有的集群范围资源方面的限制，例如 Namespace、Ingress 和 Storage Classes、Nodes 以及 Capsule 涵盖的其他资源。 capsule-proxy存在信息泄露漏洞。攻击者利用该漏洞可以获取敏感信息。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
projectcapsule capsule-proxy < 0.4.5 -

II. Public POCs for CVE-2023-46254

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-46254

请登录查看更多情报信息。

Patches & Fixes for CVE-2023-46254 (1)

Vendor Advisories for CVE-2023-46254 (1)

IV. Related Vulnerabilities

Same product: capsule-proxy
Same vendor: projectcapsule
Same weakness: CWE-200

V. Comments for CVE-2023-46254

Anonymous User
2026-01-15 06:09:10

Zaproxy alias impedit expedita quisquam pariatur exercitationem. Nemo rerum eveniet dolores rem quia dignissimos.

Leave a comment