Vulnerability-Lookup

CNVD-2017-33215

Vulnerability from cnvd - Published: 2017-11-09

Title

Eclipse Kura命令执行漏洞

Description

Eclipse Kura是Eclipse基金会的一个基于OSGi的M2M服务网关应用框架。 Eclipse Kura 2.1.0之前的版本中存在安全漏洞。攻击者可利用该漏洞登录设备，执行命令，或控制设备。

Severity

高

Patch Name

Eclipse Kura命令执行漏洞的补丁

Patch Description

Eclipse Kura是Eclipse基金会的一个基于OSGi的M2M服务网关应用框架。 Eclipse Kura 2.1.0之前的版本中存在安全漏洞。攻击者可利用该漏洞登录设备，执行命令，或控制设备。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

厂商已发布了漏洞修复程序，请及时关注更新： https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681

Reference

https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681

Impacted products

Name
Eclipse Kura <2.1.0

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-7649"
    }
  },
  "description": "Eclipse Kura\u662fEclipse\u57fa\u91d1\u4f1a\u7684\u4e00\u4e2a\u57fa\u4e8eOSGi\u7684M2M\u670d\u52a1\u7f51\u5173\u5e94\u7528\u6846\u67b6\u3002\r\n\r\n\r\nEclipse Kura 2.1.0\u4e4b\u524d\u7684\u7248\u672c\u4e2d\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u767b\u5f55\u8bbe\u5907\uff0c\u6267\u884c\u547d\u4ee4\uff0c\u6216\u63a7\u5236\u8bbe\u5907\u3002",
  "discovererName": "Jens Reimann",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=514681",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-33215",
  "openTime": "2017-11-09",
  "patchDescription": "Eclipse Kura\u662fEclipse\u57fa\u91d1\u4f1a\u7684\u4e00\u4e2a\u57fa\u4e8eOSGi\u7684M2M\u670d\u52a1\u7f51\u5173\u5e94\u7528\u6846\u67b6\u3002\r\n\r\n\r\nEclipse Kura 2.1.0\u4e4b\u524d\u7684\u7248\u672c\u4e2d\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u767b\u5f55\u8bbe\u5907\uff0c\u6267\u884c\u547d\u4ee4\uff0c\u6216\u63a7\u5236\u8bbe\u5907\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "Eclipse Kura\u547d\u4ee4\u6267\u884c\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "Eclipse Kura \u003c2.1.0"
  },
  "referenceLink": "https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681",
  "serverity": "\u9ad8",
  "submitTime": "2017-09-13",
  "title": "Eclipse Kura\u547d\u4ee4\u6267\u884c\u6f0f\u6d1e"
}

CVE-2017-7649 (GCVE-0-2017-7649)

Vulnerability from cvelistv5 – Published: 2017-09-11 16:00 – Updated: 2024-09-16 17:34

Summary

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.

Severity

No CVSS data available.

CWE

privileged remote code execution

Assigner

eclipse CNA under the mitre root

CNA scorecard C 66/100 over 204 records in the last 180 days details

References

2 references

URL	Tags
https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681	x_refsource_CONFIRM
https://github.com/eclipse/kura/issues/956	x_refsource_CONFIRM

Impacted products

1 product

Vendor	Product	Version
Eclipse Foundation	Eclipse Kura Installer	Affected: unspecified , < 2.1.0 (custom)

Date Public

2017-04-04 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T16:12:27.904Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/eclipse/kura/issues/956"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Eclipse Kura Installer",
          "vendor": "Eclipse Foundation",
          "versions": [
            {
              "lessThan": "2.1.0",
              "status": "affected",
              "version": "unspecified",
              "versionType": "custom"
            }
          ]
        }
      ],
      "datePublic": "2017-04-04T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "The network enabled distribution of Kura before 2.1.0 takes control over the device\u0027s 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."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "privileged remote code execution",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-09-11T15:57:01.000Z",
        "orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
        "shortName": "eclipse"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/eclipse/kura/issues/956"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security@eclipse.org",
          "DATE_PUBLIC": "2017-04-04T00:00:00",
          "ID": "CVE-2017-7649",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Eclipse Kura Installer",
                      "version": {
                        "version_data": [
                          {
                            "version_affected": "\u003c",
                            "version_value": "2.1.0"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Eclipse Foundation"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "The network enabled distribution of Kura before 2.1.0 takes control over the device\u0027s 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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "privileged remote code execution"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681",
              "refsource": "CONFIRM",
              "url": "https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681"
            },
            {
              "name": "https://github.com/eclipse/kura/issues/956",
              "refsource": "CONFIRM",
              "url": "https://github.com/eclipse/kura/issues/956"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
    "assignerShortName": "eclipse",
    "cveId": "CVE-2017-7649",
    "datePublished": "2017-09-11T16:00:00.000Z",
    "dateReserved": "2017-04-11T00:00:00.000Z",
    "dateUpdated": "2024-09-16T17:34:17.160Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted