@grackle-ai/server
Affected
- introduced
0, fixed0.70.4(semver)
Fixed versions
0.70.4
Fix
- Fixed version
0.70.4npm install @grackle-ai/[email protected]
Advisory
Also known as: None
@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 is small (React-markdown is configured safely, no dangerouslySetInnerHTML, Vite does not generate source maps), the absence of these headers means any future XSS vulnerability would have no secondary defense layer.
Affected code:
packages/server/src/index.ts — all res.writeHead() calls only set Content-Type, with no security headersPatches
0.70.4
Fix: Add security headers to all HTML/API responses:
res.writeHead(200, {
"Content-Type": contentType,
"Content-Security-Policy": "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:",
"X-Frame-Options": "DENY",
"X-Content-Type-Options": "nosniff"
});
Workarounds
Use a reverse proxy (nginx, Caddy) in front of the Grackle server to inject security headers.
References
packages/server/src/index.tsMedium Basis: The source's own band: MODERATE
0, fixed 0.70.4 (semver)0.70.4
0.70.4npm install @grackle-ai/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0