Vulnerability-Lookup

CNVD-2020-33730

Vulnerability from cnvd - Published: 2020-06-20

Title

Puppet信任管理问题漏洞

Description

Puppet是美国Puppet实验室的一套基于客户端/服务器（C/S）架构的配置管理工具，它可用于管理配置文件、用户、cron任务、软件包、系统服务等。Puppet Agent是一个Puppet代理端程序。 Puppet中存在信任管理问题漏洞，该漏洞源于错误的证书验证。远程攻击者可利用该漏洞获取敏感信息。

Severity

中

Patch Name

Puppet信任管理问题漏洞的补丁

Patch Description

Formal description

厂商已发布了漏洞修复程序，请及时关注更新: https://puppet.com/security/cve/CVE-2020-7942/

Reference

https://nvd.nist.gov/vuln/detail/CVE-2020-7942

Impacted products

Name
['Puppet Puppet 6.，<6.13.0', 'Puppet Puppet 5.5.，<5.5.19', 'Puppet Agent 6.，<6.13.0', 'Puppet Agent 5.5.，<5.5.19']

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2020-7942",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2020-7942"
    }
  },
  "description": "Puppet\u662f\u7f8e\u56fdPuppet\u5b9e\u9a8c\u5ba4\u7684\u4e00\u5957\u57fa\u4e8e\u5ba2\u6237\u7aef/\u670d\u52a1\u5668\uff08C/S\uff09\u67b6\u6784\u7684\u914d\u7f6e\u7ba1\u7406\u5de5\u5177\uff0c\u5b83\u53ef\u7528\u4e8e\u7ba1\u7406\u914d\u7f6e\u6587\u4ef6\u3001\u7528\u6237\u3001cron\u4efb\u52a1\u3001\u8f6f\u4ef6\u5305\u3001\u7cfb\u7edf\u670d\u52a1\u7b49\u3002Puppet Agent\u662f\u4e00\u4e2aPuppet\u4ee3\u7406\u7aef\u7a0b\u5e8f\u3002\n\nPuppet\u4e2d\u5b58\u5728\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u9519\u8bef\u7684\u8bc1\u4e66\u9a8c\u8bc1\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u83b7\u53d6\u654f\u611f\u4fe1\u606f\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0:\r\nhttps://puppet.com/security/cve/CVE-2020-7942/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-33730",
  "openTime": "2020-06-20",
  "patchDescription": "Puppet\u662f\u7f8e\u56fdPuppet\u5b9e\u9a8c\u5ba4\u7684\u4e00\u5957\u57fa\u4e8e\u5ba2\u6237\u7aef/\u670d\u52a1\u5668\uff08C/S\uff09\u67b6\u6784\u7684\u914d\u7f6e\u7ba1\u7406\u5de5\u5177\uff0c\u5b83\u53ef\u7528\u4e8e\u7ba1\u7406\u914d\u7f6e\u6587\u4ef6\u3001\u7528\u6237\u3001cron\u4efb\u52a1\u3001\u8f6f\u4ef6\u5305\u3001\u7cfb\u7edf\u670d\u52a1\u7b49\u3002Puppet Agent\u662f\u4e00\u4e2aPuppet\u4ee3\u7406\u7aef\u7a0b\u5e8f\u3002\r\n\r\nPuppet\u4e2d\u5b58\u5728\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u9519\u8bef\u7684\u8bc1\u4e66\u9a8c\u8bc1\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u83b7\u53d6\u654f\u611f\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": "Puppet\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Puppet   Puppet 6.*\uff0c\u003c6.13.0",
      "Puppet   Puppet 5.5.*\uff0c\u003c5.5.19",
      "Puppet   Agent 6.*\uff0c\u003c6.13.0",
      "Puppet   Agent 5.5.*\uff0c\u003c5.5.19"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2020-7942",
  "serverity": "\u4e2d",
  "submitTime": "2020-03-09",
  "title": "Puppet\u4fe1\u4efb\u7ba1\u7406\u95ee\u9898\u6f0f\u6d1e"
}

CVE-2020-7942 (GCVE-0-2020-7942)

Vulnerability from cvelistv5 – Published: 2020-02-19 20:52 – Updated: 2024-08-04 09:48

Summary

Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19

Severity

No CVSS data available.

CWE

Arbitrary retrieval

Assigner

puppet

References

1 reference

URL	Tags
https://puppet.com/security/cve/CVE-2020-7942/	x_refsource_CONFIRM

Impacted products

2 products

Vendor	Product	Version
Puppet	Puppet	Affected: 5.5.x prior to 5.5.19 Affected: Fixed in 5.5.19 Affected: 6.x prior to 6.13.0 Affected: Fixed in 6.13.0
Puppet	Puppet Agent	Affected: 5.5.x prior to 5.5.19 Affected: Fixed in 5.5.19 Affected: 6.x prior to 6.13.0 Affected: Fixed in 6.13.0

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T09:48:24.553Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://puppet.com/security/cve/CVE-2020-7942/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Puppet",
          "vendor": "Puppet",
          "versions": [
            {
              "status": "affected",
              "version": "5.5.x prior to 5.5.19"
            },
            {
              "status": "affected",
              "version": "Fixed in 5.5.19"
            },
            {
              "status": "affected",
              "version": "6.x prior to 6.13.0"
            },
            {
              "status": "affected",
              "version": "Fixed in 6.13.0"
            }
          ]
        },
        {
          "product": "Puppet Agent",
          "vendor": "Puppet",
          "versions": [
            {
              "status": "affected",
              "version": "5.5.x prior to 5.5.19"
            },
            {
              "status": "affected",
              "version": "Fixed in 5.5.19"
            },
            {
              "status": "affected",
              "version": "6.x prior to 6.13.0"
            },
            {
              "status": "affected",
              "version": "Fixed in 6.13.0"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node\u0027s catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "Arbitrary retrieval",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2020-04-02T19:00:07.000Z",
        "orgId": "ca2a266c-be2f-4d4b-92d0-47b76b1a9c4e",
        "shortName": "puppet"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://puppet.com/security/cve/CVE-2020-7942/"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security@puppet.com",
          "ID": "CVE-2020-7942",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Puppet",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "5.5.x prior to 5.5.19"
                          },
                          {
                            "version_value": "Fixed in 5.5.19"
                          },
                          {
                            "version_value": "6.x prior to 6.13.0"
                          },
                          {
                            "version_value": "Fixed in 6.13.0"
                          }
                        ]
                      }
                    },
                    {
                      "product_name": "Puppet Agent",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "5.5.x prior to 5.5.19"
                          },
                          {
                            "version_value": "Fixed in 5.5.19"
                          },
                          {
                            "version_value": "6.x prior to 6.13.0"
                          },
                          {
                            "version_value": "Fixed in 6.13.0"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Puppet"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node\u0027s catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19"
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Arbitrary retrieval"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://puppet.com/security/cve/CVE-2020-7942/",
              "refsource": "CONFIRM",
              "url": "https://puppet.com/security/cve/CVE-2020-7942/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ca2a266c-be2f-4d4b-92d0-47b76b1a9c4e",
    "assignerShortName": "puppet",
    "cveId": "CVE-2020-7942",
    "datePublished": "2020-02-19T20:52:03.000Z",
    "dateReserved": "2020-01-23T00:00:00.000Z",
    "dateUpdated": "2024-08-04T09:48:24.553Z",
    "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.

Action not permitted

CNVD-2020-33730

CVE-2020-7942 (GCVE-0-2020-7942)

Tags

Sightings

Nomenclature

Related by attack behaviour