CVE-2017-4013
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 · uneditedBanner Disclosure in the server in McAfee Network Data Loss Prevention (NDLP) 9.3.x allows remote attackers to obtain product information via HTTP response header.
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 confidenceMcAfee Network Data Loss Prevention (NDLP) 9.3.x exposes product version and identity information through HTTP response headers, allowing remote attackers to perform reconnaissance via banner grabbing. This information disclosure can aid attackers in identifying vulnerable versions for targeted exploitation.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm NDLP web interface is accessibleIdentify the hostname or IP of the NDLP server and attempt an HTTP or HTTPS request to common web ports (80, 443, 8443) or the configured NDLP management portAffected if The NDLP web interface responds to HTTP requests
-
Check installed NDLP versionUse the product's management console, check installed software listing on the NDLP server, or query the NDLP service for its version informationAffected if The installed version is 9.3.0 or any version lower than 9.3.0
-
Inspect HTTP response headers for information disclosureSend an HTTP GET request to the NDLP web interface (e.g., curl -I https://<ndlp-host>:<port>) and examine all response headers, specifically looking at Server, X-Powered-By, and custom headersAffected if Response headers contain McAfee product name, version number (particularly 9.3.x or lower), or other NDLP identity information such as 'ePO' or specific NDLP branding
-
Verify header exposure on all NDLP endpointsTest multiple NDLP URLs and management interfaces, as some endpoints may reveal headers while others do notAffected if Any publicly accessible NDLP endpoint returns version or product identity information in HTTP headers
The environment is affected if NDLP is running with version 9.3.0 or lower AND its HTTP responses expose product name or version information in headers such as Server, X-Powered-By, or custom headers.
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 NDLP web server to suppress or obfuscate sensitive HTTP response headers that reveal product name and version information.
- 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-4013 — 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-4013 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