dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2025-23060

HIGH · 8.1 CVSS v3.1 Published 2025-02-04
Fix available
A fix is available. Upgrade to 6.11.10 / 6.12.4 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 HPE Aruba Networking ClearPass Policy Manager may, under certain circumstances, expose sensitive unencrypted information. Exploiting this vulnerability could allow an attacker to perform a man-in-the-middle attack, potentially granting unauthorized access to network resources as well as enabling data tampering.

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

HPE Aruba Networking ClearPass Policy Manager contains a vulnerability that under certain circumstances exposes sensitive information in an unencrypted manner, enabling man-in-the-middle attacks. This could allow attackers to intercept credentials or session data, potentially gaining unauthorized access to network resources and tampering with data in transit.

MitigationApply available patches from HPE Aruba Networking and review TLS/cryptographic configurations to ensure all sensitive communications are properly encrypted. Verify network segmentation to limit MITM attack vectors.

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.10>= 6.12.0, < 6.12.4

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify ClearPass Policy Manager version
    Access the ClearPass admin UI or use CLI to retrieve the installed version number (typically found in the About or System Dashboard section)
    Affected if The installed version falls within >= 6.11.0 and < 6.11.10, or >= 6.12.0 and < 6.12.4
  2. Confirm ClearPass is exposing sensitive data
    Inspect network traffic or TLS configuration to determine if credentials or session data are being transmitted without encryption
    Affected if Sensitive communications (authentication credentials, session tokens) are being sent in cleartext or over unencrypted channels
  3. Check for unencrypted administrative interfaces
    Review the ClearPass configuration for administrative access methods and verify whether HTTP (non-TLS) is enabled for login or API endpoints
    Affected if HTTP (port 80) or non-TLS administrative access is enabled and accessible
  4. Verify TLS configuration for internal communications
    Examine the TLS/cryptographic settings within ClearPass to ensure all internal and external communications use proper encryption
    Affected if TLS is disabled or weak ciphers are configured for sensitive data flows

A user is affected if their ClearPass version is 6.11.0 through 6.11.9 or 6.12.0 through 6.12.3 AND sensitive credentials or session data can be intercepted in transit due to unencrypted communication channels.

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.10 / 6.12.4 or later
Fixed in 6.11.106.12.4
Interim mitigation

Apply available patches from HPE Aruba Networking and review TLS/cryptographic configurations to ensure all sensitive communications are properly encrypted. Verify network segmentation to limit MITM attack vectors.

Recommended fix High confidence

ClearPass Policy Manager 6.11.10 or later for 6.11.x branch; 6.12.4 or later for 6.12.x branch

  1. 1. Identify the currently installed ClearPass Policy Manager version via the WebUI or CLI
  2. 2. If running version 6.11.x, plan an upgrade to version 6.11.10 or later within the 6.11.x release train
  3. 3. If running version 6.12.x, plan an upgrade to version 6.12.4 or later within the 6.12.x release train
  4. 4. Review HPE Aruba Networking release notes for upgrade prerequisites and procedures
  5. 5. Perform a full backup of the ClearPass configuration before upgrading
  6. 6. Schedule a maintenance window as upgrades require service interruption
  7. 7. Follow HPE official upgrade procedures to upgrade to the appropriate fixed version
  8. 8. After upgrade, verify the ClearPass Policy Manager services are running correctly
Caveat Review HPE release notes for each upgrade target version for any known compatibility or configuration changes before proceeding

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

Fix this in Clearpass Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23060 — 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-2025-23060 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