Belkin Wemo Switch 28B WW_2.00.11057.PVT-OWRT-SNS Rule Processing upnp/control/rules1 ruleDbBody input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Belkin Wemo Switch 28B WW_2.00.11057.PVT-OWRT-SNS. Affected by this vulnerability is an unknown functionality of the file upnp/control/rules1 of the component Rule Processing. The manipulation of the argument ruleDbBody leads to input validation. This vulnerability is traded as CVE-2019-17532. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Belkin Wemo Switch 28B WW_2.00.11057.PVT-OWRT-SNS and classified as problematic. This issue affects some unknown processing of the file upnp/control/rules1 of the component Rule Processing. The manipulation of the argument ruleDbBody with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:
An issue was discovered on Belkin Wemo Switch 28B WW_2.00.11057.PVT-OWRT-SNS devices. They allow remote attackers to cause a denial of service (persistent rules-processing outage) via a crafted ruleDbBody element in a StoreRules request to the upnp/control/rules1 URI, because database corruption occurs.
The weakness was shared 10/12/2019. The identification of this vulnerability is CVE-2019-17532 since 10/12/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: 🔍
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
10/12/2019 🔍10/12/2019 🔍
10/13/2019 🔍
01/08/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2019-17532 (🔍)
GCVE (CVE): GCVE-0-2019-17532
GCVE (VulDB): GCVE-100-143429
Entry
Created: 10/13/2019 17:05Updated: 01/08/2024 10:04
Changes: 10/13/2019 17:05 (37), 10/13/2019 17:10 (17), 01/08/2024 10:04 (3)
Complete: 🔍
Cache ID: 216:145:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.