# CVE-2021-36232: Privilege escalation in n/a

> An authenticated attacker can escalate privileges in MIK.starlight due to improper authorization in multiple functions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8h4j-5rm7-8xxj

## What is CVE-2021-36232?

CVE-2021-36232 is a high-severity vulnerability in n/a, published on 31 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Authorization in multiple functions in MIK.starlight 7.9.5.24363 allows an authenticated attacker to escalate privileges.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-36232?

It affects 1 product.


Products: Unit4 Mik.starlight.

## How do I fix CVE-2021-36232?

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

## Is CVE-2021-36232 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-36231](https://insights.sbomify.com/CVE-2021-36231/): Deserialization in n/a (high 8.8)
- [CVE-2021-36233](https://insights.sbomify.com/CVE-2021-36233/): Path traversal in n/a (medium 6.5)
- [CVE-2021-36234](https://insights.sbomify.com/CVE-2021-36234/): Hardcoded credentials in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36232 and fix it if it is affected.

What it is: CVE-2021-36232 is a high-severity vulnerability in n/a, published on 31 Aug 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-2021-36232 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-2021-36232/ (Markdown: https://insights.sbomify.com/CVE-2021-36232/index.md)
```

## Sources

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

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