{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25558 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-25558 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25558 is a high-severity unsafe deserialization vulnerability in datahub-project datahub, published on 10 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-25558 and fix it if it is affected.\n\nWhat it is: CVE-2023-25558 is a high-severity unsafe deserialization vulnerability in datahub-project datahub, published on 10 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-25558 in the wild and no public exploit code.\n\nAffected product: datahub-project datahub. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-25558/ (Markdown: https://insights.sbomify.com/CVE-2023-25558/index.md)","id":"CVE-2023-25558","markdown":"https://insights.sbomify.com/CVE-2023-25558/index.md","name":"CVE-2023-25558","record":{"aliases":["GHSA-hrwp-2q5c-86wv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"DataHub metadata platform","requires_auth":"low_privilege","summary":"Attackers can achieve remote code execution via unsafe deserialization of Java objects in SSO id_token claims when SSO is enabled.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub","vendor":"datahub_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Deserialization of untrusted data in DataHub","id":"CVE-2023-25558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"System account impersonation in DataHub","id":"CVE-2023-25559"},"packages":[],"prev":{"headline":"Server-Side Request Forgery in DataHub","id":"CVE-2023-25557"},"products":["datahub"],"published":"2023-02-10","related":[{"cvss_score":7.5,"headline":"Default Privileges allow for high level operations for low privileged users in datahub","id":"CVE-2024-22409","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":7.1,"headline":"Privilege escalation through email sign-up in datahub","id":"CVE-2023-47629","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":6.4,"headline":"Insecure Use of HMAC-SHA1 For Session Signing in datahub","id":"CVE-2023-47640","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":4.2,"headline":"Session Expiration Misconfiguration in datahub","id":"CVE-2023-47628","kev_date_added":null,"published":"2023-11-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["datahub-project"]},"summary":"Attackers can achieve remote code execution via unsafe deserialization of Java objects in SSO id_token claims when SSO is enabled.","url":"https://insights.sbomify.com/CVE-2023-25558/"}