Skip to main content
Mallory
Back to vulnerabilities
High

Arbitrary Log File Path in NVIDIA Triton Inference Server for Linux

IdentifiersCVE-2024-0087CWE-73· External Control of File Name or…

NVIDIA Triton Inference Server for Linux contains a critical improper file path control vulnerability in its logging functionality. An attacker or user able to invoke the relevant logging API can set the log output location to an arbitrary file path; if the targeted file already exists, Triton appends log data to that file. NVIDIA classifies this issue as CWE-73. The vulnerability affects Triton Inference Server for Linux versions 22.09 through 24.03 and is fixed in version 24.04. Because attacker-controlled log appends can modify sensitive files depending on runtime privileges and filesystem layout, successful exploitation may enable follow-on compromise scenarios beyond simple file corruption.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

According to NVIDIA, successful exploitation may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The practical impact depends on what files the Triton process can write to and how appended content influences those files. In high-privilege or poorly isolated deployments, arbitrary append access to existing files can potentially be leveraged to alter configuration or startup-related files, disrupt service operation, expose sensitive information through manipulated logging targets, or support privilege escalation and further compromise.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, restrict access to Triton logging APIs to authorized users only, in line with NVIDIA's Secure Deployment Considerations guidance. Limit network exposure of management and API surfaces, especially in shared or untrusted environments. Run Triton with the least privileges necessary, constrain writable filesystem locations, use container or OS-level isolation to prevent writes to sensitive host files, and monitor for anomalous changes to log configuration and unexpected appends to existing files.

Remediation

Patch, then assume compromise.

Upgrade NVIDIA Triton Inference Server for Linux to version 24.04 or later. NVIDIA states that version 24.04 contains the fix for CVE-2024-0087. Review deployments running versions 22.09 through 24.03 and prioritize patching internet-exposed or multi-tenant instances. After upgrading, validate that logging destinations cannot be user-controlled in an unsafe manner and review filesystem permissions for the Triton service account.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NvidiaTriton Inference Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2024-0087
NVD
nvd.nist.gov/vuln/detail/CVE-2024-0087
MITRE CWE · CWE-73
External Control of File Name or Path
Vendor Advisory
nvidia.custhelp.com/app/answers/detail/a_id/5535