CVE-2017-9383: n/a vulnerability

CVE-2017-9383: An issue was discovered on Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices.

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 17:02 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE describes Vera home automation controllers exposing a UPnP action that makes the device fetch a user-supplied URL. A misused or exposed device could be turned into an internal network request point. The bundle does not provide CVSS, confirmed exploitation, or a named vendor fix. Exposure is limited to environments with the named VeraEdge or Veralite firmware versions and reachable UPnP services. Risk rises if ports 3480 or 80 are reachable from untrusted networks, guest Wi-Fi, or the public internet. Treat as a focused IoT exposure issue. Prioritize if Vera controllers are internet-facing, on sensitive networks, or used in facilities operations. If only isolated on trusted LANs, handle through normal remediation tracking. Mitigation focus: Inventory VeraEdge 1.7.19 and Veralite 1.7.481 devices.; Restrict ports 3480 and 80 to trusted management networks.; Disable unnecessary UPnP or remote access where operationally feasible..

Prepared: Jun 6, 2026, 20:39 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-9383 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 17, 2019, 19:41 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
20190609 Newly releases IoT security issuesCVE reference · mailing-list, x_refsource_BUGTRAQ
https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Vera_sec_issues.pdfCVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.