CVE-2023-25558
The processing of the `id_token` is done in an unsafe manner which is not properly accounted for by the DataHub frontend.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.03%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
DataHub is an open-source metadata platform. When the DataHub frontend is configured to authenticate via SSO, it will leverage the pac4j library. The processing of the `id_token` is done in an unsafe manner which is not properly accounted for by the DataHub frontend. Specifically, if any of the id_token claims value start with the {#sb64} prefix, pac4j considers the value to be a serialized Java object and will deserialize it. This issue may lead to Remote Code Execution (RCE) in the worst case. Although a `RestrictedObjectInputStream` is in place, that puts some restriction on what classes can be deserialized, it still allows a broad range of java packages and potentially exploitable with different gadget chains. Users are advised to upgrade. There are no known workarounds. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-086.
- CVSS 3.1
- 8.8 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 1.03% probability · 62th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-502
- Affected
- datahub project/datahub
- Source
- security-advisories@github.com
References
- https://github.com/datahub-project/datahub/commit/2a182f484677d056730d6b4e9f0143e67368359fPatch
- https://github.com/datahub-project/datahub/security/advisories/GHSA-hrwp-2q5c-86wvVendor Advisory
- https://github.com/datahub-project/datahub/commit/2a182f484677d056730d6b4e9f0143e67368359fPatch
- https://github.com/datahub-project/datahub/security/advisories/GHSA-hrwp-2q5c-86wvVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.