{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47629 exists.","fix":"No fix has been published for CVE-2023-47629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-47629 is a high-severity vulnerability in datahub-project datahub, published on 14 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-47629 and fix it if it is affected.\n\nWhat it is: CVE-2023-47629 is a high-severity vulnerability in datahub-project datahub, published on 14 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47629 exists.\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-47629/ (Markdown: https://insights.sbomify.com/CVE-2023-47629/index.md)","id":"CVE-2023-47629","markdown":"https://insights.sbomify.com/CVE-2023-47629/index.md","name":"CVE-2023-47629","record":{"aliases":["GHSA-vj59-23ww-p6c8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"DataHub metadata platform","requires_auth":"low_privilege","summary":"Attackers can escalate privileges to admin by signing up via invite link if the default user is removed but policies remain, affecting DataHub instances.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub","vendor":"datahub_project"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"DataHub is an open-source metadata platform. In affected versions sign-up through an invite link does not properly restrict users from signing up as privileged accounts. If a user is given an email sign-up link they can potentially create an admin account given certain preconditions. If the default datahub user has been removed, then the user can sign up for an account that leverages the default policies giving admin privileges to the datahub user. All DataHub instances prior to the patch that have removed the datahub user, but not the default policies applying to that user are affected. Users are advised to update to version 0.12.1 which addresses the issue. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Privilege escalation through email sign-up in datahub","id":"CVE-2023-47629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Attacker can cause Kyverno user to unintentionally consume insecure image","id":"CVE-2023-47630"},"packages":[],"prev":{"headline":"Session Expiration Misconfiguration in datahub","id":"CVE-2023-47628"},"products":["datahub"],"published":"2023-11-14","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.5,"headline":"Deserialization of untrusted data in DataHub","id":"CVE-2023-25558","kev_date_added":null,"published":"2023-02-10"},{"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["datahub-project"]},"summary":"Attackers can escalate privileges to admin by signing up via invite link if the default user is removed but policies remain, affecting DataHub instances.","url":"https://insights.sbomify.com/CVE-2023-47629/"}