# CVE-2020-35593: Privilege escalation in n/a

> Local attackers can escalate privileges on systems running BMC PATROL Agent by exploiting the pconfig restart command.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 5 Sep 2023
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-8hxx-8cjf-cxvg

## What is CVE-2020-35593?

CVE-2020-35593 is a high-severity vulnerability in n/a, published on 5 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BMC PATROL Agent through 20.08.00 allows local privilege escalation via vectors involving pconfig +RESTART -host.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-35593?

It affects 1 product.


Products: Bmc Patrol Agent.

## How do I fix CVE-2020-35593?

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

## Is CVE-2020-35593 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-35593 exists.

## Other vulnerabilities in n/a

- [CVE-2008-5982](https://insights.sbomify.com/CVE-2008-5982/): Other in n/a (critical 10.0)
- [CVE-1999-0801](https://insights.sbomify.com/CVE-1999-0801/): Auth bypass in n/a (critical 10.0)
- [CVE-1999-0443](https://insights.sbomify.com/CVE-1999-0443/): Auth bypass in n/a (critical 10.0)
- [CVE-2023-34257](https://insights.sbomify.com/CVE-2023-34257/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-8352](https://insights.sbomify.com/CVE-2019-8352/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35593 and fix it if it is affected.

What it is: CVE-2020-35593 is a high-severity vulnerability in n/a, published on 5 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-35593 exists.

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-2020-35593/ (Markdown: https://insights.sbomify.com/CVE-2020-35593/index.md)
```

## Sources

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

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