dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-31849

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A path traversal vulnerability exists in the Java version of CData Connect < 23.4.8846 when running using the embedded Jetty server, which could allow an unauthenticated remote attacker to gain complete administrative access to the application.

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

A path traversal vulnerability exists in the Java version of CData Connect prior to version 23.4.8846 when running on the embedded Jetty server, allowing unauthenticated remote attackers to access files outside the intended directory boundaries and gain complete administrative access to the application.

MitigationUpgrade CData Connect Java version to 23.4.8846 or later. If immediate upgrade is not feasible, restrict network access to the embedded Jetty server interface.

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

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
High
Availability
High

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

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 CData Connect installation and version
    Locate the CData Connect installation directory and check the version file or application metadata. Common locations include /opt/cdataconnect, C:\Program Files\CData Connect, or a user-defined install path. Look for a version.txt, about dialog, or check the application startup logs for the version number.
    Affected if The installed version is any version prior to 23.4.8846
  2. Confirm Java version of CData Connect
    Check if the Java-based CData Connect is installed rather than the .NET version. Examine the installation directory for JAR files or Java-related executables. The CData Connect Java version typically includes jetty-server files or runs with java.exe.
    Affected if The Java version of CData Connect is installed (not .NET)
  3. Determine if running on embedded Jetty server
    Examine the running processes or startup configuration. Look for Jetty server processes (jetty.exe, java.exe with jetty in the command line) or check the configuration files in the installation directory for jetty.xml, start.jar, or similar Jetty-specific components.
    Affected if CData Connect is running on the embedded Jetty server (as opposed to being deployed on an external application server)
  4. Check network exposure of the web interface
    Review firewall rules, network configuration, or the server's accessible IP addresses/ports. Determine if the CData Connect web interface (typically ports 8080, 8443, or custom configured ports) is reachable from untrusted networks.
    Affected if The embedded Jetty web interface is exposed to untrusted or public networks

You are affected if you are running any version of CData Connect Java prior to 23.4.8846 on the embedded Jetty server with network accessibility to the web interface.

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 CData Connect Java version to 23.4.8846 or later. If immediate upgrade is not feasible, restrict network access to the embedded Jetty server interface.

Recommended fix High confidence

CData Connect version 23.4.8846 or later (Java version)

  1. 1. Back up the current CData Connect configuration and data directory
  2. 2. Download CData Connect version 23.4.8846 or later from the official CData software portal
  3. 3. Stop the currently running CData Connect service
  4. 4. Install the updated version following standard upgrade procedures
  5. 5. Verify the installation completed successfully
  6. 6. Restart the CData Connect service
  7. 7. Confirm the application is accessible and functioning normally
Caveat Review CData release notes for any breaking changes between your current version and 23.4.8846 before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31849 — 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-2024-31849 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