Horizon Alert
Summary of the vulnerability and why it matters
A vulnerability exists in the Hestia Control Panel, affecting how it handles custom document-root values, which could allow a low-privileged user to execute arbitrary code with root privileges. This issue arises from improper handling of single quotes when writing to configuration files, leading to a PATH injection that can be exploited when the search feature is used.
- Unescaped quotes allow code execution.
- Affects web hosting control, potentially critical systems.
- Confirm relevance and investigate exposure.
Attack Path
How an attacker could exploit the issue
An attacker with low-level access to the Hestia Control Panel can inject a malicious path into a web domain's configuration. When the system's search feature is used, this injected path can cause a script to execute arbitrary commands with root privileges, potentially leading to full system compromise.
- Requires authenticated panel user access.
- Triggered by the ordinary Search feature.
- Risk of arbitrary code execution as root.
Live Threat
Current exploitation, exposure, and threat context
A low-privileged authenticated user with a web domain could potentially execute arbitrary code as root when the search feature is used. This occurs because an improper handling of single quotes in a custom document-root value allows for the injection of a malicious PATH field into a configuration file. When the search script is invoked, it can then load this forged field, leading to the execution of a malicious command.
- System configuration data at risk.
- Arbitrary code execution via crafted search path.
- Root-level access to the system.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Hestia Control Panel's `update_object_value()` function in `func/main.sh` is vulnerable, potentially impacting application owners and infrastructure teams responsible for its deployment and management. The immediate priority is to identify all instances of Hestia Control Panel, determine their reachability and business criticality, and confirm the accountable owner for each. Subsequent remediation planning should be risk-based.
- Application and infrastructure teams own remediation.
- Verify Hestia Control Panel reachability and criticality.
- Plan risk-based remediation and vendor coordination.