LiveActive security incident?Get immediate response
CVE Record

CVE-2017-17674: BMC Remedy Mid Tier 9.1SP3 is affected by remote and local file inclusion.

BMC Remedy Mid Tier 9.1SP3 is affected by remote and local file inclusion. Due to the lack of restrictions on what can be targeted, the system can be vulnerable to attacks such as system fingerprinting, internal port scanning, Server Side Request Forgery (SSRF), or remote code execution (RCE).

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

Security readout for executives and security teams

Plain-English summary

CVE-2017-17674 affects BMC Remedy Mid Tier 9.1SP3. The issue allowed unsafe file inclusion targets, which could let an attacker make the server access local or remote resources. Business impact could include internal reconnaissance, data exposure, SSRF-style access to internal services, or possibly code execution.

Executive priority

Prioritize remediation for any reachable Remedy Mid Tier 9.1SP3 instance. Even without confirmed active exploitation, the potential SSRF and RCE impact creates meaningful enterprise risk.

Technical view

The CVE describes remote and local file inclusion in BMC Remedy Mid Tier 9.1SP3 due to insufficient restrictions on inclusion targets. The public record cites risks including system fingerprinting, internal port scanning, SSRF, and RCE. The bundle does not provide CVSS, CWE, exploit maturity, or precise fixed-version details.

Likely exposure

Organizations are most likely exposed if they still operate BMC Remedy Mid Tier 9.1SP3, especially on internet-facing or broadly reachable internal portals.

Exploitation context

The source bundle includes a public Full Disclosure reference, but does not show CISA KEV listing or confirmed active exploitation. Treat this as publicly known but not source-confirmed as actively exploited.

Researcher notes

Evidence is limited to the CVE description, BMC advisory reference, and Full Disclosure reference. No CVSS, CWE, affected CPEs, exploit status, or exact fixed build is included in the provided bundle.

Mitigation direction

  • Inventory BMC Remedy Mid Tier deployments and identify any 9.1SP3 instances.
  • Review BMC’s Remedy AR System security fixes guidance for applicable vendor remediation.
  • Apply the relevant BMC fixes or upgrade according to vendor guidance.
  • Restrict Mid Tier access to trusted networks and authenticated users where possible.
  • Limit server outbound access to internal services and untrusted remote destinations.
  • Monitor Remedy Mid Tier logs for unusual resource inclusion or server-side retrieval patterns.

Validation and detection

  • Confirm whether any deployed Remedy Mid Tier instance is version 9.1SP3.
  • Verify vendor security fixes have been applied using BMC documentation and change records.
  • Check external exposure of Remedy Mid Tier through asset inventory and perimeter scans.
  • Review logs for suspicious requests referencing remote URLs, local paths, or internal services.
  • Validate egress controls block unnecessary server-side outbound connections.
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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-17674 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
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

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.