dbcve.org
Blade Maintenance EntityApplication · Hp

CVE-2020-7131

CRITICAL · 9.0 CVSS v3.1 Published 2020-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Critical vulnerability in HPE NonStop systems' maintenance infrastructure where an open UDP port 17185 on the Maintenance LAN allows remote attackers with network access to cause information disclosure, denial-of-service attacks, local memory corruption, and potentially achieve complete system control. The vulnerability exists in Blade Maintenance Entity, Integrated Maintenance Entity, and Maintenance Entity products.

MitigationBlock UDP port 17185 at the Maintenance LAN network switch or firewall boundary to prevent unauthorized access. For supported RVUs (J06.19.00-J06.23.01), apply vendor SPRs T1805A01^AAI and T4805A01^AAZ; no fix available for older RVUs, H-Series, or T2805 product.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Blade Maintenance EntityApplication
Affected:>= t4805a01, <= t4805a01\^aay
Integrated Maintenance EntityApplication
Affected:>= t2805a01, <= t2805a01\^aau
Maintenance EntityApplication
Affected:>= t1805a01, <= t1805a01\^aah

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify UDP port 17185 is listening
    Run 'netstat -an | grep 17185' or 'nmap -sU -p 17185 <localhost>' to check if UDP port 17185 is open and listening on the system
    Affected if UDP port 17185 is open and bound to a service, indicating the Maintenance Entity is running
  2. Identify Maintenance Entity product type
    Check which HPE NonStop maintenance product is installed: Blade Maintenance Entity, Integrated Maintenance Entity, or Maintenance Entity. Consult system inventory or run 'version' command for maintenance subsystem
    Affected if Any of the three listed maintenance products are installed
  3. Check installed version of HP Blade Maintenance Entity
    Query the system for the version of the Blade Maintenance Entity (t4805). Compare the installed version string against the range t4805a01 through t4805a01^aay
    Affected if Installed version falls within t4805a01 to t4805a01^aay inclusive
  4. Check installed version of HP Integrated Maintenance Entity
    Query the system for the version of the Integrated Maintenance Entity (t2805). Compare the installed version string against the range t2805a01 through t2805a01^aau
    Affected if Installed version falls within t2805a01 to t2805a01^aau inclusive
  5. Check installed version of HP Maintenance Entity
    Query the system for the version of the Maintenance Entity (t1805). Compare the installed version string against the range t1805a01 through t1805a01^aah
    Affected if Installed version falls within t1805a01 to t1805a01^aah inclusive
  6. Verify Maintenance LAN accessibility
    Confirm whether the Maintenance LAN network segment is accessible from untrusted networks or if UDP port 17185 is exposed to non-administrative network segments
    Affected if The Maintenance LAN or UDP port 17185 is accessible from untrusted network segments

The system is affected if any of the three maintenance products are installed with a version falling within the specified ranges AND UDP port 17185 is open and accessible on the Maintenance LAN.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Block UDP port 17185 at the Maintenance LAN network switch or firewall boundary to prevent unauthorized access. For supported RVUs (J06.19.00-J06.23.01), apply vendor SPRs T1805A01^AAI and T4805A01^AAZ; no fix available for older RVUs, H-Series, or T2805 product.

Recommended fix High confidence

T4805A01^AAZ (Blade Maintenance Entity) and T1805A01^AAI (Integrated Maintenance Entity) for RVUs J06.19.00 - J06.23.01

  1. 1. Identify the specific Maintenance Entity product installed (Blade Maintenance Entity, Integrated Maintenance Entity, or Maintenance Entity)
  2. 2. Verify the current SPR version installed on the system
  3. 3. For Blade Maintenance Entity (t4805a01 through t4805a01^aay): Upgrade to SPR T4805A01^AAZ
  4. 4. For Integrated Maintenance Entity (t2805a01 through t2805a01^aau): Upgrade to SPR T1805A01^AAI
  5. 5. Confirm the RVU (Release Version Update) is within J06.19.00 - J06.23.01 range before applying fixes
  6. 6. Apply the SPR update following HPE standard maintenance procedures
  7. 7. Verify the fix was applied successfully by checking the SPR version
  8. 8. (Optional - defense in depth) If upgrade not possible, configure network switch or firewall to block UDP port 17185 on the Maintenance LAN
Caveat SPR upgrades require system downtime; verify compatibility with all connected systems and ensure proper backup before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blade Maintenance Entity Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,528.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7131 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data