First published: Fri Oct 28 2022(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Datahub | <0.8.45 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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.
CVE-2022-39366 has a severity rating of 9.8 (Critical).
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.
Yes, upgrading DataHub to version 0.8.45 or later fixes 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).