NetSight
low2.1No CVE yet

GHSA-8g29-8xwr-qmhr

@grackle-ai/server JSON.parse lacks try-catch logic in its gRPC Service AdapterConfig Handling

Impact

### 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 unexpected state could cause an unhandled exception that crashes the gRPC handler. Additionally, the parsed result is cast as `Record<string, unknown>` and passed to adapter methods without property validation, creating a theoretical prototype pollution surface if the database is compromised. **Affected code:** - `packages/server/src/grpc-service.ts:415` — `reconnectOrProvision` handler - `packages/server/src/grpc-service.ts:482` — `stopEnvironment` handler - `packages/server/src/grpc-service.ts:498` — `destroyEnvironment` handler ### Patches **Fix:** Wrap in try-catch and return a meaningful gRPC error: ```typescript let config: Record<string, unknown>; try { config = JSON.parse(env.adapterConfig) as Record<string, unknown>; } catch { throw new ConnectError("Invalid adapter configuration", Code.Internal); } ``` ### Workarounds Ensure database integrity. Back up the SQLite database regularly. ### Resources - CWE-754: Improper Check for Unusual or Exceptional Conditions - File: `packages/server/src/grpc-service.ts`

An attacker can exploit this over the network, with an administrator account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of outages.

Affected packages

EcosystemPackageAffectedFixed in
npm@grackle-ai/server<= 0.70.50.70.6

Weakness classification

References