CVE-2025-64171
Description
A cross-namespace authorization flaw has been identified in the MARIN3R operator’s DiscoveryServiceCertificate resource. The flaw occurs because the operator mistakenly treats certain inputs as valid, bypassing Kubernetes Role-Based Access Control (RBAC). When a user has permission to create DiscoveryServiceCertificate objects in one Kubernetes namespace, they could exploit the vulnerability to indirectly read Secret objects in other namespaces that they should not have access to.
Statement
The severity is considered Moderate, because exploitation can be done over the network via the K8s API (AV:N), no unusual conditions are required for the attack (AC:L), however, the attacker must already hold permissions to create DiscoveryServiceCertificate objects in some namespace, without requiring elevated privileges beyond what the user already has for creating DiscoveryServiceCertificate objects. It enables unauthorized disclosure of sensitive secrets across namespace boundaries (only confidentiality impact), without affecting integrity or availability.
Mitigation
As an interim workaround, restrict permissions so that only trusted cluster administrators can create DiscoveryServiceCertificate resources until the update is applied
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data; Read Files or Directories
An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
Integrity
Technical Impact: Modify Application Data; Modify Files or Directories
An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control
Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
