Loading vulnerability…
A buffer overflow vulnerability exists in Astonsoft DeepBurner Pro and Free versions 1.8.0 and earlier. The vulnerability is triggered when a user opens a specially crafted .dbr file containing an excessively long file name tag, leading to a buffer overflow condition. This flaw allows for the execution of arbitrary code in the context of the user running the application.
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 (1 hidden).
This repository contains a single Metasploit module (deepburner_path.rb) that exploits a stack-based buffer overflow vulnerability in AstonSoft DeepBurner (versions 1.9.0.228, 1.8.0, and possibly others) on Windows. The exploit works by generating a specially crafted DeepBurner project file (.dbr) with a maliciously long 'path' attribute in a file entry, which triggers the overflow when opened by the victim. The module allows the attacker to embed a Metasploit payload (up to 512 bytes, avoiding null bytes) that will be executed with the privileges of the user who opens the file. The exploit can be delivered via email, download, or potentially via a browser if the .dbr extension is registered to DeepBurner. The repository is structured as a standard Metasploit exploit module, written in Ruby, and leverages Metasploit's fileformat and SEH exploitation mixins. No network endpoints are present; the main fingerprintable artifacts are the generated .dbr file and the crafted file entry within it.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.