Skip to content

acryl-datahub missing JWT signature check

Critical severity GitHub Reviewed Published Oct 28, 2022 in datahub-project/datahub • Updated Feb 1, 2023

Package

pip acryl-datahub (pip)

Affected versions

< 0.8.45

Patched versions

0.8.45

Description

Missing JWT signature check (GHSL-2022-078)

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.

Impact

This issue may lead to an authentication bypass.

Resources

References

@maggiehays maggiehays published to datahub-project/datahub Oct 28, 2022
Published by the National Vulnerability Database Oct 28, 2022
Published to the GitHub Advisory Database Oct 31, 2022
Reviewed Oct 31, 2022
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L

EPSS score

0.605%
(79th percentile)

Weaknesses

CVE ID

CVE-2022-39366

GHSA ID

GHSA-r8gm-v65f-c973

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.