Bluewave-labs Checkmate
Checkmate: Sensitive Bearer Token Exposure via Public Status Pages When showURL Setting is Enabled
Checkmate is an open-source, self-hosted tool designed to track and monitor server hardware, uptime, response times, and incidents in real-time with beautiful visualizations. From 3.3.0 until 3.9.2, enabling the global showURL setting causes the unauthenticated GET /api/v1/status-page/:url endpoint to return complete monitor objects from server/src/controllers/statusPageController.ts. The response includes the secret field used by HttpProvider.ts as an HTTP Authorization credential, even though BaseStatusPage.tsx does not display that value, allowing visitors to extract credentials from the JSON response and use them against monitored services. This issue is fixed in version 3.9.2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.3.0, < 3.9.2
Fixed in 3.9.2
Mitigation
Upgrade Checkmate to 3.9.2 or later.
References
- Vendor advisory github.com/bluewave-labs/Checkmate/security/ad…
- Patch github.com/bluewave-labs/Checkmate/pull/3758
- Patch github.com/bluewave-labs/Checkmate/commit/cc18…
1 more
- Release notes github.com/bluewave-labs/Checkmate/releases/ta…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.