dbcve.org
PlannerApplication · Pronestor

CVE-2019-17390

HIGH · 7.8 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 8.1.77 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
An issue was discovered in the Outlook add-in in Pronestor Planner before 8.1.77. There is local privilege escalation in the Health Monitor service because PronestorHealthMonitor.exe access control is mishandled, aka PNB-2359.

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 confidence

A local privilege escalation vulnerability exists in the Pronestor Planner Health Monitor service (PronestorHealthMonitor.exe) due to mishandled access controls. The Outlook add-in component loads this service with improper permission configuration, allowing a local attacker to exploit the misconfigured access control to gain elevated privileges on the affected system.

MitigationUpgrade Pronestor Planner to version 8.1.77 or later to receive the vendor patch. If immediate upgrade is not feasible, review and correct NTFS permissions and service ACLs on PronestorHealthMonitor.exe to ensure only authorized users/processes can interact with the 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
PlannerApplication
Affected:< 8.1.77

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Pronestor Planner installation
    Check for the presence of Pronestor Planner by looking in Program Files or Program Files (x86) for a Pronestor folder, or search for PronestorHealthMonitor.exe on the system using: Get-ChildItem -Path "C:\Program Files","C:\Program Files (x86)" -Recurse -Filter "PronestorHealthMonitor.exe" -ErrorAction SilentlyContinue
    Affected if The PronestorHealthMonitor.exe file is found on the system
  2. Identify installed Pronestor Planner version
    Locate the Pronestor installation directory and check for version information in registry: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object {$_.DisplayName -like "*Pronestor*"} | Select-Object DisplayName, DisplayVersion, or check version file in installation folder
    Affected if The installed version is lower than 8.1.77 or version cannot be determined (missing)
  3. Confirm Health Monitor service exists
    Check if PronestorHealthMonitor.exe service is registered: Get-Service -Name "*Pronestor*" -ErrorAction SilentlyContinue or check services.msc for Pronestor Health Monitor service
    Affected if The Pronestor Health Monitor service is installed and running on the system
  4. Inspect service executable permissions
    Right-click PronestorHealthMonitor.exe in the installation folder, go to Properties > Security, or run: icacls "[path to PronestorHealthMonitor.exe]" to view ACLs. Check if Users, Everyone, or non-admin groups have Write, Modify, or Full Control permissions
    Affected if Non-privileged users or groups have excessive permissions (Write, Modify, or Full Control) on the service executable
  5. Check for Outlook add-in component
    In Microsoft Outlook, go to File > Options > Add-ins or check registry at HKCU:\SOFTWARE\Microsoft\Office\*\Addins\ for Pronestor add-in entries, or search for Pronestor Outlook-related DLLs in the installation folder
    Affected if The Pronestor Outlook add-in component is installed and loads the vulnerable service

A system is affected if Pronestor Planner is installed with a version lower than 8.1.77 AND the PronestorHealthMonitor.exe service exists with improper ACLs that allow non-privileged users to interact with the service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 8.1.77 or later
Fixed in 8.1.77
Interim mitigation

Upgrade Pronestor Planner to version 8.1.77 or later to receive the vendor patch. If immediate upgrade is not feasible, review and correct NTFS permissions and service ACLs on PronestorHealthMonitor.exe to ensure only authorized users/processes can interact with the service.

Fix this in Planner Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-17390 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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