Chartbrew
Chartbrew: Private chart data disclosure via forgeable CB_SECRET share tokens
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, Chart share and embed tokens were signed with CB_SECRET, including known or shipped-default values in stock source and repository Docker Compose installs. The vulnerable surface is chart share-token verification and filter-access routes for private charts. An attacker who knows the deployment's CB_SECRET targets a private chart that has been shared at least once so a share-policy row exists, then forges a Chart-subject token for that chart id. The known signing key permits valid Chart tokens, and the filter-access path accepts sequential integer ids without requiring a legitimate share link; token expiry and revocation are ineffective once the secret is known. The condition requires a known or default secret and an existing share-policy row. A bare container where CB_SECRET is undefined is outside this path, and a unique secret excludes it only while the value remains unknown and unpredictable. An unauthenticated attacker can enumerate integer ids and read arbitrary private chart data, including chartData, without possessing a legitimate share link. This issue is fixed in version 5.2.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 5.2.3
Fixed in 5.2.3
Mitigation
Upgrade chartbrew to 5.2.3 or later.
References
- Vendor advisory github.com/chartbrew/chartbrew/security/adviso…
- Patch github.com/chartbrew/chartbrew/commit/07fff78d…
- Release notes github.com/chartbrew/chartbrew/releases/tag/v5…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.