CVE-2002-1872: Weak Encryption
Microsoft SQL Server 6.0 through 2000, with SQL Authentication enabled, uses weak password encryption (XOR), which allows remote attackers to sniff and decrypt the password.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Change the server authentication mode to Windows Authentication only to prevent use of SQL Authentication (which uses weak XOR password encryption).
Microsoft SQL Server 6.0 through 2000 Authentication mode = Windows Authentication only (disable SQL Authentication) - Compensating control
Restrict network access to the SQL Server instance (e.g., firewall/ACL) so only trusted hosts/networks can reach the service to reduce the risk of remote attackers sniffing SQL Authentication credentials.
Event History
Frequently Asked Questions
What is the severity of CVE-2002-1872?
CVE-2002-1872 is considered a critical vulnerability due to its potential for remote exploitation.
How do I fix CVE-2002-1872?
To mitigate CVE-2002-1872, it is recommended to disable SQL Authentication or upgrade to a version of SQL Server that uses stronger password encryption.
Which versions of Microsoft SQL Server are affected by CVE-2002-1872?
CVE-2002-1872 affects Microsoft SQL Server versions 6.0 through 2000, including various service packs.
What type of attack is possible with CVE-2002-1872?
CVE-2002-1872 allows attackers to sniff and decrypt weakly encrypted passwords, enabling unauthorized access to the database.
Is there a workaround for CVE-2002-1872?
A workaround for CVE-2002-1872 includes using integrated Windows authentication instead of SQL Authentication.