dbcve.org
DatahubApplication · Datahub Project

CVE-2023-47640

HIGH · 8.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 0.11.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
DataHub is an open-source metadata platform. The HMAC signature for DataHub Frontend sessions was being signed using a SHA-1 HMAC with the frontend secret key. SHA1 with a 10 byte key can be brute forced using sufficient resources (i.e. state level actors with large computational capabilities). DataHub Frontend was utilizing the Play LegacyCookiesModule with default settings which utilizes a SHA1 HMAC for signing. This is compounded by using a shorter key length than recommended by default for the signing key for the randomized secret value. An authenticated attacker (or attacker who has otherwise obtained a session token) could crack the signing key for DataHub and obtain escalated privileges by generating a privileged session cookie. Due to key length being a part of the risk, deployments should update to the latest helm chart and rotate their session signing secret. All deployments using the default helm chart configurations for generating the Play secret key used for signing are affected by this vulnerability. Version 0.11.1 resolves this vulnerability. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DataHub Frontend uses SHA-1 HMAC with a short (10 byte) key for signing session cookies via Play LegacyCookiesModule default settings. This weak cryptographic configuration allows attackers with sufficient computational resources to brute force the signing key and forge privileged session cookies.

MitigationUpgrade DataHub to version 0.11.1 and rotate the session signing secret immediately to address the weak SHA-1 HMAC implementation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DatahubApplication
Affected:< 0.11.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DataHub installation
    Locate the DataHub installation and determine its version by checking the deployed datahub-frontend jar or container image tag, or by querying the running service's version endpoint if available
    Affected if The installed DataHub version is below 0.11.1
  2. Locate session signing configuration
    Find the configuration file or environment variable that defines the session signing secret for the DataHub frontend (typically in application.yml, application.conf, or an environment variable controlling Play session settings)
    Affected if No explicit session signing secret is configured, leaving the default weak key in use
  3. Verify the HMAC algorithm used for cookies
    Examine the DataHub frontend configuration for the cookie signing algorithm setting (related to Play LegacyCookiesModule or session cookie configuration)
    Affected if SHA-1 is explicitly configured or is the default algorithm for session cookie signing
  4. Check session secret key length
    Inspect the configured session signing secret value to determine its byte length
    Affected if The secret key is 10 bytes or shorter, matching the weak configuration described in the CVE

A user is affected if running any DataHub version below 0.11.1 with the default SHA-1 HMAC and short (10-byte) key configuration for session cookie signing still in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.11.1 or later
Fixed in 0.11.1
Interim mitigation

Upgrade DataHub to version 0.11.1 and rotate the session signing secret immediately to address the weak SHA-1 HMAC implementation.

Recommended fix High confidence

0.11.1

  1. Upgrade DataHub to version 0.11.1 or later using the updated helm chart
  2. After upgrading, rotate the session signing secret by generating a new Play secret key and updating your helm chart configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datahub Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47640 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data