CVE-2014-2390
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site request forgery (CSRF) vulnerability in the User Management module in McAfee Network Security Manager (NSM) before 6.1.15.39 7.1.5.x before 7.1.5.15, 7.1.15.x before 7.1.15.7, 7.5.x before 7.5.5.9, and 8.x before 8.1.7.3 allows remote attackers to hijack the authentication of users for requests that modify user accounts via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCSRF vulnerability in McAfee Network Security Manager's User Management module allows remote attackers to hijack authenticated user sessions and make unauthorized changes to user accounts. The attack exploits the lack of anti-CSRF tokens in the User Management functionality, enabling malicious requests to be forged on behalf of an authenticated administrator.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 6.1.15, < 6.1.15.39>= 7.1.5, < 7.1.5.15>= 7.1.15, < 7.1.15.7>= 7.5.5, < 7.5.5.9>= 8.1.7, < 8.1.7.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify NSM version via web interfaceLog into the McAfee Network Security Manager web interface and navigate to Help > About, or check the login page footer for the version number. Alternatively, access the server directly and check the installation directory for version files.Affected if The displayed version falls within any of these ranges: 6.1.15 to 6.1.15.38, 7.1.5 to 7.1.5.14, 7.1.15 to 7.1.15.6, 7.5.5 to 7.5.5.8, or 8.1.7 to 8.1.7.2
-
Confirm User Management module is exposedAccess the User Management interface via the NSM web console, typically at /userManagement or similar path under the NSM web application. Verify the page loads successfully with administrative credentials.Affected if The User Management module is accessible and functional on the web interface, indicating the vulnerable attack surface is exposed.
-
Verify anti-CSRF protection absence in User Management formsUsing a browser developer tool or HTTP proxy, capture a POST request when creating or modifying a user in the User Management module. Inspect the request headers and body for anti-CSRF tokens such as 'csrfToken', 'csrf', or 'token' parameters.Affected if The HTTP requests to User Management endpoints contain no anti-CSRF token parameters in the request body and no custom CSRF-related headers, confirming the vulnerability is present.
The environment is affected if the installed McAfee NSM version falls within the affected ranges AND the web-based User Management module is accessible without anti-CSRF token protection in its requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data6.1.15.397.1.5.157.1.15.7
Upgrade McAfee NSM to version 6.1.15.39, 7.1.5.15, 7.1.15.7, 7.5.5.9, or 8.1.7.3 or later. Additionally, implement anti-CSRF tokens in all User Management forms and validate the Origin/Referer headers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2390 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data