Impact

The successful exploitation of this MFA bypass vulnerability could have severe consequences for organizations utilizing Devolutions Server. An attacker who has already obtained legitimate user credentials (e.g., through phishing or credential stuffing) could then gain full access to the privileged access management system, bypassing the crucial second factor of authentication. This level of access would allow the attacker to retrieve sensitive credentials, access management tools, and potentially control critical infrastructure. The primary impact is unauthorized access, which can lead to data exfiltration, system compromise, or further lateral movement within the victim's network. The advisory does not specify observed victims or targeted sectors but emphasizes the high risk posed by this type of security bypass.

Recommendation

• Prioritize and immediately apply all available security updates from Devolutions for Devolutions Server to remediate the MFA bypass vulnerability.
• Review access logs for Devolutions Server for any suspicious authentication attempts that successfully bypass MFA or originate from unusual locations/IPs.
• Implement strict password policies and ensure robust initial authentication mechanisms to prevent initial credential compromise, as this vulnerability requires an already authenticated attacker.

Attack Chain

1. Reconnaissance: An attacker identifies a publicly exposed SurrealDB instance, potentially through port scanning or misconfiguration.
2. Vulnerability Identification: The attacker identifies the accessible WebSocket /rpc endpoint, which is vulnerable to unauthenticated input.
3. Payload Crafting: The attacker crafts a malicious JSON payload characterized by extremely deep nesting of objects ({}), arrays ([]), or parentheses (()).
4. Connection Establishment: The attacker establishes a WebSocket connection to the identified /rpc endpoint on the vulnerable SurrealDB server.
5. Malicious Request: The crafted, deeply nested JSON payload is sent by the attacker over the established WebSocket connection to the SurrealDB server.
6. Vulnerable Parsing: The SurrealDB server's value and JSON parser attempts to process the incoming payload but fails to enforce its configured recursion depth limits due to the identified vulnerability.
7. Resource Exhaustion: The uncontrolled recursive parsing of the deeply nested JSON payload rapidly consumes and exhausts the server's available memory resources.
8. Denial of Service: The SurrealDB process crashes as a result of the memory exhaustion, rendering the database service completely unavailable to legitimate users.

Impact

The primary impact of this vulnerability is a complete Denial of Service for affected SurrealDB instances. An unauthenticated remote attacker can trigger a server crash with a single malicious WebSocket message, requiring no prior credentials or query execution privileges. This vulnerability can lead to significant downtime for any applications or services relying on the SurrealDB instance, causing operational disruption and potential data inconsistencies if the server crashes unexpectedly during write operations. There are no known workarounds other than restricting network access or patching.

Recommendation

• Patch CVE-GHSA-q729-696q-g9pq immediately: Upgrade all SurrealDB instances to version 3.1.0 or later to apply the fix for this vulnerability.
• Restrict Network Access: Implement network access controls (firewalls, security groups) to restrict access to the WebSocket /rpc endpoint to only trusted clients or internal networks.

Attack Chain

1. Initial Access: An attacker gains local access to a system hosting an OpenClaw Gateway instance configured for trusted-proxy deployments. This could be via another compromised application or a low-privilege user account.
2. Discovery: The attacker probes the local system to identify the specific network port on which the OpenClaw Gateway's proxy-facing service is listening.
3. Direct Connection: The attacker establishes a direct network connection from their local process to the discovered OpenClaw Gateway port, bypassing the legitimate trusted proxy infrastructure.
4. Header Forgery: The attacker crafts and sends HTTP requests containing forged identity headers, mimicking those that would normally be generated and supplied by a trusted upstream proxy.
5. Vulnerable Processing: The affected OpenClaw Gateway instance (versions < 2026.5.18) accepts and processes these forged identity headers from the direct local connection without proper validation.
6. Identity Assumption: The Gateway attributes the operator identity specified in the forged headers to the local attacker's process.
7. Privilege Escalation / Unauthorized Actions: The attacker, now operating with the assumed operator identity, performs unauthorized actions such as modifying configurations, accessing sensitive data, or escalating privileges within the OpenClaw system.

Impact

The successful exploitation of this vulnerability can lead to significant security breaches. If an attacker can successfully forge identity headers, they can impersonate an authorized operator within the OpenClaw environment. The practical impact is highly dependent on the privileges associated with the impersonated operator and the specific configurations of the OpenClaw Gateway. This could result in unauthorized configuration changes, data manipulation or exfiltration, or complete administrative control over the OpenClaw instance. Organizations with shared hosting environments or those running multiple applications on the same server as OpenClaw are particularly at risk, as any compromised local process could leverage this flaw.

Recommendation

• Patch Immediately: Upgrade all OpenClaw Gateway instances to version 2026.5.18 or newer to remediate the vulnerability described in GHSA-rggc-m335-3wvj.
• Network Segmentation: Implement network controls to bind the trusted-proxy ingress behind the actual trusted proxy and firewall direct same-host access to the Gateway port, as mentioned in the GHSA-rggc-m335-3wvj mitigations.
• Feature Disablement: Disable the affected trusted-proxy feature if it is not explicitly required for your operational workflow to reduce the attack surface.
• Access Control: Ensure that lower-trust applications or users on the same host cannot reach the OpenClaw Gateway's proxy-facing port, following the hardening advice from GHSA-rggc-m335-3wvj.

Impact

Successful exploitation of these vulnerabilities in Dell PowerProtect Data Domain could lead to severe consequences for affected organizations. Attackers could gain elevated privileges, execute arbitrary code on the affected systems, and bypass existing security controls, potentially leading to full compromise of the data protection environment. The vulnerabilities also open avenues for Denial of Service attacks, rendering critical backup and recovery services unavailable, and Cross-Site Scripting attacks that could compromise administrative sessions. Furthermore, sensitive information could be disclosed, and critical files manipulated, undermining data integrity and confidentiality. While no specific victim count or targeted sectors were detailed in the advisory, any organization using Dell PowerProtect Data Domain is at risk of these potential impacts.

Recommendation

• Prioritize and immediately apply all available security patches and updates for Dell PowerProtect Data Domain from Dell Technologies.
• Regularly review security advisories from Dell and CERT-Bund (BSI) for new vulnerabilities affecting Dell PowerProtect Data Domain.