CVE-2014-9565
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 · uneditedCross-site request forgery (CSRF) vulnerability in IBM Flex System EN6131 40Gb Ethernet and IB6131 40Gb Infiniband Switch firmware 3.4.0000 and earlier.
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 confidenceCross-site request forgery (CSRF) vulnerability in IBM Flex System EN6131 40Gb Ethernet and IB6131 40Gb Infiniband Switch firmware 3.4.0000 and earlier allows attackers to trick authenticated administrators into executing unintended actions via malicious requests.
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<= 3.4.0.0.0.0<= 3.4.0.0.0.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Identify the switch modelAccess the switch CLI or web interface and confirm the hardware model is either IBM IB6131 40Gb Infiniband Switch or IBM EN6131 40Gb Ethernet Switch. Use 'show version' command in CLI or check the system information page in the web interface.Affected if The model is IBM IB6131 or IBM EN6131
-
Check the installed firmware versionRun 'show version' command via CLI or check the firmware version in the switch web interface under System > Firmware or similar management section. Note the full firmware version string.Affected if The firmware version is 3.4.0000 or earlier (versions <= 3.4.0.0.0.0)
-
Verify administrative interface exposureCheck if the switch web management interface or CLI is accessible from untrusted networks. Review network ACLs, VLAN configurations, and firewall rules that control access to the switch management IP on ports 80, 443, or SSH (22).Affected if The administrative interface is reachable from networks outside trusted administrative subnets
-
Confirm administrative authentication stateReview active administrative sessions on the switch using 'show sessions' or 'show users' command in CLI. Check if any administrators are currently logged in via web or CLI.Affected if Any administrative session is active while the management interface is network-accessible
A user is affected if they have an IBM IB6131 or EN6131 switch running firmware version 3.4.0000 or earlier, with the administrative interface accessible from networks where untrusted parties could potentially trick an authenticated administrator into clicking a malicious link.
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 dataUpdate firmware to a patched version beyond 3.4.0000. As an interim control, restrict administrative access to trusted networks only and monitor for suspicious administrative actions.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9565 — 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-2014-9565 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