CVE-2018-11747

Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. In version 1.4.0, a unique certificate will be generated on installation or the user will be able to provide their own TLS certificate for ingress.
Configurations

Configuration 1 (hide)

cpe:2.3:a:puppet:discovery:*:*:*:*:*:*:*:*

History

21 Nov 2024, 03:43

Type Values Removed Values Added
References () https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E - () https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E -
References () https://puppet.com/security/cve/CVE-2018-11747 - Vendor Advisory () https://puppet.com/security/cve/CVE-2018-11747 - Vendor Advisory

Information

Published : 2019-03-21 16:00

Updated : 2024-11-21 03:43


NVD link : CVE-2018-11747

Mitre link : CVE-2018-11747

CVE.ORG link : CVE-2018-11747


JSON object : View

Products Affected

puppet

  • discovery
CWE
CWE-295

Improper Certificate Validation