BE126 WiFI Repeater 1.0 Telnet Service hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in BE126 WiFI Repeater 1.0. Affected by this vulnerability is an unknown functionality of the component Telnet Service. Performing a manipulation with the input root:root results in hard-coded credentials.
This vulnerability is reported as CVE-2017-8772. The attack is possible to be carried out remotely. No exploit exists.
It is suggested to use restrictive firewalling.
Details
A vulnerability, which was classified as critical, was found in BE126 WiFI Repeater 1.0 (Wireless LAN Software). This affects an unknown code of the component Telnet Service. The manipulation with the input value root:root leads to a hard-coded credentials vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
On BE126 WIFI repeater 1.0 devices, an attacker can log into telnet (which is open by default) with default credentials as root (username:"root" password:"root") and can: 1. Read the entire file system; 2. Write to the file system; or 3. Execute any code that attacker desires (malicious or not).
The bug was discovered 05/03/2017. The weakness was disclosed 09/20/2017 (Website). It is possible to read the advisory at digitalwhisper.co.il. This vulnerability is uniquely identified as CVE-2017-8772 since 05/03/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1110.001 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 140 days. During that time the estimated underground price was around $0-$5k.
It is possible to mitigate the weakness by firewalling .
The entry VDB-106886 is pretty similar. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
05/03/2017 🔍05/03/2017 🔍
09/20/2017 🔍
09/20/2017 🔍
09/20/2017 🔍
11/18/2019 🔍
Sources
Advisory: digitalwhisper.co.ilStatus: Not defined
CVE: CVE-2017-8772 (🔍)
GCVE (CVE): GCVE-0-2017-8772
GCVE (VulDB): GCVE-100-106887
See also: 🔍
Entry
Created: 09/20/2017 23:19Updated: 11/18/2019 08:33
Changes: 09/20/2017 23:19 (60), 11/18/2019 08:33 (2)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.