GHSA-8g29-8xwr-qmhr — @grackle-ai/server
GHSA-8g29-8xwr-qmhr is a security vulnerability in @grackle-ai/server. A fix is available for @grackle-ai/server — see the affected versions and patch details below.
@grackle-ai/server JSON.parse lacks try-catch logic in its gRPC Service AdapterConfig Handling
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@grackle-ai/servernpmDescription
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—reconnectOrProvisionhandlerpackages/server/src/grpc-service.ts:482—stopEnvironmenthandlerpackages/server/src/grpc-service.ts:498—destroyEnvironmenthandler
Patches
Fix: Wrap in try-catch and return a meaningful gRPC error:
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @grackle-ai/server | all versions | 0.70.6npm install @grackle-ai/server@0.70.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @grackle-ai/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @grackle-ai/server to 0.70.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8g29-8xwr-qmhr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8g29-8xwr-qmhr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8g29-8xwr-qmhr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8g29-8xwr-qmhr in your dependencies?
O3 Security finds GHSA-8g29-8xwr-qmhr across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.