CVE-2022-23674
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 remote authenticated stored cross-site scripting (xss) vulnerability was discovered in Aruba ClearPass Policy Manager version(s): 6.10.4 and below, 6.9.9 and below, 6.8.9-HF2 and below, 6.7.x and below. Aruba has released updates to ClearPass Policy Manager that address this security vulnerability.
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 remote authenticated stored cross-site scripting (XSS) vulnerability in Aruba ClearPass Policy Manager allows an authenticated attacker to inject malicious JavaScript into the application that persists and executes when other users view the injected content.
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.7.14>= 6.8.0, < 6.8.9>= 6.9.0, <= 6.9.9>= 6.10.0, <= 6.10.4= 6.8.9CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Check ClearPass Policy Manager version via web UILog into the ClearPass admin web interface and navigate to the About or System Information page, typically found under Administration > About or in the footer of the admin dashboardAffected if The displayed version falls within <= 6.7.14, >= 6.8.0 and < 6.8.9, = 6.8.9, >= 6.9.0 and <= 6.9.9, or >= 6.10.0 and <= 6.10.4
-
Check ClearPass Policy Manager version via CLIAccess the ClearPass server via SSH or console and run the command 'show version' or 'cat /etc/version' to retrieve the installed versionAffected if The version output matches any of the affected ranges listed above
-
Verify web interface is enabledConfirm that the ClearPass Policy Manager web administration interface is accessible and operational by attempting to reach the login pageAffected if The web interface is accessible (which is the default configuration for ClearPass Policy Manager)
If the installed ClearPass Policy Manager version is 6.7.x and <= 6.7.14, 6.8.x and < 6.8.9 or = 6.8.9, 6.9.x and <= 6.9.9, or 6.10.x and <= 6.10.4, the environment is affected by this stored XSS vulnerability.
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.8.9
Apply the vendor-released updates for ClearPass Policy Manager to address this vulnerability. For affected versions, upgrade to 6.10.5, 6.9.10, 6.8.9-HF3, or 6.7.13 or later as appropriate.
Upgrade to 6.7.15 or later for 6.7.x; 6.8.9 or later for 6.8.x; 6.9.10 or later for 6.9.x; 6.10.5 or later for 6.10.x
- 1. Identify the current installed version of ClearPass Policy Manager by accessing the Administration > Server Management > Server Configuration dashboard.
- 2. Review the current backup status and ensure a recent configuration backup exists before proceeding with any upgrade.
- 3. Download the appropriate upgrade image from the Aruba Support Portal (https://asp.arubanetworks.com) for the target fixed version.
- 4. Upload the upgrade image through the ClearPass Policy Manager web interface under Administration > Server Management > Server Upgrade.
- 5. Initiate the upgrade process and monitor the progress; the system will automatically reboot upon completion.
- 6. After the system restarts, verify the upgrade was successful by checking the version number in Administration > Server Management > Server Configuration.
- 7. Clear browser cache and test the application functionality to ensure the XSS vulnerability is remediated.
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-23674 — 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-23674 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