# CVE-2020-13421: Missing authorization in n/a

> Attackers can create users, modify permissions, or reset passwords without proper authorization, leading to privilege escalation and account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 6 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hjj2-x4c3-xqp4

## What is CVE-2020-13421?

CVE-2020-13421 is a critical missing authorization vulnerability in n/a, published on 6 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenIAM before 4.2.0.3 has Incorrect Access Control for the Create User, Modify User Permissions, and Password Reset actions.

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

It affects 1 product.


Products: Openiam Openiam.

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

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

## Is CVE-2020-13421 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-13420](https://insights.sbomify.com/CVE-2020-13420/): Code injection in n/a (critical 9.8)
- [CVE-2020-13422](https://insights.sbomify.com/CVE-2020-13422/): Missing authorization in n/a (high 8.1)
- [CVE-2020-13418](https://insights.sbomify.com/CVE-2020-13418/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-13419](https://insights.sbomify.com/CVE-2020-13419/): Path traversal in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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