dbcve.org
VeristandApplication · Ni

CVE-2024-6791

HIGH · 7.8 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to after 2024 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
A directory path traversal vulnerability exists when loading a vsmodel file in NI VeriStand that may result in remote code execution. Successful exploitation requires an attacker to get a user to open a specially crafted .vsmodel file. This vulnerability affects VeriStand 2024 Q2 and prior versions.

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

A directory path traversal vulnerability exists in NI VeriStand's vsmodel file loading mechanism. By crafting a malicious .vsmodel file containing path traversal sequences (e.g., ../../), an attacker can potentially access or write files outside the intended directory, leading to remote code execution when a user opens the file.

MitigationDo not open untrusted or unsolicited .vsmodel files. Update to VeriStand versions beyond 2024 Q2 when patches become available. Apply the principle of least privilege to limit file system 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
VeristandApplication
Affected:<= 2024= 2024

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installed VeriStand version
    Use NI software licensing tools or check Add/Remove Programs for NI VeriStand version number
    Affected if Version is 2024 or any version <= 2024 (the exact version number determines if patch has been applied)
  2. Determine if vsmodel file loading is in use
    Search for .vsmodel files on systems with VeriStand installed, or review project configurations that reference vsmodel files
    Affected if vsmodel files are actively loaded or processed by VeriStand in the environment
  3. Inspect .vsmodel files for path traversal patterns
    Open or parse .vsmodel files in a text editor or hex viewer and look for sequences like ../ or ..\ in file content
    Affected if Any .vsmodel file contains path traversal sequences pointing outside the expected directory
  4. Review recent vsmodel file modifications
    Check file system for .vsmodel files modified recently, especially those in unexpected directories outside typical project folders
    Affected if There are newly created or modified .vsmodel files from untrusted or unknown sources

Your environment is affected if you have NI VeriStand 2024 or any version <= 2024 and you load or process .vsmodel files, particularly from untrusted sources.

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 a release after 2024
Interim mitigation

Do not open untrusted or unsolicited .vsmodel files. Update to VeriStand versions beyond 2024 Q2 when patches become available. Apply the principle of least privilege to limit file system access.

Recommended fix Moderate confidence

VeriStand 2024 Q3 or later (latest available version)

  1. Navigate to the official NI (National Instruments) website or NI Download Center
  2. Locate the NI VeriStand software downloads section
  3. Download the latest version of VeriStand (version after 2024 Q2)
  4. Backup any existing projects and configurations
  5. Close any running instances of VeriStand
  6. Run the installer for the new VeriStand version
  7. Follow the installation wizard prompts to complete the upgrade
  8. Verify the installation was successful by launching VeriStand

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

Fix this in Veristand Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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