CVE-2023-48396: Apache SeaTunnel Web Authentication vulnerability

The vulnerability stems from the hardcoded JWT secretKey in application.yml. While specific function names are not explicitly provided in the commit or descriptions, the presence of a static secret in the configuration directly impacts all JWT-related functions that rely on this key. The commit fixes this by removing the hardcoded value, confirming that the key's presence in the configuration enabled the exploit. Standard JWT implementations use the secretKey for token signing/validation, so any functions handling these operations would inherit the vulnerability.