CVE-2024-0129
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 · uneditedNVIDIA NeMo contains a vulnerability in SaveRestoreConnector where a user may cause a path traversal issue via an unsafe .tar file extraction. A successful exploit of this vulnerability may lead to code execution 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 confidenceNVIDIA NeMo's SaveRestoreConnector contains a path traversal vulnerability during .tar file extraction. An attacker can craft a malicious tar archive containing files with path traversal sequences (e.g., ../../etc/passwd) that, when extracted, write files to arbitrary locations outside the intended directory, leading to code execution and data tampering.
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<= r2.0.0rc0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed NeMo versionRun 'pip show nemo' or 'pip show nemo-llm' to see the installed version. Also check any version file in the NeMo package directory.Affected if Version is r2.0.0rc0 or any version lower than r2.0.0 (the affected range is <= r2.0.0rc0)
-
Locate SaveRestoreConnector usageSearch codebase for imports or references to 'SaveRestoreConnector' class (e.g., grep -r 'SaveRestoreConnector' or inspect NeMo's framework modules that handle model saving/loading).Affected if The SaveRestoreConnector class is present in your NeMo installation and is being used for save/restore operations.
-
Identify tar extraction operationsInspect code paths that invoke SaveRestoreConnector's extraction logic, particularly any .tar archive handling. Look for tarfile module usage in conjunction with SaveRestoreConnector.Affected if Your application uses SaveRestoreConnector to extract .tar files, especially from untrusted or external sources.
-
Check extraction target directoryReview the configuration or code specifying the target directory for extraction. Determine if it can be influenced by user input or external sources.Affected if The target extraction directory is writable or can be controlled by an attacker, or if files are extracted to locations outside a sandboxed directory.
-
Audit for path traversal in tar handlingReview any custom or bundled tar extraction code for validation that extracted paths stay within the target directory. Check for absence of path normalization and traversal sequence checks.Affected if No validation exists to prevent '../' sequences or to ensure extracted files stay within the intended directory.
You are affected if you have NeMo version r2.0.0rc0 or earlier installed AND use the SaveRestoreConnector to extract .tar files from any source, without additional path traversal validation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement secure tar extraction by validating that all extracted file paths remain within the intended target directory, rejecting any paths containing traversal sequences (../) or absolute paths, or use a sandboxed extraction approach.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-0129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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