CVE-2017-9381: n/a vulnerability

CVE-2017-9381: 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 user with the capability of installing or deleting apps on the device using the web management interface. It seems that the device does not implement any cross-site request forgery protection mechanism which allows an attacker to trick a user who navigates to an attacker controlled page to install or delete an application on the device. Note: The cross-site request forgery is a systemic issue across all other functionalities of the device.

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

Security readout for executives and security teams

CVE-2017-9381 is a cross-site request forgery issue in Vera VeraEdge 1.7.19 and Veralite 1.7.481. A malicious page could cause a logged-in device user to install or delete apps through the web management interface without intending to. Sources also describe CSRF as systemic across other device functions. Exposure is most relevant where VeraEdge 1.7.19 or Veralite 1.7.481 devices are still in use and administrators access the web management interface from browsers that may also visit untrusted sites. Treat this as a moderate operational risk for legacy Vera home automation deployments. Prioritize devices that remain managed through browser-based consoles or are reachable from broader internal networks. Mitigation focus: Check Vera vendor guidance for fixed firmware or supported upgrade paths.; Restrict management interface access to trusted networks or VPN users.; Avoid browsing untrusted sites while authenticated to the device console..

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-9381 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, 17:27 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.