# CVE-2022-36120: Missing authorization in n/a

> Authenticated users can bypass access controls in misconfigured Blue Prism servers to execute arbitrary MSSQL stored procedures via the getChartData function.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jf8w-hx4f-6vr5

## What is CVE-2022-36120?

CVE-2022-36120 is a high-severity missing authorization vulnerability in n/a, published on 25 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Blue Prism Enterprise 6.0 through 7.01. In a misconfigured environment that exposes the Blue Prism Application server, it is possible for an authenticated user to reverse engineer the Blue Prism software and circumvent access controls for the getChartData administrative function. Using a low/no privilege Blue Prism user account, the attacker can alter the server's settings by abusing the getChartData method, allowing the Blue Prism server to execute any MSSQL stored procedure by name.

## Which versions are affected by CVE-2022-36120?

It affects 1 product.


Products: Ssctech Blue Prism Enterprise.

## How do I fix CVE-2022-36120?

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

## Is CVE-2022-36120 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36121](https://insights.sbomify.com/CVE-2022-36121/): Missing authorization in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36120 and fix it if it is affected.

What it is: CVE-2022-36120 is a high-severity missing authorization vulnerability in n/a, published on 25 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36120 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-2022-36120/ (Markdown: https://insights.sbomify.com/CVE-2022-36120/index.md)
```

## Sources

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

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