{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-29037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-29037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29037 is a critical vulnerability in acryldata datahub-helm, published on 20 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-29037 and fix it if it is affected.\n\nWhat it is: CVE-2024-29037 is a critical vulnerability in acryldata datahub-helm, published on 20 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-29037 in the wild and no public exploit code.\n\nAffected product: acryldata datahub-helm. 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-2024-29037/ (Markdown: https://insights.sbomify.com/CVE-2024-29037/index.md)","id":"CVE-2024-29037","markdown":"https://insights.sbomify.com/CVE-2024-29037/index.md","name":"CVE-2024-29037","record":{"aliases":["GHSA-82p6-9h7m-9h8j"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"DataHub Helm charts","requires_auth":"none","summary":"Attackers can generate valid personal access tokens using a static default secret key if Metadata Service Authentication was manually enabled during specific deployments.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub-helm","vendor":"datahub"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-1394","name":"Use of Default Cryptographic Key"}],"description":"datahub-helm provides the Kubernetes Helm charts for deploying Datahub and its dependencies on a Kubernetes cluster. Starting in version 0.1.143 and prior to version 0.2.182, due to configuration issues in the helm chart, if there was a successful initial deployment during a limited window of time, personal access tokens were possibly created with a default secret key. Since the secret key is a static, publicly available value, someone could inspect the algorithm used to generate personal access tokens and generate their own for an instance. Deploying with Metadata Service Authentication enabled would have been difficult during window of releases. If someone circumvented the helm settings and manually set Metadata Service Authentication to be enabled using environment variables directly, this would skip over the autogeneration logic for the Kubernetes Secrets and DataHub GMS would default to the signing key specified statically in the application.yml. Most deployments probably did not attempt to circumvent the helm settings to enable Metadata Service Authentication during this time, so impact is most likely limited. Any deployments with Metadata Service Authentication enabled should ensure that their secret values are properly randomized. Version 0.2.182 contains a patch for this issue. As a workaround, one may reset the token signing key to be a random value, which will invalidate active personal access tokens.","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":"Default secret use for initial deployment","id":"CVE-2024-29037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"tpm2 does not detect if quote was not generated by TPM","id":"CVE-2024-29038"},"packages":[],"prev":{"headline":"Saleor Storefront session leak in cache","id":"CVE-2024-29036"},"products":["datahub-helm"],"published":"2024-03-20","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["acryldata"]},"summary":"Attackers can generate valid personal access tokens using a static default secret key if Metadata Service Authentication was manually enabled during specific deployments.","url":"https://insights.sbomify.com/CVE-2024-29037/"}