Loading vulnerability…
Altap Servant Salamander versions 2.5 with Portable Executable Viewer 2.02 (English Trial) and 2.0 with Portable Executable Viewer 1.00 (English Trial) contain a stack-based buffer overflow in the PE viewer's processing of a PDB debug filename. A PE file containing an overly long PDB debug filename can trigger the overflow and permit arbitrary code execution.
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 exploit module targeting a buffer overflow vulnerability in Altap Salamander version 2.5 or earlier (CVE-2007-3314). The exploit works by generating a specially crafted file (default name: msf-salamander-pdb.exe) that, when opened with the Portable Executable Viewer plugin in a vulnerable Salamander installation, triggers a stack-based buffer overflow via the PDB file string, allowing the attacker to overwrite the SEH and execute arbitrary code. The module allows the user to specify a payload (up to 1024 bytes, avoiding certain bad characters) which will be executed with the privileges of the user who opens the file. The exploit is local in nature, requiring user interaction to open the malicious file. The repository structure is typical for a Metasploit module, with the main exploit logic contained in a single Ruby file. No network endpoints are involved; the attack is file-based.
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.