title: Vault's Google Cloud Secrets Engine Removed Existing IAM Conditions When Creating / Updating Rolesets
description: The Vault and Vault Enterprise ("Vault") Google Cloud secrets engine did not preserve existing Google Cloud IAM Conditions upon creating or updating rolesets. Fixed in Vault 1.13.0.
problem types: CWE-732: Incorrect Permission Assignment for Critical Resource
affected:
{
vendor: HashiCorp
product: Vault
platforms: [Windows, MacOS, Linux, x86, ARM, 64 bit, 32 bit]
versions:
lessThan: 1.13.0, status: affected, version: 0.10.0, versionType: semver
defaultStatus: unaffected
}
{
vendor: HashiCorp
product: Vault Enterprise
platforms: [Windows, MacOS, Linux, x86, ARM, 64 bit, 32 bit]
versions:
lessThan: 1.13.0, status: affected, version: 0.10.0, versionType: semver
defaultStatus: unaffected
}
metrics:
format: CVSS
scenarios: GENERAL
cvssV3_1: [
version: 3.1
attackVector: NETWORK
attackComplexity: HIGH
privilegesRequired: HIGH
userInteraction: REQUIRED
scope: CHANGED
confidentialityImpact: HIGH
integrityImpact: HIGH
availabilityImpact: HIGH
baseSeverity: HIGH
baseScore: 7.6
vectorString: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
]