Seiko SkyBridge MB-A100/SkyBridge MB-A110 up to 4.2.0 Web UI weak password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Seiko SkyBridge MB-A100 and SkyBridge MB-A110 up to 4.2.0. This vulnerability affects unknown code of the component Web UI. Performing a manipulation results in weak password. This vulnerability is identified as CVE-2023-25072. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Seiko SkyBridge MB-A100 and SkyBridge MB-A110 up to 4.2.0. It has been classified as problematic. This affects an unknown code of the component Web UI. The manipulation with an unknown input leads to a weak password vulnerability. CWE is classifying the issue as CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. This is going to have an impact on confidentiality. The summary by CVE is:
Use of weak credentials exists in SkyBridge MB-A100/110 firmware Ver. 4.2.0 and earlier, which may allow a remote unauthenticated attacker to decrypt password for the WebUI of the product.
The weakness was released 05/10/2023. The advisory is shared at jvn.jp. This vulnerability is uniquely identified as CVE-2023-25072 since 03/15/2023. 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 vulnerability database at EUVD (EUVD-2023-29051). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: Weak passwordCWE: CWE-521
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
03/15/2023 🔍05/10/2023 🔍
05/10/2023 🔍
10/28/2025 🔍
Sources
Advisory: jvn.jpStatus: Not defined
CVE: CVE-2023-25072 (🔍)
GCVE (CVE): GCVE-0-2023-25072
GCVE (VulDB): GCVE-100-228561
EUVD: 🔍
Entry
Created: 05/10/2023 08:58Updated: 10/28/2025 04:54
Changes: 05/10/2023 08:58 (38), 06/02/2023 08:57 (11), 10/28/2025 04:54 (16)
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.