CVE-2024-51772
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 authenticated RCE vulnerability in the ClearPass Policy Manager web-based management interface allows remote authenticated users to run arbitrary commands on the underlying host. Successful exploitation could allow an attacker to execute arbitrary commands on the underlying operating system.
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 confidenceAuthenticated RCE vulnerability in ClearPass Policy Manager's web-based management interface allows remote authenticated users to execute arbitrary commands on the underlying host operating system.
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.11.0, < 6.11.10>= 6.12.0, < 6.12.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 ClearPass Policy Manager installationCheck if ClearPass Policy Manager is present by running 'show version' on the CLI or checking the web interface login page for ClearPass brandingAffected if ClearPass Policy Manager is not installed, then not affected
-
Determine installed versionRun 'show version' command via CLI or check the web interface footer/login page for version informationAffected if Version is 6.11.0 through 6.11.9 OR 6.12.0 through 6.12.2 (note: versions 6.11.10+ and 6.12.3+ are patched)
-
Verify web management interface is accessibleAttempt to access the ClearPass web interface via browser on port 443 (HTTPS) or check if the web service is running via CLI command such as 'show web-server status'Affected if Web management interface is not exposed or not running, then less likely to be exploitable externally
-
Confirm authentication is enabledCheck if local or external authentication providers (Active Directory, LDAP, etc.) are configured and enabled in ClearPass via 'Configuration > Authentication > Sources'Affected if Authentication is disabled and no users can log in, the RCE cannot be exploited since it requires valid credentials
Environment is affected if ClearPass Policy Manager version is 6.11.0-6.11.9 or 6.12.0-6.12.2 AND the web management interface is accessible with valid authentication enabled.
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.11.106.12.3
Apply vendor patch immediately; restrict management interface access to trusted IP addresses and minimize the number of authenticated users with administrative privileges.
Upgrade to ClearPass Policy Manager 6.11.10 or 6.12.3 (or later stable release)
- 1. Log into ClearPass Policy Manager admin interface and navigate to Administration > System > Status to confirm the current version.
- 2. Review the HPE ClearPass Policy Manager upgrade guide and release notes for the target fixed version (6.11.10 or 6.12.3).
- 3. Schedule a maintenance window as upgrades may require service downtime.
- 4. Perform a full backup of the ClearPass Policy Manager configuration via Administration > Backup & Restore.
- 5. Download the appropriate upgrade image from the HPE support portal (support.hpe.com) for your target version.
- 6. Upload the upgrade package through the web interface (Administration > Server Manager > Server Configuration) or CLI as documented.
- 7. Monitor the upgrade process and verify the service restarts successfully.
- 8. Confirm the new version (6.11.10 or 6.12.3) is installed under Administration > System > Status.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51772 — 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-51772 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