Loading vulnerability…
A buffer overflow vulnerability exists in Samba versions 2.2.2 through 2.2.6. The flaw occurs when an encrypted password is processed during authentication: specifically, when a DOS codepage string is converted to a little-endian UCS2 unicode string, insufficient bounds checking allows a remote attacker to overflow a buffer. This can be triggered by sending a specially crafted encrypted password to the Samba 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.
This repository contains a single Metasploit exploit module targeting a buffer overflow vulnerability in Samba versions 2.2.2 through 2.2.6 (CVE-2002-1318). The exploit abuses improper length checking in encrypted password change requests via the SMB NTTrans protocol. The module is written in Ruby and leverages the Metasploit framework's SMB client mixin to communicate with the target over TCP port 139. The exploit crafts and sends specially crafted SMB NTTrans and NTTrans Secondary requests to trigger the overflow and inject a customizable payload (typically a shell). The payload is provided by Metasploit and can be configured by the user. The exploit is operational and can be used to gain remote code execution on vulnerable Linux systems running the affected Samba versions. The repository structure is standard for Metasploit modules, with the exploit logic contained in a single Ruby file.
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.