dbcve.org
System Networking Rackswitch G8332 FirmwareOperating system · Ibm

CVE-2014-4752

HIGH · 10.0 CVSS v2.0 Published 2014-09-23
Fix available
A fix is available. Upgrade to after 7.9.1.0 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
IBM System Networking G8052, G8124, G8124-E, G8124-ER, G8264, G8316, and G8264-T switches before 7.9.10.0; EN4093, EN4093R, CN4093, SI4093, EN2092, and G8264CS switches before 7.8.6.0; Flex System Interconnect Fabric before 7.8.6.0; 1G L2-7 SLB switch for Bladecenter before 21.0.21.0; 10G VFSM for Bladecenter before 7.8.14.0; 1:10G switch for Bladecenter before 7.4.8.0; 1G switch for Bladecenter before 5.3.5.0; Server Connectivity Module before 1.1.3.4; System Networking RackSwitch G8332 before 7.7.17.0; and System Networking RackSwitch G8000 before 7.1.7.0 have hardcoded credentials, which makes it easier for remote attackers to obtain access via unspecified vectors.

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

Multiple IBM System Networking switch models contain hardcoded credentials (embedded usernames and passwords in firmware) that allow remote attackers to bypass authentication and gain full administrative access to affected devices. The vulnerability affects various RackSwitch, Flex System, BladeCenter, and System Networking switch models across different firmware branches.

MitigationApply vendor-supplied firmware updates to patched versions (7.9.10.0, 7.8.6.0, or later depending on model). If immediate patching is not possible, isolate affected switches behind strict network segmentation, disable unnecessary remote management access, and implement additional authentication layers such as RADIUS or TACACS+ for management 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
System Networking Rackswitch G8332 FirmwareOperating system
Affected:<= 7.7.16.0<= 7.1.6.0
System Networking Rackswitch G8332Hardware / appliance
Affected:all versions
Bladecenter 1g FirmwareOperating system
Affected:<= 5.3.4.0
Bladecenter 1gHardware / appliance
Affected:all versions
System Networking Rackswitch G8052 FirmwareOperating system
Affected:<= 7.9.1.0
System Networking Rackswitch G8124 FirmwareOperating system
Affected:<= 7.9.1.0
System Networking Rackswitch G8124e FirmwareOperating system
Affected:<= 7.9.1.0
System Networking Rackswitch G8124er FirmwareOperating system
Affected:<= 7.9.1.0

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify the switch model
    Log into the switch CLI and run 'show system' or 'show version' to display the product name and model number
    Affected if The model is any of: RackSwitch G8332, BladeCenter 1G, RackSwitch G8052, RackSwitch G8124, RackSwitch G8124e, or RackSwitch G8124er
  2. Retrieve the firmware version
    Run 'show version' or 'show firmware' in the switch CLI to display the installed firmware version
    Affected if The firmware version cannot be determined or is not displayed
  3. Check if G8332 is affected
    Compare the installed firmware version against the affected ranges: versions <= 7.7.16.0 or <= 7.1.6.0, or any version if not branch-specific
    Affected if The installed version is 7.7.16.0 or lower, or 7.1.6.0 or lower, or is an all-versions G8332 unit
  4. Check if BladeCenter 1G is affected
    Compare the installed firmware version against the affected range: <= 5.3.4.0
    Affected if The installed version is 5.3.4.0 or lower, or is an all-versions BladeCenter 1G unit
  5. Check if G8052, G8124, G8124e, or G8124er are affected
    Compare the installed firmware version against the affected range: <= 7.9.1.0
    Affected if The installed version is 7.9.1.0 or lower for any of these four models

The environment is affected if the switch model is any of the listed RackSwitch or BladeCenter models AND the installed firmware version falls within or below the specified version thresholds, or if it is an all-versions variant.

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 a release after 7.9.1.0
Interim mitigation

Apply vendor-supplied firmware updates to patched versions (7.9.10.0, 7.8.6.0, or later depending on model). If immediate patching is not possible, isolate affected switches behind strict network segmentation, disable unnecessary remote management access, and implement additional authentication layers such as RADIUS or TACACS+ for management access.

Recommended fix High confidence

Upgrade to firmware version 7.9.10.0 or later for G8052/G8124 series; 7.8.6.0 or later for EN4093/EN2092 series; 7.7.17.0 or later for G8332; 7.1.7.0 or later for G8000; 5.3.5.0 or later for 1G Bladecenter switches; 21.0.21.0 or later for 1G L2-7 SLB (specific to each product model)

  1. 1. Identify the specific switch model from the affected product list (G8052, G8124, G8124-E, G8124-ER, G8264, G8316, G8264-T, EN4093, EN4093R, CN4093, SI4093, EN2092, G8264CS, Flex System Interconnect Fabric, 1G L2-7 SLB, 10G VFSM, 1:10G, 1G switch for Bladecenter, Server Connectivity Module, G8332, or G8000)
  2. 2. Determine the current firmware version by accessing the switch management interface or using CLI command 'show version'
  3. 3. Download the appropriate fixed firmware version from IBM support website based on your switch model: For G8052/G8124 series: upgrade to 7.9.10.0 or later; For EN4093/EN2092 series: upgrade to 7.8.6.0 or later; For G8332: upgrade to 7.7.17.0 or later; For G8000: upgrade to 7.1.7.0 or later; For 1G Bladecenter switches: upgrade to 5.3.5.0 or later; For 1G L2-7 SLB: upgrade to 21.0.21.0 or later
  4. 4. Backup current switch configuration using 'upload config' or management interface
  5. 5. Upload and install the new firmware via TFTP, FTP, or management interface using 'firmware upload' or equivalent command
  6. 6. Verify firmware installation success with 'show version'
  7. 7. Reboot the switch if required by the firmware update process
  8. 8. After reboot, verify the new firmware version is installed and test network connectivity
Caveat Firmware upgrades may cause brief network downtime; review release notes for any configuration changes or migration requirements before upgrading

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

Fix this in System Networking Rackswitch G8332 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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