Knowledge Center

McAfee Security Bulletin: Vulnerability Manager 7.5.9 hotfix remediates CSRF vulnerabilities in the MVM Enterprise Manager
Security Bulletins ID:   SB10135
Last Modified:  4/7/2017


 Impact of Vulnerability:  Cross-Site Request Forgery (CSRF)
 CVE Numbers:  CVE-2015-7612
 Severity Rating:  Medium
 Base / Overall CVSS v2 Scores:  6.2 / 5.4
 Recommendations: Install the provided hotfix for the applicable McAfee Vulnerability Manager (MVM) version in your environment:
  • For MVM 7.5.9:
  • For MVM 7.5.8 or earlier, run FSUpdate or go to http://update.foundstone.com to upgrade to 7.5.9, then install the hotfix from the Product Downloads site.
 Security Bulletin Replacement:  None
 Affected Software:  MVM 7.5.9 and earlier
 Location of Updated Software:  http://www.mcafee.com/us/downloads/downloads.aspx

Article contents:


The Organizations page in MVM Enterprise Manager is the main page for accessing organizational properties and users. This page is susceptible to Cross-Site Request Forgery (CSRF) attacks by modification of the HTTP request. Prosecution of this attack requires an active administrator session. The hotfix noted in this Security Bulletin will remediate this issue.

Multiple cross-site request forgery (CSRF) vulnerabilities in the Organizations page in Enterprise Manager in McAfee Vulnerability Manager (MVM) 7.5.9 and earlier allow remote attackers to hijack the authentication of administrators for requests that have unspecified impact via unknown vectors.
Affected Components:
  • MVM Enterprise Manager (web portal) component


Go to the Product Downloads site and download the applicable product patch/hotfix files:
Product Type Version Release Date
McAfee Vulnerability Manager 7.5.9 Hotfix September 2015

Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, security updates, patches, and hotfixes.  Review the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions on how to install these updates.

Product Specific Notes

MVM Affected Versions:
  • MVM 7.5.9 and earlier
MVM Protected Versions:
  • None


None. Install the provided hotfix mentioned in this Security Bulletin.


None. Install the provided hotfix mentioned in this Security Bulletin.


McAfee credits Giovanni Delvecchio from SmartNet s.r.l. for reporting this flaw.

Frequently Asked Questions (FAQs)

How do I know whether my McAfee product is vulnerable or not?

For MVM:
  1. To determine whether your product patch level is vulnerable:
    1. Log on to the MVM Enterprise Manager.
    2. Click the Version 7.5 link and examine the FoundScan database hot fix version value. If the value is 7.5.9 (or earlier), your product is vulnerable. Otherwise, your product is not vulnerable.
  2. If your product is version 7.5.9, to determine whether your system has the hotfix applied:
    1. Log on to the Windows Desktop on the MVM Enterprise Manager system, either directly or using RDP.
    2. Click Start, Run, type notepad, and click OK.
    3. Click File, Open and review the following file in the installation directory:
      The first portion of the file will display the file version and hotfix number, as follows:
      <?php //003af
      // (C) 1999 - 2011 McAfee, Inc. All rights reserved.
      If the version number is (and later), you have the hotfix applied and your product is not vulnerable. Otherwise, the hotfix is not applied and your product is vulnerable.
What is CVSS?
CVSS, or Common Vulnerability Scoring System, is the result of the National Infrastructure Advisory Council’s effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, please visit the CVSS website at: http://www.first.org/cvss/.

When calculating CVSS v2 scores, McAfee has adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We do not factor into a score any potential follow-on exploits that might be made possible by successful exploitation of the issue being scored.

CVSS v3 scoring is in final review as of March 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved.
What are the CVSS scoring metrics that have been used?
 Base Score 6.2
 Related exploit range (AccessVector) Adjacent Network (A)
 Attack complexity (AccessComplexity) High (H)
 Level of authentication needed (Authentication) Single (S)
 Confidentiality impact Partial (P)
 Integrity impact Complete (C)
 Availability impact Complete (C)
 Temporal Score (Overall) 5.4
 Availability of exploit (Exploitability) Not Defined (ND)
 Type of fix available (RemediationLevel) Official Fix (OF)
 Level of verification that vulnerability exists (ReportConfidence) Confirmed (C)

NOTE: The below CVSS version 2.0 vector was used to generate this score.

Where can I find a list of all security bulletins or how do I report a product vulnerability?
To find a list of all security bulletins, or if you have information about a security issue or vulnerability with a McAfee product, please visit our product security website at: http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx.




The information provided in this security bulletin is provided as is without warranty of any kind. McAfee disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if McAfee 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.
Any future product release dates mentioned in this security bulletin are intended to outline our general product direction and they should not be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates are not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion and may be changed or cancelled at any time.

Rate this document

Did this article resolve your issue?

Please provide any comments below

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.