CVE-2024-27312
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 · uneditedZohocorp ManageEngine PAM360 version 6601 is vulnerable to authorization vulnerability which allows a low-privileged user to perform admin actions. Note: This vulnerability affects only the PAM360 6600 version. No other versions are applicable to this vulnerability.
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 · moderate confidenceManageEngine PAM360 version 6601 contains an authorization flaw that permits authenticated low-privileged users to bypass role-based access controls and execute administrative operations. This represents a privilege escalation vulnerability where the application's access control logic fails to properly validate user permissions before allowing sensitive actions.
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< 6.6= 6.6CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Determine PAM360 installation versionAccess the PAM360 admin console and navigate to the About or Settings page to view the installed version number. Alternatively, check the installation directory for a version file or examine the application's startup logs for the version string.Affected if The installed version is 6601 or any version below 6.6 (e.g., 6.5.x, 6.4.x)
-
Verify application is accessible and runningConfirm the PAM360 web interface is reachable and the service is active. Attempt to log in with a standard user account to verify the application accepts authentication.Affected if The application is running and accessible with user authentication enabled
-
Identify low-privileged user accountsUsing an administrative account, navigate to the Users or User Management section and enumerate accounts with non-administrative roles (e.g., Standard User, Operator, or custom roles with limited permissions).Affected if Low-privileged user accounts exist in the system with restricted role assignments
-
Review role-based access control configurationExamine the Roles or Access Control settings to confirm that non-administrative roles have limited permissions and are explicitly restricted from administrative operations.Affected if RBAC is configured but may contain misconfigurations allowing permission bypass
-
Check for unauthorized administrative actions in audit logsReview PAM360 audit or activity logs for instances where low-privileged users have performed administrative operations (e.g., password resets, asset management, configuration changes).Affected if Audit logs show low-privileged users executing operations outside their assigned role permissions
A system is affected if it runs PAM360 version 6601 or any version below 6.6 and has low-privileged authenticated users who can potentially bypass role restrictions to perform administrative actions.
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 · scoped6.6
Apply the vendor-provided patch for PAM360 version 6601; if unavailable, implement compensating controls such as strict role segregation and enhanced monitoring of low-privileged account activity until a fix is released.
PAM360 version 6.6 or later (upgrade to the latest stable release)
- 1. Back up the current PAM360 installation and database before proceeding with any upgrade.
- 2. Download the latest version of ManageEngine PAM360 from the official ManageEngine website (www.manageengine.com).
- 3. Stop the PAM360 service to ensure a clean upgrade process.
- 4. Install or upgrade to PAM360 version 6.6 or later (preferably the most recent stable release).
- 5. Start the PAM360 service after the upgrade completes.
- 6. Verify that the upgrade was successful by logging into the PAM360 console.
- 7. Test with a low-privileged user account to confirm that unauthorized admin actions are no longer possible.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27312 — 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-2024-27312 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