CVE-2018-6447
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 Reflective XSS Vulnerability in HTTP Management Interface in Brocade Fabric OS versions before Brocade Fabric OS v9.0.0, v8.2.2c, v8.2.1e, v8.1.2k, v8.2.0_CBN3, v7.4.2g could allow authenticated attackers with access to the web interface to hijack a user’s session and take over the account.
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 reflected cross-site scripting (XSS) vulnerability exists in the HTTP management interface of Brocade Fabric OS. The vulnerability allows authenticated attackers with web interface access to inject malicious scripts through unsanitized input, enabling session hijacking and account takeover.
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= 2.1.2= 2.2= 3.1= 5.0.5b= 5.2.0= 5.2.0a= 7.4.0= 7.4.1= 7.4.1a= 7.4.1b= 7.4.1c= 7.4.1dCVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Fabric OS versionLog into the switch via CLI and run the command 'version' or 'firmwareShow' to display the installed Fabric OS versionAffected if The displayed version matches one of these: 2.1.2, 2.2, 3.1, 5.0.5b, 5.2.0, 5.2.0a, 7.4.0, 7.4.1, 7.4.1a, 7.4.1b, 7.4.1c, or 7.4.1d
-
Verify HTTP management interface is enabledCheck the web management configuration using the CLI command 'webui --show' or 'httpcfg' to see if the HTTP/HTTPS management interface is enabledAffected if The HTTP management interface status shows as enabled or active
-
Confirm web interface is accessibleAttempt to access the management IP via HTTP port 80 or HTTPS port 443 from a management station to confirm the web interface is reachableAffected if The web login page loads successfully, indicating the interface is exposed on the network
-
Check authentication statusVerify that user accounts with web interface access exist by running 'userconfig --show' or checking the defined users with web login privilegesAffected if Any user account has web interface access permissions enabled
You are affected if your Fabric OS version matches any of the listed affected versions AND the HTTP management interface is enabled and accessible with valid user credentials.
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 dataUpgrade Brocade Fabric OS to version v9.0.0 or later, or apply the vendor-specified patches for vulnerable versions (v8.2.2c, v8.2.1e, v8.1.2k, v8.2.0_CBN3, v7.4.2g). Limit web management interface access to trusted networks and users.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6447 — 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-6447 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