dbcve.org
KuraApplication · Eclipse

CVE-2017-7649

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-11
Fix available
A fix is available. Upgrade to after 2.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The network enabled distribution of Kura before 2.1.0 takes control over the device's firewall setup but does not allow IPv6 firewall rules to be configured. Still the Equinox console port 5002 is left open, allowing to log into Kura without any user credentials over unencrypted telnet and executing commands using the Equinox "exec" command. As the process is running as "root" full control over the device can be acquired. IPv6 is also left in auto-configuration mode, accepting router advertisements automatically and assigns a MAC address based IPv6 address.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kura物联网框架在2.1.0之前的版本中,防火墙模块虽然接管了设备防火墙配置,但存在IPv6防火墙规则无法配置的缺陷,导致Equinox控制台端口5002在IPv6网络环境下保持开放状态且无任何认证保护。攻击者可利用未加密的telnet协议直接连接该端口,通过Equinox的exec命令以root权限执行任意命令从而完全控制设备。

Mitigation将Kura升级至2.1.0或更高版本以修复防火墙漏洞,同时在网络层面配置IPv6防火墙规则阻止对端口5002的未授权访问,或禁用不必要的IPv6自动配置。

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KuraApplication
Affected:<= 2.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Eclipse Kura installation and version
    Check if Eclipse Kura is installed by looking for its installation directory (typically /opt/kura or /usr/local/kura) and locate the kura.version file or manifest containing the version number. On Debian-based systems, you may also run 'dpkg -l | grep kura' or 'apt list --installed | grep kura'.
    Affected if Eclipse Kura version 2.0.2 or lower is installed
  2. Verify IPv6 network stack is active
    Run 'ip -6 addr show' or 'cat /proc/net/if_inet6' to confirm IPv6 is enabled on the system. You can also check with 'sysctl net.ipv6.conf.all.disable_ipv6' (value of 0 means IPv6 is active).
    Affected if IPv6 is enabled on the system where Kura is running
  3. Check if port 5002 is listening on IPv6
    Run 'netstat -tulpn | grep :5002' or 'ss -tulpn | grep :5002' to see if port 5002 is bound to an IPv6 address (:: or 0.0.0.0). The output will show whether the Equinox console is listening on IPv6.
    Affected if Port 5002 is listening on an IPv6 address (:: or 0.0.0.0) and is accessible from the network
  4. Inspect IPv6 firewall rules for port 5002
    Run 'ip6tables -L -n' or 'ip6tables -L -n -v' to list IPv6 firewall rules. Search for any DROP, REJECT, or ACCEPT rules specifically targeting port 5002 or the equinox service.
    Affected if No IPv6 firewall rule exists to block or restrict access to port 5002, leaving it exposed to unauthenticated connections

The system is affected if Eclipse Kura version 2.0.2 or lower is installed with IPv6 enabled and port 5002 is accessible on IPv6 without firewall protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.2
Interim mitigation

将Kura升级至2.1.0或更高版本以修复防火墙漏洞,同时在网络层面配置IPv6防火墙规则阻止对端口5002的未授权访问,或禁用不必要的IPv6自动配置。

Recommended fix High confidence

Kura 2.1.0

  1. Upgrade Kura to version 2.1.0 or later to remediate this vulnerability
  2. After upgrading, verify that the Equinox console (port 5002) is no longer exposed or is properly secured with authentication
  3. Review and configure IPv6 firewall rules if IPv6 is in use
  4. Disable IPv6 auto-configuration if router advertisements are not expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kura Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7649 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data