# CVE-2022-44718: Open redirect in n/a

> An authenticated administrator can exploit an open redirection vulnerability in NetScout nGeniusONE to redirect users to malicious external sites.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N`)
- **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:** 27 Jan 2023
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-qxrv-gqvh-97cr

## What is CVE-2022-44718?

CVE-2022-44718 is a low-severity vulnerability in n/a, published on 27 Jan 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in NetScout nGeniusONE 6.3.2 build 904. Open Redirection can occur (issue 2 of 2). After successful login, an attacker must visit the vulnerable parameter and inject a crafted payload to successfully redirect to an unknown host. The attack vector is Network, and the Attack Complexity required is High. Privileges required are administrator, User Interaction is required, and Scope is unchanged. The user must visit the vulnerable parameter and inject a crafted payload to successfully redirect to an unknown host.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Netscout Ngeniusone.

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

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

## Is CVE-2022-44718 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-32985](https://insights.sbomify.com/CVE-2025-32985/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2023-26999](https://insights.sbomify.com/CVE-2023-26999/): XML external entity in n/a (critical 9.8)
- [CVE-2021-45981](https://insights.sbomify.com/CVE-2021-45981/): XML external entity in n/a (critical 9.8)
- [CVE-2021-45983](https://insights.sbomify.com/CVE-2021-45983/): Code injection in n/a (critical 9.8)
- [CVE-2022-44715](https://insights.sbomify.com/CVE-2022-44715/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44718 is a low-severity vulnerability in n/a, published on 27 Jan 2023. 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-44718 in the wild and no public exploit code.

Affected product: n/a. 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-44718/ (Markdown: https://insights.sbomify.com/CVE-2022-44718/index.md)
```

## Sources

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

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