Cisco Show/Share prior 5%282%29 Administration Page access control

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Cisco Show and Share. This issue affects some unknown processing of the component Administration Page. This manipulation causes access control. This vulnerability appears as CVE-2011-2584. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in Cisco Show and Share. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component Administration Page. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Cisco Show and Share 5(2), 5.2(1), and 5.2(2) before 5.2(2.1) allows remote attackers to access the (1) Encoders and Pull Configurations, (2) Push Configurations, (3) Video Encoding Formats, and (4) Transcoding administration pages, and cause a denial of service (live event outage) or obtain potentially sensitive information, via unspecified vectors, aka Bug ID CSCto73758.
The weakness was presented 10/19/2011 by Andy Yang with stratsec (Website). The advisory is shared at xforce.iss.net. This vulnerability is known as CVE-2011-2584. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 5%282%29 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (70757), SecurityFocus (BID 50282†) and Vulnerability Center (SBV-33593†). See VDB-59174 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.cisco.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Show/Share 5%282%29
Timeline
06/27/2011 🔍10/19/2011 🔍
10/19/2011 🔍
10/19/2011 🔍
10/19/2011 🔍
10/25/2011 🔍
03/23/2015 🔍
11/24/2021 🔍
Sources
Vendor: cisco.comAdvisory: xforce.iss.net
Researcher: Andy Yang
Organization: stratsec
Status: Not defined
CVE: CVE-2011-2584 (🔍)
GCVE (CVE): GCVE-0-2011-2584
GCVE (VulDB): GCVE-100-59173
X-Force: 70757
SecurityFocus: 50282 - Cisco Show and Share Anonymous Access Security Bypass Vulnerability
Vulnerability Center: 33593 - [cisco-sa-20111019-sns] Cisco Show and Share \x3C 5.2(2.1) Unauthorized Configuration Files Access, High
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 11/24/2021 14:19
Changes: 03/23/2015 16:50 (48), 04/04/2017 11:11 (11), 11/24/2021 14:19 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.