Vulnerability Details : CVE-2022-39366
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.
Vulnerability category: BypassGain privilege
Products affected by CVE-2022-39366
- cpe:2.3:a:datahub_project:datahub:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2022-39366
0.61%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 79 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2022-39366
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
9.8
|
CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
3.9
|
5.9
|
NIST | |
|
9.9
|
CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L |
3.9
|
5.3
|
GitHub, Inc. |
CWE ids for CVE-2022-39366
-
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.Assigned by: security-advisories@github.com (Secondary)
-
The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.Assigned by: security-advisories@github.com (Secondary)
-
The product does not verify, or incorrectly verifies, the cryptographic signature for data.Assigned by: nvd@nist.gov (Primary)
References for CVE-2022-39366
-
https://codeql.github.com/codeql-query-help/java/java-missing-jwt-signature-check/
Missing JWT signature check — CodeQL query help documentationThird Party Advisory
-
https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L30
datahub/StatelessTokenService.java at aa146db611e3a4ca3aa17bb740783f789d4444d3 · datahub-project/datahub · GitHubExploit;Third Party Advisory
-
https://github.com/datahub-project/datahub/releases/tag/v0.8.45
Release DataHub v0.8.45 · datahub-project/datahub · GitHubThird Party Advisory
-
https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L134
datahub/StatelessTokenService.java at aa146db611e3a4ca3aa17bb740783f789d4444d3 · datahub-project/datahub · GitHubExploit;Third Party Advisory
-
https://github.com/datahub-project/datahub/security/advisories/GHSA-r8gm-v65f-c973
Missing JWT signature check · Advisory · datahub-project/datahub · GitHubThird Party Advisory
Jump to