dbcve.org
SeatunnelApplication · Apache

CVE-2023-49198

HIGH · 7.5 CVSS v3.1 Published 2024-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Mysql security vulnerability in Apache SeaTunnel. Attackers can read files on the MySQL server by modifying the information in the MySQL URL allowLoadLocalInfile=true&allowUrlInLocalInfile=true&allowLoadLocalInfileInPath=/&maxAllowedPacket=655360 This issue affects Apache SeaTunnel: 1.0.0. Users are recommended to upgrade to version [1.0.1], which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability allows attackers to read arbitrary files from the MySQL server by manipulating JDBC connection URL parameters (allowLoadLocalInfile, allowUrlInLocalInfile, allowLoadLocalInfileInPath) that enable dangerous file loading capabilities. This is a Server-Side Request Forgery/Local File Inclusion through MySQL connection configuration.

MitigationUpgrade Apache SeaTunnel from version 1.0.0 to version 1.0.1 or later which contains the fix for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SeatunnelApplication
Affected:= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Seatunnel installation
    Locate the Seatunnel installation directory and check the version file or use version command if available
    Affected if The installed version is exactly 1.0.0
  2. Verify MySQL connector usage
    Inspect project configuration files (pom.xml, connectors.yaml, or similar) to determine if MySQL source or sink connectors are configured
    Affected if MySQL connector is in use
  3. Examine JDBC connection configurations
    Search configuration files for JDBC connection strings that include MySQL URLs, particularly looking for allowLoadLocalInfile, allowUrlInLocalInfile, or allowLoadLocalInfileInPath parameters
    Affected if JDBC URL contains any of the parameters: allowLoadLocalInfile=true, allowUrlInLocalInfile=true, or allowLoadLocalInfileInPath is set

You are affected if running Apache Seatunnel version 1.0.0 with MySQL connector configurations that include the dangerous JDBC file-loading parameters in the connection URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache SeaTunnel from version 1.0.0 to version 1.0.1 or later which contains the fix for this vulnerability.

Recommended fix High confidence

1.0.1

  1. Download Apache SeaTunnel version 1.0.1 from the official Apache repository
  2. Upgrade your SeaTunnel installation to version 1.0.1
  3. Verify the MySQL connector configuration does not contain the vulnerable parameters (allowLoadLocalInfile, allowUrlInLocalInfile, allowLoadLocalInfileInPath)
  4. Test that MySQL connections function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seatunnel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49198 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data