CVE-2013-0526
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 · uneditedping.php in Global Console Manager 16 (GCM16) and Global Console Manager 32 (GCM32) before 1.20.0.22575 on the IBM Avocent 1754 KVM switch allows remote authenticated users to execute arbitrary commands via shell metacharacters in the (1) count or (2) size parameter.
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 confidenceCommand injection vulnerability in the ping.php script of Global Console Manager (GCM16/GCM32) on IBM Avocent 1754 KVM switches. Authenticated users can execute arbitrary OS commands via shell metacharacters in the count or size parameters, leading to full device compromise.
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<= 1.18.0.22011<= 1.18.0.22011CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the KVM switch web interface or check the physical device label to confirm it is an IBM Avocent 1754 KVM switch with Global Console Manager GCM16 or GCM32 firmware installedAffected if The device is an Avocent 1754 KVM with GCM16/GCM32 firmware
-
Check the installed firmware versionLog into the GCM web management interface and navigate to the firmware version information page, typically found under Administration or System Info settings. Compare the firmware version number to 1.18.0.22011Affected if The firmware version is 1.18.0.22011 or lower
-
Verify the web management interface is enabledConfirm that the HTTP/HTTPS web interface for the KVM switch is currently enabled and accessible on the networkAffected if The web interface is enabled and reachable
-
Check if ping.php script existsAccess the ping.php script via the web interface path, typically at /ping.php or /cgi-bin/ping.php on the GCM web serverAffected if The ping.php script is present and accessible
-
Confirm authentication access existsDetermine if valid user credentials for the GCM web interface exist or can be obtained, since the vulnerability requires authenticated accessAffected if Authenticated access to the GCM web interface is possible
A user is affected if they have an IBM Avocent 1754 KVM switch running GCM16 or GCM32 firmware version 1.18.0.22011 or lower with the web interface enabled and the ping.php script accessible to an authenticated user.
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 GCM16/GCM32 firmware to version 1.20.0.22575 or later to patch the command injection vulnerability. If immediate patching is not possible, restrict access to the web management interface to trusted IP addresses only.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0526 — 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-2013-0526 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