CVE-2023-47640 Insecure Use of HMAC-SHA1 For Session Signing in datahub
Weak HMAC-SHA1 signing allows attackers to brute-force session keys and escalate privileges in DataHub deployments using default configurations.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-47640?
CVE-2023-47640 is a medium-severity vulnerability in datahub-project datahub, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-327
Which versions are affected by CVE-2023-47640?
It affects 1 product.
Products include Datahub Project Datahub.
How do I fix CVE-2023-47640?
No fix has been published for CVE-2023-47640 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-47640 being exploited?
There is no known exploitation of CVE-2023-47640 in the wild and no public exploit code.