dbcve.org
Network Data Loss PreventionApplication · Mcafee

CVE-2017-3968

CRITICAL · 9.1 CVSS v3.0 Published 2018-06-13
Fix available
A fix is available. Upgrade to 8.2.7.42.2 / 9.3.4.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Session fixation vulnerability in the web interface in McAfee Network Security Manager (NSM) before 8.2.7.42.2 and McAfee Network Data Loss Prevention (NDLP) before 9.3.4.1.5 allows remote attackers to disclose sensitive information or manipulate the database via a crafted authentication cookie.

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 · high confidence

Session fixation vulnerability in the web interface allows remote attackers to hijack sessions via a crafted authentication cookie. The attacker can disclose sensitive information or manipulate the database by setting or predicting the session identifier before user authentication.

MitigationUpgrade McAfee Network Security Manager to version 8.2.7.42.2 or later, and McAfee Network Data Loss Prevention to version 9.3.4.1.5 or later. Review and invalidate existing sessions after patching.

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
Network Data Loss PreventionApplication
Affected:< 9.3.4.1.5
Network Security ManagerApplication
Affected:< 8.2.7.42.2

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed McAfee product
    Determine if McAfee Network Data Loss Prevention (NDLP) or McAfee Network Security Manager (NSM) is installed on the system. Check installed programs via system inventory or product-specific management console.
    Affected if Either product is installed with a version lower than 9.3.4.1.5 (NDLP) or 8.2.7.42.2 (NSM)
  2. Determine product version
    Access the product management console or use product-specific commands to retrieve the exact installed version number. Compare against the affected version ranges.
    Affected if Installed version is below 9.3.4.1.5 for NDLP or below 8.2.7.42.2 for NSM
  3. Verify web interface is enabled
    Check if the web-based management interface is accessible and enabled. This is typically on port 443 or 8443. Attempt to access the login page.
    Affected if The web interface is accessible and the product version is in the affected range
  4. Inspect session cookie configuration
    Log into the web interface and examine the authentication cookie (often JSESSIONID or similar). Check if the session ID is set or predictable before authentication completes.
    Affected if Session identifier can be set or determined prior to successful login, indicating vulnerability
  5. Review session management settings
    Check the product configuration for session management settings. Look for whether session IDs are regenerated after authentication.
    Affected if Session IDs are not regenerated after successful login, confirming the session fixation condition

The environment is affected if McAfee Network Data Loss Prevention below 9.3.4.1.5 or McAfee Network Security Manager below 8.2.7.42.2 is installed with the web interface enabled and session IDs are not regenerated post-authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.2.7.42.2 / 9.3.4.1.5 or later
Fixed in 8.2.7.42.29.3.4.1.5
Interim mitigation

Upgrade McAfee Network Security Manager to version 8.2.7.42.2 or later, and McAfee Network Data Loss Prevention to version 9.3.4.1.5 or later. Review and invalidate existing sessions after patching.

Recommended fix High confidence

Network Data Loss Prevention: 9.3.4.1.5 or later | Network Security Manager: 8.2.7.42.2 or later

  1. Upgrade McAfee Network Data Loss Prevention (NDLP) to version 9.3.4.1.5 or later
  2. Upgrade McAfee Network Security Manager (NSM) to version 8.2.7.42.2 or later
  3. After upgrade, verify the web interface is accessible and functioning normally
  4. Review authentication cookie behavior to confirm session fixation vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Network Data Loss Prevention Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3968 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-3968 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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