Web Authentication vulnerability in Apache SeaTunnel. Since the jwt key is hardcoded in the application, an attacker can forge
any token to log in any user.
Attacker can get secret key in /seatunnel-server/seatunnel-app/src/main/resources/application.yml and then create a token.
This issue affects Apache SeaTunnel: 1.0.0.
Users are recommended to upgrade to version 1.0.1, which fixes the issue.
References
Configurations
No configuration.
History
01 Aug 2024, 13:45
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.1 |
30 Jul 2024, 13:15
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
|
References |
|
30 Jul 2024, 09:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-07-30 09:15
Updated : 2024-08-01 13:45
NVD link : CVE-2023-48396
Mitre link : CVE-2023-48396
CVE.ORG link : CVE-2023-48396
JSON object : View
Products Affected
No product.
CWE
CWE-290
Authentication Bypass by Spoofing