Vulnerability Description
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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Seatunnel | 1.0.0 |
Related Weaknesses (CWE)
References
- http://www.openwall.com/lists/oss-security/2024/07/30/1Mailing ListThird Party Advisory
- https://lists.apache.org/thread/1tdxfjksx0vb9gtyt77wlr6rdcy1qwmwMailing ListVendor Advisory
- http://www.openwall.com/lists/oss-security/2024/07/30/1Mailing ListThird Party Advisory
- https://lists.apache.org/thread/1tdxfjksx0vb9gtyt77wlr6rdcy1qwmwMailing ListVendor Advisory
FAQ
What is CVE-2023-48396?
CVE-2023-48396 is a vulnerability with a CVSS score of 9.1 (CRITICAL). 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-...
How severe is CVE-2023-48396?
CVE-2023-48396 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2023-48396?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Seatunnel.