dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-31850

HIGH · 8.6 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 →
95/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 Arc < 23.4.8839 when running using the embedded Jetty server, which could allow an unauthenticated remote attacker to gain access to sensitive information and perform limited actions.

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 Arc prior to version 23.4.8839 when running on the embedded Jetty server. An unauthenticated remote attacker can exploit this to access sensitive files outside the intended web root directory through specially crafted path traversal sequences in HTTP requests.

MitigationUpgrade CData Arc to version 23.4.8839 or later. If immediate upgrading is not feasible, restrict network access to the Jetty server interface using firewall rules or network segmentation to prevent unauthenticated external access.

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

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

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. Confirm CData Arc Java installation
    Locate the CData Arc installation directory. In the installation folder, identify if this is the Java version (typically indicated by a 'lib' folder containing JAR files or a startup script with 'jetty' or 'java' in the name).
    Affected if The environment has CData Arc installed and is the Java version running on embedded Jetty.
  2. Verify Jetty server is in use
    Examine the CData Arc startup configuration or running processes. Look for 'jetty' in process listings, configuration files, or the web server identifier in HTTP responses from the Arc interface.
    Affected if CData Arc is running on the embedded Jetty server (required condition for this vulnerability).
  3. Check installed version number
    Access the CData Arc administration interface or check the 'version' file in the installation directory. Compare the version to 23.4.8839.
    Affected if The installed version is earlier than 23.4.8839.
  4. Assess network exposure of Jetty interface
    Determine if the CData Arc Jetty server port (default 8080 or 8443) is accessible from untrusted networks. Check firewall rules, binding addresses (0.0.0.0 vs 127.0.0.1), and network ACLs.
    Affected if The Jetty server is network-accessible to unauthenticated attackers (required for remote exploitation).

A user is affected if CData Arc Java version is earlier than 23.4.8839, running on the embedded Jetty server, and the Jetty interface is accessible from untrusted networks.

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 Arc to version 23.4.8839 or later. If immediate upgrading is not feasible, restrict network access to the Jetty server interface using firewall rules or network segmentation to prevent unauthenticated external access.

Recommended fix Moderate confidence

CData Arc 23.4.8839 or later

  1. Identify the current CData Arc Java version installed
  2. Download CData Arc version 23.4.8839 or later from the official vendor (CData)
  3. Backup the current CData Arc installation and configuration
  4. Stop the CData Arc service
  5. Install the upgraded version (23.4.8839 or later)
  6. Restart the CData Arc service
  7. Verify the installation and test that the application functions correctly
  8. Confirm the embedded Jetty server is running the patched version
Caveat Review release notes for any configuration or behavior changes between your current version and 23.4.8839

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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