CVE-2023-25558: Deserialization of untrusted data in DataHub
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 idtoken is done in an unsafe manner which is not properly accounted for by the DataHub frontend. Specifically, if any of the idtoken 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2023-25558?
CVE-2023-25558 is a vulnerability in the DataHub open-source metadata platform that allows for unsafe processing of the 'id_token' when the frontend is configured to authenticate via Single Sign-On (SSO).
How does CVE-2023-25558 impact DataHub?
CVE-2023-25558 can allow an attacker to exploit the unsafe processing of the 'id_token' and potentially gain unauthorized access to the DataHub frontend when it is configured for SSO authentication.
What is the severity of CVE-2023-25558?
The severity of CVE-2023-25558 is rated as high with a CVSS score of 8.8.
How can CVE-2023-25558 be fixed?
To fix CVE-2023-25558, it is recommended to upgrade DataHub to a version higher than 0.9.5 that includes the relevant security patches.
What is the Common Weakness Enumeration (CWE) identifier for CVE-2023-25558?
The CWE identifier for CVE-2023-25558 is CWE-502.