Horizon Alert
Summary of the vulnerability and why it matters
Fooocus, an image generation software, has a critical vulnerability where an attacker could execute arbitrary code on an instance by exploiting how the web UI processes metadata. This issue stems from the unsafe use of a function that processes JSON inputs. While a fix is being developed, no patched version is currently available, meaning organizations need to assess if their use of Fooocus could be exposed.
- Attackers can run unauthorized code remotely.
- Critical flaw in image generation software needs awareness.
- Confirm relevance and exposure of this technology.
Attack Path
How an attacker could exploit the issue
An attacker could exploit this vulnerability by interacting with the Fooocus web UI, which lacks proper security for processing user-supplied metadata. If an attacker can send specially crafted JSON data containing malicious code within the metadata, the software's use of an unsafe `eval` function could allow them to execute arbitrary commands on the system running Fooocus.
- No authentication required.
- Triggered by processing metadata JSON.
- Leads to arbitrary code execution.
Live Threat
Current exploitation, exposure, and threat context
When supported by the advisory, remote attackers with access to the Fooocus web UI could execute arbitrary code on the instance by sending specially crafted metadata JSON, potentially affecting the integrity and availability of the system.
- Arbitrary code execution on the instance.
- Unsafe eval of crafted JSON metadata.
- System compromise or unauthorized actions.
Operational Fix
Recommended remediation, mitigation, and detection steps
Fooocus, an image generation tool, presents a critical remote code execution vulnerability in its web UI that could allow an attacker to execute arbitrary code. Given its typical use as a personal or internal tool, responsibility for addressing this likely falls to individual users or internal platform teams managing GPU resources, rather than dedicated enterprise security teams. The first step is to determine if any instances of Fooocus are exposed externally or accessible by unauthorized users, and then to plan remediation based on this exposure and business criticality.
- Identify and assess affected Fooocus instances.
- Confirm reachability and business criticality.
- Plan remediation with vendor coordination.