| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $25k-$100k | 0.00 |
Summary
A vulnerability labeled as very critical has been found in Phoenix Contact Product. This vulnerability affects unknown code. Such manipulation leads to data authenticity. This vulnerability is documented as CVE-2022-31800. The attack can be executed remotely. Additionally, an exploit exists.
Details
A vulnerability was found in Phoenix Contact Product (the affected version unknown). It has been rated as very critical. Affected by this issue is an unknown part. The manipulation with an unknown input leads to a data authenticity vulnerability. Using CWE to declare the problem leads to CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.
The weakness was released 06/21/2022 as VDE-2022-025. The advisory is shared for download at cert.vde.com. This vulnerability is handled as CVE-2022-31800 since 05/30/2022. Technical details are unknown but an exploit is available. The current price for an exploit might be approx. USD $25k-$100k (estimation calculated on 06/21/2022).
It is declared as highly functional. As 0-day the estimated underground price was around $25k-$100k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (CERT VDE): 🔍
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: Data authenticityCWE: CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
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/30/2022 🔍06/21/2022 🔍
06/21/2022 🔍
06/21/2022 🔍
Sources
Advisory: VDE-2022-025Status: Not defined
CVE: CVE-2022-31800 (🔍)
GCVE (CVE): GCVE-0-2022-31800
GCVE (VulDB): GCVE-100-202436
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/21/2022 13:04Changes: 06/21/2022 13:04 (48)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.