CVE-2021-42773
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 · uneditedBroadcom 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, could allow a user to retrieve an arbitrary file from a remote host with the GetDumpFile command. 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 confidenceArbitrary file retrieval vulnerability in Broadcom Emulex HBA Manager/One Command Manager. The GetDumpFile command allows an unauthenticated user (in non-secure mode) to retrieve any file from the host system when the software is not configured in Strictly Local Management mode.
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>= 11.0.0, < 11.4.425.0>= 12.0.0, < 12.8.542.31CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Broadcom Emulex HBA Manager versionLocate the HBA Manager installation directory or check the installed software list. Common locations include C:\Program Files\Emulex\HBA Manager or /opt/emulex/hba-manager. Look for version information in the application UI, installer logs, or registry entries on Windows systems.Affected if Installed version falls within 11.0.0 to 11.4.425.0 (exclusive of 11.4.425.0) or 12.0.0 to 12.8.542.31 (exclusive of 12.8.542.31)
-
Confirm One Command Manager version if applicableIf using One Command Manager variant, check the version through the management console, command-line interface (ociocm -version), or the installer package. The same version ranges apply.Affected if Installed version falls within the affected ranges specified above
-
Verify Strictly Local Management mode configurationAccess the HBA Manager or One Command Manager administrative interface. Navigate to Security Settings or Management Mode configuration. Check whether Strictly Local Management mode is enabled. On Windows, this may also be verifiable through registry keys under HKLM\Software\Emulex or within the configuration XML files in the application directory.Affected if Strictly Local Management mode is DISABLED or not configured - this is the condition that makes the vulnerability exploitable
-
Check network exposure of management interfaceDetermine if the HBA Manager web interface (typically on ports 8080 or 8443) or API endpoints are accessible from network segments outside the local host. Review firewall rules and network ACLs protecting the management service.Affected if The management interface is reachable from unauthenticated network sources and Strictly Local Management is not enabled
You are affected if Broadcom Emulex HBA Manager or One Command Manager with a vulnerable version is installed AND Strictly Local Management mode is not enabled, allowing unauthenticated access to the GetDumpFile command.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.4.425.012.8.542.31
Enable Strictly Local Management mode to restrict access, or upgrade to version 11.4.425.0 or 12.8.542.31 or later.
11.4.425.0 (for 11.x line) or 12.8.542.31 (for 12.x line)
- Upgrade Emulex HBA Manager to version 11.4.425.0 or later if currently on the 11.x release line
- Upgrade Emulex HBA Manager to version 12.8.542.31 or later if currently on the 12.x release line
- As an additional mitigation, configure the product to use Strictly Local Management mode to prevent remote file retrieval
- After upgrading, verify that the GetDumpFile command is properly restricted and requires appropriate authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-42773 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-42773 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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