Yokogawa STARDOM FCN Controller/STARDOM FCJ Controller up to R4.31 hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Yokogawa STARDOM FCN Controller and STARDOM FCJ Controller up to R4.31. This affects an unknown function. The manipulation results in hard-coded credentials. This vulnerability is cataloged as CVE-2022-30997. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as very critical has been found in Yokogawa STARDOM FCN Controller and STARDOM FCJ Controller up to R4.31. Affected is an unknown code block. The manipulation with an unknown input 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. CVE summarizes:
Use of hard-coded credentials vulnerability exists in STARDOM FCN Controller and FCJ Controller R4.10 to R4.31, which may allow an attacker with an administrative privilege to read/change configuration settings or update the controller with tampered firmware.
The weakness was shared 06/29/2022 as icsa-22-174-01. The advisory is available at cisa.gov. This vulnerability is traded as CVE-2022-30997 since 05/31/2022. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/01/2024). This vulnerability is assigned to T1110.001 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- R4.0
- R4.1
- R4.2
- R4.3
- R4.4
- R4.5
- R4.6
- R4.7
- R4.8
- R4.9
- R4.10
- R4.11
- R4.12
- R4.13
- R4.14
- R4.15
- R4.16
- R4.17
- R4.18
- R4.19
- R4.20
- R4.21
- R4.22
- R4.23
- R4.24
- R4.25
- R4.26
- R4.27
- R4.28
- R4.29
- R4.30
- R4.31
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 6.3
CNA 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/31/2022 🔍06/29/2022 🔍
06/29/2022 🔍
08/01/2024 🔍
Sources
Advisory: icsa-22-174-01Status: Confirmed
CVE: CVE-2022-30997 (🔍)
GCVE (CVE): GCVE-0-2022-30997
GCVE (VulDB): GCVE-100-202914
Entry
Created: 06/29/2022 08:08Updated: 08/01/2024 18:30
Changes: 06/29/2022 08:08 (38), 07/16/2022 11:59 (18), 08/01/2024 18:30 (26)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.