# CVE-2013-4181: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into the oVirt Engine and RHEV-M web interface via the RedirectServlet.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q75j-qph2-cwg9, RHSA-2013:1210

## What is CVE-2013-4181?

CVE-2013-4181 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Sep 2013. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the addAlert function in the RedirectServlet servlet in oVirt Engine and Red Hat Enterprise Virtualization Manager (RHEV-M), as used in Red Hat Enterprise Virtualization 3 and 3.2, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

## Which versions are affected by CVE-2013-4181?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rhevm` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-backend` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-config` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-dbscripts` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-genericapi` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-notification-service` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-restapi` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-setup` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-setup-plugin-allinone` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-tools-common` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-userportal` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |
| `rhevm-webadmin-portal` | Red Hat:rhev_manager:3 | All versions | 0:3.2.3-0.42.el6ev |

Products: Redhat Enterprise Virtualization.

## How do I fix CVE-2013-4181?

Apply the vendor's patch.

## Is CVE-2013-4181 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5201](https://insights.sbomify.com/CVE-2015-5201/): Auth bypass in Enterprise Virtualization Hypervisor (aka RHEV-H) (high 7.5)
- [CVE-2013-2151](https://insights.sbomify.com/CVE-2013-2151/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2152](https://insights.sbomify.com/CVE-2013-2152/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-2176](https://insights.sbomify.com/CVE-2013-2176/): Privilege escalation in n/a (high 7.2)
- [CVE-2017-2614](https://insights.sbomify.com/CVE-2017-2614/): Auth bypass in ovirt-engine-extension-aaa-jdbc (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4181 and fix it if it is affected.

What it is: CVE-2013-4181 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Sep 2013. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-4181 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-2013-4181/ (Markdown: https://insights.sbomify.com/CVE-2013-4181/index.md)
```

## Sources

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

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