CVE-2022-35405
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 · uneditedZoho ManageEngine Password Manager Pro before 12101 and PAM360 before 5510 are vulnerable to unauthenticated remote code execution. (This also affects ManageEngine Access Manager Plus before 4303 with authentication.)
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 confidenceZoho ManageEngine Password Manager Pro before version 12101 and PAM360 before version 5510 contain an unauthenticated remote code execution vulnerability, allowing attackers to execute arbitrary code without credentials. This critical flaw affects the core authentication mechanism and can be exploited remotely over the network.
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< 4.3= 4.3< 5.5= 5.5< 12.1= 12.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if a Zoho password management product is installedCheck for running processes or installed software named 'ManageEngine Password Manager Pro', 'ManageEngine PAM360', or 'ManageEngine Access Manager Plus'. On Windows, review installed programs in Add/Remove Programs. On Linux, check for /opt/ManageEngine/* directories or running Java processes with these product names.Affected if Any of these three products are found running or installed on the system
-
Determine the installed version of Password Manager ProFor Password Manager Pro, check the version by opening the admin console and looking at the login page footer, or locate the build number in the installation directory (typically in a version.txt or build.info file in the product's root folder).Affected if The installed version is lower than 12.1.01 (or build number less than 12101)
-
Determine the installed version of PAM360For PAM360, check the version by viewing the login page footer in the admin console, or locate the build file in the installation directory. The version format is typically displayed as 5.x.x where the full build number like 5510 corresponds to version 5.5.510.Affected if The installed version is lower than 5.5.510 (or build number less than 5510)
-
Determine the installed version of Access Manager PlusFor Access Manager Plus, check the version by viewing the admin console login page footer or checking the build.info file in the installation directory.Affected if The installed version is lower than 4.3 or equals exactly 4.3
-
Assess network exposure of the productCheck firewall rules, network configuration, and listen addresses to determine if the product's web interface (typically on ports 8080, 8443, or 7272) is accessible from untrusted networks or the internet. Review any exposed IP addresses in the product's server configuration.Affected if The web interface is reachable from untrusted networks without VPN or segmentation
If any of these three products are installed and the version falls within the affected ranges (< 4.3 or = 4.3 for Access Manager Plus, < 5.5 or = 5.5 for PAM360, < 12.1 or = 12.1 for Password Manager Pro) and the service is network-accessible, the environment is vulnerable to unauthenticated remote code execution.
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 · scoped4.35.512.1
Upgrade Password Manager Pro to version 12101 or higher, PAM360 to version 5510 or higher, and Access Manager Plus to version 4303 or higher. Until patches are applied, restrict network exposure to these services and implement network segmentation.
Password Manager Pro: 12.1.01+ | PAM360: 5.5.10+ | Access Manager Plus: 4.3.03+
- 1. Identify which ManageEngine product(s) are in use (Password Manager Pro, PAM360, or Access Manager Plus)
- 2. Check current installed version of the affected product
- 3. For Password Manager Pro: Upgrade to version 12101 (12.1.01) or later
- 4. For PAM360: Upgrade to version 5510 (5.5.10) or later
- 5. For Access Manager Plus: Upgrade to version 4303 (4.3.03) or later
- 6. After upgrade, verify the new version is running
- 7. Review release notes for any additional post-upgrade configuration requirements
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-35405 — 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-35405 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