GitHub Advisoryadvisory · Go

GHSA-c37v-3c8w-crq8 zot logs secrets

MEDIUM Published 2025-05-22 Modified 2025-05-28 Official page ↗
Aliases
CVE-2025-48374
Ecosystem
Go
Packages
zotregistry.dev/zot
Severity
Moderate
CVSS vector
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
Weaknesses
CWE-532
Reviewed
2025-05-22

Affected packages

• Go zotregistry.dev/zot: < 1.4.4-0.20250522160828-8a99a3ed231f → fixed in 1.4.4-0.20250522160828-8a99a3ed231f

Description

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

Related

Alias · CVE (1)

  • CVE-2025-48374 zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. vulnerability

Weakness · CWE (1)

  • CWE-532 Insertion of Sensitive Information into Log File weakness

References