CVE-2017-2786
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 · uneditedA denial of service vulnerability exists in the psnotifyd application of the Pharos PopUp printer client version 9.0. A specially crafted packet can be sent to the victim's computer and can lead to an out of bounds read causing a crash and a denial of service.
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 confidenceA denial of service vulnerability exists in the psnotifyd service of Pharos PopUp printer client version 9.0. The vulnerability is caused by an out-of-bounds read when the application processes a specially crafted network packet, leading to a crash and service unavailability.
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.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/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.
-
Confirm Pharos PopUp installation and versionLocate the Pharos PopUp installation directory (commonly in Program Files\Pharos) and check the version information in the application properties, or use the Windows Add/Remove Programs feature to view the installed version.Affected if The installed version is exactly 9.0 (matches = 9.0 in affected versions)
-
Verify psnotifyd service is presentCheck for the psnotifyd service on the system using 'services.msc' or by running 'sc query psnotifyd' in command prompt. This service is the specific component affected by the vulnerability.Affected if The psnotifyd service exists and is installed on the system
-
Check psnotifyd service running statusUsing Services console or 'sc query psnotifyd' command, determine whether the psnotifyd service is currently running.Affected if The psnotifyd service is currently running (the vulnerability triggers when processing network packets)
-
Assess network exposure of psnotifydIdentify the listening port for psnotifyd (typically configured during installation) using 'netstat -an' or by reviewing Pharos PopUp configuration files. Determine if the service is bound to network-accessible interfaces versus localhost only.Affected if The psnotifyd service is bound to a network-accessible IP address and port, making it reachable from other systems
A system is affected if it runs Pharos PopUp version 9.0 with the psnotifyd service running and exposed to network traffic.
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 dataRestrict network access to the psnotifyd service using firewall rules or network segmentation to prevent unauthenticated packets from reaching the affected system. If available, apply vendor patches for Pharos PopUp printer client version 9.0.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2786 — 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-2786 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