dbcve.org
DvcApplication · Trcore

CVE-2024-11310

HIGH · 7.5 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 6.4 or later.
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
The DVC from TRCore has a Path Traversal vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to read arbitrary system files.

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 · moderate confidence

DVC from TRCore contains a path traversal vulnerability that allows unauthenticated remote attackers to manipulate file path inputs and read arbitrary system files on the host system.

MitigationApply vendor patches when available; implement strict input validation with path canonicalization and whitelist-based file access controls to prevent directory traversal attacks.

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
DvcApplication
Affected:>= 6.0, < 6.4

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. Confirm Trcore Dvc is installed
    Identify the Dvc installation location by searching for executable files named 'dvc', 'Dvc', or looking in common installation directories such as /opt/trcore, /usr/local/trcore, or the application's install root. Use commands like 'which dvc' or 'find / -name "*dvc*" -type f 2>/dev/null' to locate the binary.
    Affected if The Trcore Dvc application binary is found on the system
  2. Determine the installed version
    Run the Dvc application with a version flag. Common approaches include executing 'dvc --version', 'dvc -v', checking a version file in the installation directory, or consulting the application's about/info panel if a GUI exists. Compare the output against the affected range.
    Affected if The reported version is 6.0, 6.1, 6.2, or 6.3 (any version >= 6.0 but < 6.4)
  3. Verify the web service or API endpoint is exposed
    Check if the Dvc application exposes a web interface, REST API, or network service that accepts file path inputs. Review configuration files (such as config.xml, settings.conf, or similar) for enabled network listeners, port bindings, or file upload/path parameter endpoints.
    Affected if The Dvc web service or API accepting file path parameters is accessible over the network or to unauthenticated users
  4. Identify accessible file input parameters
    Review the application's API endpoints or web forms that accept file paths as input. Look for parameters named similarly to 'file', 'path', 'filename', 'upload', or 'directory'. These are typically found in route definitions, API documentation, or by inspecting network traffic during normal operation.
    Affected if The application accepts file path parameters in any accessible endpoint without strict validation

The system is affected if Trcore Dvc version 6.0 through 6.3 is installed and exposes a network service or API that accepts file path inputs from unauthenticated users.

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
Upgrade available Upgrade to 6.4 or later
Fixed in 6.4
Interim mitigation

Apply vendor patches when available; implement strict input validation with path canonicalization and whitelist-based file access controls to prevent directory traversal attacks.

Recommended fix Moderate confidence

6.4 or later

  1. Check the current installed DVC version using: dvc --version
  2. Upgrade DVC to version 6.4 or later using the appropriate package manager (pip install dvc>=6.4 or conda install dvc>=6.4)
  3. Verify the upgrade was successful by running: dvc --version

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

Fix this in Dvc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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