JoeyTheGreat
asked on
Site security wont pass.
I have a site running windows 2003 server, to which port 80 is open. I'm getting this failing rating from security compliance. the following is the patches they want. I installed them and still get non compliance.
Description: vulnerable Microsoft.NET Framework version: 1.1.4322 site &ipaddress Windows Server 2003Feb 10 16:28:55 2011newSeverity: Area of Concern CVE: CVE-2007-0041 CVE-2007-0042 CVE-2007-0043 9.32352new11Impact: On a workstation, a remote attacker could execute arbitrary commands when a user opens a specially crafted web page. On a server, a remote attacker could gain unauthorized access to configuration files. Background: The .NET Framework is a programming model for building Windows applications. Resolution Install the patch referenced in Microsoft Security Bulletins [http://www.microsoft.com/technet/securi ty/bulletin/ms10-041.mspx]
Description: vulnerable Microsoft.NET Framework version: 1.1.4322 site &ipaddress Windows Server 2003Feb 10 16:28:55 2011newSeverity: Area of Concern CVE: CVE-2007-0041 CVE-2007-0042 CVE-2007-0043 9.32352new11Impact: On a workstation, a remote attacker could execute arbitrary commands when a user opens a specially crafted web page. On a server, a remote attacker could gain unauthorized access to configuration files. Background: The .NET Framework is a programming model for building Windows applications. Resolution Install the patch referenced in Microsoft Security Bulletins [http://www.microsoft.com/technet/securi ty/bulletin/ms10-041.mspx]
Try to connect widows update services, and install all patches givn by Microsoft
Try restarting Application pool on your IIS.
I think you have to restart the whole computer after this update.
ASKER
I did restart after installing the updates.
I have the same problem... I have installed all windows updates and I can not get this message to go away in my security scans.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
good advice, ill give it a try
ASKER
everydody had good ideas but none did anything to pass the failed state.
I was having this exact same issue, and I wanted to share some information that I found. To get past the compliance issue for me, the resolution was tied to IIS. In IIS, go to your default website, and likely any other websites you have listed, and change .NET being used from 1.1.4322 to 2.0.50727.
On my Citrix server, this was easy. There was a ASP .NET tab on the website with a convenient dropdown for the version of .NET to implement.
On my OWA server, this was much more painful. The tab was not there. Instead you go to Home Directory (tab), Configuration (of the App Pool) and edit each .net aspnet_isapi.dll to point to your new framework path. Example new path: C:\WINDOWS\Microsoft.NET\F
However, the nightmare is just beginning. As soon as you do this, owa is shot, and all of your phone email apps are going to bug out. The solution: http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html
Get Metabase Explorer from IIS 6.0 Resource Kit http://www.microsoft.com/downloads/en/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&DisplayLang=en
Backup the IIS Metabase by opening IIS Manager, right-click default website (and any others you have), select "save configuration to a file," and save. Then delete the OWA Virtual Directories in your default web site: Exadmin, Exchange, Exchweb, Microsoft-server-activesyn
Open Start, Programs, IIS Resources, Metabase Explorer, Metabase Explorer.
Expand Server (local)>LM
Right-click DS2MB key and delete
Open services.msc and restart Microsoft Exchange System Attendant Service. This will recreate your deleted virtual directories.
"Almost that is, as there’s one more little thing to do. We need to reset the access permissions to Anonymous on the ExchWeb virtual directory. In order to do so start the IIS Manager then right-click the ExchWeb virtual directory and select Properties. Now select the Directory Security tab and click Edit under Authentication and access control. Make sure the Anonymous access and Integrated Windows Authentication check boxes are enabled then click OK and Apply. If an Inheritance Overrides dialog box pops up make sure you click Select All then OK. Under Authentication and access control, click Edit then clear the Integrated Windows authentication check box again. Click OK twice and you’re done."
On my Citrix server, this was easy. There was a ASP .NET tab on the website with a convenient dropdown for the version of .NET to implement.
On my OWA server, this was much more painful. The tab was not there. Instead you go to Home Directory (tab), Configuration (of the App Pool) and edit each .net aspnet_isapi.dll to point to your new framework path. Example new path: C:\WINDOWS\Microsoft.NET\F
However, the nightmare is just beginning. As soon as you do this, owa is shot, and all of your phone email apps are going to bug out. The solution: http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html
Get Metabase Explorer from IIS 6.0 Resource Kit http://www.microsoft.com/downloads/en/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&DisplayLang=en
Backup the IIS Metabase by opening IIS Manager, right-click default website (and any others you have), select "save configuration to a file," and save. Then delete the OWA Virtual Directories in your default web site: Exadmin, Exchange, Exchweb, Microsoft-server-activesyn
Open Start, Programs, IIS Resources, Metabase Explorer, Metabase Explorer.
Expand Server (local)>LM
Right-click DS2MB key and delete
Open services.msc and restart Microsoft Exchange System Attendant Service. This will recreate your deleted virtual directories.
"Almost that is, as there’s one more little thing to do. We need to reset the access permissions to Anonymous on the ExchWeb virtual directory. In order to do so start the IIS Manager then right-click the ExchWeb virtual directory and select Properties. Now select the Directory Security tab and click Edit under Authentication and access control. Make sure the Anonymous access and Integrated Windows Authentication check boxes are enabled then click OK and Apply. If an Inheritance Overrides dialog box pops up make sure you click Select All then OK. Under Authentication and access control, click Edit then clear the Integrated Windows authentication check box again. Click OK twice and you’re done."