Summary
A directory traversal flaw in the cluster-admin:backup-datastore component of Controller v12.0.5 allows crafted requests to escape intended filesystem paths.
Under certain configurations, an attacker could leverage this to read or manipulate files outside the backup scope, potentially exposing sensitive system or application data.
Affected context
The vulnerability exists in environments running Controller v12.0.5 where the cluster-admin:backup-datastore component exposes a filesystem-backed backup or restore endpoint.
It becomes relevant when user-controlled path parameters are accepted by backup or datastore APIs and are mapped to directories on the host or container filesystem without strict canonicalization and validation.
Installations that mount sensitive directories, logs, or configuration paths into the backup service process are more exposed, as traversal outside the intended backup root can reach high-value files.
Exploit preconditions
- Attack surface: Network-accessible backup or datastore API exposed by the cluster-admin:backup-datastore component.
- Required access: Ability to send crafted requests to the vulnerable endpoint; this may be unauthenticated or require low-privileged credentials depending on deployment.
- Trigger point: User-supplied path, filename, or backup target parameter that is concatenated or otherwise combined with a server-side base directory.
- Why exploitation is possible: The component fails to correctly normalize and constrain user-controlled paths to a fixed root, permitting sequences like parent directory references to resolve outside the intended backup directory.
Why this happens
This vulnerability is an instance of CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
The application treats user input as part of a filesystem path and joins it with a base directory without robust normalization, canonicalization, and enforcement of a strict allowed path prefix.
As a result, specially crafted values can traverse directories (for example, by using parent directory segments) and cause the backup or datastore logic to access unintended files or directories on the underlying filesystem.
Potential impact
- Attackers may read sensitive configuration files, credentials, or keys accessible to the backup process.
- Attackers may obtain logs, database snapshots, or other data that reveal internal topology or secrets.
- In implementations that support writing or restoring files, attackers could overwrite or inject files, potentially influencing application behavior.
- Exposure of enough sensitive information could enable lateral movement or privilege escalation within the environment.
General mitigation guidance
Mitigation generally focuses on strict path handling and minimizing filesystem exposure in backup components.
Recommended defensive patterns include:
- Enforcing a fixed, non-configurable root directory for all backup-related file operations and rejecting any path that resolves outside it.
- Canonicalizing and normalizing all user-supplied paths before use, and verifying they remain within the allowed directory using robust filesystem APIs rather than string checks alone.
- Replacing user-controlled file path parameters with opaque, server-generated identifiers that map to known safe locations.
- Running the backup-datastore component with least-privilege filesystem permissions so that even if traversal is attempted, access to sensitive system areas is restricted.
- Avoiding mounting wide portions of the host filesystem into the backup service; prefer narrowly scoped, dedicated volumes.
How teams detect issues like this
Effective detection often combines code-centric and operational techniques:
- Static analysis rules targeting direct concatenation of user input into filesystem paths and uses of file APIs without prior canonicalization and bounds checking.
- Code review checklists that flag any backup or datastore logic where request parameters influence on-disk paths or filenames.
- Runtime monitoring and logging of suspicious path patterns (such as repeated parent directory sequences or access attempts to unexpected directories) in backup-related endpoints.
- Security testing and fuzzing of backup APIs with malformed and traversal-oriented payloads to validate path normalization defenses.

