CVE-2022-39366criticalCWE-287CWE-303

CVE-2022-39366: critical vulnerability in datahub-project datahub

DataHub missing JWT signature check

Published · Updated

Follow this CVE+ Monitor datahub+ Monitor acryl-datahub

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

28Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 9.9epss 1.1%
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L
Affected products
datahub-project · datahub
Related CVEs — datahub-project datahub

In the same product, most dangerous first.

CVE-2023-25558HIGHDeserialization of untrusted data in DataHubEPSS 1.0%CVE-2023-25557HIGHServer-Side Request Forgery in DataHubEPSS 0.7%CVE-2024-22409HIGHDefault Privileges allow for high level operations for low privileged users in datahubEPSS 0.7%CVE-2023-25560HIGHJSON Injection in DataHubEPSS 0.6%CVE-2023-25559HIGHSystem account impersonation in DataHubEPSS 0.5%CVE-2023-47629HIGHPrivilege escalation through email sign-up in datahubEPSS 0.5%