# CVE-2023-48396: Apache SeaTunnel Web: Authentication bypass

> Attackers can forge JWT tokens using a hardcoded key to bypass authentication and log in as any user in Apache SeaTunnel Web.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-cp2c-x2pc-fph7

## What is CVE-2023-48396?

CVE-2023-48396 is a critical vulnerability in Apache SeaTunnel Web, published on 30 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2023-48396?

2 open source packages ship an affected version, including org.apache.seatunnel:seatunnel-web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.seatunnel:seatunnel-web` | Maven | All versions | 1.0.1 |
| `org.apache.seatunnel:seatunnel-web` | Maven | All versions | 1.0.1 |

Products: Apache Seatunnel.

## How do I fix CVE-2023-48396?

Upgrade org.apache.seatunnel:seatunnel-web to 1.0.1 or later.

## Is CVE-2023-48396 being exploited?

There is no known exploitation of CVE-2023-48396 in the wild and no public exploit code.

## Other vulnerabilities in Apache SeaTunnel Web

- [CVE-2023-49198](https://insights.sbomify.com/CVE-2023-49198/): Apache SeaTunnel Web: Arbitrary file read vulnerability (high 7.5)
- [CVE-2025-32896](https://insights.sbomify.com/CVE-2025-32896/): Apache SeaTunnel: Unauthenticated insecure access (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48396 and fix it if it is affected.

What it is: CVE-2023-48396 is a critical vulnerability in Apache SeaTunnel Web, published on 30 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-48396 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.seatunnel:seatunnel-web (Maven): affected all versions; fixed in 1.0.1
- org.apache.seatunnel:seatunnel-web (Maven): affected all versions; fixed in 1.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-48396/ (Markdown: https://insights.sbomify.com/CVE-2023-48396/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-48396
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-48396
- OSV: https://osv.dev/vulnerability/CVE-2023-48396

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-48396/
Summaries are generated and may contain mistakes; the official description above is the record.