CVE-2024-26301
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 · uneditedA vulnerability in the web-based management interface of ClearPass Policy Manager could allow a remote attacker authenticated with low privileges to access sensitive information. A successful exploit allows an attacker to retrieve information which could be used to potentially gain further access to network services supported by ClearPass Policy Manager.
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 confidenceClearPass Policy Manager's web-based management interface has an access control flaw allowing authenticated low-privilege users to access sensitive information that should be restricted to higher-privilege accounts. This information disclosure could enable further network service compromise.
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.9.0, < 6.9.13>= 6.10.0, < 6.10.8>= 6.11.0, <= 6.11.6= 6.9.13= 6.10.8= 6.12.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify ClearPass Policy Manager versionAccess the web UI: navigate to Administration > About > Copyrights, or use CLI: show version on the applianceAffected if The installed version falls within 6.9.0-6.9.13, 6.10.0-6.10.8, 6.11.0-6.11.6, or is exactly 6.12.0
-
Confirm web-based management interface is enabledCheck if the ClearPass Policy Manager web UI is accessible on ports 443 or 8080, or verify in CLI: show http-server statusAffected if The web management interface is exposed and accessible
-
Inspect for unauthorized access to sensitive endpointsReview ClearPass audit logs at Monitoring > Logs > Audit, filtering for low-privilege users accessing restricted areas like Administration > Server Settings, or sensitive API endpoints under /api/Affected if Low-privilege users have accessed functionality or data designated for Super Admin roles
A user is affected if they run a ClearPass Policy Manager version within the affected ranges AND have the web UI enabled AND have non-admin user accounts, with potential evidence of unauthorized access in audit logs.
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.9.136.10.8
Apply vendor patches when available. Until then, restrict web management interface access to only necessary personnel and monitor for anomalous access patterns from low-privilege accounts.
Upgrade to 6.9.13 (for 6.9.x), 6.10.8 (for 6.10.x), or 6.11.7 or later (for 6.11.x)
- Identify the currently installed ClearPass Policy Manager version via the web UI (Help > About) or CLI
- Schedule a maintenance window for the upgrade process
- Back up the ClearPass Policy Manager configuration via the web UI (Administration > Backup & Restore) or CLI
- Download the appropriate upgrade image from the Aruba support portal (www.arubanetworks.com) for your version path
- Upload the upgrade image via the web UI (Administration > Software Update) or via CLI
- Follow the on-screen prompts to install the upgrade and allow the system to reboot
- After reboot, verify the new version is installed (Help > About) and confirm all services are running
- Verify the vulnerability is remediated by checking that the specific low-privilege information disclosure is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26301 — 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-26301 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