CVE-2022-37882
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 · uneditedVulnerabilities in the ClearPass Policy Manager web-based management interface allow remote authenticated users to run arbitrary commands on the underlying host. A successful exploit could allow an attacker to execute arbitrary commands as root on the underlying operating system leading to complete system compromise in Aruba ClearPass Policy Manager version(s): 6.10.x: 6.10.6 and below; 6.9.x: 6.9.11 and below. Aruba has released upgrades for Aruba ClearPass Policy Manager that address these security vulnerabilities.
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 confidenceAuthenticated command injection vulnerability in Aruba ClearPass Policy Manager web interface allows remote users with valid credentials to execute arbitrary OS commands with root privileges. The flaw stems from insufficient input validation in web management functions, enabling attackers to break out of the application sandbox and compromise the underlying host.
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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Determine installed ClearPass Policy Manager versionAccess the web management interface and navigate to Administration > Server Management > Server Diagnostics, or run 'show version' via CLI on the applianceAffected if The installed version falls within 6.9.0 to 6.9.11, or 6.10.0 to 6.10.6
-
Verify web management interface is enabledCheck if the ClearPass Policy Manager web UI (port 443/TCP or 80/TCP) is accessible from network locations where untrusted users could connectAffected if The web management interface is exposed to untrusted networks without strong access controls
-
Review user accounts for unauthorized administrative accountsNavigate to Administration > User Management > Users in the web UI, or query the database via CLI with 'sqlite3 /var/lib/clearpass/data/clearpass.db "SELECT name,role_id FROM operator WHERE role_id=1"'Affected if Unexpected or unknown administrator-level accounts exist beyond those created by your organization
-
Inspect system logs for suspicious command executionReview /var/log/clearpass/auth.log and /var/log/messages for patterns indicating command injection, such as unusual shell metacharacters or unexpected command paths spawned from web requestsAffected if Logs show commands containing shell metacharacters (such as ; | & $()) originating from web management endpoints, or commands executed as root from unexpected sources
You are affected if your ClearPass Policy Manager version is 6.9.0 through 6.9.11 or 6.10.0 through 6.10.6, and the web management interface is accessible to authenticated users or potential attackers.
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 Aruba-provided software upgrades to ClearPass Policy Manager 6.10.x to version 6.10.7 or higher, and 6.9.x to version 6.9.12 or higher. Prioritize patching for internet-facing instances due to the high impact of complete system compromise.
Upgrade to ClearPass Policy Manager 6.9.12 or later (for 6.9.x branch), or 6.10.7 or later (for 6.10.x branch)
- 1. Obtain the upgrade package from the Aruba support portal (https://asp.arubanetworks.com) for your specific version path (6.9.x or 6.10.x)
- 2. Ensure you have a complete backup of the ClearPass Policy Manager configuration and, if possible, a system snapshot or snapshot before proceeding
- 3. Log into the ClearPass Policy Manager web-based management interface as an administrator
- 4. Navigate to the Administration > Server Manager > Server Configuration section, or use the CLI for upgrades
- 5. Upload the appropriate upgrade package (.tar.gz or similar) for version 6.9.12 (if on 6.9.x) or 6.10.7 (if on 6.10.x)
- 6. Follow the on-screen prompts to apply the upgrade, confirming when prompted
- 7. Allow the upgrade to complete - do not interrupt the process
- 8. After the system restarts, verify the new version by checking Help > About in the web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37882 — 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-37882 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