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.
Metrics
Affected Vendors & Products
References
History
Fri, 11 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Thu, 10 Jul 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache seatunnel |
|
| CPEs | cpe:2.3:a:apache:seatunnel:1.0.0:*:*:*:*:*:*:* | |
| Vendors & Products |
Apache
Apache seatunnel |
Status: PUBLISHED
Assigner: apache
Published: 2024-07-30T08:15:33.731Z
Updated: 2025-02-13T17:18:18.107Z
Reserved: 2023-11-16T06:55:43.177Z
Link: CVE-2023-48396
Updated: 2024-08-02T21:30:34.963Z
Status : Analyzed
Published: 2024-07-30T09:15:02.540
Modified: 2025-07-10T18:49:05.210
Link: CVE-2023-48396
No data.