Windriver VxWorks up to 6.8 Hardcoded Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Windriver VxWorks 5/5.5/6/6.4/6.8. This affects an unknown function of the component Hardcoded Credentials. Performing a manipulation results in credentials management. This vulnerability is cataloged as CVE-2010-2966. There is no exploit available.
Details
A vulnerability was found in Windriver VxWorks 5/5.5/6/6.4/6.8 (Hardware Driver Software). It has been classified as critical. This affects some unknown processing of the component Hardcoded Credentials. The manipulation with an unknown input leads to a credentials management vulnerability. CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
The INCLUDE_SECURITY functionality in Wind River VxWorks 6.x, 5.x, and earlier uses the LOGIN_USER_NAME and LOGIN_USER_PASSWORD (aka LOGIN_PASSWORD) parameters to create hardcoded credentials, which makes it easier for remote attackers to obtain access via a (1) telnet, (2) rlogin, or (3) FTP session.
The weakness was shared 08/05/2010 as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is uniquely identified as CVE-2010-2966 since 08/04/2010. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
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 SecurityFocus (BID 42114†) and Vulnerability Center (SBV-27016†). The entry VDB-54250 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.5
VulDB Temp Score: 7.5
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: Credentials managementCWE: CWE-255
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/02/2010 🔍08/02/2010 🔍
08/04/2010 🔍
08/05/2010 🔍
08/05/2010 🔍
09/06/2010 🔍
03/19/2015 🔍
07/31/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
CVE: CVE-2010-2966 (🔍)
GCVE (CVE): GCVE-0-2010-2966
GCVE (VulDB): GCVE-100-54249
CERT: 🔍
SecurityFocus: 42114 - VxWorks Insecure Password Hashing Vulnerability
Vulnerability Center: 27016 - VxWorks 6.x and 5.x Allows Remote Attackers to Gain Access, High
See also: 🔍
Entry
Created: 03/19/2015 14:37Updated: 07/31/2024 16:01
Changes: 03/19/2015 14:37 (50), 03/03/2017 18:03 (9), 07/31/2024 16:01 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.