CVE-2023-25001
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 · uneditedA maliciously crafted SKP file in Autodesk Navisworks 2023 and 2022 be used to trigger use-after-free vulnerability. 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 confidenceA use-after-free vulnerability in Autodesk Navisworks 2022 and 2023 can be triggered by opening a maliciously crafted SKP file, potentially allowing arbitrary code execution. The vulnerability exists in the SKP file parsing logic where memory is accessed after being freed.
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= 2022= 2023CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Navisworks installationCheck if Autodesk Navisworks is installed by looking for its executable. Common install paths: C:\Program Files\Autodesk\Navisworks Manager 2022\ or C:\Program Files\Autodesk\Navisworks Manager 2023\, or use Control Panel > Programs and Features to list installed software.Affected if Navisworks is not installed on the system.
-
Determine installed Navisworks versionRight-click on the Navisworks executable (e.g., nwman.exe or FlickerFree.exe in the installation folder), select Properties, and check the File Version or Product Version. Alternatively, check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Navisworks for the InstallVersion value.Affected if The version is 2022 or 2023 (exactly as listed in affected versions).
-
Confirm SKP file handling capabilityNavisworks includes SKP (SketchUp) file import functionality. Check if the SKP file parser module exists in the installation directory, typically in a translator or plug-in subfolder, or attempt to identify if SKP files have been opened previously.Affected if The SKP file parsing module is present and SKP files can be opened in Navisworks.
-
Review recent file opening activityExamine recent documents or check application logs if available, or ask users whether they have opened .SKP files in Navisworks. On Windows, check recent files in %APPDATA%\Autodesk\Navisworks\ for recently opened SKP files.Affected if SKP files have been opened in the vulnerable Navisworks version.
The system is affected if Autodesk Navisworks version 2022 or 2023 is installed and SKP files can be or have been opened in it, as the use-after-free vulnerability is triggered during malicious SKP file parsing.
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 dataDo not open untrusted or unverified SKP files in vulnerable Navisworks versions. Apply vendor patches when released.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25001 — 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-2023-25001 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