{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25562 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-25562 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25562 is a medium-severity authentication bypass vulnerability in datahub-project datahub, published on 10 Feb 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-25562 and fix it if it is affected.\n\nWhat it is: CVE-2023-25562 is a medium-severity authentication bypass vulnerability in datahub-project datahub, published on 10 Feb 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-25562 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-25562/ (Markdown: https://insights.sbomify.com/CVE-2023-25562/index.md)","id":"CVE-2023-25562","markdown":"https://insights.sbomify.com/CVE-2023-25562/index.md","name":"CVE-2023-25562","record":{"aliases":["GHSA-3974-hxjh-m3jj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DataHub metadata platform","requires_auth":"high_privilege","summary":"Attackers can bypass authentication by reusing session cookies from logged-out sessions, gaining unauthorized access to the DataHub platform.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub","vendor":"datahub"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"DataHub is an open-source metadata platform. In versions of DataHub prior to 0.8.45 Session cookies are only cleared on new sign-in events and not on logout events. Any authentication checks using the `AuthUtils.hasValidSessionCookie()` method could be bypassed by using a cookie from a logged out session, as a result any logged out session cookie may be accepted as valid and therefore lead to an authentication bypass to the system. Users are advised to upgrade. There are no known workarounds for this issue. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-083.","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":"Failure to Invalidate Session on Logout in DataHub","id":"CVE-2023-25562","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"GSS-NTLMSSP vulnerable to multiple out-of-bounds reads when decoding NTLM fields","id":"CVE-2023-25563"},"packages":[],"prev":{"headline":"Login fail open on JAAS misconfiguration in DataHub","id":"CVE-2023-25561"},"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":8.2,"headline":"JSON Injection in DataHub","id":"CVE-2023-25560","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":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 bypass authentication by reusing session cookies from logged-out sessions, gaining unauthorized access to the DataHub platform.","url":"https://insights.sbomify.com/CVE-2023-25562/"}