Secuno
ENNL
Book demo

CVE-2024-29037

Datahub Datahub-helm vulnerability

9.1 CRITICALEPSS 0.60%
  1. Published20 Mar 2024

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Datahub Datahub-helm≥ 0.1.143 < 0.2.182

Remediation

Fixed in
Datahub Datahub-helm≥ 0.2.182

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-758709.1
Punk versions before 0.18 for Perl allow session cookie forgery via an empty default…
CVE-2026-50398.8
TP-Link TL-WR841N v13 uses DES-CBC encryption in the TDDPv2 debug protocol with a…
CVE-2025-417449.1
Sprecher Automations SPRECON-E series uses default cryptographic keys that allow an…
CVE-2025-417429.8
Sprecher Automations SPRECON-E-C,  SPRECON-E-P, SPRECON-E-T3 is vulnerable to attack by…
CVE-2025-550499.1
Use of Default Cryptographic Key…
CVE-2025-449549.0
RUCKUS SmartZone (SZ) before 6.1.2p3 Refresh Build has a hardcoded SSH private key for…

Frequently asked

Is CVE-2024-29037 being actively exploited?

CVE-2024-29037 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.60%.

How severe is CVE-2024-29037?

CVE-2024-29037 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.60% probability of exploitation.

Which products are affected by CVE-2024-29037?

Affected products include Datahub Datahub-helm.

How do I fix CVE-2024-29037?

Upgrade affected software to a fixed version, for example Datahub Datahub-helm 0.2.182 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-29037 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.