Compliance reports might show that some McAfee Enterprise products install legacy versions of Microsoft Visual C++ libraries. We have assessed that these legacy libraries do not impair product functionality, and will be updated in the future, as appropriate.
The following table lists affected products and future update plans. This table will be updated as new information becomes available.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
| Product |
Visual Studio
Version in Use |
Effect to Product |
Migration
Plans |
| Drive Encryption |
Visual Studio 2005 |
Product functionality is not impacted.
Previously disclosed Visual Studio 2005 vulnerabilities do not affect Drive Encryption. Drive Encryption does not use the affected runtime components. |
To be addressed in future product releases. |
| ePolicy Orchestrator |
Visual Studio 2008 |
Product functionality is not impacted.
Previously disclosed Visual Studio vulnerabilities do not affect ePolicy Orchestrator. ePolicy Orchestrator does not use the affected runtime for its operation. These legacy runtimes got installed by ePolicy Orchestrator to support managed products that depended on them.
If you do not use products that require Visual Studio C++ 2008 runtime libraries, they can be safely uninstalled. |
No plans to upgrade; future ePO releases will not install Visual Studio C++ 2008. |
| File and Removable Media Protection |
Visual Studio 2005 and 2008 |
Product functionality is not impacted.
Previously disclosed Visual Studio 2005 vulnerabilities do not affect File and Removable Media Protection. File and Removable Media Protection does not use the affected runtime components. |
To be addressed in future product releases. |
| MOVE AntiVirus Multi-Platform 3.6.1 |
Visual Studio 2008 |
|
EOL and will not be upgraded. |
| Security for Lotus Domino 7.5.3 |
Visual Studio 2003, 2005 |
Product functionality is not impacted.
Previously disclosed Visual Studio 2003 and 2005 vulnerabilities do not affect Security for Lotus Domino. Security for Lotus Domino does not use the affected runtime components. |
EOL and will not be upgraded. |
| Security for Microsoft Exchange 8.0 |
Visual Studio 2003, 2005 |
|
EOL and will not be upgraded. |
| Security for Microsoft Exchange 8.5.1 |
Visual Studio 2003, 2005 |
Product functionality is not impacted.
Previously disclosed Visual Studio 2003 and 2005 vulnerabilities do not affect Security for Microsoft Exchange. Security for Microsoft Exchange does not use the affected runtime components. |
EOL and will not be upgraded. |
| Security for Microsoft SharePoint 3.0 |
Visual Studio 2003, 2005 |
Product functionality is not impacted.
Previously disclosed Visual Studio 2003 and 2005 vulnerabilities do not affect Security for Microsoft SharePoint. Security for Microsoft SharePoint does not use the affected runtime components. |
EOL and will not be upgraded. |
| VirusScan Enterprise |
Visual Studio 2008 Professional |
Product functionality is not impacted.
Previously disclosed Visual Studio 2005 vulnerabilities do not affect VirusScan Enterprise. VirusScan Enterprise does not use the affected runtime components. |
EOL and will not be upgraded. |
| Vulnerability Manager |
Visual Studio 2005 |
|
EOL and will not be upgraded. |
NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.
- EOL period—The time frame that runs from the day we announce product discontinuation, until the last date that we formally support the product. In general, after the EOL period is announced, no enhancements are made.
- EOL date—The last day that the product is supported, according to the terms of our standard support offering.
