Code execution via uninitialized JT parser memory
Published Jul 15, 2025 · Updated Jul 15, 2025
Use of uninitialized memory in SOLIDWORKS eDrawings 2025 SP0 through SP2 allows remote attackers to execute code through a crafted JT file. The JT parser accesses memory before properly initializing it, and malformed parser input leads to code execution in the current process. Exploitation requires a user to visit a malicious page or open the file; the resulting code runs with that user's application privileges.
Summary
What happened
Use of uninitialized memory in SOLIDWORKS eDrawings 2025 SP0 through SP2 allows remote attackers to execute code through a crafted JT file. The JT parser accesses memory before properly initializing it, and malformed parser input leads to code execution in the current process. Exploitation requires a user to visit a malicious page or open the file; the resulting code runs with that user's application privileges.
The record
- CVE
- CVE-2025-6974
- Published
- Jul 15, 2025
- Updated
- Jul 15, 2025
- Vendor
- Dassault Systèmes
- Product
- SOLIDWORKS eDrawings
- Classifications
- CWE-457, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2025CVE publishedPublication date reported by the CVE source.
- Jul 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Release SOLIDWORKS Desktop 2025 SP0 <=Release SOLIDWORKS Desktop 2025 SP2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo