| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Cisco WebEx Meeting Server 1.5. This affects an unknown part of the file p.php. This manipulation causes access control (User Name). This vulnerability is tracked as CVE-2014-3286. Moreover, an exploit is present.
Details
A vulnerability has been found in Cisco WebEx Meeting Server 1.5 (Unified Communication Software) and classified as problematic. Affected by this vulnerability is some unknown functionality of the file p.php. The manipulation with an unknown input leads to a access control vulnerability (User Name). The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality.
The weakness was disclosed 06/06/2014 with Cisco as CSCuj81685 / CSCuj81688 / CSCuj81665 / CSCuj81744 / CSCuj81661 as confirmed security notice (Website). The advisory is shared at tools.cisco.com. This vulnerability is known as CVE-2014-3286 since 05/07/2014. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a exploit are known. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/20/2021). MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is declared as highly functional. By approaching the search of inurl:p.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (93662), SecurityFocus (BID 67922†) and Secunia (SA58571†). Additional details are provided at tools.cisco.com. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.cisco.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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
Name: User NameClass: Access control / User Name
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/07/2014 🔍06/06/2014 🔍
06/06/2014 🔍
06/08/2014 🔍
06/09/2014 🔍
06/11/2014 🔍
06/20/2021 🔍
Sources
Vendor: cisco.comAdvisory: CSCuj81685 / CSCuj81688 / CSCuj81665 / CSCuj81744 / CSCuj81661
Organization: Cisco
Status: Confirmed
CVE: CVE-2014-3286 (🔍)
GCVE (CVE): GCVE-0-2014-3286
GCVE (VulDB): GCVE-100-13477
X-Force: 93662 - Cisco WebEx Meeting Server returned message information disclosure, Medium Risk
SecurityFocus: 67922 - Cisco WebEx Meeting Server CVE-2014-3286 User Enumeration Vulnerability
Secunia: 58571 - Cisco WebEx Meeting Server User Enumeration Weaknesses, Not Critical
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
Entry
Created: 06/09/2014 16:59Updated: 06/20/2021 17:56
Changes: 06/09/2014 16:59 (44), 04/03/2019 09:31 (21), 06/20/2021 17:56 (3)
Complete: 🔍
Cache ID: 216:7BF: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.