OIDC client-secret disclosure via unsanitized startup logging
Published May 22, 2025 · Updated May 23, 2025
Sensitive-data exposure in The zot Project zot before 2.1.3 allows local users to read an OIDC client secret from startup logs. Config.Sanitize copied OpenID provider data without replacing ClientSecret, so startup logging serialized the live value to stdout. Exposure requires a configured Keycloak OIDC provider and access to the container's stdout logs; it discloses that provider's client secret.
Summary
What happened
Sensitive-data exposure in The zot Project zot before 2.1.3 allows local users to read an OIDC client secret from startup logs. Config.Sanitize copied OpenID provider data without replacing ClientSecret, so startup logging serialized the live value to stdout. Exposure requires a configured Keycloak OIDC provider and access to the container's stdout logs; it discloses that provider's client secret.
The record
- CVE
- CVE-2025-48374
- Published
- May 22, 2025
- Updated
- May 23, 2025
- Vendor
- The zot Project
- Product
- zot
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.4-0.20250522160828-8a99a3ed231f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream Keycloak startup-log proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo