Show And ShareApplication · Cisco
CVE-2011-2585
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 · uneditedCisco Show and Share 5(2), 5.2(1), and 5.2(2) before 5.2(2.1) allows remote authenticated users to upload and execute arbitrary code by leveraging video upload privileges, aka Bug ID CSCto69857.
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 confidenceCisco Show and Share versions 5(2), 5.2(1), and 5.2(2) before 5.2(2.1) contains an authenticated arbitrary file upload vulnerability where users with video upload privileges can upload and execute arbitrary code by bypassing file type restrictions in the video upload functionality.
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
Show And ShareApplication
<= 5.2\(2\)= 5\(2\)= 5.2\(1\)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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 Cisco Show and Share installationLocate the Cisco Show and Share application in your environment - this is a web-based video sharing platform typically deployed on Cisco Media Gateway or video management servers. Check for its management interface or service running on your systems.Affected if Cisco Show and Share software is present in the environment
-
Determine installed versionAccess the Cisco Show and Share admin console or check the software version through the management interface. Compare the version number against the affected range: versions 5(2), 5.2(1), 5.2(2), or any version prior to 5.2(2.1).Affected if The installed version is 5(2), 5.2(1), 5.2(2), or any version earlier than 5.2(2.1)
-
Verify video upload functionality is enabledCheck the Cisco Show and Share configuration to determine if the video upload feature is enabled. This is typically found in the admin settings under video upload or content upload permissions.Affected if Video upload functionality is enabled and accessible to users
-
Identify users with video upload privilegesReview user accounts and roles in the Cisco Show and Share administration panel to identify which users have video upload or content creator privileges.Affected if There are user accounts assigned video upload permissions (any non-administrative user with this capability increases exposure)
The environment is affected if Cisco Show and Share version 5(2), 5.2(1), 5.2(2), or versions before 5.2(2.1) is installed AND the video upload feature is enabled with user accounts having upload privileges.
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 to Cisco Show and Share version 5.2(2.1) or later. Until the upgrade is completed, restrict video upload privileges to only highly trusted users and implement additional server-side file type validation and upload directory execution restrictions.
Fix this in Show And Share
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2585 — 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-2011-2585 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