SAP Business One 2005 A versions 6.80.123 and 6.80.320 contain a stack-based buffer overflow in NT_Naming_Service.exe. A remote attacker can send an oversized GIOP request to the service listening on TCP port 30000 to trigger the overflow and 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 exploit module targeting a stack buffer overflow vulnerability in SAP Business One 2005 License Manager (NT Naming Service, A and B releases). The exploit connects to the service on TCP port 30000 and sends a specially crafted payload that overflows a stack buffer, overwriting the return address and enabling arbitrary code execution. The module allows for customizable payloads (up to 400 bytes, avoiding null bytes) and is capable of executing code with the privileges of the License Manager service. The exploit is operational and leverages the Metasploit framework for payload handling and session management. The only file present is a Ruby script structured as a standard Metasploit module, and no additional endpoints or configuration files are included.
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.