Alcatel-Lucent OmniPCX 4400 /etc/password hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Alcatel-Lucent OmniPCX 4400. This impacts an unknown function of the file /etc/password. Executing a manipulation can lead to hard-coded credentials. This vulnerability is handled as CVE-2002-1691. There is not any exploit available.
Details
A vulnerability has been found in Alcatel-Lucent OmniPCX 4400 and classified as very critical. This vulnerability affects some unknown functionality of the file /etc/password. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Alcatel OmniPCX 4400 installs known user accounts and passwords in the /etc/password file by default, which allows remote attackers to gain unauthorized access.
The weakness was released 12/31/2002 (Website). The advisory is shared for download at marc.theaimsgroup.com. This vulnerability was named CVE-2002-1691 since 06/21/2005. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/09/2018). The MITRE ATT&CK project declares the attack technique as T1110.001.
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 (8224) and SecurityFocus (BID 4127†). Entries connected to this vulnerability are available at VDB-18224, VDB-18225 and VDB-18226. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / 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
02/19/2002 🔍12/31/2002 🔍
12/31/2002 🔍
06/21/2005 🔍
08/04/2014 🔍
06/09/2018 🔍
Sources
Advisory: marc.theaimsgroup.comStatus: Not defined
CVE: CVE-2002-1691 (🔍)
GCVE (CVE): GCVE-0-2002-1691
GCVE (VulDB): GCVE-100-19336
X-Force: 8224 - Alcatel OmniPCX 4400 default user accounts
SecurityFocus: 4127
See also: 🔍
Entry
Created: 08/04/2014 16:28Updated: 06/09/2018 11:06
Changes: 08/04/2014 16:28 (47), 06/09/2018 11:06 (6)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.