| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Cisco Secure Desktop 3.1.1.45. This affects an unknown part. Performing a manipulation results in Local Privilege Escalation. This vulnerability is cataloged as CVE-2006-5807. There is no exploit available.
Details
A vulnerability was found in Cisco Secure Desktop 3.1.1.45. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a local privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Cisco Secure Desktop (CSD) before 3.1.1.45 allows local users to escape out of the secure desktop environment by using certain applications that switch to the default desktop, aka "System Policy Evasion".
The bug was discovered 11/08/2006. The weakness was shared 11/08/2006 by Titon with Bastard Labs (Website). The advisory is shared at cisco.com. This vulnerability is uniquely identified as CVE-2006-5807 since 11/08/2006. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
It is declared as proof-of-concept.
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 (30130), SecurityFocus (BID 20964†), OSVDB (30307†), Secunia (SA22747†) and SecurityTracker (ID 1017195†). The entries VDB-2672, VDB-2671, VDB-2670 and VDB-33190 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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.9VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.9
VulDB Temp Score: 5.6
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: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
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
11/08/2006 🔍11/08/2006 🔍
11/08/2006 🔍
11/08/2006 🔍
11/08/2006 🔍
11/08/2006 🔍
11/08/2006 🔍
11/09/2006 🔍
11/09/2006 🔍
11/12/2006 🔍
03/12/2015 🔍
07/10/2019 🔍
Sources
Vendor: cisco.comAdvisory: cisco.com
Researcher: Titon
Organization: Bastard Labs
Status: Confirmed
CVE: CVE-2006-5807 (🔍)
GCVE (CVE): GCVE-0-2006-5807
GCVE (VulDB): GCVE-100-33189
X-Force: 30130
SecurityFocus: 20964 - Cisco Secure Desktop Multiple Vulnerabilities
Secunia: 22747 - Cisco Secure Desktop Multiple Vulnerabilities, Less Critical
OSVDB: 30307 - Cisco Secure Desktop (CSD) Unspecified System Policy Evasion
SecurityTracker: 1017195
Vulnerability Center: 13073 - [cisco-sa-20061108-csd] Cisco Secured Desktop Policy Restrictions Bypass, Medium
Vupen: ADV-2006-4409
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 07/10/2019 16:48
Changes: 03/12/2015 22:21 (70), 07/10/2019 16:48 (1)
Complete: 🔍
Cache ID: 216:6EB: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.