CVE-2019-19119
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 issue was discovered in PRTG 7.x through 19.4.53. Due to insufficient access control on local registry keys for the Core Server Service, a non-administrative user on the local machine is able to access administrative credentials.
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 confidencePRTG Network Monitor versions 7.x through 19.4.53 contain insufficient access control on local registry keys for the Core Server Service, allowing non-administrative users to read registry keys containing administrative credentials, enabling local privilege escalation.
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>= 7.0, <= 19.4.53.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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Check PRTG Network Monitor versionOpen PRTG Administration Tool or check Programs and Features to find the installed version of PRTG Network MonitorAffected if The installed version is greater than or equal to 7.0 and less than or equal to 19.4.53
-
Locate PRTG registry keys for Core Server credentialsNavigate to the registry keys storing PRTG Core Server Service credentials. These are typically under the PRTG installation registry path (commonly HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG or HKEY_CURRENT_USER\SOFTWARE\Paessler\PRTG)Affected if Registry keys containing administrative credentials exist for the PRTG Core Server Service
-
Verify registry key permissions for non-administrative usersRight-click the affected registry keys, select Permissions, and check if Users or Non-Admin groups have Read or Full Control access. Use 'reg query' with limited user account or check Effective Access to verify non-admin permissionsAffected if Non-administrative users or groups have Read or higher permissions on the credential-containing registry keys
-
Test read access with limited user accountUsing a non-administrative Windows account, attempt to read the PRTG registry keys using regedit or reg query commandAffected if A non-administrative user can successfully read registry keys that contain administrative credentials
A user is affected if running PRTG Network Monitor version 7.0 through 19.4.53 and non-administrative accounts have read access to registry keys storing Core Server administrative credentials.
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 NTFS/registry permissions on the affected PRTG registry keys to administrative-only users, or upgrade to a patched version of PRTG.
- 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-2019-19119 — 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-2019-19119 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