Microsoft SQL Server Convert Function Remote Memory Corruption Vulnerability
2008-07-08T00:00:00
ID SMNTC-30082 Type symantec Reporter Symantec Security Response Modified 2008-07-08T00:00:00
Description
Description
Microsoft SQL Server is prone to a remote memory-corruption vulnerability because it fails to perform adequate boundary checks on user-supplied input. Authenticated attackers can exploit this issue to execute arbitrary code and completely compromise affected computers. Failed attacks will likely cause denial-of-service conditions.
Technologies Affected
Microsoft SQL Server 2000
Microsoft SQL Server 2000 Desktop Engine
Microsoft SQL Server 2000 Desktop Engine SP1
Microsoft SQL Server 2000 Desktop Engine SP2
Microsoft SQL Server 2000 Desktop Engine SP3
Microsoft SQL Server 2000 Desktop Engine SP4
Microsoft SQL Server 2000 Itanium Edition
Microsoft SQL Server 2000 Itanium Edition SP1
Microsoft SQL Server 2000 Itanium Edition SP2
Microsoft SQL Server 2000 Itanium Edition SP3
Microsoft SQL Server 2000 Itanium Edition SP4
Microsoft SQL Server 2000 SP1
Microsoft SQL Server 2000 SP2
Microsoft SQL Server 2000 SP3
Microsoft SQL Server 2000 SP4
Microsoft Windows 2000 Advanced Server SP4
Microsoft Windows 2000 Datacenter Server SP4
Microsoft Windows 2000 Professional SP4
Microsoft Windows 2000 Server SP4
VMWare Vcenter Update Manager 1.0
VMWare Vcenter Update Manager 4.0
VMWare Vcenter Update Manager 4.1
VMWare VirtualCenter 2.5
VMWare VirtualCenter 2.5 Update 1
VMWare VirtualCenter 2.5 Update 2
VMWare VirtualCenter 2.5 Update 4
VMWare VirtualCenter 2.5 Update 5
VMWare VirtualCenter 2.5 Update 6
VMWare VirtualCenter 2.5.Update 3 Build 11983
VMWare vCenter 4.0
VMWare vCenter 4.1
Recommendations
Disallow anonymous access to services. Permit access for trusted individuals only.
Permitting access only for trusted individuals will greatly reduce the likelihood of attacks.
Run all software as a nonprivileged user with minimal access rights.
To mitigate the impact of a successful exploit, run the affected application as a user with minimal access rights.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploit attempts of memory-corruption vulnerabilities.
The vendor has released an advisory and fixes. Please see the references for more information.
{"id": "SMNTC-30082", "type": "symantec", "bulletinFamily": "software", "title": "Microsoft SQL Server Convert Function Remote Memory Corruption Vulnerability", "description": "### Description\n\nMicrosoft SQL Server is prone to a remote memory-corruption vulnerability because it fails to perform adequate boundary checks on user-supplied input. Authenticated attackers can exploit this issue to execute arbitrary code and completely compromise affected computers. Failed attacks will likely cause denial-of-service conditions.\n\n### Technologies Affected\n\n * Microsoft SQL Server 2000 \n * Microsoft SQL Server 2000 Desktop Engine \n * Microsoft SQL Server 2000 Desktop Engine SP1 \n * Microsoft SQL Server 2000 Desktop Engine SP2 \n * Microsoft SQL Server 2000 Desktop Engine SP3 \n * Microsoft SQL Server 2000 Desktop Engine SP4 \n * Microsoft SQL Server 2000 Itanium Edition \n * Microsoft SQL Server 2000 Itanium Edition SP1 \n * Microsoft SQL Server 2000 Itanium Edition SP2 \n * Microsoft SQL Server 2000 Itanium Edition SP3 \n * Microsoft SQL Server 2000 Itanium Edition SP4 \n * Microsoft SQL Server 2000 SP1 \n * Microsoft SQL Server 2000 SP2 \n * Microsoft SQL Server 2000 SP3 \n * Microsoft SQL Server 2000 SP4 \n * Microsoft Windows 2000 Advanced Server SP4 \n * Microsoft Windows 2000 Datacenter Server SP4 \n * Microsoft Windows 2000 Professional SP4 \n * Microsoft Windows 2000 Server SP4 \n * VMWare Vcenter Update Manager 1.0 \n * VMWare Vcenter Update Manager 4.0 \n * VMWare Vcenter Update Manager 4.1 \n * VMWare VirtualCenter 2.5 \n * VMWare VirtualCenter 2.5 Update 1 \n * VMWare VirtualCenter 2.5 Update 2 \n * VMWare VirtualCenter 2.5 Update 4 \n * VMWare VirtualCenter 2.5 Update 5 \n * VMWare VirtualCenter 2.5 Update 6 \n * VMWare VirtualCenter 2.5.Update 3 Build 11983 \n * VMWare vCenter 4.0 \n * VMWare vCenter 4.1 \n\n### Recommendations\n\n**Disallow anonymous access to services. Permit access for trusted individuals only.** \nPermitting access only for trusted individuals will greatly reduce the likelihood of attacks.\n\n**Run all software as a nonprivileged user with minimal access rights.** \nTo mitigate the impact of a successful exploit, run the affected application as a user with minimal access rights.\n\n**Deploy network intrusion detection systems to monitor network traffic for malicious activity.** \nDeploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.\n\n**Implement multiple redundant layers of security.** \nSince this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploit attempts of memory-corruption vulnerabilities.\n\nThe vendor has released an advisory and fixes. Please see the references for more information.\n", "published": "2008-07-08T00:00:00", "modified": "2008-07-08T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "href": "https://www.symantec.com/content/symantec/english/en/security-center/vulnerabilities/writeup.html/30082", "reporter": "Symantec Security Response", "references": [], "cvelist": [], "lastseen": "2018-03-13T12:07:43", "viewCount": 1, "enchantments": {"score": {"value": 0.6, "vector": "NONE", "modified": "2018-03-13T12:07:43", "rev": 2}, "dependencies": {"references": [{"type": "trendmicroblog", "idList": ["TRENDMICROBLOG:83CF76ED2F779A162F6FE7688839D2BF"]}], "modified": "2018-03-13T12:07:43", "rev": 2}, "vulnersScore": 0.6}, "affectedSoftware": [{"version": "2.5 Update 1 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 SP1 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Desktop Engine SP1 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Desktop Engine SP3 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Desktop Engine SP2 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "1.0 ", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 Itanium Edition SP1 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2.5 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2.5 Update 2 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 Itanium Edition SP2 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Datacenter Server SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "2.5 Update 5 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "4.0 ", "name": "VMWare vCenter", "operator": "eq"}, {"version": "2000 Server SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "2000 Professional SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "2000 Itanium Edition SP3 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Advanced Server SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "4.1 ", "name": "VMWare vCenter", "operator": "eq"}, {"version": "2000 Desktop Engine ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 SP2 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "4.0 ", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 Desktop Engine SP4 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2.5 Update 4 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2.5 Update 6 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 SP4 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2.5.Update 3 Build 11983 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 SP3 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Itanium Edition SP4 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "4.1 ", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 Itanium Edition ", "name": "Microsoft SQL Server", "operator": "eq"}], "immutableFields": []}