dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2024-41915

HIGH · 8.8 CVSS v3.1 Published 2024-07-30
Fix available
A fix is available. Upgrade to 6.11.9 / 6.12.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability in the web-based management interface of ClearPass Policy Manager could allow an authenticated remote attacker to conduct SQL injection attacks against the ClearPass Policy Manager instance. An attacker could exploit this vulnerability to obtain and modify sensitive information in the underlying database potentially leading to complete compromise of the ClearPass Policy Manager cluster.

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 confidence

SQL injection vulnerability in the web-based management interface of ClearPass Policy Manager allows authenticated remote attackers to inject malicious SQL queries, potentially compromising the underlying database and the entire ClearPass Policy Manager cluster.

MitigationApply vendor-supplied patches for ClearPass Policy Manager when available; in the interim, restrict management interface access to trusted users only and monitor for anomalous SQL patterns in logs.

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
Clearpass Policy ManagerApplication
Affected:>= 6.11.0, < 6.11.9>= 6.12.0, < 6.12.2

CVSS 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
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed ClearPass Policy Manager version
    Log into the ClearPass CLI or admin web interface and locate the version information, typically found in About or System Diagnostics sections
    Affected if The version number falls within 6.11.0 through 6.11.8 OR 6.12.0 through 6.12.1 (the affected ranges)
  2. Verify the web-based management interface is accessible
    Confirm the ClearPass Policy Manager web administration portal (HTTPS) is reachable from network locations
    Affected if The management interface is exposed to untrusted networks or users
  3. Confirm authentication to the management interface is possible
    Verify that valid administrator credentials exist and can log into the ClearPass web interface
    Affected if Authenticated access to the web management interface is possible, which is required for exploitation
  4. Review management interface access controls
    Check the IP access list or network restrictions configured for the ClearPass admin portal in the network settings
    Affected if No IP-based restrictions are applied, allowing broad access to the management interface

You are affected if your ClearPass Policy Manager version is 6.11.x below 6.11.9 or 6.12.x below 6.12.2 AND the web-based management interface is accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.11.9 / 6.12.2 or later
Fixed in 6.11.96.12.2
Interim mitigation

Apply vendor-supplied patches for ClearPass Policy Manager when available; in the interim, restrict management interface access to trusted users only and monitor for anomalous SQL patterns in logs.

Recommended fix High confidence

6.11.9 or later (for 6.11.x branch); 6.12.2 or later (for 6.12.x branch)

  1. 1. Identify the current installed version of ClearPass Policy Manager by checking the Administration > Server Manager > Server Configuration section.
  2. 2. If running version 6.11.x and less than 6.11.9, plan to upgrade to version 6.11.9 or later.
  3. 3. If running version 6.12.x and less than 6.12.2, plan to upgrade to version 6.12.2 or later.
  4. 4. Review HPE ClearPass Policy Manager release notes for any prerequisites or known issues before upgrading.
  5. 5. Perform a full backup of the ClearPass Policy Manager configuration.
  6. 6. Schedule a maintenance window as the upgrade may require service interruption.
  7. 7. Download the appropriate upgrade package from the HPE Support portal (support.hpe.com).
  8. 8. Apply the upgrade following the official HPE upgrade procedure documentation.
Caveat Review release notes for any configuration changes or backward compatibility notices before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clearpass Policy Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41915 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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