Service crash via malformed TDS headers
Published Jan 18, 2000 · Updated Aug 1, 2024
Malformed TDS headers in Microsoft SQL Server 7.0 allow remote attackers to crash the database service via crafted network packets. Microsoft identifies specially placed NULL bytes in the header as the trigger but does not disclose the internal faulty operation. Exploitation requires unauthenticated network access to port 1433; the crash is recoverable by restarting the service and grants neither database access nor administrative control.
Summary
What happened
Malformed TDS headers in Microsoft SQL Server 7.0 allow remote attackers to crash the database service via crafted network packets. Microsoft identifies specially placed NULL bytes in the header as the trigger but does not disclose the internal faulty operation. Exploitation requires unauthenticated network access to port 1433; the crash is recoverable by restarting the service and grants neither database access nor administrative control.
The record
- CVE
- CVE-1999-0999
- Published
- Jan 18, 2000
- Updated
- Aug 1, 2024
- Vendor
- Microsoft Corporation
- Product
- SQL Server
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2000CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us