Loading vulnerability…
CVE-2010-20114 affects VariCAD EN up to and including version 2010-2.05. The vulnerability is a stack-based buffer overflow in the application's parsing of .dwb drawing files. The software does not properly validate the length of input data embedded in a .dwb file, which allows a specially crafted file to overwrite stack memory and corrupt critical memory structures during parsing. An attacker can exploit this by delivering a malicious .dwb file and inducing a user to open it in the vulnerable application, which can lead to arbitrary code execution in the context of the user running VariCAD EN.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/varicad_dwb.rb) that exploits a stack-based buffer overflow vulnerability in VariCAD 2010-2.05 EN (CVE-2010-20114). The exploit works by generating a specially crafted .dwb file (default name: msf.dwb) that, when opened by a victim in the vulnerable version of VariCAD on Windows, triggers the buffer overflow and executes arbitrary code (the payload). The payload is customizable and can be any Metasploit-compatible payload up to 1024 bytes, avoiding certain bad characters. The attack vector is local, requiring social engineering to convince a user to open the malicious file. The module leverages SEH (Structured Exception Handler) overwrite techniques and is operational, providing a working exploit with customizable payloads. No network endpoints are involved; the only fingerprintable endpoint is the malicious file itself.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.