zotregistry.dev/zot
Affected
- introduced
0, fixed1.4.4-0.20250522160828-8a99a3ed231f(semver)
Fixed versions
1.4.4-0.20250522160828-8a99a3ed231f
Fix
- Fixed version
1.4.4-0.20250522160828-8a99a3ed231fgo get zotregistry.dev/[email protected]
Advisory
Also known as: CVE-2025-48374, GO-2025-3705
zot logs secrets
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
Medium Basis: The source's own band: MODERATE
0, fixed 1.4.4-0.20250522160828-8a99a3ed231f (semver)1.4.4-0.20250522160828-8a99a3ed231f
1.4.4-0.20250522160828-8a99a3ed231fgo get zotregistry.dev/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0