# CVE-2019-19460: Privilege escalation in n/a

> The webserver runs with SYSTEM privileges by default, allowing attackers to write to any file system path if combined with other vulnerabilities.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v5mw-2gc6-7h62

## What is CVE-2019-19460?

CVE-2019-19460 is a medium-severity vulnerability in n/a, published on 3 Dec 2019. 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 SALTO ProAccess SPACE 5.4.3.0. The product's webserver runs as a Windows service with local SYSTEM permissions by default. This is against the principle of least privilege. An attacker who is able to exploit CVE-2019-19458 or CVE-2019-19459 is basically able to write to every single path on the file system, because the webserver is running with the highest privileges available.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Saltosystem Proaccess Space.

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

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

## Is CVE-2019-19460 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19459](https://insights.sbomify.com/CVE-2019-19459/): Path traversal in n/a (critical 9.8)
- [CVE-2019-19458](https://insights.sbomify.com/CVE-2019-19458/): Path traversal in n/a (high 8.6)
- [CVE-2019-19457](https://insights.sbomify.com/CVE-2019-19457/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19460 is a medium-severity vulnerability in n/a, published on 3 Dec 2019. 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-19460 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-19460/ (Markdown: https://insights.sbomify.com/CVE-2019-19460/index.md)
```

## Sources

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

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