Microsoft Forefront is a discontinued family of line-of-business security software by Microsoft Corporation. Microsoft Forefront products are designed to help protect computer networks, network servers (such as Microsoft Exchange Server and Microsoft SharePoint Server) and individual devices.[1] As of 2015, the only actively developed Forefront product is Forefront Identity Manager.
Components[edit]
Forefront includes the following products:[2]
I heared a rumor that this was supposed to happen by the end of 2012, but I really need someone to explain this to me a bit better. We are looking to upgrade to SCEP 2012, and providing EOL dates to the powers that be would help my case a lot. Microsoft Forefront Threat Management Gateway (Forefront TMG), formerly known as Microsoft Internet Security and Acceleration Server (ISA Server), is a network router, firewall, antivirus program, VPN server and web cache from Microsoft Corporation. It runs on Windows Server and works by inspecting all network traffic that passes through it. Compare Microsoft Forefront (Discontinued Product) vs Symantec Endpoint Security. 138 verified user reviews and ratings. SCEP is a light weight client which is minimally impactful on the user end. Forefront's management console provides excellent monitoring. Microsoft Forefront Client Security is designed for any mid- to large–size organization that needs a single solution for protection, detection, and removal of spyware, rootkits, and other emerging threats, as well as traditional attacks, such as viruses, worms, and Trojan horses. End of life for Microsoft Forefront Client Security was on July 14, 2015. Customers are encouraged to migrate to System Center Endpoint Protection. For more information, visit the Microsoft.
- Identity Manager: State-based identity management software product, designed to manage users' digital identities, credentials and groupings throughout the lifecycle of their membership of an enterprise computer system[3]
Rebranded[edit]
- System Center Endpoint Protection: A business antivirus software product that can be controlled over the network, formerly known as Forefront Endpoint Protection, Forefront Client Security and Client Protection.[4][5]
- Exchange Online Protection: A software as a service version of Forefront Protect for Exchange Server: Instead of installing a security program on the server, the customer re-routes its email traffic to the Microsoft online service before receiving them. [6]
Discontinued[edit]
- Threat Management Gateway: Discontinued server product that provides three functions: Routing, firewall and web cache. Formerly called Internet Security and Acceleration Server or ISA Server.[7][8]
- Unified Access Gateway: Discontinued server product that protects network assets by encrypting all inbound access request from authorized users. Supports Virtual Private Networks (VPN) and DirectAccess. Formerly called Intelligent Application Gateway.[9][10]
- Server Management Console: Discontinued web-based application that enables management of multiple instances of Protection for Exchange, Protection for SharePoint and Microsoft Antigen from a single interface.[11][12]
- Protection for Exchange: A discontinued software product that detects viruses, spyware, and spam by integrating multiple scanning engines from security partners in a single solution to protect Exchange messaging environments. FPE provides an administration console that includes customizable configuration settings, filtering options, monitoring features and reports, and integration with the Forefront Online Protection for Exchange (FOPE) product. After installation, managing FPE on multiple Exchange servers can be done with the Protection Server Management Console. Additionally, FPE can be managed using Windows PowerShell, a command-line shell and task-based scripting technology that enables the automation of system administration tasks.[7][13][14]
- Protection for SharePoint: A discontinued product that protects Microsoft SharePoint Server document libraries. It enforces rules that prevent documents containing malware, sensitive information, or out-of-policy content from being uploaded. Protection Server Management Console or Windows PowerShell can be used to manage Protection for SharePoint Server on multiple servers.[7][15][16]
- Security for Office Communications Server: Protects computers running Microsoft Office Communications Server from malware. Formerly called Antigen for Instant Messaging.[17]
History[edit]
The predecessor to the Forefront server protection products was the Antigen line of antivirus products created by Sybari Software. Sybari was acquired by Microsoft in 2005, and the first Microsoft-branded version of the product was called Microsoft Forefront Security for SharePoint (FSSP) Version 10. FSSP Version 10 supports Microsoft Office SharePoint Server 2007 or Microsoft Windows SharePoint Services version 3, whereas FPSP (the last version of the product) supports Microsoft Office SharePoint Server 2010, Microsoft SharePoint Foundation 2010, Microsoft Office SharePoint Server 2007 SP1, or Windows SharePoint Services version 3 SP1.
See also[edit]
References[edit]
- ^'Microsoft Forefront Protection'. Microsoft. Retrieved 29 September 2009.
- ^'Microsoft Forefront FAQ'. Microsoft. Retrieved 29 September 2009.
- ^Forefront Identity Manager
- ^Forefront Endpoint Protection
- ^Forefront Client Security
- ^Forefront Online Protection for Exchange
- ^ abc'Important Changes to Forefront Product Roadmaps'. Microsoft TechNet. Microsoft Corporation. 12 September 2012. Archived from the original on 18 October 2012. Retrieved 22 September 2012.
- ^Forefront Threat Management Gateway
- ^Forefront Unified Access Gateway
- ^'Important Changes to the Forefront Product Line'. Server & Cloud Blog. Microsoft. 17 December 2013. Archived from the original on 21 December 2014. Retrieved 21 December 2014.
- ^'Forefront Protection Server Management Console'. TechNet. Microsoft. 10 November 2010. Retrieved 7 October 2012.
- ^Hicks, Richard (12 September 2012). 'Forefront TMG 2010 End of Life Statement'. Retrieved 22 September 2012.
- ^Forefront Protection for Exchange Server
- ^Microsoft Forefront Protection 2010 for Exchange Server
- ^Forefront Protection for SharePoint
- ^Microsoft Forefront Protection 2010 for SharePoint on Microsoft Download Center
- ^Forefront for Office Communications Server
External links[edit]
- Microsoft Forefront Server Protection Blog on TechNet Blogs
Security Bulletin
Vulnerability in Microsoft Antimalware Client Could Allow Elevation of Privilege (2823482)
Published: April 09, 2013 | Updated: October 08, 2013
Version: 1.2
General Information
Executive Summary
This security update resolves a privately reported vulnerability in the Microsoft Antimalware Client. The vulnerability could allow elevation of privilege due to the pathnames used by the Microsoft Antimalware Client. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected system. The attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. An attacker must have valid logon credentials to exploit this vulnerability. The vulnerability could not be exploited by anonymous users.
This security update is rated Important for the Microsoft Antimalware Client in supported versions of Windows Defender for Windows 8 and Windows RT. This security update has no severity rating for the Microsoft Antimalware Client in other Microsoft antimalware programs. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting pathnames used by the Microsoft Antimalware Client. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Most customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Knowledge Base Article
Knowledge Base Article | 2823482 |
---|---|
File information | Yes |
SHA1/SHA2 hashes | Yes |
Known issues | None |
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.
Affected Software
Antimalware Software | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
---|---|---|---|
Windows Defender for Windows 8 and Windows RT[1] (2781197) | Elevation of Privilege | Important | None |
Anti-malware Software | Microsoft Antimalware Improper Pathname Vulnerability - CVE-2013-0078 | Aggregate Severity Rating | |
---|---|---|---|
Windows Defender for Windows 8 and Windows RT | **Important** Elevation of Privilege | **Important** |
Microsoft Antimalware Improper Pathname Vulnerability - CVE-2013-0078
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code in the security context of the LocalSystem account and take complete control of the system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. An attacker must have valid logon credentials to exploit this vulnerability. The vulnerability could not be exploited by anonymous users.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2013-0078.
Mitigating Factors
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- An attacker must have valid logon credentials to exploit this vulnerability. The vulnerability could not be exploited by anonymous users.
- In a Windows 8 default configuration, a standard user does not have permissions to write files to the root directory on the system. This mitigates the vulnerability because, in a default configuration, a standard user would not have the necessary permissions to exploit the vulnerability.
Workarounds
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Correct the Windows Defender image pathname on Windows 8 and Windows RT systems
Use this workaround to block attack vectors for the vulnerability on Windows 8 and Windows RT systems.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Create a backup of the registry keys. Backup copies can be made using a managed deployment script by performing the following command as an administrator:
Regedit.exe /e c:tempWindefend_backup.reg HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesWinDefend
Note When run as an administrator, the above command creates a file named 'Windefend_backup.reg' in the c:temp folder.
Create a text file named Windefend_ImagePath_fix.reg with the following contents:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesWinDefend] 'ImagePath'=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00, 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73, 00,20,00,44,00,65,00,66,00,65,00,6e,00,64,00,65,00,72,00,5c,00,4d,00,73,00, 4d,00,70,00,45,00,6e,00,67,00,2e,00,65,00,78,00,65,00,22,00,00,00
Save the Windefend_ImagePath_fix.reg file to the c:temp folder.
Run the registry script file you created in step 2 on the target system by using one of the following methods:
Method #1:
Double-click the Windefend_ImagePath_fix.reg file.
The following confirmation message should be displayed:
The keys and values contained in C:tempWindefend_ImagePath_fix.reg have been successfully added to the registry.
Method #2:
Alternatively, perform the following command as an administrator:
Regedit /s c:tempWindefend_ImagePath_fix.reg
Warning When using the command line method above, no confirmation message is displayed. You will not be notified as to whether or not the registry keys and values were successfully added to the registry.
Impact of workaround. None. This workaround changes the image pathname to the correct value.
How to undo the workaround.
Restore the backup file you created in step 1, above, by using one of the following methods:
Double-click the Windefend_backup.reg file.
The following confirmation message should be displayed:
The keys and values contained in C:tempWindefend_backup.reg have been successfully added to the registry.
Alternatively, perform the following command as an administrator:
Regedit /s c:tempWindefend_backup.reg
Warning When using the command line method above, no confirmation message is displayed. You will not be notified as to whether or not the registry keys and values were successfully added to the registry.
FAQ
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability.
What causes the vulnerability?
This vulnerability is caused when improper pathnames are used by the Microsoft Antimalware Client.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could execute arbitrary code in the security context of the LocalSystem account and take complete control of the system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
An attacker must have valid logon credentials to exploit this vulnerability. The vulnerability could not be exploited by anonymous users.
What is theLocalSystemaccount?
The LocalSystem account is a predefined local account used by the service control manager. It has extensive privileges on the local computer, and acts as the computer on the network. Its token includes the NT AUTHORITYSYSTEM and BUILTINAdministrators SIDs; these accounts have access to most system objects. A service that runs in the context of the LocalSystem account inherits the security context of the Service Control Manager. Most services do not need such a high privilege level. For more information, see the MSDN article, LocalSystem Account.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability.
What systems are primarily at risk from the vulnerability?
Windows 8 workstations are primarily at risk.
What does the update do?
The update addresses the vulnerability by correcting pathnames used by the Microsoft Antimalware Client.
When this securityadvisorywas issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
When this securityadvisorywas issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that these vulnerabilities had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Several resources are available to help administrators deploy security updates.
- Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates and common security misconfigurations.
- Windows Server Update Services (WSUS), Systems Management Server (SMS), and System Center Configuration Manager (SCCM) help administrators distribute security updates.
- The Update Compatibility Evaluator components included with Application Compatibility Toolkit aid in streamlining the testing and validation of Windows updates against installed applications.
For more information about these tools and guidance in deploying security updates across networks, see Security Tools for IT Pros.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Antimalware Client update
Prerequisites
This security update requires that you have one of the following antimalware programs installed: Katy perry top 10 songs mp3 free download.
- Windows Defender for Windows 8 and Windows RT
Installing the Update
Administrators of enterprise antimalware deployments should ensure that their update management software is configured to automatically approve and distribute Microsoft Antimalware Client, Microsoft Malware Protection Engine, and definition updates.
Super Nisqually 1.0.3 for Mac is available as a free download on our software library. The most popular version among Super Nisqually for Mac users is 1.0. The actual developer of this software for Mac is gamehouse.nisqually. The software is categorized as Games.
For enterprise deployments as well as end users, typically the update is downloaded and installed via update management software or automatic updating. Backup blackberry contacts to computer.
End users can also manually update their antimalware client software by checking for updates using the Microsoft Update or the Windows Update service depending on the operating system and antimalware software. Refer to the following table for details:
Software | Update Mechanism |
---|---|
Windows Defender for Windows 8 and Windows RT | Windows Update |
The update packages for Windows Defender for Windows 8 are also available from the Microsoft Download Center. See Microsoft Knowledge Base Article 2781197 for download links.
Verifying Update Installation
You can verify that this update has been installed by verifying the version number for the Microsoft Antimalware Client.
If your version of the Microsoft Antimalware Client is equal to 4.2.223.0, then the update has been installed.
Note If the version of the Microsoft Antimalware Client is equal to or greater than version 4.2.223.0, then the antimalware program is not affected by the vulnerability and you do not need to take any further action.
For more information on how to verify the client version number that your software is currently using, see the section, 'Verifying Update Installation', in Microsoft Knowledge Base Article 2510781.
Restart Requirement
Yes, you must restart your system after you apply this security update.
Removing the Update
Click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.
Microsoft Forefront Client Security End Of Life Support
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Bruce Monroe of Intel for reporting the Microsoft Antimalware Improper Pathname Vulnerability (CVE-2013-0078)
- Shai Sarfaty for reporting the Microsoft Antimalware Improper Pathname Vulnerability (CVE-2013-0078)
- Tony Robotham of Centrica for reporting the Microsoft Antimalware Improper Pathname Vulnerability (CVE-2013-0078)
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
Microsoft Forefront Client
How to obtain help and support for this security update
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
Disclaimer
The information provided in the Microsoft Knowledge Base is provided 'as is' without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (April 9, 2013): Bulletin published.
- V1.1 (April 16, 2013): Bulletin revised to announce a detection change in the 2781197 package to correct a reoffering issue. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.
- V1.2 (October 8, 2013): Bulletin revised to announce a detection change in the 2781197 package. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.
Built at 2014-04-18T13:49:36Z-07:00