Security readout for executives and security teams
Plain-English summary
Older network-enabled Eclipse Kura installations could expose a management console over unencrypted telnet without requiring credentials. Because Kura ran as root, a reachable vulnerable device could be fully controlled. The sources do not show confirmed active exploitation.
Executive priority
Treat reachable vulnerable devices as urgent because the issue can lead to full device control. Prioritize internet-facing, partner-connected, and operational technology networks first, then complete fleet-wide version and IPv6 exposure review.
Technical view
Kura before 2.1.0 left Equinox console port 5002 open while IPv6 firewall rules were not configurable. IPv6 remained in autoconfiguration mode, accepting router advertisements and assigning a MAC-based IPv6 address. The Equinox console allowed command execution through its exec capability under the root-running Kura process.
Likely exposure
Exposure is most likely on devices using the network-enabled Eclipse Kura distribution before 2.1.0, especially where IPv6 is enabled or reachable and port 5002 is not filtered.
Exploitation context
The source bundle does not cite CISA KEV inclusion or confirmed exploitation. The described condition is high impact because it combines unauthenticated telnet access, command execution, unencrypted transport, and root privileges when reachable.
Researcher notes
The bundle provides no CVSS, CWE, exploit confirmation, or detailed patch notes. The strongest evidence is the CVE description and Eclipse/GitHub references. Do not broaden impact beyond Kura before 2.1.0 network-enabled deployments without additional vendor evidence.
Mitigation direction
- Upgrade affected Kura deployments to 2.1.0 or later where applicable.
- Check Eclipse guidance for the specific Kura installer or distribution in use.
- Block external and untrusted IPv6 access to port 5002.
- Disable or restrict Equinox console exposure where supported.
- Review IPv6 firewall and router advertisement handling on deployed devices.
Validation and detection
- Inventory all Eclipse Kura devices and record installed versions.
- Identify devices using the network-enabled distribution before 2.1.0.
- Confirm whether IPv6 is enabled, routable, or autoconfigured on each device.
- Verify port 5002 is not reachable from untrusted networks.
- Confirm console access requires approved authentication and encryption controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2017-7649 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681CVE reference · x_refsource_CONFIRM
- https://github.com/eclipse/kura/issues/956CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.