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

> An elevated privileges issue in Spring MVC calls allows attackers to gain higher access levels in Code Insight.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 17 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-24jf-233j-q8x3

## What is CVE-2020-12083?

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

### Official description

An elevated privileges issue related to Spring MVC calls impacts Code Insight v7.x releases up to and including 2020 R1 (7.11.0-64).

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

It affects 1 product.


Products: Flexera Flexnet Code Insight.

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

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

## Is CVE-2020-12083 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12082](https://insights.sbomify.com/CVE-2020-12082/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12083 is a critical vulnerability in n/a, published on 17 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-12083 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-12083/ (Markdown: https://insights.sbomify.com/CVE-2020-12083/index.md)
```

## Sources

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

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