CVE-2022-24447
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis authorization bypass vulnerability in Zoho ManageEngine Key Manager Plus prior to version 6200 allows users with Operator-level privileges to export stored SSL certificates along with their associated private key pairs. The application service fails to properly restrict the certificate/key export functionality, permitting lower-privileged users to access sensitive cryptographic material they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.9= 6.0= 6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Key Manager Plus installationLocate the ManageEngine Key Manager Plus installation directory, typically found under the ManageEngine folder in Program Files (Windows) or /opt (Linux/Unix). Look for the product executable or service.Affected if The product is installed on the system
-
Determine installed versionCheck the version of Key Manager Plus by accessing the product's web interface (usually on port 6767) and viewing the About/Help section, or by locating a version file in the installation directory.Affected if Unable to determine the version from the product interface or installation files
-
Compare version against affected rangesCompare your installed version number to the affected versions: any build <= 5.9, build 6.0, or build 6.1. Versions prior to 6200 are considered vulnerable.Affected if The installed version is 5.9 or lower, exactly 6.0, or exactly 6.1 (any build before 6200)
-
Verify Operator-level accounts existLog into Key Manager Plus as an administrator and review user accounts in the User Management section to confirm Operator-level users are configured.Affected if Operator-level accounts exist in the system and the product version is in the affected range
A user is affected if ManageEngine Key Manager Plus version is 5.9 or lower, 6.0, or 6.1 (any version before 6200) and Operator-level accounts are present in the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade ManageEngine Key Manager Plus to version 6200 or later to remediate this authorization vulnerability. Restrict Operator-level accounts until the upgrade is completed.
Version 6200 (6.2.0) or later
- 1. Back up the current ManageEngine Key Manager Plus installation and database
- 2. Download Key Manager Plus version 6200 or later from the official ManageEngine download portal (https://www.manageengine.com/key-manager/)
- 3. Stop the Key Manager Plus service
- 4. Install the upgrade following standard ManageEngine upgrade procedures
- 5. Start the Key Manager Plus service
- 6. Verify the fix by confirming that Operator-level users can no longer export SSL certificates and associated private keys without proper authorization
- 7. Test with different user roles to ensure proper access controls are enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24447 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24447 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data