# CVE-2021-29201: Cross-site scripting in HPE Integrated Lights-Out 4 (iLO 4) For HPE Gen9 servers; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers

> Remote attackers can execute arbitrary scripts in the context of HPE iLO management interfaces, potentially compromising administrative sessions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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:** 25 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fff6-fgfx-622h

## What is CVE-2021-29201?

CVE-2021-29201 is a medium-severity cross-site scripting vulnerability in HPE Integrated Lights-Out 4 (iLO 4) For HPE Gen9 servers; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, published on 25 May 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A remote xss vulnerability was discovered in HPE Integrated Lights-Out 4 (iLO 4); HPE SimpliVity 380 Gen9; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers; HPE SimpliVity 380 Gen10; HPE SimpliVity 2600; HPE SimpliVity 380 Gen10 G; HPE SimpliVity 325; HPE SimpliVity 380 Gen10 H version(s): Prior to version 2.78.

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

## Which versions are affected by CVE-2021-29201?

It affects 2 products.


Products: Hp Integrated Lights-Out 4, Hp Integrated Lights-Out 5.

## How do I fix CVE-2021-29201?

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

## Is CVE-2021-29201 being exploited?

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

## Other vulnerabilities in HPE Integrated Lights-Out 4 (iLO 4) For HPE Gen9 servers; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers

- [CVE-2023-28083](https://insights.sbomify.com/CVE-2023-28083/): Cross-site scripting in Integrated Lights-Out (high 8.3)
- [CVE-2022-23704](https://insights.sbomify.com/CVE-2022-23704/): A potential security vulnerability has been identified in Integrated Lights-Out 4 (iLO 4). (high 7.5)
- [CVE-2013-4843](https://insights.sbomify.com/CVE-2013-4843/): Information disclosure in n/a (medium 6.8)
- [CVE-2021-29202](https://insights.sbomify.com/CVE-2021-29202/): Memory corruption in HPE Integrated Lights-Out 4 (iLO 4) For HPE Gen9 servers; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers (medium 6.7)
- [CVE-2020-7202](https://insights.sbomify.com/CVE-2020-7202/): Information disclosure in HPE ProLiant Servers, Apollo Products, Converged Systems, and Synergy Compute Modules with Integrated Lights-Out 5 (iLO 5), or Integrated Lights-Out 4 (iLO 4) (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29201 and fix it if it is affected.

What it is: CVE-2021-29201 is a medium-severity cross-site scripting vulnerability in HPE Integrated Lights-Out 4 (iLO 4) For HPE Gen9 servers; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers, published on 25 May 2021. 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-2021-29201 in the wild and no public exploit code.

Affected product: HPE Integrated Lights-Out 4 (iLO 4) For HPE Gen9 servers; HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers. 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-2021-29201/ (Markdown: https://insights.sbomify.com/CVE-2021-29201/index.md)
```

## Sources

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

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