GHSA-c37v-3c8w-crq8
Suggest an improvement- Source
- https://github.com/advisories/GHSA-c37v-3c8w-crq8
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/05/GHSA-c37v-3c8w-crq8/GHSA-c37v-3c8w-crq8.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-c37v-3c8w-crq8
- Aliases
- Published
- 2025-05-22T20:33:39Z
- Modified
- 2025-05-28T19:47:48Z
- Severity
-
- 5.5 (Medium) CVSS_V4 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P CVSS Calculator
- Summary
- zot logs secrets
- Details
-
Summary
When using Keycloak as an oidc provider, the clientsecret gets printed into the container stdout logs for an example at container startup.
Details
Container Image (15.04.2025): ghcr.io/project-zot/zot-linux-amd64:latest Here is an example how the configuration can look which causes the above stated problem:
http: address: "0.0.0.0" port: 5000 externalUrl: "https://zot.example.com" auth: { failDelay: 1, openid: { providers: { oidc: { name: "Keycloak", clientid: "zot-client-id", clientsecret: fsdfkmmiwljasdklfsjaskldjfkljewijrf234i52k3j45l, keypath: "", issuer: "https://keycloak.example.com/realms/example", scopes: ["openid"] } } } }PoC
Set up a blank new zot k8s deployment with the code snippet above.
Impact
exposure of secrets, on configuring a oidc provider
- Database specific
{ "github_reviewed_at": "2025-05-22T20:33:39Z", "cwe_ids": [ "CWE-532" ], "nvd_published_at": "2025-05-22T21:15:37Z", "severity": "MODERATE", "github_reviewed": true }- References
Affected packages
Go / zotregistry.dev/zot
Package
- Name
- zotregistry.dev/zot
- View open source insights on deps.dev
- Purl
- pkg:golang/zotregistry.dev/zot