CVE-2023-5077
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Vault Google Cloud secrets engine failed to preserve existing Google Cloud IAM Conditions when creating or updating rolesets. This meant that whenever an administrator modified a roleset (whether creating new ones or updating existing), any IAM conditions previously attached to that roleset in GCP were silently discarded, potentially weakening access controls without administrator awareness.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.10.0, < 1.13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Vault versionRun `vault version` or check the Vault server logs at startup to identify the exact version numberAffected if The version is >= 0.10.0 and < 1.13.0, placing it within the affected range
-
Determine if the Google Cloud secrets engine is enabledRun `vault secrets list` and look for a path with type 'gcp' or 'gcpkms'Affected if The Google Cloud secrets engine is enabled and in use
-
Identify existing GCP rolesetsRun `vault list gcp/rolesets` (or the appropriate path based on your engine mount point) to list all configured rolesetsAffected if Any rolesets exist, indicating the engine was used to manage GCP access
-
Check for roleset modification timestampsUse Vault audit logs or run `vault read gcp/roleset/<name>` for each roleset to review configuration history or timestamps of creation/updatesAffected if Rolesets were created or updated at any point while using an affected Vault version (>= 0.10.0, < 1.13.0)
-
Inspect GCP IAM rolesets for missing conditionsIn the Google Cloud Console or via `gcloud iam rolesets list` or `gcloud iam rolesets get-iam-policy`, examine each roleset to verify whether IAM conditions are attachedAffected if Any roleset lacks an IAM condition that was expected to be present, or you cannot account for the condition state since the roleset was created or modified
Your environment is affected if you run a vulnerable Vault version (>= 0.10.0, < 1.13.0) with the GCP secrets engine enabled and have created or updated any rolesets, as IAM conditions on those GCP rolesets may have been silently lost.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.13.0
Upgrade to Vault 1.13.0 or later to fix this issue. Organizations should audit their GCP IAM rolesets after upgrading to identify and reapply any IAM conditions that may have been inadvertently lost during previous roleset modifications.
Vault 1.13.0
- Review the Vault upgrade documentation and ensure your current version is compatible with upgrading to 1.13.0
- Perform a backup of your Vault data and configuration
- Upgrade Vault to version 1.13.0 or later
- After upgrading, verify that the Google Cloud secrets engine correctly preserves IAM Conditions when creating or updating rolesets
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5077 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data