LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2394: Sensitive Parameter Exposure in Puppet Bolt prior to 3.24

Puppet Bolt prior to version 3.24.0 will print sensitive parameters when planning a run resulting in them potentially being logged when run programmatically, such as via Puppet Enterprise.

MediumCVSS 4.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Puppet Bolt could expose secrets by printing sensitive plan parameters. If Bolt runs are automated or routed through Puppet Enterprise, those values may be captured in logs. The main business risk is limited confidentiality loss, especially where logs are widely retained, forwarded, or accessible to operators.

Executive priority

Treat as a targeted remediation item, not an emergency. Prioritize teams using Bolt with secrets in automated runs or centralized logs, because remediation is straightforward but historical log exposure may require secret rotation.

Technical view

CVE-2022-2394 is a CWE-200 information exposure issue in Puppet Bolt before 3.24.0. During plan execution, sensitive parameters could be printed and potentially logged when runs are performed programmatically, including through Puppet Enterprise. CVSS 3.1 is 4.1: network attack vector, low complexity, low privileges, user interaction required, changed scope, low confidentiality impact.

Likely exposure

Exposure is most likely where Puppet Bolt versions before 3.24.0 are used for plans containing secrets, tokens, passwords, or sensitive parameters, especially in automated pipelines, Puppet Enterprise workflows, or centralized logging environments.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Abuse would depend on access to run output or logs containing printed sensitive parameters, not on remote code execution or service disruption.

Researcher notes

The source bundle identifies information exposure only. It does not provide exploit details, observed attacks, or broader affected products beyond Puppet Bolt before 3.24.0. Validation should focus on version checks, sensitive parameter handling, and log exposure paths.

Mitigation direction

  • Identify Puppet Bolt deployments and confirm whether versions are before 3.24.0.
  • Upgrade affected Bolt installations to 3.24.0 or follow current Puppet vendor guidance.
  • Review automated Puppet Enterprise or CI runs for sensitive plan parameters.
  • Restrict access to Bolt, Puppet Enterprise, CI, and log aggregation outputs.
  • Rotate secrets confirmed to have appeared in logs.

Validation and detection

  • Inventory installed Puppet Bolt versions across workstations, automation hosts, and Puppet Enterprise integrations.
  • Search relevant logs for sensitive plan parameter names or known secret values.
  • Review plan definitions for parameters intended to remain confidential.
  • Confirm post-upgrade runs no longer print sensitive parameter values.
  • Check log retention and forwarding paths for historical exposure.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2394 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N2.31.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.1Medium
CVSS 3.1 vector shape for CVE-2022-2394Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PuppetBolt3.24.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.