Skip to content

← Actionable
Low, CVSS 3.2

Sensitive Terraform Output Values Printed At Info Logging Level In Kitchen-Terraform

CVE-2023-30618GHSA-65g2-x53q-cmf6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (kitchen-terraform 7.0.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.2 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N
EPSS
  • CVE-2023-30618: 0.21% estimated exploitation activity in the next 30 days; percentile 11.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Kitchen-Terraform v7.0.0 introduced a regression which caused all Terraform output values, including sensitive values, to be printed at the info logging level during the kitchen converge action. Prior to v7.0.0, the output values were printed at the debug level to avoid writing sensitive values to the terminal by default. Original Report @brettcurtis: Hopefully, I'm not doing something stupid here, but I'm seeing sensitive outputs printed in the kitchen output. You can check this action for an example: https://github.com/osinfra-io/terraform-google-project/actions/runs/4700065515/jobs/8334277309#step:5:215 It's not really a sensitive value just used it as an example.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-65g2-x53q-cmf6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-30618

Advisory: Sensitive Terraform Output Values Printed At Info Logging Level In Kitchen-Terraform
IDs: CVE-2023-30618, GHSA-65g2-x53q-cmf6
Record: https://patchnext.com/advisories/cve-2023-30618 (revision 1, source checked 26 Oct 2026, 15:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: kitchen-terraform 7.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems kitchen-terraform: affected >= 7.0.0, < 7.0.1; fixed in 7.0.1

## Suggested inspection (read-only)
- RubyGems kitchen-terraform: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on kitchen-terraform.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-65g2-x53q-cmf6 (GitHub-reviewed advisory GHSA-65g2-x53q-cmf6 lists affected ranges: RubyGems kitchen-terraform >=7.0.0 <7.0.1)

Commands are suggestions: review each one before running it.

Loading voting…