@grackle-ai/server
Affected
- introduced
0, fixed0.70.1(semver)
Fixed versions
0.70.1
Fix
- Fixed version
0.70.1npm install @grackle-ai/[email protected]
Advisory
Also known as: None
@grackle-ai/server: Unescaped Error String in renderPairingPage() HTML Template
Impact
The renderPairingPage() function embeds the error parameter directly into HTML without escaping:
const errorHtml = error ? `<p style="color:#e74c3c">${error}</p>` : "";
All current call sites pass hardcoded strings, so this is not exploitable today. However, the function is architecturally fragile — if a future code change passes user-controlled or dynamic content into the error parameter, it would create an XSS vulnerability.
The renderAuthorizePage() function in the same file correctly uses escapeHtml() for dynamic content, making this an inconsistency.
Affected code:
packages/server/src/index.ts:64-89 — renderPairingPage() with unescaped error interpolationpackages/server/src/index.ts:130 — renderAuthorizePage() correctly uses escapeHtml()Patches
v0.70.1
Fix: Apply escapeHtml() to the error parameter:
const errorHtml = error ? `<p style="color:#e74c3c">${escapeHtml(error)}</p>` : "";
Workarounds
No workaround needed — all current callers pass hardcoded strings.
Resources
packages/server/src/index.tsLow Basis: The source's own band: LOW
0, fixed 0.70.1 (semver)0.70.1
0.70.1npm 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