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

> An operator-level user can improperly access stored SSL certificates and private keys due to insufficient authorization checks in Key Manager Plus.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 2 Mar 2022
- **Updated:** 30 May 2025
- **Also known as:** GHSA-9mj5-r67q-gqfq

## What is CVE-2022-24447?

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

### Official description

An issue was discovered in Zoho ManageEngine Key Manager Plus before 6200. A service exposed by the application allows a user, with the level Operator, to access stored SSL certificates and associated key pairs during export.

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

It affects 1 product.


Products: Zohocorp Manageengine Key Manager Plus.

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

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

## Is CVE-2022-24447 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28382](https://insights.sbomify.com/CVE-2021-28382/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2022-24446](https://insights.sbomify.com/CVE-2022-24446/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24447 is a medium-severity missing authorization vulnerability in n/a, published on 2 Mar 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-24447 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-24447/ (Markdown: https://insights.sbomify.com/CVE-2022-24447/index.md)
```

## Sources

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

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