Summary
Ceph's Monitor subscription handler may allow a CephX identity with only read-only monitor permissions to access the entire configuration-key store through a crafted subscription request. Because the store can contain disk-encryption passphrases and cluster-management SSH keys, successful exploitation could enable privilege escalation, host compromise, and full cluster takeover.
Affected context
The issue occurs in Ceph Monitor deployments where the subscription handler processes Monitor subscription messages without adequately checking whether the requesting CephX identity is authorized to read configuration-key data. It is particularly significant in environments where the configuration-key store contains OSD encryption secrets or cephadm management credentials. Exploitation depends on the affected handler being reachable by a low-privileged CephX account.
Exploit preconditions
- Attack surface: Ceph Monitor subscription handling
- Required access: A valid CephX identity with at least
mon allow rcapabilities - Trigger point: Processing of a crafted
MMonSubscribemessage - Why exploitation is possible: Authorization checks do not sufficiently restrict access to the configuration-key store, allowing a read-only identity to retrieve data beyond its intended privileges
Why this happens
The vulnerability results from an authorization boundary failure in the Monitor subscription handler. The handler permits a principal with limited monitor-read permissions to access configuration-key data without verifying that the requested store contents are within that principal's authorization scope. This maps to CWE-285: Improper Authorization, where an application fails to enforce the required permissions for a sensitive operation or resource.
Potential impact
- Sensitive configuration secrets may be disclosed
- OSD disk-encryption passphrases could be exposed
- Ceph management SSH private keys could be obtained
- An attacker could escalate from a read-only account to administrative control
- Cluster nodes may be compromised through exposed management credentials
- Storage data could be accessed, altered, or disrupted
- The wider cluster and connected infrastructure could be affected
General mitigation guidance
Mitigation generally focuses on enforcing resource-level authorization for configuration-key operations and reducing the sensitivity of data available to low-privileged identities.
Common defensive patterns include:
- Enforcing explicit permission checks before returning configuration-key contents
- Separating read-only monitor access from access to sensitive configuration stores
- Applying least-privilege CephX capabilities and removing unnecessary identities
- Limiting the scope and privileges of cluster-management credentials
- Storing secrets through mechanisms that provide isolation, rotation, and access auditing
- Avoiding default configurations that grant host-wide administrative access when narrower privileges are practical
- Monitoring and restricting access to Monitor service endpoints
How teams detect issues like this
Organizations can assess for this class of issue through:
- Static and behavioral review of Monitor message handlers for missing authorization checks
- Code review signals where capability checks are performed at the service level but not at the sensitive-resource level
- Tests that verify read-only CephX identities cannot retrieve configuration-key contents
- Policy checks requiring explicit authorization for secret-store access
- Audit monitoring for unusual configuration-key reads or subscription requests from low-privileged identities
- Automated security testing that exercises authorization boundaries across CephX capability profiles

