LiveActive security incident?Get immediate response
CVE Record

CVE-2017-9387: 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 shell script called relay.sh which is used for creating new SSH relays for the device so that the device connects to Vera servers. All the parameters passed in this specific script are logged to a log file called log.relay in the /tmp folder. The user can also read all the log files from the device using a script called log.sh. However, when the script loads the log files it displays them with content-type text/html and passes all the logs through the ansi2html binary which converts all the character text including HTML meta-characters correctly to be displayed in the browser. This allows an attacker to use the log files as a storing mechanism for the XSS payload and thus whenever a user navigates to that log.sh script, it enables the XSS payload and allows an attacker to execute his malicious payload on the user's browser.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Affected VeraEdge 1.7.19 and Veralite 1.7.481 devices can store attacker-supplied script content in relay logs. When a user views logs through log.sh, that content may run in the browser. This is mainly a risk to administrators or users who open device logs.

Executive priority

Prioritize if these devices manage physical security, automation, or sensitive environments. The issue is not confirmed as actively exploited, but stored XSS against administrators can support account compromise or operational disruption.

Technical view

relay.sh logs all supplied parameters to /tmp/log.relay. log.sh lets users read logs, serves them as text/html, and processes them through ansi2html. The source states this enables stored XSS when malicious log content is later viewed in a browser.

Likely exposure

Exposure appears limited to Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices where attackers can influence relay.sh parameters and a user can access log.sh. The sources do not define broader affected versions or deployment prevalence.

Exploitation context

No provided source or KEV listing indicates active exploitation. Public vulnerability details exist from 2019, but the bundle does not provide exploit prevalence, exploit maturity, authentication requirements, or a vendor patch status.

Researcher notes

Key unknowns are authentication requirements, exact attacker path to relay.sh input, affected firmware range, and patch availability. Analysis should stay scoped to the two versions named in the CVE description unless vendor evidence expands coverage.

Mitigation direction

  • Check Vera vendor guidance for fixed firmware or supported remediation.
  • Restrict device administration and log viewing to trusted networks and users.
  • Limit external access to device management interfaces.
  • Treat log viewing on affected devices as potentially unsafe.
  • Retire or isolate unsupported affected devices.

Validation and detection

  • Inventory VeraEdge and Veralite devices and record firmware versions.
  • Confirm whether any devices run VeraEdge 1.7.19 or Veralite 1.7.481.
  • Review whether log.sh is reachable by non-administrative or remote users.
  • Check vendor advisories for patch status before making changes.
  • Review access controls around device management interfaces.
Prepared
Confidence
medium
Sources
4

Public sources used

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-9387 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
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

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.