dbcve.org
Emulex Hba ManagerApplication · Broadcom

CVE-2021-42774

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-12
Fix available
A fix is available. Upgrade to 11.4.425.0 / 12.8.542.31 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Broadcom Emulex HBA Manager/One Command Manager versions before 11.4.425.0 and 12.8.542.31, if not installed in Strictly Local Management mode, have a buffer overflow vulnerability in the remote firmware download feature that could allow remote unauthenticated users to perform various attacks. In non-secure mode, the user is unauthenticated.

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

Buffer overflow vulnerability in the remote firmware download feature of Broadcom Emulex HBA Manager/One Command Manager allows remote unauthenticated code execution when not configured in Strictly Local Management mode, affecting versions prior to 11.4.425.0 and 12.8.542.31.

MitigationUpgrade to version 11.4.425.0/12.8.542.31 or later, or enable Strictly Local Management mode to prevent remote unauthenticated access.

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
Emulex Hba ManagerApplication
Affected:>= 11.0.0, < 11.4.425.0>= 12.0.0, < 12.8.542.31

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify if Broadcom Emulex HBA Manager is installed
    Check for the presence of One Command Manager or HBA Manager software on the system. Look for installation directories such as C:\Program Files\Emulex\ or /opt/emulex/ or check the Windows Add/Remove Programs list.
    Affected if The software is present on the system
  2. Determine the installed version
    Open One Command Manager or HBA Manager and navigate to the About or Help section to view the software version. Alternatively, check the version in the Windows registry under HKLM\SOFTWARE\Emulex or in the installed package details.
    Affected if The version falls within 11.0.0 to 11.4.424.99 OR 12.0.0 to 12.8.542.30
  3. Check if Strictly Local Management mode is disabled
    In One Command Manager, navigate to Settings or Security configuration and verify whether Strictly Local Management mode is enabled. This setting controls whether remote management interfaces are accessible.
    Affected if Strictly Local Management mode is disabled or not configured, making the remote firmware download feature accessible over the network
  4. Verify remote management interface accessibility
    Check if the remote management port (typically port 8080 or 8443 for One Command Manager web interface) is exposed to network access. Use netstat or check firewall rules to determine if the management interface is listening on non-loopback addresses.
    Affected if The management interface is reachable from network addresses and Strictly Local Management mode is disabled

The environment is affected if Broadcom Emulex HBA Manager/One Command Manager is installed with a version between 11.0.0-11.4.424.99 or 12.0.0-12.8.542.30 AND Strictly Local Management mode is disabled, allowing remote network access to the firmware download feature.

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
Upgrade available Upgrade to 11.4.425.0 / 12.8.542.31 or later
Fixed in 11.4.425.012.8.542.31
Interim mitigation

Upgrade to version 11.4.425.0/12.8.542.31 or later, or enable Strictly Local Management mode to prevent remote unauthenticated access.

Recommended fix High confidence

Emulex HBA Manager 11.4.425.0 or later (for 11.x branch); Emulex HBA Manager 12.8.542.31 or later (for 12.x branch)

  1. Identify the currently installed Emulex HBA Manager or One Command Manager version
  2. Determine which version branch (11.x or 12.x) is in use
  3. For 11.x versions: download Emulex HBA Manager version 11.4.425.0 or later from Broadcom support portal
  4. For 12.x versions: download Emulex HBA Manager version 12.8.542.31 or later from Broadcom support portal
  5. Follow Broadcom's documented upgrade procedure to install the fixed version
  6. After upgrade, verify the installed version matches the fixed release

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

Fix this in Emulex Hba Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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