Description

A vulnerability was identified in Gitlawb openclaude up to 0.30.0. Impacted is the function waitForCallback of the file src/services/api/xaiOAuthCallback.ts of the component xAI OAuth Callback Handler. The manipulation of the argument Error leads to denial of service. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.3",
  "pubDate": "2026-09-14T12:17:51.223Z",
  "pubdate": "2026-09-14T12:17:51.223Z",
  "executiveSummary": "A denial of service (DoS) vulnerability exists in the xAI OAuth Callback Handler component of Gitlawb openclaude, specifically within the waitForCallback function. The vulnerability arises due to improper handling of the Error argument, allowing an unauthenticated remote attacker to trigger a service disruption.\nThis vulnerability affects all versions of openclaude up to and including 0.30.0. The flaw resides in src/services/api/xaiOAuthCallback.ts. By exploiting this weakness, a remote attacker can force the application into an unstable state, effectively terminating the service for all users. Given the public availability of an exploit, the risk profile is elevated. The project maintainers have been notified of this security deficiency, though no formal patch or response has been provided to date.",
  "technicalDetails": "The vulnerability is located in the waitForCallback function within the src/services/api/xaiOAuthCallback.ts file of the Gitlawb openclaude xAI OAuth Callback Handler. The root cause of this denial of service (DoS) condition is the insecure processing of the 'Error' argument during the OAuth callback workflow.\nTechnical analysis suggests that the implementation fails to adequately sanitize or validate the Error object passed to the function. When an attacker supplies a malformed or specifically crafted error input, the application fails to handle the exception gracefully. This leads to an unhandled exception or an unstable state in the event loop, causing the process to crash or hang indefinitely.\nThe attack flow follows a predictable pattern: 1) An attacker initiates an OAuth callback request directed toward the vulnerable endpoint. 2) The attacker crafts an Error object input that deviates from the expected schema, intentionally triggering a logic error within waitForCallback. 3) Upon receiving the request, the application executes the callback handler, which processes the malicious argument. 4) The improper handling of this argument induces a failure state that results in the termination of the service or the blockage of the event loop, thereby preventing any further service execution.\nThe vulnerability is remotely exploitable, requiring no prior authentication or administrative privileges. Because the xAI OAuth Callback Handler is intended to process external inputs, it is inherently exposed to the network. The exploitation is trivial, as the payload logic simply involves crafting an HTTP request that leverages the problematic Error argument. Once the malicious request is parsed, the vulnerability is triggered immediately, resulting in a total denial of service for the affected instance. Given that the exploit is publicly available, the barrier to entry for potential adversaries is minimal. The impact is significant, as it effectively renders the openclaude authentication service inoperable, preventing users from accessing protected resources and causing a complete outage of the impacted component."
}