Loading vulnerability…
A buffer overflow vulnerability exists in SAPLPD 6.28 and earlier, included in SAP GUI 7.10, and in SAPSprint before version 1018. The vulnerability is triggered by sending long arguments to the LPD commands 0x01 through 0x05, which can cause a buffer overflow condition. This allows remote attackers to execute arbitrary code on the affected system.
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 exploit module targeting a stack buffer overflow vulnerability in SAP SAPlpd version 6.28.0.1 (SAP Release 6.40) on Windows. The exploit connects to the LPD service on TCP port 515 and sends a specially crafted payload that overflows a buffer, allowing arbitrary code execution. The module is operational and allows the attacker to specify a custom Metasploit payload (up to 400 bytes, avoiding null and newline characters). The exploit is configurable for the target's IP and port, and is designed to work against the default configuration of the vulnerable SAPlpd service. The code is written in Ruby and follows the standard Metasploit module structure, making it easy to use within the Metasploit framework. The main exploit logic is contained in the 'exploit' method, which constructs and sends the malicious buffer to the target, then invokes the Metasploit handler to manage the session if exploitation is successful.
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.