The Server Message Block (SMB) implementation for Windows NT 4.0, 2000, XP, and Server 2003 does not properly validate…
No fixed version listed yet.Check the vendor advisory. References ↓
The Server Message Block (SMB) implementation in Windows NT 4.0, 2000, XP, and Server 2003 fails to properly validate certain SMB packets, specifically Transaction responses carrying Trans or Trans2 commands. An attacker with network access to the affected system can send crafted responses, such as Trans2 FIND_FIRST2 responses with oversized file name length fields, to execute arbitrary code remotely.
Official description · CVE.org
The Server Message Block (SMB) implementation for Windows NT 4.0, 2000, XP, and Server 2003 does not properly validate certain SMB packets, which allows remote attackers to execute arbitrary code via Transaction responses containing (1) Trans or (2) Trans2 commands, aka the "Server Message Block Vulnerability," and as demonstrated using Trans2 FIND_FIRST2 responses with large file name length fields.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Exploit-DB) appeared 4 months after disclosure. No confirmed exploitation is recorded.
- Disclosedday 0
- Public exploit codeExploit-DB+4 mo
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.