# CVE-2020-7131: Memory corruption in Integrated Maintenance Entity T1805; Maintenance Entity T2805; Blade Maintenance Entity FW T4805

> Attackers on the Maintenance LAN can exploit an open UDP port to cause memory corruption, leading to system control, denial of service, or information disclosure.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6vcx-5chv-mvq3

## What is CVE-2020-7131?

CVE-2020-7131 is a critical memory corruption vulnerability in Integrated Maintenance Entity T1805; Maintenance Entity T2805; Blade Maintenance Entity FW T4805, published on 24 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

This document describes a security vulnerability in Blade Maintenance Entity, Integrated Maintenance Entity and Maintenance Entity products. All J/H-series NonStop systems have a security vulnerability associated with an open UDP port 17185 on the Maintenance LAN which could result in information disclosure, denial-of-service attacks or local memory corruption against the affected system and a complete control of the system may also be possible. This vulnerability exists only if one gains access to the Maintenance LAN to which Blade Maintenance Entity, Integrated Maintenance Entity or Maintenance Entity product is connected. **Workaround:** Block the UDP port 17185(In the Maintenance LAN Network Switch/Firewall). Fix: Install following SPRs, which are already available: * T1805A01^AAI (Integrated Maintenance Entity) * T4805A01^AAZ (Blade Maintenance Entity). These SPRs are also usable with the following RVUs: * J06.19.00 ? J06.23.01. No fix planned for the following RVUs: J06.04.00 ? J06.18.01. No fix planned for H-Series NonStop systems. No fix planned for the product T2805 (Maintenance Entity).

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 3 products.


Products: Hp Blade Maintenance Entity, Hp Integrated Maintenance Entity, Hp Maintenance Entity.

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

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

## Is CVE-2020-7131 being exploited?

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

## Other vulnerabilities in Integrated Maintenance Entity T1805; Maintenance Entity T2805; Blade Maintenance Entity FW T4805

- [CVE-2019-5394](https://insights.sbomify.com/CVE-2019-5394/): Information disclosure in HPE NonStop Maintanence Entity (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7131 is a critical memory corruption vulnerability in Integrated Maintenance Entity T1805; Maintenance Entity T2805; Blade Maintenance Entity FW T4805, published on 24 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7131 in the wild and no public exploit code.

Affected product: Integrated Maintenance Entity T1805; Maintenance Entity T2805; Blade Maintenance Entity FW T4805. 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-7131/ (Markdown: https://insights.sbomify.com/CVE-2020-7131/index.md)
```

## Sources

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

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