Auth bypass in Datahub
CVE-2022-39366
DataHub is an open-source metadata platform. Prior to version 0.8.45, the `StatelessTokenService` of the DataHub metadata service (GMS) does not verify the signature of JWT tokens. This allows an attacker to connect to DataHub instances as any user if Metadata Service authentication is enabled. This vulnerability occurs because the `StatelessTokenService` of the Metadata service uses the `parse` method of `io.jsonwebtoken.JwtParser`, which does not perform a verification of the cryptographic token signature. This means that JWTs are accepted regardless of the used algorithm. This issue may lead to an authentication bypass. Version 0.8.45 contains a patch for the issue. There are no known workarounds.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.9 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L.
EPSS exploit prediction
EPSS 0.011, 67.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Datahub
- Datahub-Project Datahub — versions < 0.8.45
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (p-/p-). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/datahub-project/datahub/security/advisories/GHSA-r8gm-v65f-c973 (Third Party Advisory)
- codeql.github.com/codeql-query-help/java/java-missing-jwt-signature-check/ (Third Party Advisory)
- github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d… (Exploit, Third Party Advisory)
- github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d… (Exploit, Third Party Advisory)
- github.com/datahub-project/datahub/releases/tag/v0.8.45 (Third Party Advisory)