CVE-2017-9388: n/a vulnerability

CVE-2017-9388: 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 a web user interface that allows a user to manage the device. As a part of the functionality the device firmware file contains a file known as proxy.sh which allows the device to proxy a specific request to and from from another website. This is primarily used as a method of communication between the device and Vera website when the user is logged in to the https://home.getvera.com and allows the device to communicate between the device and website. One of the parameters retrieved by this specific script is "url". This parameter is not sanitized by the script correctly and is passed in a call to "eval" to execute "curl" functionality. This allows an attacker to escape from the executed command and then execute any commands of his/her choice.

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

Security readout for executives and security teams

CVE-2017-9388 is a command injection flaw in Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. A web UI proxy script handles a url parameter unsafely and can allow arbitrary command execution. Business urgency depends on whether these legacy IoT controllers remain deployed and reachable. Likely limited to organizations or sites still using Vera VeraEdge 1.7.19 or Veralite 1.7.481. Exposure is higher if the device web UI or Vera-linked remote management path is reachable from untrusted networks. Prioritize asset discovery and exposure reduction. This is high impact if affected devices are reachable, but evidence is incomplete on patch status, authentication requirements, and exploitation in the wild. Mitigation focus: Inventory Vera VeraEdge and Veralite devices and firmware versions.; Check vendor guidance for fixed firmware or official remediation.; Remove internet exposure to the Vera web interface where possible..

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-9388 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, 16:52 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.