Vulnerability-Lookup

CNVD-2019-17471

Vulnerability from cnvd - Published: 2019-06-14

Title

Elastic Cloud Enterprise (ECE) 信息泄露漏洞（CNVD-2019-17471）

Description

Elastic Cloud Enterprise (ECE) 是荷兰Elasticsearch公司的一套用于管理、监控和配置Elasticsearch、Kibana和X-Pack的软件包。 Elastic Cloud Enterprise (ECE) 存在信息泄露漏洞，攻击者可通过直接连接ZooKeeper，利用该漏洞访问其他已知集群ID的用户的配置信息。

Severity

中

Patch Name

Elastic Cloud Enterprise (ECE) 信息泄露漏洞（CNVD-2019-17471）的补丁

Patch Description

Formal description

厂商已发布了漏洞修复程序，请及时关注更新： https://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778

Reference

https://nvd.nist.gov/vuln/detail/CVE-2018-3825

Impacted products

Name
ElasticSearch Elastic Cloud Enterprise (ECE) <1.1.4

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-3825",
      "cveUrl": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3825"
    }
  },
  "description": "Elastic Cloud Enterprise (ECE) \u662f\u8377\u5170Elasticsearch\u516c\u53f8\u7684\u4e00\u5957\u7528\u4e8e\u7ba1\u7406\u3001\u76d1\u63a7\u548c\u914d\u7f6eElasticsearch\u3001Kibana\u548cX-Pack\u7684\u8f6f\u4ef6\u5305\u3002\n\nElastic Cloud Enterprise (ECE) \u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u76f4\u63a5\u8fde\u63a5ZooKeeper\uff0c\u5229\u7528\u8be5\u6f0f\u6d1e\u8bbf\u95ee\u5176\u4ed6\u5df2\u77e5\u96c6\u7fa4ID\u7684\u7528\u6237\u7684\u914d\u7f6e\u4fe1\u606f\u3002",
  "discovererName": "unknown",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2019-17471",
  "openTime": "2019-06-14",
  "patchDescription": "Elastic Cloud Enterprise (ECE) \u662f\u8377\u5170Elasticsearch\u516c\u53f8\u7684\u4e00\u5957\u7528\u4e8e\u7ba1\u7406\u3001\u76d1\u63a7\u548c\u914d\u7f6eElasticsearch\u3001Kibana\u548cX-Pack\u7684\u8f6f\u4ef6\u5305\u3002\r\n\r\nElastic Cloud Enterprise (ECE) \u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u76f4\u63a5\u8fde\u63a5ZooKeeper\uff0c\u5229\u7528\u8be5\u6f0f\u6d1e\u8bbf\u95ee\u5176\u4ed6\u5df2\u77e5\u96c6\u7fa4ID\u7684\u7528\u6237\u7684\u914d\u7f6e\u4fe1\u606f\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": "Elastic Cloud Enterprise (ECE) \u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-17471\uff09\u7684\u8865\u4e01",
  "products": {
    "product": "ElasticSearch Elastic Cloud Enterprise (ECE) \u003c1.1.4"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2018-3825",
  "serverity": "\u4e2d",
  "submitTime": "2018-09-21",
  "title": "Elastic Cloud Enterprise (ECE) \u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-17471\uff09"
}

CVE-2018-3825 (GCVE-0-2018-3825)

Vulnerability from cvelistv5 – Published: 2018-09-19 19:00 – Updated: 2024-08-05 04:57

Summary

In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 a default master encryption key is used in the process of granting ZooKeeper access to Elasticsearch clusters. Unless explicitly overwritten, this master key is predictable across all ECE deployments. If an attacker can connect to ZooKeeper directly they would be able to access configuration information of other tenants if their cluster ID is known.

Severity

No CVSS data available.

CWE

CWE-321 - Use of Hard-coded Cryptographic Key

Assigner

elastic mitre root

References

2 references

URL	Tags
https://www.elastic.co/community/security	x_refsource_CONFIRM
https://discuss.elastic.co/t/elastic-cloud-enterp…	x_refsource_CONFIRM

Impacted products

1 product

Vendor	Product	Version
Elastic	Elastic Cloud Enterprise (ECE)	Affected: before 1.1.4

Date Public

2018-06-13 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T04:57:24.044Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://www.elastic.co/community/security"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Elastic Cloud Enterprise (ECE)",
          "vendor": "Elastic",
          "versions": [
            {
              "status": "affected",
              "version": "before 1.1.4"
            }
          ]
        }
      ],
      "datePublic": "2018-06-13T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 a default master encryption key is used in the process of granting ZooKeeper access to Elasticsearch clusters. Unless explicitly overwritten, this master key is predictable across all ECE deployments. If an attacker can connect to ZooKeeper directly they would be able to access configuration information of other tenants if their cluster ID is known."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-321",
              "description": "CWE-321: Use of Hard-coded Cryptographic Key",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2018-09-19T18:57:01.000Z",
        "orgId": "271b6943-45a9-4f3a-ab4e-976f3fa05b5a",
        "shortName": "elastic"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://www.elastic.co/community/security"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security@elastic.co",
          "ID": "CVE-2018-3825",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Elastic Cloud Enterprise (ECE)",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "before 1.1.4"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Elastic"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 a default master encryption key is used in the process of granting ZooKeeper access to Elasticsearch clusters. Unless explicitly overwritten, this master key is predictable across all ECE deployments. If an attacker can connect to ZooKeeper directly they would be able to access configuration information of other tenants if their cluster ID is known."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "CWE-321: Use of Hard-coded Cryptographic Key"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://www.elastic.co/community/security",
              "refsource": "CONFIRM",
              "url": "https://www.elastic.co/community/security"
            },
            {
              "name": "https://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778",
              "refsource": "CONFIRM",
              "url": "https://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "271b6943-45a9-4f3a-ab4e-976f3fa05b5a",
    "assignerShortName": "elastic",
    "cveId": "CVE-2018-3825",
    "datePublished": "2018-09-19T19:00:00.000Z",
    "dateReserved": "2018-01-02T00:00:00.000Z",
    "dateUpdated": "2024-08-05T04:57:24.044Z",
    "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.

Detection rules are retrieved from Rulezet.

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.