# CVE-2019-19119: Information disclosure in n/a

> Local non-admin users can access administrative credentials due to insufficient access control on registry keys in PRTG Core Server Service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mcpx-9c5r-qxfc

## What is CVE-2019-19119?

CVE-2019-19119 is a medium-severity vulnerability in n/a, published on 3 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2019-19119?

It affects 1 product.


Products: Paessler Prtg Network Monitor.

## How do I fix CVE-2019-19119?

No fix has been published for CVE-2019-19119 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-19119 being exploited?

There is no known exploitation of CVE-2019-19119 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-19410](https://insights.sbomify.com/CVE-2018-19410/): Paessler PRTG Network Monitor Local File Inclusion (critical 9.8, exploited in the wild)
- [CVE-2018-9276](https://insights.sbomify.com/CVE-2018-9276/): Paessler PRTG Network Monitor OS Command Injection (high 7.2, exploited in the wild)
- [CVE-2020-10374](https://insights.sbomify.com/CVE-2020-10374/): Command injection in n/a (critical 9.8)
- [CVE-2023-51630](https://insights.sbomify.com/CVE-2023-51630/): Paessler PRTG Network Monitor Cross-Site Scripting Authentication Bypass Vulnerability (high 8.8)
- [CVE-2023-31452](https://insights.sbomify.com/CVE-2023-31452/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19119 and fix it if it is affected.

What it is: CVE-2019-19119 is a medium-severity vulnerability in n/a, published on 3 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19119 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-19119/ (Markdown: https://insights.sbomify.com/CVE-2019-19119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-19119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-19119
- OSV: https://osv.dev/vulnerability/CVE-2019-19119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-19119/
Summaries are generated and may contain mistakes; the official description above is the record.