CVE-2022-43540
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 exists in the ClearPass OnGuard macOS agent that allows for an attacker with local macOS instance access to potentially obtain sensitive information. A successful exploit could allow an attacker to retrieve information that is of a sensitive nature 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 · high confidenceA local information disclosure vulnerability exists in the ClearPass OnGuard macOS agent. An attacker with local access to a macOS system running the OnGuard agent can potentially retrieve sensitive information from the agent or its configuration. The vulnerability has low attack complexity requiring local access (AV:L) but does not require privileges (PR:N) according to the CVSS metrics.
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
- None
- Availability
- None
CVSS:3.1/AV:L/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 if OnGuard agent is installed on macOSCheck for OnGuard installation by looking for the agent process or installed application files. Common locations include /Applications folder and running processes via Activity Monitor or 'ps aux' command.Affected if OnGuard agent is present and running on the macOS system
-
Determine ClearPass Policy Manager versionAccess the ClearPass Policy Manager web interface or administrative console and navigate to the version information page. Alternatively, check the About section in the admin GUI.Affected if The installed version falls within >= 6.9.0 and < 6.9.12, or >= 6.10.0 and < 6.10.7
-
Check OnGuard agent version on endpointsOn each macOS endpoint with OnGuard installed, check the agent version through the agent UI or by querying the installed package version using system utilities.Affected if The OnGuard agent version does not match the patched versions (6.9.12+ or 6.10.7+) corresponding to the Policy Manager version
-
Inspect OnGuard configuration files for exposureExamine OnGuard configuration directories on macOS systems for any configuration files that may contain sensitive information such as credentials, tokens, or network settings accessible to local users.Affected if Sensitive information is stored in readable configuration files accessible to local users without elevated privileges
A system is affected if it runs a vulnerable version of ClearPass Policy Manager (6.9.0-6.9.11 or 6.10.0-6.10.6) with corresponding OnGuard macOS agents, allowing a local unprivileged attacker to access sensitive agent configuration data.
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
Apply the vendor-supplied patch by upgrading ClearPass Policy Manager to versions higher than 6.10.7 (for 6.10.x) or 6.9.12 (for 6.9.x), and ensure all deployed OnGuard macOS agents are updated to the corresponding patched versions.
ClearPass Policy Manager 6.9.12 or later (6.9.x branch); ClearPass Policy Manager 6.10.7 or later (6.10.x branch)
- 1. Backup current ClearPass Policy Manager configuration and data
- 2. Download the fixed version from Aruba Support Portal (6.9.12 for 6.9.x branch or 6.10.7 for 6.10.x branch)
- 3. Review Aruba upgrade documentation and release notes for prerequisites
- 4. Schedule maintenance window as upgrades may require service interruption
- 5. Run pre-upgrade checks using Aruba provided tools
- 6. Perform the upgrade following Aruba's official upgrade procedure
- 7. After upgrade, verify all services are running correctly
- 8. Validate that the ClearPass OnGuard agent is functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43540 — 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-43540 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