Security readout for executives and security teams
Plain-English summary
CVE-2017-17678 is a DOM-based cross-site scripting issue reported in BMC Remedy Mid Tier 9.1SP3. It could let attacker-controlled content run in a user's browser when they interact with an affected legacy utility. The source bundle does not provide CVSS, CWE, exploit status, or complete affected-version data.
Executive priority
Treat this as a targeted remediation item for legacy Remedy environments, especially externally reachable portals. The business urgency is moderate unless exposure is confirmed on internet-facing systems or sensitive user sessions.
Technical view
The record describes DOM XSS in a legacy utility within BMC Remedy Mid Tier 9.1SP3. Structured affected-product data is incomplete, listing n/a values, so exposure should be confirmed against deployed Remedy Mid Tier versions and BMC's referenced security fixes page. No source in the bundle establishes active exploitation.
Likely exposure
Organizations may be exposed if they still run BMC Remedy Mid Tier 9.1SP3 or related 9.1 deployments containing the legacy utility. Internet-facing or broadly accessible service-desk portals increase browser-session risk.
Exploitation context
The bundle references a 2017 public disclosure and BMC's security-fix page, but it does not include evidence of exploitation in the wild. The CVE is not marked as CISA KEV.
Researcher notes
Evidence is limited. The CVE record identifies BMC Remedy Mid Tier 9.1SP3 and DOM-based XSS, but lacks CVSS, CWE, CPE, and detailed affected ranges. Avoid assuming broader BMC products or exploitation without vendor confirmation.
Mitigation direction
- Identify any BMC Remedy Mid Tier 9.1SP3 deployments.
- Review BMC's referenced security-fix guidance for applicable updates.
- Apply vendor-provided fixes or upgrade guidance where relevant.
- Restrict access to Remedy Mid Tier while remediation is pending.
- Use browser and application controls to reduce XSS impact.
Validation and detection
- Inventory Remedy Mid Tier versions and deployment locations.
- Confirm whether the referenced legacy utility exists in deployed instances.
- Check whether BMC security fixes are applied.
- Review vulnerability-scan results for DOM-based XSS findings.
- Review access logs for unusual activity around the utility.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2017-17678 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.bmc.com/docs/ars91/en/9-1-00-fixes-available-for-remedy-ar-system-security-vulnerabilities-800555806.htmlCVE reference, mitre
- https://seclists.org/fulldisclosure/2017/Oct/52CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.