dbcve.org
Triton Inference ServerApplication · Nvidia

CVE-2024-0087

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 24.04 or later.
See remediation →
94/100
Remediation priority · Urgent
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 where a user can set the logging location to an arbitrary file. If this file exists, logs are appended to the file. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, 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 · high confidence

NVIDIA Triton Inference Server allows authenticated users to configure the log file path to an arbitrary location on the filesystem. When the specified file already exists, the server appends log data to it. This arbitrary file write capability can be exploited for privilege escalation, data tampering, or code execution by targeting sensitive files such as configuration files, cron jobs, or shell scripts.

MitigationRestrict log file path configuration to a designated logging directory and implement path validation to prevent path traversal. Apply the principle of least privilege to the logging configuration.

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:>= 20.10, < 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Triton Inference Server version
    Run 'tritonserver --version' or check the Docker image tag if running in a container. On Linux, also check '/opt/tritonserver/bin/tritonserver --version' if installed via installer.
    Affected if The installed version is 20.10 or higher but lower than 24.04
  2. Verify if HTTP/REST API or GRPC endpoint is accessible
    Check if the Triton Inference Server HTTP/REST API or gRPC port (typically 8000 for HTTP, 8001 for gRPC, 8002 for metrics) is exposed and accessible to authenticated users. Confirm server is running with 'curl http://localhost:8000/v2/health/ready' or equivalent.
    Affected if The server API is accessible, allowing authenticated users to send configuration requests including log path settings
  3. Inspect logging configuration for arbitrary path settings
    Review server configuration files (config.pbtxt), environment variables (TRITON_LOG_FILE or similar), and any custom startup scripts. Look for log_file, log_dir, or similar settings.
    Affected if Logging is configured to allow arbitrary file paths outside a designated logging directory, or if the configuration allows path traversal in log file settings
  4. Check file permissions on logging directory
    Examine the directory where logs are written. If using default configuration, check /var/log/tritonInferenceServer or the configured log output path. Verify if low-privilege authenticated users can write to sensitive system locations.
    Affected if The logging configuration permits paths outside a restricted logging directory, enabling potential writes to cron, ssh keys, or configuration directories

The environment is affected if Triton Inference Server version is 20.10 through 23.xx (before 24.04) and the server exposes an API that allows authenticated users to configure log file paths to arbitrary locations on the filesystem.

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 log file path configuration to a designated logging directory and implement path validation to prevent path traversal. Apply the principle of least privilege to the logging configuration.

Recommended fix High confidence

Triton Inference Server 24.04 or later for Linux

  1. 1. Backup your current Triton Inference Server configuration and any custom model repository settings.
  2. 2. Stop the running Triton Inference Server service.
  3. 3. Upgrade Triton Inference Server to version 24.04 or later for Linux.
  4. 4. Verify the installation by checking the version: `tritonserver --version`
  5. 5. Review and restore your configuration files as needed.
  6. 6. Restart the Triton Inference Server service.
  7. 7. Validate that the logging configuration no longer allows arbitrary file paths and test that the service operates normally.

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

Fix this in Triton Inference Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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