@grantjs/server@1.22.0
Server SDK for Grant authorization - Middleware and guards for Express, Fastify, NestJS, and Next.js
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe client sends the complete inbound Cookie header to the configured Grant API during authorization checks, potentially exposing unrelated session credentials. This exceeds the SDK’s need to transmit its extracted Grant token and is credential exfiltration.
Static reason
No blocking static signals were detected.
Trigger
An application invokes an authorization check with a request containing a Cookie header.
Impact
Unrelated application session cookies or other credentials in that header can be disclosed to the Grant API host.
Mechanism
The client copies the complete incoming Cookie header into the outbound request, rather than forwarding only the Grant token it extracted.
Attack narrative
When an application checks authorization for a request, the client extracts a Grant token but also copies the entire incoming Cookie header into the outbound request to the configured Grant API. That can disclose unrelated application cookies and session credentials to that host. The forwarding happens as part of the normal authorization request.
AI rationale
The client sends the complete inbound Cookie header to the configured Grant API during authorization checks, potentially exposing unrelated session credentials. This exceeds the SDK’s need to transmit its extracted Grant token and is credential exfiltration.
Evidence
dist/grant-client-1Cd2jhvZ.js
Network endpoints1
Caller-configured apiUrl (documented example: https://api.grant.com)
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- GrantClient sends authorization checks as POST requests to the configured Grant API.
- When a request has a Cookie header, the client forwards the entire header to that API, alongside the extracted Grant token.
- The package is an authorization SDK whose middleware invokes these checks for protected requests.
Evidence against
- The destination API URL is supplied by the application, and the example uses Grant’s API.
- Cookie and bearer-token support are part of the documented authorization purpose.
- The manifest has no install or lifecycle scripts.
Behavioral surface
EnvironmentVars
Source & flagged code
4 flaggeddist/grant-client-1Cd2jhvZ.jsView file
179const fullUrl = url.startsWith("http") ? url : `${this.config.apiUrl}${url}`;
const headers = {
"Content-Type": "application/json",
...init?.headers
};
if (request) {
const token = await extractTokenFromRequest(request, this.config);
if (token) headers["Authorization"] = `Bearer ${token}`;
const req = request;
if (req.headers?.cookie) headers["Cookie"] = req.headers.cookie;
}
return fetchFn(fullUrl, {
...init,
headers,
credentials: this.config.credentials ?? "include"
});
}
};
export { extractTokenFromRequest as i, _defineProperty as n, extractBearerToke
High
Ai Review Evidence
When a request has a Cookie header, the client forwards the entire header to that API, alongside the extracted Grant token.
dist/grant-client-1Cd2jhvZ.jsView on unpkg · L179138const response = await this.fetchWithAuth("/api/auth/is-authorized", {
method: "POST",
body: JSON.stringify({
permission: {
resource,
action
},
context: { resource: options?.context?.resource || null }
})
}, request);
Medium
Stripped Provenance Metadata
GrantClient sends authorization checks as POST requests to the configured Grant API.
dist/grant-client-1Cd2jhvZ.jsView on unpkg · L138Findings
1 High4 Medium1 Low
HighAi Review Evidencedist/grant-client-1Cd2jhvZ.js
MediumEnvironment Vars
MediumStripped Provenance Metadatadist/grant-client-1Cd2jhvZ.js
MediumStripped Provenance Metadatapackage.json
MediumStripped Provenance Metadatapackage.json
LowScripts Present
Affected versions and remediation
This report applies to @grantjs/server@1.22.0.
See all versions of @grantjs/server for other recorded verdicts.
- Avoid installing @grantjs/server@1.22.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.