CVE-2022-22229
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 · uneditedAn Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability, a stored XSS (or persistent), in the Control Center Controller web pages of Juniper Networks Paragon Active Assurance (Formerly Netrounds) allows a high-privilege attacker with 'WRITE' permissions to store one or more malicious scripts that will infect any other authorized user's account when they accidentally trigger the malicious script(s) while managing the device. Triggering these attacks enables the attacker to execute commands with the permissions up to that of the superuser account. This issue affects: Juniper Networks Paragon Active Assurance (Formerly Netrounds) All versions prior to 3.1.1; 3.2 versions prior to 3.2.1.
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 stored XSS vulnerability in the Control Center Controller web pages of Juniper Networks Paragon Active Assurance allows authenticated attackers with WRITE permissions to inject malicious scripts that persist and execute when other users interact with affected device management pages, potentially enabling command execution with superuser privileges.
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< 3.1.1= 3.2.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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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.
-
Verify Paragon Active Assurance Control Center versionAccess the Control Center web interface and navigate to the version/about information page, or use the administrative CLI to retrieve the installed Paragon Active Assurance Control Center version number.Affected if The installed version is lower than 3.1.1, or exactly equals 3.2.0.
-
Confirm Control Center web interface is enabledVerify that the Control Center Controller web service is running and accessible by attempting to reach the web portal URL.Affected if The web interface is accessible and the version falls within the affected range.
-
Identify users with WRITE permissionsReview user accounts and roles configured in the Control Center under Administration or User Management settings to identify accounts granted WRITE access.Affected if Any user account with WRITE permissions exists in the system, enabling potential exploitation.
-
Inspect Control Center Controller pages for injected scriptsAs an administrator, examine the device management pages under the Control Center Controller section for any unexpected script tags, JavaScript event handlers, or suspicious HTML in configuration fields, device names, or policy settings.Affected if Malicious script content is found persisted in any configuration or device management fields accessible through the Control Center Controller pages.
A user is affected if their Paragon Active Assurance Control Center version is below 3.1.1 or exactly 3.2.0, the web interface is accessible, and users with WRITE permissions exist in the system.
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 · scoped3.1.1
Upgrade to Paragon Active Assurance version 3.1.1 or 3.2.1 or later to obtain the vendor patch for this vulnerability.
Upgrade to Paragon Active Assurance Control Center 3.1.1+ (if on 3.1.x) or 3.2.1+ (if on 3.2.x)
- Identify the current version of Paragon Active Assurance Control Center by checking the system information or admin interface
- If running version < 3.1.1, plan upgrade to version 3.1.1 or later in the 3.1.x branch
- If running version 3.2.0, plan upgrade to version 3.2.1 or later in the 3.2.x branch
- Review Juniper Networks upgrade documentation and release notes for Paragon Active Assurance
- Perform the upgrade following the documented procedure, ensuring proper backups are in place
- Verify the upgrade was successful by checking the version number in the Control Center
- Confirm the XSS vulnerability is resolved by validating that user input is properly sanitized in the Control Center Controller web pages
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22229 — 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-22229 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