Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-29081 is a critical-severity Path Traversal (CWE-22) vulnerability in Zohocorp Manageengine Password Manager Pro. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Zoho ManageEngine Access Manager Plus before version 4302, Password Manager Pro before 12007, and PAM360 before 5401 contain an access-control bypass vulnerability on several REST API endpoints including SSOutAction, SSLAction, LicenseMgr, GetProductDetails, GetDashboard, FetchEvents, and Synchronize. The flaw, tracked as CWE-22, is triggered when an attacker supplies the ../RestAPI substring in requests to those URLs, allowing unauthorized access despite the products' intended controls. The issue carries a CVSS 3.1 score of 9.8 reflecting network-accessible exploitation with no required credentials or user interaction.
An unauthenticated remote attacker can leverage the bypass to reach restricted functionality on the affected REST endpoints, resulting in full compromise of confidentiality, integrity, and availability of the privileged-access management systems.
Vendor advisories at the referenced ManageEngine and Tenable URLs describe the affected builds and direct administrators to apply the fixed releases (Access Manager Plus 4302, Password Manager Pro 12007, and PAM360 5401) to close the exposure. The associated EPSS score stands at 0.8803 with no material post-disclosure climb from a lower baseline.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-33492
Vulnerability Data
Zoho ManageEngine Access Manager Plus before 4302, Password Manager Pro before 12007, and PAM360 before 5401 are vulnerable to access-control bypass on a few Rest API URLs (for SSOutAction. SSLAction. LicenseMgr. GetProductDetails. GetDashboard. FetchEvents. and Synchronize) via the ../RestAPI substring.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces access-control policy on the affected REST endpoints so that the ../RestAPI bypass cannot grant unauthorized access.
Requires validation of all input strings (including URL paths) to block the path-traversal sequence that evades the intended access controls.
Mandates prompt application of the vendor patches (4302/12007/5401) that eliminate the access-control flaw in the listed products.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.