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).
CVE-2017-17674
CRITICALNVD 9.89.8—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 3.3%, top 13% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EPSS
- 79.2%
- KEV
- Not listed
Published
May 19, 2021
Last Modified
July 9, 2026
Advisory Details (2)
Auto-updated Jul 9, 2026No patch confirmed yet.
generic
Full Disclosure: Multiple vulnerabilities in BMC Remedy
https://seclists.org/fulldisclosure/2017/Oct/52Vendor Advisories for CVE-2017-17674(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2017-17674?
CVE-2017-17674 is a critical vulnerability published on May 19, 2021. 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).
When was CVE-2017-17674 disclosed?
CVE-2017-17674 was first published in the National Vulnerability Database on May 19, 2021, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17674 actively exploited?
CVE-2017-17674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-17674?
CVE-2017-17674 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-17674?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-17674, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-17674
Is Your Infrastructure Affected by CVE-2017-17674?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.