Skip to content

Vault GitHub Action did not correctly mask multi-line secrets in output

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Jan 25, 2024

Package

actions hashicorp/vault-action (GitHub Actions)

Affected versions

< 2.2.0

Patched versions

2.2.0

Description

HashiCorp vault-action (aka Vault GitHub Action) before 2.2.0 allows attackers to obtain sensitive information from log files because a multi-line secret was not correctly registered with GitHub Actions for log masking.

The vault-action implementation did not correctly handle the marking of multi-line variables. As a result, multi-line secrets were not correctly masked in vault-action output.

Remediation:
Customers using vault-action should evaluate the risk associated with this issue, and consider upgrading to vault-action 2.2.0 or newer. Please refer to https://github.com/marketplace/actions/hashicorp-vault for more information.

References

Published by the National Vulnerability Database May 7, 2021
Published to the GitHub Advisory Database May 24, 2022
Reviewed Jul 29, 2022
Last updated Jan 25, 2024

Severity

High

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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
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:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.176%
(56th percentile)

Weaknesses

CVE ID

CVE-2021-32074

GHSA ID

GHSA-4mgv-m5cm-f9h7

Source code

Credits

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