Loading vulnerability…
Multiple buffer overflows exist in LScube libnemesi 0.6.4-rc1 and earlier. These occur in several RTSP handler functions: a long version string in a reply can overflow handle_rtsp_pkt in rtsp_handlers.c; long headers can overflow send_pause_request, send_play_request, send_setup_request, or send_teardown_request in rtsp_send.c (e.g., via the Content-Base header); and a long Transport header can overflow get_transport_str_sctp, get_transport_str_tcp, or get_transport_str_udp in rtsp_transport.c. These vulnerabilities allow remote attackers to 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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.