CVE-2016-9570
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 · uneditedcb.exe in Carbon Black 5.1.1.60603 allows attackers to cause a denial of service (out-of-bounds read, invalid pointer dereference, and application crash) by leveraging access to the NetMon named pipe.
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 confidenceThe cb.exe component in Carbon Black versions prior to the fix contains a vulnerability where attackers with access to the NetMon named pipe can trigger an out-of-bounds read and invalid pointer dereference, causing the application to crash and resulting in denial of service.
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= 5.1.1.60603CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 the installed Carbon Black versionLocate the Carbon Black installation directory and retrieve version information from the cb.exe file properties or the product's built-in version reporting mechanismAffected if The installed version is 5.1.1.60603 or any version prior to the fix (versions before the patch addressing CVE-2016-9570)
-
Confirm the presence of the cb.exe componentVerify that the cb.exe executable exists on the system, typically found in the Carbon Black installation directoryAffected if The cb.exe component is present and running on the system (this is the vulnerable component)
-
Check for NetMon named pipe accessibilityIdentify whether the NetMon named pipe is exposed and accessible on the system; this may require checking named pipe ACLs or monitoring for pipe creationAffected if The NetMon named pipe exists and is accessible to untrusted users (this is the attack vector that triggers the vulnerability)
-
Monitor for application crashesReview system logs, event logs, or Carbon Black application logs for recent unexpected crashes or termination of the cb.exe processAffected if The cb.exe process has crashed or terminated unexpectedly, which may indicate exploitation of this vulnerability
The environment is affected if the installed Carbon Black version is 5.1.1.60603 or earlier AND the NetMon named pipe is accessible, as this combination allows attackers to trigger the out-of-bounds read leading to denial of service.
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 dataApply the vendor-supplied patch or upgrade Carbon Black to a version that addresses CVE-2016-9570. Additionally, restrict access to the NetMon named pipe to reduce attack surface.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9570 — 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-2016-9570 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