dbcve.org
Service Pack For ProliantApplication · Hp

CVE-2020-7135

HIGH · 7.8 CVSS v3.1 Published 2020-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A potential security vulnerability has been identified in the disk drive firmware installers named Supplemental Update / Online ROM Flash Component on HPE servers running Linux. The vulnerable software is included in the HPE Service Pack for ProLiant (SPP) releases 2018.06.0, 2018.09.0, and 2018.11.0. The vulnerable software is the Supplemental Update / Online ROM Flash Component for Linux (x64) software. The installer in this software component could be locally exploited to execute arbitrary code. Drive Models can be found in the Vulnerability Resolution field of the security bulletin. The 2019_03 SPP and Supplemental update / Online ROM Flash Component for Linux (x64) after 2019.03.0 has fixed this issue.

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

Vulnerability in HPE disk drive firmware installer (Supplemental Update/Online ROM Flash Component for Linux x64) where the installer can be exploited to execute arbitrary code locally. Affects SPP versions 2018.06.0, 2018.09.0, and 2018.11.0 on HPE ProLiant servers running Linux.

MitigationUpdate HPE Service Pack for ProLiant (SPP) to version 2019.03 or later, or apply the patched Supplemental Update/Online ROM Flash Component for Linux (x64) released after 2019.03.0.

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
Service Pack For ProliantApplication
Affected:= 2018.06.0= 2018.09.0= 2018.11.0= 2019.03.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Identify installed SPP version
    Check the HPE Service Pack for ProLiant version by examining system documentation, ILO web interface, or running HP utility commands (such as 'hponcfg' or checking /opt/hp directory contents) that report the SPP version. The version is typically displayed as a date-based release like 2018.06.0, 2018.09.0, 2018.11.0, or 2019.03.0.
    Affected if The installed SPP version matches 2018.06.0, 2018.09.0, 2018.11.0, or 2019.03.0.
  2. Confirm Linux operating system
    Run 'uname -a' or 'cat /etc/os-release' to verify the server is running a Linux distribution.
    Affected if The server is running Linux (x64).
  3. Locate the Online ROM Flash Component
    Search for the HPE firmware installer binary or package. Common paths include /usr/lib/x86_64-linux-gnu/hp/, /opt/hp/firmware, or check for packages named 'online-rom-flash' or similar using 'rpm -qa' or 'dpkg -l'. The component may appear as a firmware update tool for disk drives.
    Affected if The Online ROM Flash Component for Linux x64 (disk drive firmware installer) is installed on the system.
  4. Check firmware update tool permissions
    Inspect the permissions and ownership of the firmware installer binary using 'ls -la <path-to-installer>' to confirm the tool is present and executable.
    Affected if The disk drive firmware installer exists and is executable by authorized users.

A system is affected if it runs Linux on an HPE ProLiant server with Service Pack for ProLiant version 2018.06.0, 2018.09.0, 2018.11.0, or 2019.03.0 and has the Online ROM Flash Component for Linux x64 installed.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update HPE Service Pack for ProLiant (SPP) to version 2019.03 or later, or apply the patched Supplemental Update/Online ROM Flash Component for Linux (x64) released after 2019.03.0.

Fix this in Service Pack For Proliant Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7135 — 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-7135 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