{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25560 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-25560 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25560 is a high-severity code injection 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-25560 and fix it if it is affected.\n\nWhat it is: CVE-2023-25560 is a high-severity code injection 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-25560 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-25560/ (Markdown: https://insights.sbomify.com/CVE-2023-25560/index.md)","id":"CVE-2023-25560","markdown":"https://insights.sbomify.com/CVE-2023-25560/index.md","name":"CVE-2023-25560","record":{"aliases":["GHSA-6rpf-5cfg-h8f3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"DataHub metadata platform","requires_auth":"low_privilege","summary":"Attackers can inject JSON to bypass authentication and create system accounts, leading to full system compromise in DataHub.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub","vendor":"datahub"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"DataHub is an open-source metadata platform. The AuthServiceClient which is responsible for creation of new accounts, verifying credentials, resetting them or requesting access tokens, crafts multiple JSON strings using format strings with user-controlled data. This means that an attacker may be able to augment these JSON strings to be sent to the backend and that can potentially be abused by including new or colliding values. This issue may lead to an authentication bypass and the creation of system accounts, which effectively can lead to full system compromise. Users are advised to upgrade. There are no known workarounds for this vulnerability. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-080.","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":"JSON Injection in DataHub","id":"CVE-2023-25560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Login fail open on JAAS misconfiguration in DataHub","id":"CVE-2023-25561"},"packages":[],"prev":{"headline":"System account impersonation in DataHub","id":"CVE-2023-25559"},"products":["datahub"],"published":"2023-02-10","related":[{"cvss_score":9.9,"headline":"DataHub missing JWT signature check","id":"CVE-2022-39366","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":8.2,"headline":"System account impersonation in DataHub","id":"CVE-2023-25559","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":7.5,"headline":"DataHub's LDAP Ingestion Source vulnerable to MITM attack through TLS downgrade","id":"CVE-2026-25644","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.5,"headline":"Server-Side Request Forgery in DataHub","id":"CVE-2023-25557","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":6.9,"headline":"Failure to Invalidate Session on Logout in DataHub","id":"CVE-2023-25562","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":5.7,"headline":"Login fail open on JAAS misconfiguration in DataHub","id":"CVE-2023-25561","kev_date_added":null,"published":"2023-02-10"}],"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 inject JSON to bypass authentication and create system accounts, leading to full system compromise in DataHub.","url":"https://insights.sbomify.com/CVE-2023-25560/"}