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

> Low-privilege users can delete API keys of other users, including administrators, leading to potential privilege escalation and service disruption.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A: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:** 28 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-55ph-7h5c-gfhx

## What is CVE-2022-31884?

CVE-2022-31884 is a medium-severity missing authorization vulnerability in n/a, published on 28 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Marval MSM v14.19.0.12476 has an Improper Access Control vulnerability which allows a low privilege user to delete other users API Keys including high privilege and the Administrator users API Keys.

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

It affects 1 product.


Products: Marvalglobal Marval Msm.

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

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

## Is CVE-2022-31884 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31885](https://insights.sbomify.com/CVE-2022-31885/): Command injection in n/a (critical 9.8)
- [CVE-2022-31887](https://insights.sbomify.com/CVE-2022-31887/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-31883](https://insights.sbomify.com/CVE-2022-31883/): Information disclosure in n/a (high 8.8)
- [CVE-2022-31886](https://insights.sbomify.com/CVE-2022-31886/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31884 is a medium-severity missing authorization vulnerability in n/a, published on 28 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31884 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-31884/ (Markdown: https://insights.sbomify.com/CVE-2022-31884/index.md)
```

## Sources

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

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