CVE-2017-3935
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 · uneditedNetwork Data Loss Prevention is vulnerable to MIME type sniffing which allows older versions of Internet Explorer to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the intended content type.
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 confidenceNetwork Data Loss Prevention fails to specify proper Content-Type headers on HTTP responses, allowing older Internet Explorer versions to perform MIME-type sniffing. This can cause the browser to misinterpret response content as a different MIME type (e.g., treating plain text as HTML), potentially leading to script execution or information disclosure.
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<= 9.3.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Network DLP versionAccess the product administration console or use the product's version information command/interface to determine the exact installed version numberAffected if The installed version is 9.3.0 or any earlier version within the 9.x line
-
Confirm web management interface is accessibleVerify that the Network DLP web-based management console or any HTTP endpoints are reachable on the networkAffected if The web interface is enabled and accessible, as this is the vector through which affected HTTP responses are served
-
Capture HTTP response headers from the applianceUse a browser (preferably an older Internet Explorer version for accurate testing) or a tool like curl with the -I flag to request pages from the NDLPs web interface and inspect the response headersAffected if The HTTP responses lack a Content-Type header entirely, or contain an incorrect/missing Content-Type value, AND do not include the X-Content-Type-Options: nosniff header
-
Test for MIME sniffing vulnerabilityIf possible, access a plain text endpoint served by NDLPs and observe whether the browser interprets it as HTML or executes script content (this confirms active exploitation potential)Affected if The server serves content without proper Content-Type headers, allowing the browser to misinterpret the MIME type
You are affected if your installed McAfee Network DLP version is 9.3.0 or lower AND the web interface serves HTTP responses missing proper Content-Type headers or the X-Content-Type-Options: nosniff header.
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 dataConfigure the application to explicitly send correct Content-Type headers for all responses, or set the X-Content-Type-Options: nosniff header to disable MIME sniffing in browsers.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3935 — 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-3935 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