Action not permitted
Modal body text goes here.
ghsa-gqvf-892r-vjm5
Vulnerability from github
Published
2021-04-13 15:42
Modified
2023-07-05 19:26
Severity
Summary
Improper Certificate Validation in Puppet
Details
Previously, Puppet operated on the 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 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": [ { "package": { "ecosystem": "RubyGems", "name": "puppet" }, "ranges": [ { "events": [ { "introduced": "6.0.0" }, { "fixed": "6.13.0" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "RubyGems", "name": "puppet" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "5.5.19" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2020-7942" ], "database_specific": { "cwe_ids": [ "CWE-295" ], "github_reviewed": true, "github_reviewed_at": "2021-04-07T23:15:22Z", "nvd_published_at": "2020-02-19T21:15:00Z", "severity": "MODERATE" }, "details": "Previously, Puppet operated on the 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 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.", "id": "GHSA-gqvf-892r-vjm5", "modified": "2023-07-05T19:26:32Z", "published": "2021-04-13T15:42:19Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-7942" }, { "type": "WEB", "url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/puppet/CVE-2020-7942.yml" }, { "type": "WEB", "url": "https://puppet.com/security/cve/CVE-2020-7942" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ], "summary": "Improper Certificate Validation in Puppet" }
gsd-2020-7942
Vulnerability from gsd
Modified
2021-04-13 00:00
Details
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 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.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2020-7942", "description": "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", "id": "GSD-2020-7942", "references": [ "https://www.suse.com/security/cve/CVE-2020-7942.html", "https://access.redhat.com/errata/RHSA-2020:4366" ] }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "affected": [ { "package": { "ecosystem": "RubyGems", "name": "puppet", "purl": "pkg:gem/puppet" } } ], "aliases": [ "CVE-2020-7942", "GHSA-gqvf-892r-vjm5" ], "details": "Previously, Puppet operated on a model that a node with a valid certificate\nwas entitled to all information in the system and that a compromised certificate\nallowed access to everything in the infrastructure. When a node\u0027s catalog falls\nback to the `default` node, the catalog can be retrieved for a different node by\nmodifying facts for the Puppet run. This issue can be mitigated by setting\n`strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet\n6.13.0 changes the default behavior for strict_hostname_checking from false to\ntrue. It is recommended that Puppet Open Source and Puppet Enterprise users that\nare not upgrading still set `strict_hostname_checking` to `true` to ensure secure\nbehavior.\n", "id": "GSD-2020-7942", "modified": "2021-04-13T00:00:00.000Z", "published": "2021-04-13T00:00:00.000Z", "references": [ { "type": "WEB", "url": "https://puppet.com/security/cve/CVE-2020-7942/" } ], "schema_version": "1.4.0", "severity": [ { "score": 6.5, "type": "CVSS_V3" } ], "summary": "Improper Certificate Validation in Puppet" } }, "namespaces": { "cve.org": { "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/" } ] } }, "github.com/rubysec/ruby-advisory-db": { "cve": "2020-7942", "cvss_v3": 6.5, "date": "2021-04-13", "description": "Previously, Puppet operated on a model that a node with a valid certificate\nwas entitled to all information in the system and that a compromised certificate\nallowed access to everything in the infrastructure. When a node\u0027s catalog falls\nback to the `default` node, the catalog can be retrieved for a different node by\nmodifying facts for the Puppet run. This issue can be mitigated by setting\n`strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet\n6.13.0 changes the default behavior for strict_hostname_checking from false to\ntrue. It is recommended that Puppet Open Source and Puppet Enterprise users that\nare not upgrading still set `strict_hostname_checking` to `true` to ensure secure\nbehavior.\n", "gem": "puppet", "ghsa": "gqvf-892r-vjm5", "patched_versions": [ "~\u003e 5.5.19", "\u003e= 6.13.0" ], "title": "Improper Certificate Validation in Puppet", "url": "https://puppet.com/security/cve/CVE-2020-7942/" }, "gitlab.com": { "advisories": [ { "affected_range": "\u003e=6.0.0 \u003c6.13.0", "affected_versions": "All versions starting from 6.0.0 before 6.13.0", "cvss_v2": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "cwe_ids": [ "CWE-1035", "CWE-295", "CWE-937" ], "date": "2020-04-02", "description": "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 changes the default behavior for strict_hostname_checking from false to true.", "fixed_versions": [ "6.13.0" ], "identifier": "CVE-2020-7942", "identifiers": [ "CVE-2020-7942" ], "not_impacted": "All versions before 6.0.0, all versions starting from 6.13.0", "package_slug": "gem/puppet", "pubdate": "2020-02-19", "solution": "Upgrade to version 6.13.0 or above.", "title": "Improper Certificate Validation", "urls": [ "https://nvd.nist.gov/vuln/detail/CVE-2020-7942", "https://puppet.com/security/cve/CVE-2020-7942/" ], "uuid": "d592d279-26bc-4b0a-93a9-c4f746912b9a" } ] }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "5.5.19", "versionStartIncluding": "5.5.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "6.13.0", "versionStartIncluding": "6.0.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "5.5.19", "versionStartIncluding": "5.5.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "6.13.0", "versionStartIncluding": "6.0.0", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security@puppet.com", "ID": "CVE-2020-7942" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "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" } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-295" } ] } ] }, "references": { "reference_data": [ { "name": "https://puppet.com/security/cve/CVE-2020-7942/", "refsource": "CONFIRM", "tags": [ "Vendor Advisory" ], "url": "https://puppet.com/security/cve/CVE-2020-7942/" } ] } }, "impact": { "baseMetricV2": { "acInsufInfo": false, "cvssV2": { "accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "SINGLE", "availabilityImpact": "NONE", "baseScore": 4.0, "confidentialityImpact": "PARTIAL", "integrityImpact": "NONE", "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "version": "2.0" }, "exploitabilityScore": 8.0, "impactScore": 2.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "severity": "MEDIUM", "userInteractionRequired": false }, "baseMetricV3": { "cvssV3": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1" }, "exploitabilityScore": 2.8, "impactScore": 3.6 } }, "lastModifiedDate": "2021-12-30T13:33Z", "publishedDate": "2020-02-19T21:15Z" } } }
cve-2020-7942
Vulnerability from cvelistv5
Published
2020-02-19 20:52
Modified
2024-08-04 09:48
Severity
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
References
URL | Tags |
---|---|
https://puppet.com/security/cve/CVE-2020-7942/ | x_refsource_CONFIRM |
Impacted products
Vendor | Product |
---|---|
Puppet | Puppet |
Puppet | Puppet Agent |
{ "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", "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", "dateReserved": "2020-01-23T00:00:00", "dateUpdated": "2024-08-04T09:48:24.553Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1" }
Loading...