CVE-2020-7944
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Continuous Delivery for Puppet Enterprise (CD4PE) before 3.4.0, changes to resources or classes containing Sensitive parameters can result in the Sensitive parameters ending up in the impact analysis report.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Continuous Delivery for Puppet Enterprise (CD4PE) before 3.4.0, Puppet Sensitive parameter values (designed to mask secrets, passwords, and other credentials) are improperly exposed in impact analysis reports when changes are made to resources or classes containing those Sensitive parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CD4PE versionAccess the CD4PE web UI or check the version through the Puppet Enterprise console. Navigate to the Continuous Delivery section and locate the version information typically displayed in the settings or about page.Affected if The installed version is earlier than 3.4.0 (for example, 3.3.0, 3.2.0, etc.)
-
Verify impact analysis functionality is in useCheck if the CD4PE pipeline or deployment workflow includes impact analysis steps. Review the pipeline configuration to confirm impact analysis reports are being generated as part of the change workflow.Affected if Impact analysis reports are configured and executed as part of the CD4PE workflow
-
Inspect impact analysis reports for Sensitive data exposureGenerate or retrieve an impact analysis report from a recent pipeline run that involved changes to resources or classes containing Sensitive parameters. Manually review the report output to check whether any parameter values that should be marked as Sensitive are displayed in plain text rather than being masked.Affected if Any Puppet Sensitive parameter values appear unmasked or in plain text within the impact analysis report output
A user is affected if CD4PE version is earlier than 3.4.0 AND impact analysis reports are being used, with Sensitive parameter values appearing exposed in plain text in those reports.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.4.0
Upgrade CD4PE to version 3.4.0 or later to prevent Sensitive parameter values from appearing in impact analysis reports.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7944 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data