Loading vulnerability…
A buffer overflow vulnerability exists in the TNS Listener component of Oracle 9i Database Server on Windows systems and Oracle 8 on VM. The vulnerability is triggered when a long SERVICE_NAME parameter is provided, which is not properly handled when the TNS Listener writes an error message to a log file. This improper handling allows for a buffer overflow condition.
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.
This repository contains a single Metasploit module, 'tns_service_name.rb', which exploits a stack buffer overflow vulnerability (CVE-2002-0965) in the Oracle 8i TNS Listener service on Windows. The exploit targets Oracle 8.1.7.0.0 Standard Edition running on Windows 2000 or Windows 2003, specifically when the TNS Listener is accessible on TCP port 1521. The module crafts a malicious TNS packet with an overly long SERVICE_NAME field, triggering a buffer overflow and allowing arbitrary code execution with the privileges of the TNS Listener process. The payload is customizable via the Metasploit framework and is delivered as part of the exploit. The module includes a check method to verify if the target is vulnerable by querying the TNS Listener version. The repository is structured as a typical Metasploit exploit module, written in Ruby, and is operational for remote code execution against vulnerable Oracle TNS Listener services.
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.