dbcve.org
3com Baseline Plus SwitchHardware / appliance · Hp

CVE-2013-2340

HIGH · 10.0 CVSS v2.0 Published 2013-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unspecified vulnerability on the HP ProCurve JC###A, JC###B, JD###A, JD###B, JE###A, JF###A, JF###B, JF###C, JG###A, 658250-B21, and 658247-B21; HP 3COM routers and switches; and HP H3C routers and switches allows remote attackers to execute arbitrary code or obtain sensitive information via unknown 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 · moderate confidence

This is an unspecified critical vulnerability (CVSS 10) affecting HP ProCurve switch modules (JC###A/B, JD###A/B, JE###A, JF###A/B/C, JG###A), HP 3COM routers/switches, and HP H3C routers/switches. The vulnerability allows remote attackers to execute arbitrary code or obtain sensitive information via unknown vectors.

MitigationApply vendor-supplied firmware updates immediately upon availability. If no patch exists, consider network segmentation, disabling unnecessary services, and implementing strict access controls to reduce attack surface.

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
3com Baseline Plus SwitchHardware / appliance
Affected:= 2900= 2900g= 2900g-28hpwr= 2900g-28pwr
3com RouterHardware / appliance
Affected:= 3012= 3013= 3016= 3018= 3036= 3040= 3041= 5009= 5012= 5231= 5232= 5640
3com SwitchHardware / appliance
Affected:= 4200g= 4200g-ntg= 4200g_pwr= 4210= 4210-24g= 4210-48g= 4210_pwr= 4210_pwr_9p_taa= 4500= 4500_pwr= 4510g= 4510g_pwr
3com Switch Taa CompliantHardware / appliance
Affected:= 5500g-ei= 5500g-ei-pwr= 5500g-ei-sfp
3com Taa SwitchHardware / appliance
Affected:= 5500-ei
H3c Ethernet SwitchHardware / appliance
Affected:= s5500-28c-ei= s5500-28c-ei-dc= s5500-28c-pwr-ei= s5500-28c-pwr-si= s5500-28c-si= s5500-28f-ei= s5500-52c-ei= s5500-52c-pwr-ei= s5500-52c-pwr-si= s5500-52c-si= s5600-26c= s5600-26c-pwr
H3c High Performance Main Processing UnitHardware / appliance
Affected:= msr_50_3ge
H3c Processing ModuleHardware / appliance
Affected:= msr_50_g2

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 device model
    Check the physical device label or log into the CLI and run 'display device manuinfo' or 'show system-information' to confirm the exact model number (e.g., 2900, 4200g, s5500-28c-ei, msr_50_g2)
    Affected if The model matches any of the affected products listed: HP 3COM Baseline Plus Switch (2900 series), HP 3COM Router (3012-5640 series), HP 3COM Switch (4200g-5500g series), HP H3C Ethernet Switch (s5500/s5600 series), or HP H3C Processing Module (msr_50_g2)
  2. Check firmware version
    Log into the device CLI and run 'display version' or 'show version' to obtain the installed firmware/software version
    Affected if The firmware version matches any of the specific versions listed in the affected products (e.g., 2900, 2900g, 4210-24g, s5500-28c-ei, msr_50_3ge, msr_50_g2)
  3. Verify device is HP 3COM or H3C branded
    Check the boot prompt, login banner, or run 'display device manuinfo' to confirm the vendor branding is HP 3COM or HP H3C
    Affected if The device is branded as HP 3COM or HP H3C and the model number matches the affected list
  4. Confirm management interface accessibility
    Check if remote management protocols (HTTP, HTTPS, Telnet, SSH) are enabled and accessible from network by reviewing 'display ip interface' or 'display service' output
    Affected if Remote management interfaces are exposed to untrusted networks (this is required for the remote attack vector)
  5. Review device configuration for unknown vectors
    Examine running configuration with 'display current-configuration' for any unusual or unexpected service entries, ACL modifications, or debugging features enabled
    Affected if Non-standard services, debugging features, or modified ACLs are present that could indicate exploitation attempts

You are affected if your device is an HP 3COM or HP H3C switch, router, or processing module matching any of the model numbers listed, regardless of firmware version, as this is a critical unspecified vulnerability in those specific products.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates immediately upon availability. If no patch exists, consider network segmentation, disabling unnecessary services, and implementing strict access controls to reduce attack surface.

Fix this in 3com Baseline Plus Switch Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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