CVE-2012-6610
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 · uneditedPolycom HDX Video End Points before 3.0.4 and UC APL before 2.7.1.J allows remote authenticated users to execute arbitrary commands as demonstrated by a ; (semicolon) to the ping command feature.
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 confidenceOS command injection vulnerability in the ping feature of Polycom HDX Video End Points (before 3.0.4) and UC APL (before 2.7.1.J). Authenticated remote attackers can execute arbitrary OS commands by injecting shell metacharacters (semicolon) into the ping parameter.
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.0.4< 2.7.1.jCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Polycom device model and firmware versionAccess the device web interface and check the system information page, or use SNMP/CLI to query the firmware version. Common paths: Administration > System Information or via CLI command 'show system'Affected if The firmware version is below 3.0.4 for HDX devices or below 2.7.1.J for UC APL devices
-
Confirm the device has web management interface enabledCheck if the HTTP/HTTPS management interface is enabled on the device. This is typically found in Network > Management > Web Server settings or via CLI 'show network'Affected if The web management interface is enabled and accessible on the network
-
Verify ping feature accessibilityLocate the ping diagnostic tool in the device web interface (usually under Diagnostics > Network or Administration > Tools). Confirm this feature is available to authenticated usersAffected if The ping feature is present and accessible to authenticated users on the management interface
-
Assess network exposure of management interfaceDetermine if the web management port (typically 80/443) is exposed to untrusted networks. Review firewall rules and network segmentation for the device IP addressAffected if The management interface is reachable from untrusted or external networks
You are affected if you have a Polycom HDX device with firmware < 3.0.4 or UC APL with firmware < 2.7.1.J, and the web management interface with the ping feature is accessible on your network.
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 data2.7.1.j3.0.4
Upgrade Polycom HDX endpoints to firmware 3.0.4 or later, and UC APL to 2.7.1.J or later. Until patched, restrict management interface access to trusted networks and limit ping feature usage.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6610 — 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-2012-6610 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