CVE-2018-6436
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 · uneditedA Vulnerability in the firmwaredownload command of Brocade Fabric OS command line interface (CLI) versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could allow a local attacker to escape the restricted shell and, gain root access.
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 confidenceA command injection or shell escape vulnerability exists in the firmwaredownload command of Brocade Fabric OS CLI. The flaw allows a locally authenticated attacker with access to the restricted CLI shell to escape the sandbox and execute arbitrary commands with root privileges on the underlying operating system.
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>= 7.4.2, < 7.4.2d>= 8.0.2, < 8.0.2f>= 8.1.2, < 8.1.2f>= 8.2.0, < 8.2.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Fabric OS versionExecute the 'version' command or 'firmwarerelease' command from the CLI to retrieve the currently installed Fabric OS versionAffected if The displayed version falls within one of the vulnerable ranges: >= 7.4.2 and < 7.4.2d, OR >= 8.0.2 and < 8.0.2f, OR >= 8.1.2 and < 8.1.2f, OR >= 8.2.0 and < 8.2.1
-
Verify CLI access levelConfirm you have authenticated local access to the Brocade Fabric OS CLI shell. Check if you can execute privileged commands or access the restricted shell environmentAffected if You have authenticated local CLI access and can reach the shell where the firmwaredownload command is available
-
Confirm firmwaredownload command availabilityAttempt to access or view help for the 'firmwaredownload' command in the CLI. This is typically available in the privileged exec mode or restricted shellAffected if The firmwaredownload command is accessible in your current CLI context
You are affected if your installed Fabric OS version matches any of the vulnerable version ranges AND you have authenticated local CLI access where the firmwaredownload command can be invoked.
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.
From vendor data7.4.2d8.0.2f8.1.2f
Upgrade Brocade Fabric OS to version 8.2.1, 8.1.2f, 8.0.2f, or 7.4.2d or later. Apply within planned maintenance window following vendor upgrade procedures and verify the restricted shell properly enforces access controls post-upgrade.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6436 — 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-2018-6436 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