Perses
Perses: Missing authorization in datasource proxy allows cross-scope secret disclosure
Perses is an open-source dashboard and visualization project for observability data. From 0.43.0 until 0.54.0-rc.0, the datasource creation and unsaved datasource proxy paths authorize the caller on a Datasource or GlobalDatasource scope but do not require read permission for the separately grantable associated project or global Secret before resolving it. A low-privilege user with GlobalDatasource:create or corresponding project datasource creation rights can attach a project or global Secret that the user cannot otherwise read, point the datasource at a service controlled by the user, and cause Perses to send the decrypted secret in plaintext, bypassing project and global scope separation. This issue is fixed in version 0.54.0-rc.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.43.0, < 0.54.0-rc.0
Fixed in 0.54.0-rc.0
Mitigation
Upgrade perses to 0.54.0-rc.0 or later.
References
- Vendor advisory github.com/perses/perses/security/advisories/G…
- Patch github.com/perses/perses/commit/2368c9ef4eb0a7…
- Release notes github.com/perses/perses/releases/tag/v0.54.0-…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.