CVE-2022-43534
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 ClearPass OnGuard Linux agent could allow malicious users on a Linux instance to elevate their user privileges. A successful exploit could allow these users to execute arbitrary code with root level privileges on the Linux instance in Aruba ClearPass Policy Manager version(s): ClearPass Policy Manager 6.10.x: 6.10.7 and below and ClearPass Policy Manager 6.9.x: 6.9.12 and below.
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 confidenceThe ClearPass OnGuard Linux agent has a local privilege escalation vulnerability that allows authenticated malicious users to execute arbitrary code with root privileges. This is a local privilege escalation flaw in the endpoint protection agent running on Linux systems managed by ClearPass Policy Manager.
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.12>= 6.10.0, < 6.10.7CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ClearPass Policy Manager installation and versionLocate the ClearPass Policy Manager installation and determine its installed version number (for example, via system inventory, package manager, or administrative interface)Affected if The installed version is 6.9.0 through 6.9.11 inclusive, or 6.10.0 through 6.10.6 inclusive (vulnerable ranges)
-
Check for OnGuard Linux agent deploymentDetermine whether the OnGuard Linux agent component is deployed on managed Linux endpoints in the environment (for example, via endpoint inventory, agent status check, or ClearPass administrative console)Affected if OnGuard Linux agent is installed and running on Linux systems managed by the ClearPass Policy Manager
-
Verify authenticated user accessIdentify whether standard or non-privileged user accounts have authenticated access to systems where the OnGuard Linux agent is deployedAffected if Non-root users have authenticated access to Linux endpoints with the OnGuard agent (the vulnerability allows such users to escalate to root)
You are affected if you have ClearPass Policy Manager version 6.9.0-6.9.11 or 6.10.0-6.10.6 with the OnGuard Linux agent deployed and non-administrative users have authenticated access to those endpoints.
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.126.10.7
Upgrade ClearPass Policy Manager to version 6.10.8 or higher (for 6.10.x branches) or 6.9.13 or higher (for 6.9.x branches) to address the vulnerability in the OnGuard Linux agent component.
ClearPass Policy Manager 6.9.12 (for 6.9.x branches) or 6.10.7 (for 6.10.x branches)
- 1. Identify the current installed version of ClearPass Policy Manager by navigating to Administration > About > Copyright in the ClearPass web UI
- 2. If running version 6.9.x (6.9.0 through 6.9.11), plan upgrade to version 6.9.12 or later
- 3. If running version 6.10.x (6.10.0 through 6.10.6), plan upgrade to version 6.10.7 or later
- 4. Review Aruba upgrade documentation and release notes for the target version
- 5. Take a full backup of the ClearPass configuration before upgrading
- 6. Schedule a maintenance window as the upgrade will require service downtime
- 7. Download the appropriate upgrade package from the Aruba support portal (https://asp.arubanetworks.com)
- 8. Apply the upgrade following Aruba's standard upgrade procedure for ClearPass Policy Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43534 — 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-2022-43534 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