@tachybase/module-cloud-component@1.6.58
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package is designed to fetch and load configured cloud-library code, but its authenticated fetcher forwards credentials across redirects without checking the destination origin. This creates a credential-disclosure vulnerability, so warn rather than block the package itself.
Decision evidence
public snapshot- On application startup, the service loads enabled cloud libraries.
- When an enabled remote library has no cached code, the service passes its configured URL and authentication credentials to the fetcher.
- The fetcher places bearer or basic credentials in the Authorization header.
- On a redirect, the fetcher follows the response-provided Location and recursively reuses the same credentials without checking the destination origin.
- Remote code fetching is an explicit cloud-library feature, and the service loads only libraries configured as enabled.
- The credential leak requires an authenticated remote fetch and a cross-origin redirect; the package does not hard-code a collector host.
Source & flagged code
6 flaggedPackage source executes code through a VM context API.
dist/server/services/cloud-libraries-service.jsView on unpkg · L47On application startup, the service loads enabled cloud libraries.
dist/server/services/cloud-libraries-service.jsView on unpkg · L95Findings
Affected versions and remediation
This report applies to @tachybase/module-cloud-component@1.6.58.
See all versions of @tachybase/module-cloud-component for other recorded verdicts.
- Review the evidence and your use of @tachybase/module-cloud-component@1.6.58 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.