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

> Local attackers can escalate privileges to SYSTEM by exploiting weak directory permissions and binary hijacking in ManageEngine products.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-69r6-frgh-wc7c

## What is CVE-2019-12133?

CVE-2019-12133 is a high-severity vulnerability in Zohocorp Manageengine Opmanager, published on 18 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple Zoho ManageEngine products suffer from local privilege escalation due to improper permissions for the %SYSTEMDRIVE%\ManageEngine directory and its sub-folders. Moreover, the services associated with said products try to execute binaries such as sc.exe from the current directory upon system start. This will effectively allow non-privileged users to escalate privileges to NT AUTHORITY\SYSTEM. This affects Desktop Central 10.0.380, EventLog Analyzer 12.0.2, ServiceDesk Plus 10.0.0, SupportCenter Plus 8.1, O365 Manager Plus 4.0, Mobile Device Manager Plus 9.0.0, Patch Connect Plus 9.0.0, Vulnerability Manager Plus 9.0.0, Patch Manager Plus 9.0.0, OpManager 12.3, NetFlow Analyzer 11.0, OpUtils 11.0, Network Configuration Manager 11.0, FireWall 12.0, Key Manager Plus 5.6, Password Manager Pro 9.9, Analytics Plus 1.0, and Browser Security Plus.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-427 (Uncontrolled Search Path Element)

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

It affects 18 products.


Products: Zohocorp Manageengine Analytics Plus, Zohocorp Manageengine Browser Security Plus, Zohocorp Manageengine Desktop Central, Zohocorp Manageengine Eventlog Analyzer, Zohocorp Manageengine Firewall, Zohocorp Manageengine Key Manager Plus, Zohocorp Manageengine Mobile Device Manager Plus, Zohocorp Manageengine Netflow Analyzer, Zohocorp Manageengine Network Configuration Manager, Zohocorp Manageengine O365 Manager Plus, Zohocorp Manageengine Opmanager, Zohocorp Manageengine Oputils, Zohocorp Manageengine Password Manager Pro, Zohocorp Manageengine Patch Connect Plus, Zohocorp Manageengine Patch Manager Plus, Zohocorp Manageengine Servicedesk Plus, Zohocorp Manageengine Supportcenter Plus, Zohocorp Manageengine Vulnerability Manager Plus.

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

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

## Is CVE-2019-12133 being exploited?

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

## Other vulnerabilities in Zohocorp Manageengine Opmanager

- [CVE-2020-21642](https://insights.sbomify.com/CVE-2020-21642/): Path traversal in n/a (critical 9.8)
- [CVE-2025-9428](https://insights.sbomify.com/CVE-2025-9428/): SQL Injection (high 8.3)
- [CVE-2024-52323](https://insights.sbomify.com/CVE-2024-52323/): Sensitive Data Exposure (high 8.1)
- [CVE-2020-21641](https://insights.sbomify.com/CVE-2020-21641/): XML external entity in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12133 is a high-severity vulnerability in Zohocorp Manageengine Opmanager, published on 18 Jun 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-12133 in the wild and no public exploit code.

Affected product: Zohocorp Manageengine Opmanager. 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-12133/ (Markdown: https://insights.sbomify.com/CVE-2019-12133/index.md)
```

## Sources

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

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