Vera VeraEdge/Veralite UPnP Service /port_3480 URL improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.6 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Vera VeraEdge and Veralite. This affects an unknown function of the file /port_3480 of the component UPnP Service. Executing a manipulation of the argument URL as part of Query String can lead to improper authentication. This vulnerability is registered as CVE-2017-9383. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as critical was found in Vera VeraEdge and Veralite (unknown version). This vulnerability affects an unknown code block of the file /port_3480 of the component UPnP Service. The manipulation of the argument URL as part of a Query String leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered on Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. The device provides UPnP services that are available on port 3480 and can also be accessed via port 80 using the url "/port_3480". It seems that the UPnP services provide "wget" as one of the service actions for a normal user to connect the device to an external website. It retrieves the parameter "URL" from the query string and then passes it to an internal function that uses the curl module on the device to retrieve the contents of the website.
The weakness was published 06/17/2019 as not defined mailinglist post (Bugtraq). The advisory is shared for download at seclists.org. This vulnerability was named CVE-2017-9383 since 06/02/2017. The exploitation appears to be easy. The attack can be initiated remotely. The requirement for exploitation is a single authentication. There are known technical details, 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.
Similar entries are available at VDB-136204, VDB-136205, VDB-136206 and VDB-136207. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.6VulDB Meta Temp Score: 8.6
VulDB Base Score: 7.4
VulDB Temp Score: 7.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.9
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: Improper authenticationCWE: CWE-287
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
06/02/2017 🔍06/17/2019 🔍
06/18/2019 🔍
10/05/2023 🔍
Sources
Advisory: 153242Status: Not defined
CVE: CVE-2017-9383 (🔍)
GCVE (CVE): GCVE-0-2017-9383
GCVE (VulDB): GCVE-100-136540
See also: 🔍
Entry
Created: 06/18/2019 08:24Updated: 10/05/2023 14:52
Changes: 06/18/2019 08:24 (41), 06/24/2020 17:46 (17), 10/05/2023 14:52 (3)
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.