LiveActive security incident?Get immediate response
CVE Record

CVE-2017-5715: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unaut...

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.

MediumCVSS 5.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-5715 is a processor side-channel issue tied to speculative execution and indirect branch prediction. A local user could potentially infer sensitive information from another context. It is not a typical remote code execution bug, but it matters for shared servers, virtualization, desktops, and systems handling sensitive data.

Executive priority

Treat as a coordinated platform-hardening issue with broad asset reach, not an emergency remote compromise. Prioritize environments where untrusted users or code share hardware with sensitive workloads.

Technical view

The CVE describes unauthorized information disclosure through side-channel analysis on microprocessors using speculative execution and indirect branch prediction. The supplied CVSS vector is local, high complexity, low privileges, no user interaction, changed scope, high confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is broad wherever affected speculative-execution processors are used, especially Intel microprocessor platforms, Linux systems, hypervisors, cloud or multi-user workloads, and endpoints with untrusted local code paths.

Exploitation context

The bundle does not support a claim of active exploitation; KEV is false. Exploitation requires local user access and side-channel conditions, making it harder than network exploitation but relevant in shared compute environments.

Researcher notes

Evidence is strongest for confidentiality risk and vendor update availability across major ecosystems. The supplied bundle does not prove active exploitation, specific exploit reliability, or a single universal fix across all platforms.

Mitigation direction

  • Apply relevant vendor OS, kernel, hypervisor, and platform security updates.
  • Follow CPU, firmware, and microcode guidance from the system or cloud vendor.
  • Prioritize shared, multi-tenant, and sensitive-data systems first.
  • Review vendor advisories for performance or compatibility tradeoffs.
  • Maintain browser, runtime, and virtualization stack updates where applicable.

Validation and detection

  • Inventory systems using speculative-execution processors and shared-user workloads.
  • Confirm vendor advisory applicability for each operating system and platform.
  • Verify deployed kernel, hypervisor, firmware, and microcode update status.
  • Check cloud provider or hardware vendor guidance for managed infrastructure.
  • Document accepted residual risk where mitigations are unavailable.
Prepared
Confidence
high
Sources
8

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.

cwe · medium confidence lookup

CWE-203: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-5715 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
Medium
CVSS
5.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
27Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.6CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N1.14Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.6Medium
CVSS 3.1 vector shape for CVE-2017-5715Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Intel CorporationMicroprocessors with Speculative ExecutionAllListed
Weakness

CWE details

CWE-203

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.