| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Cisco Clean Access 3.3.0. It has been classified as critical. This impacts an unknown function of the component Security Check. This manipulation causes Remote Code Execution. This vulnerability is handled as CVE-2005-2631. There is not any exploit available.
Details
A vulnerability classified as critical was found in Cisco Clean Access 3.3.0. Affected by this vulnerability is an unknown code block of the component Security Check. The manipulation with an unknown input leads to a remote code execution vulnerability. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Cisco Clean Access (CCA) 3.3.0 to 3.3.9, 3.4.0 to 3.4.5, and 3.5.0 to 3.5.3 does not properly authenticate users when invoking API methods, which could allow remote attackers to bypass security checks, change the assigned role of a user, or disconnect users.
The bug was discovered 08/17/2005. The weakness was released 08/23/2005 (Website). The advisory is shared at xforce.iss.net. This vulnerability is known as CVE-2005-2631 since 08/20/2005. 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.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $25k-$100k.
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 (21884), SecurityFocus (BID 14585†), OSVDB (18846†), Secunia (SA16472†) and Vulnerability Center (SBV-8938†). 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: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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
Class: Remote Code ExecutionCWE: Unknown
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/17/2005 🔍08/17/2005 🔍
08/17/2005 🔍
08/20/2005 🔍
08/21/2005 🔍
08/23/2005 🔍
08/23/2005 🔍
03/11/2015 🔍
06/08/2019 🔍
Sources
Vendor: cisco.comAdvisory: xforce.iss.net
Status: Not defined
CVE: CVE-2005-2631 (🔍)
GCVE (CVE): GCVE-0-2005-2631
GCVE (VulDB): GCVE-100-26101
X-Force: 21884
SecurityFocus: 14585 - Cisco Clean Access API Access Validation Vulnerability
Secunia: 16472
OSVDB: 18846 - Cisco - Clean Access - API Access Validation Issue
Vulnerability Center: 8938 - [cisco-sa-20050817-cca] Cisco Clean Access (CCA) API Access Authentication Bypass, High
Entry
Created: 03/11/2015 23:39Updated: 06/08/2019 12:56
Changes: 03/11/2015 23:39 (55), 06/08/2019 12:56 (5)
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.