dbcve.org
VredApplication · Autodesk

CVE-2024-7995

HIGH · 7.8 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 2025.2 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 maliciously crafted binary file when downloaded could lead to escalation of privileges to NT AUTHORITY/SYSTEM due to an untrusted search path being utilized in the VRED Design application. Exploitation of this vulnerability may lead to code execution.

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

The VRED Design application uses an untrusted search path when locating and loading binary files, allowing an attacker to place a malicious executable in a directory that the application searches. When a user downloads or accesses this crafted binary, the application executes it with elevated NT AUTHORITY/SYSTEM privileges, achieving privilege escalation and code execution.

MitigationUsers should only download binary files from trusted sources and avoid placing files in directories writable by other users. The vendor must fix the untrusted search path vulnerability by implementing absolute path references or secure path resolution in the application.

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
VredApplication
Affected:>= 2025, < 2025.2

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 VRED Design installation path
    Locate the VRED Design executable (vred.exe) on the system, commonly found in C:\Program Files\Autodesk\VRED\ or C:\Program Files\Autodesk\VRED Design\
    Affected if Cannot locate the VRED executable - the application may not be installed
  2. Determine installed VRED version
    Right-click on vred.exe, select Properties, and view the File Version field in the Details tab. Alternatively, run 'vred.exe -version' from command line if supported.
    Affected if Version is missing or unreadable from the executable properties
  3. Compare version against affected range
    Compare the installed version number to the affected range: >= 2025 and < 2025.2. For example, 2025.0 or 2025.1 would be affected.
    Affected if Installed version falls within >= 2025 and < 2025.2 (e.g., 2025.0, 2025.1, 2025.1.1)
  4. Check for writable directories in application search path
    Review directories where VRED loads binaries from - typically the installation folder, working directory, and any paths in the PATH environment variable accessible to the VRED process.
    Affected if Any directory in VRED's search path is writable by untrusted users (common in shared or network environments)

The environment is affected if VRED Design version is 2025.0 through 2025.1.x (i.e., >= 2025 and < 2025.2) and the application loads binaries from directories that may contain attacker-controlled files.

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 2025.2 or later
Fixed in 2025.2
Interim mitigation

Users should only download binary files from trusted sources and avoid placing files in directories writable by other users. The vendor must fix the untrusted search path vulnerability by implementing absolute path references or secure path resolution in the application.

Recommended fix High confidence

VRED 2025.2

  1. Confirm current VRED version by opening the application and checking Help > About Autodesk VRED
  2. Save and close any open projects, then close the VRED application
  3. Open a web browser and navigate to the official Autodesk support page or account portal to download VRED 2025.2
  4. Download the VRED 2025.2 installer from Autodesk's official website
  5. Uninstall the current VRED 2025.x installation via Windows Control Panel > Programs and Features
  6. Run the VRED 2025.2 installer with administrative privileges
  7. Follow the installation wizard prompts to complete the installation
  8. Launch VRED 2025.2 and verify the version via Help > About
Caveat Standard upgrade considerations apply - verify project compatibility with 2025.2 and back up custom configurations before uninstalling

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

Fix this in Vred Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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