CVE-2024-12669

Memory Safety in Autodesk Navisworks 2025 – 2025.4

Memory Safety

Published

17 December 2024

Modified

08 May 2025

Patch / advisory

View advisory

CVSS Score v3.1 7.8

Click a component to see what it means

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS Score 0.0030 21th percentile

Risk Priority 56 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-12669 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Autodesk Navisworks. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2024-51043

Vulnerability Data

A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can be used to cause a Heap-based Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context…

of the current process.

CWE(s): CWE-122 CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control

Adversaries may obfuscate command and control traffic to make it more difficult to detect.

attack.mitre.org →

T1001.002 Steganography Command And Control

Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.

attack.mitre.org →

T1003.001 LSASS Memory Credential Access

Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).

attack.mitre.org →

T1003.002 Security Account Manager Credential Access

Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.

attack.mitre.org →

T1003.004 LSA Secrets Credential Access

Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.

attack.mitre.org →

T1003.006 DCSync Credential Access

Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-12670Same product: Autodesk Navisworks

CVE-2024-12179Same product: Autodesk Navisworks

CVE-2024-7673Same product: Autodesk Navisworks

CVE-2024-7674Same product: Autodesk Navisworks

CVE-2024-12671Same product: Autodesk Navisworks

CVE-2024-11422Same product: Autodesk Navisworks

CVE-2024-12200Same product: Autodesk Navisworks

CVE-2024-12192Same product: Autodesk Navisworks

CVE-2024-12178Same product: Autodesk Navisworks

CVE-2024-12193Same product: Autodesk Navisworks

Affected Assets

autodesk

navisworks

2025 — 2025.4

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

SI-10 Information Input Validation good match

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match

blocks

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match

blocks

Timely patching removes known heap-overflow instances after they exist.

PR.PS-06 partial match

blocks

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.14 Information transfer partial match

removes

A.5.15 Access control partial match

removes

A.5.16 Identity management partial match

removes

A.5.17 Authentication information partial match

removes

A.5.18 Access rights partial match

removes

A.7.2 Physical entry partial match

removes