# CVE-2022-22190: Paragon Active Assurance Control Center: Information disclosure vulnerability in crafted URL

> Unauthenticated attackers can access sensitive configuration data via crafted URLs in Juniper Paragon Active Assurance Control Center.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h42q-jjcq-2ff4

## What is CVE-2022-22190?

CVE-2022-22190 is a high-severity missing authorization vulnerability in Juniper Networks Paragon Active Assurance, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An Improper Access Control vulnerability in the Juniper Networks Paragon Active Assurance Control Center allows an unauthenticated attacker to leverage a crafted URL to generate PDF reports, potentially containing sensitive configuration information. A feature was introduced in version 3.1 of the Paragon Active Assurance Control Center which allows users to selective share account data using a unique identifier. Knowing the proper format of the URL and the identifier of an existing object in an application it is possible to get access to that object without being logged in, even if the object is not shared, resulting in the opportunity for malicious exfiltration of user data. Note that the Paragon Active Assurance Control Center SaaS offering is not affected by this issue. This issue affects Juniper Networks Paragon Active Assurance version 3.1.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Juniper Paragon Active Assurance Control Center.

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

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

## Is CVE-2022-22190 being exploited?

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

## Other vulnerabilities in Juniper Networks Paragon Active Assurance

- [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-2022-22229](https://insights.sbomify.com/CVE-2022-22229/): Paragon Active Assurance (Formerly Netrounds): Stored Cross-site Scripting (XSS) vulnerability in web administration (high 8.4)
- [CVE-2024-21589](https://insights.sbomify.com/CVE-2024-21589/): Paragon Active Assurance Control Center: Information disclosure vulnerability (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22190 is a high-severity missing authorization vulnerability in Juniper Networks Paragon Active Assurance, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-22190 in the wild and no public exploit code.

Affected product: Juniper Networks Paragon Active Assurance. 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-22190/ (Markdown: https://insights.sbomify.com/CVE-2022-22190/index.md)
```

## Sources

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

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