{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.seatunnel:seatunnel-web. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-48396 in the wild and no public exploit code.","fix":"Upgrade org.apache.seatunnel:seatunnel-web to 1.0.1 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-48396 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2023-48396 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.seatunnel:seatunnel-web (Maven): affected all versions; fixed in 1.0.1\n- org.apache.seatunnel:seatunnel-web (Maven): affected all versions; fixed in 1.0.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-48396/ (Markdown: https://insights.sbomify.com/CVE-2023-48396/index.md)","id":"CVE-2023-48396","markdown":"https://insights.sbomify.com/CVE-2023-48396/index.md","name":"CVE-2023-48396","record":{"aliases":["GHSA-cp2c-x2pc-fph7"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache SeaTunnel Web","requires_auth":"none","summary":"Attackers can forge JWT tokens using a hardcoded key to bypass authentication and log in as any user in Apache SeaTunnel Web.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"seatunnel","vendor":"apache"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"Web Authentication vulnerability in Apache SeaTunnel. Since the jwt key is hardcoded in the application, an attacker can forge\nany token to log in any user.\n\nAttacker can get secret key in /seatunnel-server/seatunnel-app/src/main/resources/application.yml and then create a token.\nThis issue affects Apache SeaTunnel: 1.0.0.\n\nUsers are recommended to upgrade to version 1.0.1, which fixes the issue.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache SeaTunnel Web: Authentication bypass","id":"CVE-2023-48396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Information disclosure in Android","id":"CVE-2023-48397"},"packages":[{"ecosystem":"Maven","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.seatunnel:seatunnel-web","purl":null,"source":"GHSA-cp2c-x2pc-fph7"},{"ecosystem":"Maven","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.seatunnel:seatunnel-web","purl":"pkg:maven/org.apache.seatunnel/seatunnel-web","source":"GHSA-cp2c-x2pc-fph7"}],"prev":{"headline":"Kaifa Technology WebITR - SQL Injection","id":"CVE-2023-48395"},"products":["Apache SeaTunnel Web"],"published":"2024-07-30","related":[{"cvss_score":7.5,"headline":"Apache SeaTunnel Web: Arbitrary file read vulnerability","id":"CVE-2023-49198","kev_date_added":null,"published":"2024-08-21"},{"cvss_score":6.5,"headline":"Apache SeaTunnel: Unauthenticated insecure access","id":"CVE-2025-32896","kev_date_added":null,"published":"2025-06-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Apache Software Foundation"]},"summary":"Attackers can forge JWT tokens using a hardcoded key to bypass authentication and log in as any user in Apache SeaTunnel Web.","url":"https://insights.sbomify.com/CVE-2023-48396/"}