CVE-2017-3967
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 · uneditedTarget influence via framing vulnerability in the web interface in McAfee Network Security Management (NSM) before 8.2.7.42.2 allows remote attackers to inject arbitrary web script or HTML via application pages inability to break out of 3rd party HTML frames.
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 confidenceClickjacking vulnerability in McAfee NSM web interface. The application fails to implement proper frame-breaking protections, allowing attackers to embed the NSM interface within malicious third-party HTML frames and inject arbitrary web script or HTML through the application's pages.
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< 8.2.7.42.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if McAfee NSM is installedCheck running services or installed programs for 'McAfee Network Security Manager' or 'NSM'. On Windows, check Services or Programs and Features. On Linux, check for NSM installation directories.Affected if McAfee NSM is not installed on the system
-
Determine the installed NSM versionAccess the NSM web interface and check the version information typically found in the About or Help section of the application. Alternatively, check the installation directory or product release notes.Affected if The installed version is lower than 8.2.7.42.2 (e.g., 8.2.7.42.1, 8.2.6.x, etc.)
-
Check for X-Frame-Options HTTP response headerUse a browser developer tool or command-line tool (curl -I) to request a page from the NSM web interface and inspect the HTTP response headers for X-Frame-Options.Affected if The X-Frame-Options header is missing from HTTP responses, or the header value is not set to DENY or SAMEORIGIN
-
Verify frame-breaking JavaScript protectionView the page source of any NSM web interface page and search for frame-breaking JavaScript code (typically checks for top.location != self.location).Affected if No frame-breaking JavaScript code is present in the application's HTML pages
If the installed McAfee NSM version is below 8.2.7.42.2 AND the web interface can be embedded in a frame (missing X-Frame-Options header and frame-breaking script), the environment is affected by this clickjacking vulnerability.
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 data8.2.7.42.2
Upgrade to McAfee NSM version 8.2.7.42.2 or later, which includes the frame-breaking fix. Alternatively, configure X-Frame-Options: DENY or SAMEORIGIN headers at the web server/load balancer level as a compensating control.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3967 — 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-2017-3967 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