Loading vulnerability…
CVE-2005-0353 is a stack-based buffer overflow in the Sentinel LM (Lservnt) service of SafeNet Sentinel License Manager 7.2.0.2. The vulnerable service listens on UDP port 5093 and fails to properly bound-check incoming network data. By sending an overly large UDP payload to the service, a remote attacker can trigger memory corruption and overwrite control data, resulting in arbitrary code execution in the context of the Lservnt service.
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/license/sentinel_lm7_udp.rb) that exploits a stack buffer overflow vulnerability (CVE-2005-0353) in the Sentinel License Manager (SentinelLM) service, version 7.2.0.0, on various Windows platforms. The exploit targets the service via UDP port 5093, sending a specially crafted buffer that overflows the stack and allows execution of arbitrary code (Metasploit payloads). The module includes multiple targets for different Windows versions and language packs, each with a specific return address. The exploit is operational and can be used to gain remote code execution on vulnerable systems. The code is written in Ruby and is designed to be run within the Metasploit Framework.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.