CVE-2023-5077 | Vault's Google Cloud Secrets Engine Removed Existing IAM Conditions When Creating / Updating Rolesets

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.

Published: 2023-09-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5077 is rated Moderate Risk (42.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.44%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-5077

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.21% 0.44% +0.23%
2 2025-12-28 0.13% 0.21% +0.08%
3 2025-12-27 — 0.13% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5077

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.6 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 6.0 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-5077

GitHub Security Advisory for CVE-2023-5077

GHSA-86c6-3g63-5w64 · Severity: high · Ecosystem: go — Hashicorp Vault Incorrect Permission Assignment for Critical Resource vulnerability

OS Trackers for CVE-2023-5077

vendor priority summary link
alpine high CVE-2023-5077: 1 source package rows (vault); 10 state rows across 1 repos (edge-community); fixed 1, open 9. https://security.alpinelinux.org/vuln/CVE-2023-5077
redhat medium — https://access.redhat.com/security/cve/CVE-2023-5077

Affected software / configurations for CVE-2023-5077

Vendor Product Version Raw CPE
hashicorp vault >= 0.10.0, < 1.13.0 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 0.10.0, < 1.13.0 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

References for CVE-2023-5077

cvelogic Threat Intelligence