Summary
Checkmate can expose complete monitor objects, including HTTP authorization credentials, through an unauthenticated status-page API response when the global showURL setting is enabled. An attacker who can access a public status page may extract these credentials and use them against monitored services.
Affected context
The issue occurs in Checkmate deployments using the global showURL setting with publicly accessible status pages. In this configuration, the status-page endpoint may return internal monitor fields that are not rendered by the user interface, including the secret value used as an HTTP Authorization credential.
Exploit preconditions
- Attack surface: The unauthenticated status-page API endpoint
- Required access: Ability to reach a status page or obtain its URL
- Trigger point: A GET request to the status-page endpoint while showURL is enabled
- Why exploitation is possible: The API response includes complete monitor objects and does not adequately separate display data from stored authentication secrets
Why this happens
The underlying issue is excessive exposure of sensitive fields through an unauthenticated API response. The endpoint serializes complete monitor objects instead of returning a narrowly defined public representation, allowing a credential-bearing secret field to cross a public trust boundary. This maps primarily to CWE-200, Exposure of Sensitive Information to an Unauthorized Actor, and is also related to CWE-522 because the exposed value serves as an authentication credential.
Potential impact
- An attacker may obtain HTTP Authorization credentials for monitored services.
- Exposed credentials could enable unauthorized requests to those services.
- Attackers could access, alter, or disrupt externally monitored systems, depending on credential privileges.
- Credential reuse could broaden compromise beyond the original Checkmate deployment.
General mitigation guidance
Mitigation generally focuses on minimizing data returned by public endpoints and
separating presentation data from operational secrets.
Common defensive patterns include:
- Returning an explicit allowlist of fields required by the public status-page UI.
- Excluding secrets and authentication headers from API serialization by default.
- Keeping monitoring credentials in protected server-side storage and preventing their exposure to clients.
- Requiring authentication for endpoints that return internal monitor metadata.
- Applying least privilege, narrow scope, and short validity periods to service credentials.
- Treating public status-page configuration as a security boundary and reviewing exposure-related settings accordingly.
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis and API schema checks that flag serialization of fields named secret, token, password, credential, or authorization.
- Code review of controllers and serializers serving unauthenticated or public endpoints.
- Tests that verify public responses contain only documented display fields.
- Dynamic scans comparing API responses with UI-required data and searching for credential-like values.
- Policy enforcement requiring explicit response schemas and secret-redaction controls for public APIs.
Automated security review tools may help detect sensitive-field exposure when configured with project-specific data classifications.

