WAGO PFC200 03.00.39(12)/03.01.07(13)/03.02.02(14) Cloud Connectivity HTTPS Post Request input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in WAGO PFC200 03.00.39(12)/03.01.07(13)/03.02.02(14). This impacts an unknown function of the component Cloud Connectivity. The manipulation as part of HTTPS Post Request results in input validation. This vulnerability is cataloged as CVE-2019-5160. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in WAGO PFC200 03.00.39(12)/03.01.07(13)/03.02.02(14). It has been classified as critical. Affected is some unknown functionality of the component Cloud Connectivity. The manipulation as part of a HTTPS Post Request leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An exploitable improper host validation vulnerability exists in the Cloud Connectivity functionality of WAGO PFC200 Firmware versions 03.02.02(14), 03.01.07(13), and 03.00.39(12). A specially crafted HTTPS POST request can cause the software to connect to an unauthorized host, resulting in unauthorized access to firmware update functionality. An attacker can send an authenticated HTTPS POST request to direct the Cloud Connectivity software to connect to an attacker controlled Azure IoT Hub node.
The weakness was shared 03/11/2020. This vulnerability is traded as CVE-2019-5160 since 01/04/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-151318, VDB-151317, VDB-151316 and VDB-151315 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.4
VulDB Temp Score: 7.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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: Input validationCWE: CWE-20
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
01/04/2019 🔍03/11/2020 🔍
03/12/2020 🔍
04/13/2024 🔍
Sources
Advisory: talosintelligence.comStatus: Not defined
CVE: CVE-2019-5160 (🔍)
GCVE (CVE): GCVE-0-2019-5160
GCVE (VulDB): GCVE-100-151314
See also: 🔍
Entry
Created: 03/12/2020 08:34Updated: 04/13/2024 09:13
Changes: 03/12/2020 08:34 (37), 03/12/2020 08:39 (17), 04/13/2024 09:13 (17)
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.