CVE-2023-47640: Insecure Use of HMAC-SHA1 For Session Signing in datahub
First published: Tue Nov 14 2023(Updated: )
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.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Datahub | <0.11.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the vulnerability ID?
The vulnerability ID is CVE-2023-47640.
What is the severity of CVE-2023-47640?
The severity of CVE-2023-47640 is high with a CVSS score of 8.8.
What is the description of CVE-2023-47640?
CVE-2023-47640 is an insecure use of HMAC-SHA1 for session signing vulnerability in DataHub, an open-source metadata platform.
Which software versions are affected by CVE-2023-47640?
The DataHub version up to and excluding 0.11.1 is affected by CVE-2023-47640.
How can CVE-2023-47640 be fixed?
To fix CVE-2023-47640, update DataHub to a version above 0.11.1 or apply the necessary patches as suggested by the vendor.
- agent/type
- agent/event
- agent/first-publish-date
- agent/softwarecombine
- agent/weakness
- agent/severity
- agent/author
- agent/title
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- agent/software-canonical-lookup-request
- vendor/datahub project
- canonical/datahub