CVE-2022-393669.9CriticalCWE-303

CVE-2022-39366: DataHub missing JWT signature check

datahub-project · datahub

Affected: datahub-project · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.1%probability of exploitation in the next 30 days

67th percentile

050100

Higher than 67% of scored CVEs

9.9CriticalCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

datahub-project · datahub< 0.8.45

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Incorrect Implementation of Authentication Algorithm · Authentication
Vendor: datahub-project
Published: October 2022
Band: Possible (1 to 10%), October 2022

CoverageNo articles yet

No CyberSIXT article names CVE-2022-39366 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.