Miren Runtimeに認証回避の脆弱性、0.11.1で修正
Summary
Miren Runtimeの0.11.1未満では、RPCポート8443に届く相手が偽の証明書でクラスターの管理者権限を得られます。0.11.1へ更新して再起動し、アプリの再デプロイと認証情報の入れ替えまで進めてください。
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
Miren Runtimeの0.11.1未満では、RPCポート8443に届く相手が偽の証明書でクラスターの管理者権限を得られます。0.11.1へ更新して再起動し、アプリの再デプロイと認証情報の入れ替えまで進めてください。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| mirendevruntime | — | Not listed |
| Gomiren.dev/runtime |
< 0.11.1→ 0.11.1 |
0.11.1 |
Original description The description as published by the source.
Summary
The Miren Runtime RPC server (QUIC/HTTP3, default port :8443) requested TLS
client certificates but never verified that a presented certificate chained to
the cluster Certificate Authority. Because a client-certificate identity is
granted a blanket RBAC bypass, any party able to reach the RPC listener could
present a forged, self-signed certificate and be authenticated as a cluster
superuser — no valid CA signature, credential, or prior authorization
required.
Impact
This is a complete, unauthenticated authentication bypass against the cluster
control plane. An attacker who can reach the RPC port can perform any RPC
operation with full privileges: enumerate and manipulate entities, apps,
sandboxes, disks, and other cluster resources. This yields full compromise of
confidentiality, integrity, and availability of the cluster and everything it
orchestrates.
Exposure is network-reachability–gated only. Deployments that expose :8443
beyond a trusted network (e.g. 0.0.0.0/0) are remotely exploitable from the
internet by anyone; deployments that restrict :8443 to a trusted network are
exploitable by any party with access to that network.
Due to a lack of ability to detect if the RPC has been accessed unauthorized,
Miren recommends that all applications are redeployed and any credentials reference
in environment variables are rotated. A read-only script to help review standing access,
recent changes, and the exact sec…
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com