Skip to content

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

Low severity GitHub Reviewed Published Apr 21, 2023 in newcontext-oss/kitchen-terraform • Updated Nov 6, 2023

Package

bundler kitchen-terraform (RubyGems)

Affected versions

>= 7.0.0, < 7.0.1

Patched versions

7.0.1

Description

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.

References

@aaron-lane aaron-lane published to newcontext-oss/kitchen-terraform Apr 21, 2023
Published by the National Vulnerability Database Apr 21, 2023
Published to the GitHub Advisory Database Apr 24, 2023
Reviewed Apr 24, 2023
Last updated Nov 6, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2023-30618

GHSA ID

GHSA-65g2-x53q-cmf6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.