CVE-2017-9386: n/a vulnerability

CVE-2017-9386: 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 script file called "get_file.sh" which allows a user to retrieve any file stored in the "cmh-ext" folder on the device. However, the "filename" parameter is not validated correctly and this allows an attacker to directory traverse outside the /cmh-ext folder and read any file on the device. It is necessary to create the folder "cmh-ext" on the device which can be executed by an attacker first in an unauthenticated fashion and then execute a directory traversal attack.

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

Security readout for executives and security teams

CVE-2017-9386 affects Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. A web script can be abused to read files outside its intended folder because the filename input is not properly checked. For an executive, the concern is exposure of sensitive device files on home or building automation controllers. Exposure is limited to Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices identified in the sources. Risk is highest where device web interfaces are reachable from untrusted networks or the internet. The source bundle does not establish other affected versions or products. Treat this as a high-priority exposure review for legacy Vera controllers, especially if reachable beyond a trusted admin network. The immediate business action is reducing reachability and confirming whether vendor-supported remediation exists. Mitigation focus: Inventory Vera VeraEdge and Veralite controllers and record firmware versions.; Remove device management interfaces from the public internet.; Restrict access to trusted administration networks or VPN only..

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2017-9386 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:31 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.