DataHub up to 0.8.44 Metadata Service incorrect implementation of authentication algorithm

Summaryinfo

A vulnerability identified as problematic has been detected in DataHub up to 0.8.44. Impacted is an unknown function of the component Metadata Service. The manipulation leads to incorrect implementation of authentication algorithm. This vulnerability is traded as CVE-2022-39366. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in DataHub up to 0.8.44 and classified as critical. This issue affects some unknown functionality of the component Metadata Service. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. Using CWE to declare the problem leads to CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 10/29/2022 as GHSA-r8gm-v65f-c973. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-39366 since 09/02/2022. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 0.8.45 eliminates this vulnerability. The upgrade is hosted for download at github.com.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• DataHub

Version

• 0.8.0
• 0.8.1
• 0.8.2
• 0.8.3
• 0.8.4
• 0.8.5
• 0.8.6
• 0.8.7
• 0.8.8
• 0.8.9
• 0.8.10
• 0.8.11
• 0.8.12
• 0.8.13
• 0.8.14
• 0.8.15
• 0.8.16
• 0.8.17
• 0.8.18
• 0.8.19
• 0.8.20
• 0.8.21
• 0.8.22
• 0.8.23
• 0.8.24
• 0.8.25
• 0.8.26
• 0.8.27
• 0.8.28
• 0.8.29
• 0.8.30
• 0.8.31
• 0.8.32
• 0.8.33
• 0.8.34
• 0.8.35
• 0.8.36
• 0.8.37
• 0.8.38
• 0.8.39
• 0.8.40
• 0.8.41
• 0.8.42
• 0.8.43
• 0.8.44

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion