5 results · Feed
-
Low —
@grackle-ai/server JSON.parse lacks try-catch logic in its gRPC Service AdapterConfig Handling
### Impact `JSON.parse(env.adapterConfig)` is called without error handling in three locations within the gRPC service. While the data originates from the server's own SQLite database and should always be valid JSON, database corruption, migration errors, or …
-
Low —
@grackle-ai/server has a Missing Secure Flag on Session Cookie
### Impact The session cookie is set with `HttpOnly; SameSite=Lax; Path=/` but does not include the `Secure` flag. This means the cookie will be sent over plain HTTP connections. Since the server binds to `127.0.0.1` by default and uses HTTP (not HTTPS), this…
-
Medium —
@grackle-ai/server has Missing Content-Security-Policy and X-Frame-Options Headers
### Impact The HTTP server does not set `Content-Security-Policy`, `X-Frame-Options`, or `X-Content-Type-Options` headers on any response. This reduces defense-in-depth against XSS, clickjacking, and MIME-sniffing attacks. While the current XSS attack surface…
-
High —
@grackle-ai/server has Missing WebSocket Origin Header Validation
### Impact The WebSocket upgrade handler in the server validates authentication (API key token or session cookie) but does not check the `Origin` header. A malicious webpage on a different origin could initiate a WebSocket connection to `ws://localhost:3000/w…
-
Low —
@grackle-ai/server: Unescaped Error String in renderPairingPage() HTML Template
### Impact The `renderPairingPage()` function embeds the `error` parameter directly into HTML without escaping: ```typescript const errorHtml = error ? `<p style="color:#e74c3c">${error}</p>` : ""; ``` All current call sites pass hardcoded strings, so this is…