# CVE-2019-19336: Cross-site scripting in ovirt-engine

> Attackers can execute scripts in user sessions via unescaped URL parameters in the OAuth endpoint, potentially leading to account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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:** Yes
- **Published:** 19 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-969f-386j-4c9x, RHSA-2020:0498

## What is CVE-2019-19336?

CVE-2019-19336 is a medium-severity cross-site scripting vulnerability in Redhat Virtualization, published on 19 Mar 2020. 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

A cross-site scripting vulnerability was reported in the oVirt-engine's OAuth authorization endpoint before version 4.3.8. URL parameters were included in the HTML response without escaping. This flaw would allow an attacker to craft malicious HTML pages that can run scripts in the context of the user's oVirt session.

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

## Which versions are affected by CVE-2019-19336?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ovirt-engine` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-backend` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-dbscripts` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-dwh` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8-1.el7ev |
| `ovirt-engine-dwh-setup` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8-1.el7ev |
| `ovirt-engine-extensions-api-impl` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-extensions-api-impl-javadoc` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-health-check-bundler` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-metrics` | Red Hat:rhev_manager:4.3 | All versions | 0:1.3.6.2-1.el7ev |
| `ovirt-engine-restapi` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup-base` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup-plugin-cinderlib` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup-plugin-ovirt-engine` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup-plugin-ovirt-engine-common` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup-plugin-vmconsole-proxy-helper` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-setup-plugin-websocket-proxy` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-tools` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-tools-backup` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-vmconsole-proxy-helper` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-webadmin-portal` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-engine-websocket-proxy` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `ovirt-fast-forward-upgrade` | Red Hat:rhev_manager:4.3 | All versions | 0:1.0.0-16.el7ev |
| `ovirt-imageio-common` | Red Hat:rhev_manager:4.3 | All versions | 0:1.5.3-0.el7ev |
| `ovirt-imageio-common-debuginfo` | Red Hat:rhev_manager:4.3 | All versions | 0:1.5.3-0.el7ev |
| `ovirt-imageio-proxy` | Red Hat:rhev_manager:4.3 | All versions | 0:1.5.3-0.el7ev |
| `ovirt-imageio-proxy-setup` | Red Hat:rhev_manager:4.3 | All versions | 0:1.5.3-0.el7ev |
| `ovirt-web-ui` | Red Hat:rhev_manager:4.3 | All versions | 0:1.6.0-2.el7ev |
| `python2-ovirt-engine-lib` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `rhv-log-collector-analyzer` | Red Hat:rhev_manager:4.3 | All versions | 0:0.2.15-0.el7ev |
| `rhvm` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.8.2-0.4.el7 |
| `v2v-conversion-host` | Red Hat:rhev_manager:4.3 | All versions | 0:1.16.0-3.el7ev |
| `v2v-conversion-host-ansible` | Red Hat:rhev_manager:4.3 | All versions | 0:1.16.0-3.el7ev |

Products: Ovirt Ovirt-Engine, Redhat Virtualization.

## How do I fix CVE-2019-19336?

Upgrade to a fixed version.

## Is CVE-2019-19336 being exploited?

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

## Other vulnerabilities in Redhat Virtualization

- [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-2022-3193](https://insights.sbomify.com/CVE-2022-3193/): An HTML injection/reflected Cross-site scripting (XSS) vulnerability was found in the ovirt-engine. (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19336 and fix it if it is affected.

What it is: CVE-2019-19336 is a medium-severity cross-site scripting vulnerability in Redhat Virtualization, published on 19 Mar 2020. 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-2019-19336 in the wild and no public exploit code.

Affected product: Redhat Virtualization. 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-2019-19336/ (Markdown: https://insights.sbomify.com/CVE-2019-19336/index.md)
```

## Sources

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

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