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

> Attackers can escalate privileges to Domain Administrator by modifying the UserRoleKey parameter in intercepted requests.

- **Severity:** Critical 9.6 (`CVSS:3.0/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xpg5-6226-vf59

## What is CVE-2020-9002?

CVE-2020-9002 is a critical vulnerability in n/a, published on 1 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in iPortalis iCS 7.1.13.0. An attacker can gain privileges by intercepting a request and changing UserRoleKey=COMPANY_ADMIN to UserRoleKey=DOMAIN_ADMIN (to achieve Domain Administrator access).

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Iportalis Iportalis Control Portal.

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

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

## Is CVE-2020-9002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9000](https://insights.sbomify.com/CVE-2020-9000/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9002 is a critical vulnerability in n/a, published on 1 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9002 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-2020-9002/ (Markdown: https://insights.sbomify.com/CVE-2020-9002/index.md)
```

## Sources

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

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