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

> Adenza AxiomSL ControllerView allows attackers to redirect users to malicious sites via SSO login URLs, potentially facilitating phishing attacks.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 30 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4fw8-6hp7-5whp

## What is CVE-2022-22919?

CVE-2022-22919 is a medium-severity vulnerability in n/a, published on 30 Jan 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

Adenza AxiomSL ControllerView through 10.8.1 allows redirection for SSO login URLs.

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

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

It affects 1 product.


Products: Adenza Axiomsl Controllerview.

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

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

## Is CVE-2022-22919 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-24032](https://insights.sbomify.com/CVE-2022-24032/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22919 is a medium-severity vulnerability in n/a, published on 30 Jan 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-22919 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-22919/ (Markdown: https://insights.sbomify.com/CVE-2022-22919/index.md)
```

## Sources

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

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