# CVE-2022-3193: An HTML injection/reflected Cross-site scripting (XSS) vulnerability was found in the ovirt-engine.


- **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
- **Fix available:** No
- **Published:** 28 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-6g28-qxjm-5vh2

## What is CVE-2022-3193?

CVE-2022-3193 is a medium-severity vulnerability in ovirt-engine, published on 28 Sep 2022. 

### Official description

An HTML injection/reflected Cross-site scripting (XSS) vulnerability was found in the ovirt-engine. A parameter "error_description" fails to sanitize the entry, allowing the vulnerability to trigger on the Windows Service Accounts home pages.

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

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

It affects 1 product.


Products: Ovirt Ovirt-Engine.

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

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

## Is CVE-2022-3193 being exploited?

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

## Other vulnerabilities in ovirt-engine

- [CVE-2013-4367](https://insights.sbomify.com/CVE-2013-4367/): Misconfiguration in ovirt-engine (high 7.8)
- [CVE-2024-0822](https://insights.sbomify.com/CVE-2024-0822/): Ovirt: authentication bypass (high 7.5)
- [CVE-2020-35497](https://insights.sbomify.com/CVE-2020-35497/): Information disclosure in ovirt-engine (medium 6.5)
- [CVE-2020-14333](https://insights.sbomify.com/CVE-2020-14333/): Cross-site scripting in ovirt-engine (medium 6.3)
- [CVE-2019-19336](https://insights.sbomify.com/CVE-2019-19336/): Cross-site scripting in ovirt-engine (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3193 is a medium-severity vulnerability in ovirt-engine, published on 28 Sep 2022. 
Exploitation: There is no known exploitation of CVE-2022-3193 in the wild and no public exploit code.

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

## Sources

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

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