dbcve.org
Triton Inference ServerApplication · Nvidia

CVE-2024-0100

HIGH · 8.1 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 24.04 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
NVIDIA Triton Inference Server for Linux contains a vulnerability in the tracing API, where a user can corrupt system files. A successful exploit of this vulnerability might lead to denial of service and data tampering.

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

NVIDIA Triton Inference Server for Linux contains a vulnerability in its tracing API that allows a user to corrupt system files, potentially leading to denial of service and data tampering. The tracing API appears to have insufficient file handling controls that permit unauthorized system file modification.

MitigationRestrict access to the tracing API to trusted users only, and implement proper file path validation and sandboxing within the tracing functionality to prevent unauthorized system file access.

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
Triton Inference ServerApplication
Affected:>= 22.09, < 24.04

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 installed Triton Inference Server version
    Run 'tritonserver --version' or check the container image tag if running via Docker. If installed as a service, check the package version via package manager (e.g., 'dpkg -l' or 'rpm -qa' depending on Linux distro).
    Affected if Version is 22.09 or later but earlier than 24.04 (the vulnerable version range).
  2. Determine if tracing API is enabled
    Examine the Triton server configuration file (typically 'config.pbtxt' or command-line arguments). Look for tracing-related settings such as 'trace' or 'tracing' in the configuration. Check for startup flags like '--trace-file' or '--trace-level'.
    Affected if Tracing is enabled and configured with a file output path.
  3. Inspect tracing file output configuration
    Review the trace file path specified in the configuration. Check if the path allows writing to system directories outside the intended model repository. Look for absolute paths pointing to sensitive system locations.
    Affected if The trace file path is writable to a non-privileged user or points to locations outside the intended trace directory.
  4. Verify access controls on tracing API endpoint
    If Triton is serving HTTP/REST API, check the endpoint access. The tracing API typically exposes an endpoint such as '/v2/tracing' or similar. Review who can make POST requests to these endpoints.
    Affected if Untrusted or unauthenticated users can access the tracing API endpoint.

The environment is affected if running a Triton Inference Server version between 22.09 and 24.03 (exclusive of 24.04) with tracing functionality enabled and accessible to untrusted 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 24.04 or later
Fixed in 24.04
Interim mitigation

Restrict access to the tracing API to trusted users only, and implement proper file path validation and sandboxing within the tracing functionality to prevent unauthorized system file access.

Recommended fix High confidence

24.04

  1. 1. Identify the current Triton Inference Server version by running 'tritonserver --version' or checking the container image tag
  2. 2. Stop the Triton Inference Server service or container
  3. 3. Upgrade Triton Inference Server to version 24.04 or later. For containerized deployments, update the image tag to 'nvcr.io/nvidia/tritonserver:24.04-py3' or newer
  4. 4. For native installations, download and install the updated package from NVIDIA's Triton Inference Server release page
  5. 5. Restart the Triton Inference Server service or container
  6. 6. Verify the version has been updated by running 'tritonserver --version'
Caveat Review the Triton Inference Server 24.04 release notes for any API or configuration changes that may affect existing deployments

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

Fix this in Triton Inference Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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