# CVE-2022-22229: Paragon Active Assurance (Formerly Netrounds): Stored Cross-site Scripting (XSS) vulnerability in web administration

> A stored XSS vulnerability in Juniper Paragon Active Assurance allows high-privilege attackers to execute scripts and escalate privileges to superuser level.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2022
- **Updated:** 12 May 2025
- **Also known as:** GHSA-h8xr-vrcj-c52v

## What is CVE-2022-22229?

CVE-2022-22229 is a high-severity cross-site scripting vulnerability in Juniper Networks Paragon Active Assurance (Formerly Netrounds), published on 18 Oct 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-22229?

It affects 1 product.


Products: Juniper Paragon Active Assurance Control Center.

## How do I fix CVE-2022-22229?

No fix has been published for CVE-2022-22229 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22229 being exploited?

There is no known exploitation of CVE-2022-22229 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Networks Paragon Active Assurance (Formerly Netrounds)

- [CVE-2024-30381](https://insights.sbomify.com/CVE-2024-30381/): Paragon Active Assurance: probe_serviced exposes internal objects to local users (high 8.4)
- [CVE-2024-21589](https://insights.sbomify.com/CVE-2024-21589/): Paragon Active Assurance Control Center: Information disclosure vulnerability (high 7.4)
- [CVE-2022-22190](https://insights.sbomify.com/CVE-2022-22190/): Paragon Active Assurance Control Center: Information disclosure vulnerability in crafted URL (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22229 and fix it if it is affected.

What it is: CVE-2022-22229 is a high-severity cross-site scripting vulnerability in Juniper Networks Paragon Active Assurance (Formerly Netrounds), published on 18 Oct 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-22229 in the wild and no public exploit code.

Affected product: Juniper Networks Paragon Active Assurance (Formerly Netrounds). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-22229/ (Markdown: https://insights.sbomify.com/CVE-2022-22229/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22229
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22229
- OSV: https://osv.dev/vulnerability/CVE-2022-22229

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-22229/
Summaries are generated and may contain mistakes; the official description above is the record.