CVE-2022-39366: DataHub missing JWT signature check
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.
Affected Software
Event History
Frequently Asked Questions
What is CVE-2022-39366?
CVE-2022-39366 is a vulnerability in the DataHub metadata service (GMS) where the `StatelessTokenService` does not verify the signature of JWT tokens, allowing an attacker to connect to DataHub instances as any user.
What is the severity of CVE-2022-39366?
CVE-2022-39366 has a severity rating of 9.8 (Critical).
How does CVE-2022-39366 affect DataHub?
CVE-2022-39366 affects DataHub prior to version 0.8.45, and allows an attacker to connect to DataHub instances as any user if Metadata Service authentication is enabled.
Is there a fix for CVE-2022-39366?
Yes, upgrading DataHub to version 0.8.45 or later fixes CVE-2022-39366.
What are the Common Weakness Enumerations (CWE) associated with CVE-2022-39366?
The Common Weakness Enumerations (CWE) associated with CVE-2022-39366 are CWE-347 (Improper Verification of Cryptographic Signature) and CWE-287 (Improper Authentication).