# CVE-2020-24628: Code injection in HPE KVM IP Console Switches

> Remote attackers can inject code into HPE KVM IP Console Switches, potentially leading to full system compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rj6h-jm72-xm2v

## What is CVE-2020-24628?

CVE-2020-24628 is a high-severity code injection vulnerability in HPE KVM IP Console Switches, published on 2 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A remote code injection vulnerability was discovered in HPE KVM IP Console Switches version(s): G2 4x1Ex32 Prior to 2.8.3.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2020-24628?

It affects 1 product.


Products: Hpe Kvm Ip Console Switch G2 Firmware.

## How do I fix CVE-2020-24628?

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

## Is CVE-2020-24628 being exploited?

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

## Other vulnerabilities in HPE KVM IP Console Switches

- [CVE-2020-24627](https://insights.sbomify.com/CVE-2020-24627/): Cross-site scripting in HPE KVM IP Console Switches (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24628 and fix it if it is affected.

What it is: CVE-2020-24628 is a high-severity code injection vulnerability in HPE KVM IP Console Switches, published on 2 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24628 in the wild and no public exploit code.

Affected product: HPE KVM IP Console Switches. 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-2020-24628/ (Markdown: https://insights.sbomify.com/CVE-2020-24628/index.md)
```

## Sources

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

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