LiveActive security incident?Get immediate response
CVE Record

CVE-2017-17675: BMC Remedy Mid Tier 9.1SP3 is affected by log hijacking.

BMC Remedy Mid Tier 9.1SP3 is affected by log hijacking. Remote logging can be accessed by unauthenticated users, allowing for an attacker to hijack the system logs. This data can include user names and HTTP data.

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

Security readout for executives and security teams

Plain-English summary

CVE-2017-17675 affects BMC Remedy Mid Tier 9.1SP3. Public sources describe unauthenticated access to remote logging, allowing an attacker to interfere with system logs and potentially view usernames and HTTP data. The main business risk is loss of log integrity and exposure of operational or user data.

Executive priority

Treat this as a priority for organizations running BMC Remedy Mid Tier 9.1SP3. It is not confirmed as actively exploited, but unauthenticated log access can undermine incident response and expose sensitive operational data.

Technical view

The issue is described as log hijacking in BMC Remedy Mid Tier 9.1SP3. Remote logging can be reached without authentication, which may let an unauthenticated remote actor access or manipulate logging data. Available sources do not provide CVSS, CWE, detailed affected ranges beyond 9.1SP3, or confirmed exploit activity.

Likely exposure

Exposure is most likely where BMC Remedy Mid Tier 9.1SP3 is deployed and remote logging is reachable by unauthenticated users, especially from untrusted networks.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. The public disclosure indicates unauthenticated access, but this analysis does not include exploit instructions.

Researcher notes

Evidence is limited. The bundle names BMC Remedy Mid Tier 9.1SP3 and describes unauthenticated remote logging exposure. It does not include CVSS, CWE, precise endpoint details, proof of exploitation, or complete fixed-version information.

Mitigation direction

  • Review BMC's Remedy AR System security fixes page for vendor guidance.
  • Apply the applicable BMC fix or supported upgrade for affected Mid Tier deployments.
  • Limit access to Remedy Mid Tier remote logging interfaces to trusted administrative networks.
  • Review whether logging data contains usernames, HTTP data, or other sensitive fields.

Validation and detection

  • Inventory BMC Remedy Mid Tier instances and identify any 9.1SP3 deployments.
  • Confirm whether remote logging is reachable without authentication from untrusted networks.
  • Check BMC fix status for each identified Remedy Mid Tier deployment.
  • Review access logs for unexpected unauthenticated requests to logging-related functionality.
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-17675 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.