LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8315: Eclipse XML parser for the Eclipse IDE versions 2017.2.5 and earlier was found vulnerable to an XML Externa...

Eclipse XML parser for the Eclipse IDE versions 2017.2.5 and earlier was found vulnerable to an XML External Entity attack. An attacker can exploit the vulnerability by implementing malicious code on Androidmanifest.xml.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-8315 is an XML External Entity issue in an Eclipse XML parser used with AndroidManifest.xml handling in Eclipse IDE versions 2017.2.5 and earlier. A malicious Android project file could trigger unsafe XML parsing. Business urgency depends on whether developers still use the affected IDE version and open untrusted Android projects.

Executive priority

Treat this as a targeted developer-workstation risk, not a confirmed internet-scale emergency. Prioritize inventory and upgrade guidance if Android development or research teams still use old Eclipse tooling.

Technical view

The source record describes an XXE vulnerability where malicious code placed in AndroidManifest.xml can be processed by the affected Eclipse XML parser. The affected entry names Check Point Software Technologies Ltd. Eclipse versions less than or equal to 2017.2.5. The bundle provides no CVSS score, CWE mapping, fixed version, or detailed impact statement.

Likely exposure

Exposure is most plausible in developer workstations or build/research environments that use Eclipse IDE 2017.2.5 or earlier and open Android projects from untrusted or external sources.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle. The supplied sources describe exploitability through malicious AndroidManifest.xml content, but do not establish active exploitation, public weaponization, or a complete impact chain.

Researcher notes

Evidence is limited. The CVE description links the issue to XXE via AndroidManifest.xml, but the bundle lacks CVSS, CWE, patch details, and active exploitation evidence. Avoid broad claims about affected Eclipse products beyond versions 2017.2.5 and earlier as stated.

Mitigation direction

  • Inventory Eclipse IDE installations and identify versions 2017.2.5 or earlier.
  • Check Eclipse and Check Point guidance for fixed versions or recommended parser configuration.
  • Avoid opening untrusted Android projects in affected IDE versions.
  • Prefer supported, current Android development tooling where operationally feasible.
  • Apply normal workstation controls for developer machines handling third-party code.

Validation and detection

  • Confirm whether Eclipse IDE 2017.2.5 or earlier is installed on developer systems.
  • Review developer workflows for externally sourced Android projects or manifests.
  • Check endpoint logs for suspicious activity around Android project imports, if available.
  • Verify vendor advisories before claiming remediation status.
  • Document affected hosts, users, and compensating controls.
Prepared
Confidence
medium
Sources
4

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-8315 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
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Check Point Software Technologies Ltd.EclipseAll version lower or equal to 2017.2.5Listed
Weakness

CWE details

No CWE listed

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