Authenticated code execution via serialized OIDC claims
Published Feb 10, 2023 · Updated Mar 10, 2025
Deserialization in the DataHub frontend before 0.9.5 allows remote authenticated users to execute code through a crafted OIDC claim. The SSO callback passes id_token claim values to pac4j, which treats values beginning with {#sb64} as serialized Java objects and deserializes them through a permissive RestrictedObjectInputStream. OIDC SSO must be enabled and the attacker must complete the identity-provider flow; successful gadget execution can read, alter, or interrupt the frontend host.
Summary
What happened
Deserialization in the DataHub frontend before 0.9.5 allows remote authenticated users to execute code through a crafted OIDC claim. The SSO callback passes id_token claim values to pac4j, which treats values beginning with {#sb64} as serialized Java objects and deserializes them through a permissive RestrictedObjectInputStream. OIDC SSO must be enabled and the attacker must complete the identity-provider flow; successful gadget execution can read, alter, or interrupt the frontend host.
The record
- CVE
- CVE-2023-25558
- Published
- Feb 10, 2023
- Updated
- Mar 10, 2025
- Vendor
- DataHub
- Product
- DataHub
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2023CVE publishedPublication date reported by the CVE source.
- Mar 10, 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=< 0.9.5
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
No public exploit references are available in this record.
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