Loading vulnerability…
CVE-2017-14627 is a stack-based buffer overflow vulnerability in CyberLink LabelPrint 2.5. The vulnerability exists due to improper bounds checking when parsing the 'author' and 'name' parameters within the INFORMATION tag, the 'artist' parameter within the TRACK tag, and the 'default' parameter within the TEXT tag of an lpp project file. An attacker can craft a malicious lpp file with overly long values in these fields to trigger a buffer overflow and potentially execute arbitrary code.
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 (modules/exploits/windows/fileformat/cyberlink_lpp_bof.rb) that exploits a stack buffer overflow vulnerability (CVE-2017-14627) in CyberLink LabelPrint version 2.5 and below. The exploit works by generating a specially crafted .lpp project file, which, when opened by a victim in the vulnerable application, triggers a buffer overflow and allows arbitrary code execution. The module is written in Ruby and leverages Metasploit's FILEFORMAT exploit mixin. The default payload is a Meterpreter reverse TCP shell, but this can be customized. The exploit targets Windows 7, 8.1, and 10 (x64) systems. The attack vector is local, requiring user interaction to open the malicious file. The only fingerprintable endpoint is the .lpp file format itself. The repository is operational and provides a working exploit for the specified vulnerability.
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.