Microsoft is investigating a newly reported flaw that could put websites at risk of attack. The company has issued an advisory on the vulnerability, which affects Windows XP Professional SP2, Windows Server 2003, Windows Vista and Windows Server 2008. The problem exists in Windows' handling of code within its Internet Information Services (IIS) and SQL Server.
If exploited, the vulnerability could allow a user to elevate access privileges to that of the LocalSystem administration tool. Microsoft warned that companies that make extensive use of user-provided code, such as site hosts, are especially vulnerable.
View: The full story @ vnunet
If exploited, the vulnerability could allow a user to elevate access privileges to that of the LocalSystem administration tool. Microsoft warned that companies that make extensive use of user-provided code, such as site hosts, are especially vulnerable.
View: The full story @ vnunet
As for SQL Server, I don't know it's flaw history but either way it seems that MS is getting better and faster at patching and overall security.
...
According to the linked Advisory (CVE, or Technet) this isn't a bug in IIS or SQL server, it's Windows.
Do a google about nihaorr1.com and you will see how many servers are affected.
The flaw actually destroys your SQL database by injecting a javascript that redirects to nihaorr1.com and the only way to recover is to do the workaround steps that MS suggests and then restore the SQL database from a backup.
Yes if you don't have a backup you are screwed....
crapinsecure code allowing SQL injection attacks to be successful. The flaw in the Microsoft Advisory is completely different.User-provided code running in IIS, for example ISAPI filters and extensions, and ASP.NET code running in full trust may be affected by this vulnerability. IIS is not affected in the following scenarios:
• Default Installations of IIS 5.1, IIS 6.0, and IIS 7.0
• ASP.NET configured to run with a trust level lower than Full Trust.
• Classic ASP code
How is SQL Server affected?
SQL Server is affected if a user is granted administrative privileges to load and run code. A user with administrative privileges could execute specially crafted code that could leverage the attack. However, this privilege is not granted by default.
In other words, the server must have been weakened in order for this flaw to be exploited.
crapinsecure code allowing SQL injection attacks to be successful. The flaw in the Microsoft Advisory is completely different.User-provided code running in IIS, for example ISAPI filters and extensions, and ASP.NET code running in full trust may be affected by this vulnerability. IIS is not affected in the following scenarios:
• Default Installations of IIS 5.1, IIS 6.0, and IIS 7.0
• ASP.NET configured to run with a trust level lower than Full Trust.
• Classic ASP code
How is SQL Server affected?
SQL Server is affected if a user is granted administrative privileges to load and run code. A user with administrative privileges could execute specially crafted code that could leverage the attack. However, this privilege is not granted by default.
In other words, the server must have been weakened in order for this flaw to be exploited.
Having fun running ASP.net with a lower trust level and installing third parties software.
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.