Heap-based buffer overflow in Microsoft SQL Server 2000 SP4, 8.00.2050, 8.00.2039, and earlier; SQL Server 2000…
No fixed version listed yet.Check the vendor advisory. References ↓
A heap-based buffer overflow exists in Microsoft SQL Server 2000 (SP4 and earlier builds such as 8.00.2050 and 8.00.2039), its Desktop Engine (MSDE 2000) and WMSDE variants, SQL Server 2005 SP2 and 9.00.1399.06, and Windows Internal Database (WYukon) SP2, in the sp_replwritetovarbin extended stored procedure. A remote attacker who has valid authentication to the server can call that procedure with a crafted set of invalid parameters to overwrite memory, causing either a denial of service through an access violation or arbitrary code execution.
Official description · CVE.org
Heap-based buffer overflow in Microsoft SQL Server 2000 SP4, 8.00.2050, 8.00.2039, and earlier; SQL Server 2000 Desktop Engine (MSDE 2000) SP4; SQL Server 2005 SP2 and 9.00.1399.06; SQL Server 2000 Desktop Engine (WMSDE) on Windows Server 2003 SP1 and SP2; and Windows Internal Database (WYukon) SP2 allows remote authenticated users to cause a denial of service (access violation exception) or execute arbitrary code by calling the sp_replwritetovarbin extended stored procedure with a set of invalid parameters that trigger memory overwrite, aka "SQL Server sp_replwritetovarbin Limited Memory Overwrite Vulnerability."
- 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 (Metasploit) was available 1 day before disclosure.
- Public exploit codeMetasploit1 day before
- Disclosedday 0
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.