CVE-2017-2785
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 · uneditedAn exploitable buffer overflow 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 a heap based buffer overflow resulting in remote code execution. This client is always listening, has root privileges, and requires no user interaction to exploit.
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 confidenceA heap-based buffer overflow vulnerability exists in the psnotifyd application of the Pharos PopUp printer client version 9.0. An attacker can send a specially crafted packet to achieve remote code execution. The vulnerable client runs as root, listens continuously, and requires no user interaction to exploit.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 if Pharos PopUp is installedSearch for Pharos Popup software on the system using package managers, installed programs list, or file system searches for 'Pharos' or 'Popup' directories.Affected if Pharos PopUp version 9.0 is found installed on the system
-
Verify the installed versionCheck the installed Pharos PopUp version through system inventory tools, installed software list, or by querying the software directly if a version command is available.Affected if The installed version is exactly 9.0 (the affected version)
-
Locate the psnotifyd applicationSearch for the psnotifyd executable on the system, typically in Pharos installation directories or system service paths.Affected if The psnotifyd binary is present on the system
-
Check if psnotifyd service is runningQuery running processes for psnotifyd or check system service status for the Pharos popup notification service.Affected if psnotifyd is currently running as a service
-
Verify psnotifyd network listening statusCheck network connections or open ports to determine if psnotifyd is listening on any network interface (e.g., using netstat, ss, or similar tools).Affected if psnotifyd is listening on a network port and accepting connections
-
Confirm psnotifyd runs as rootCheck the process ownership of running psnotifyd instances through process inspection tools.Affected if psnotifyd is running with root privileges
A system is affected if Pharos PopUp version 9.0 is installed with the psnotifyd service running and listening on a network port as root.
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 dataImmediately restrict network access to the psnotifyd service or disable it if not essential until vendor patch is available; if the service must remain running, implement network segmentation and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2785 — 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-2785 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