Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp VaultGHSA-fp52-qw33-mfmw
HIGHGHSA-fp52-qw33-mfmw is a high-severity (CVSS 8.2) CWE-290 vulnerability in github.com/hashicorp/vault. A fix is available for github.com/hashicorp/vault — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-fp52-qw33-mfmw by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/hashicorp/vault🐹github.com/hashicorp/vault🐹github.com/hashicorp/vault🐹github.com/hashicorp/vaultReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
HashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1..
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hashicorp/vault | ≥ 0.8.1&&< 1.2.5 | 1.2.5go get github.com/hashicorp/vault@v1.2.5 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.3.0&&< 1.3.8 | 1.3.8go get github.com/hashicorp/vault@v1.3.8 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.4.0&&< 1.4.4 | 1.4.4go get github.com/hashicorp/vault@v1.4.4 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.5.0&&< 1.5.1 | 1.5.1go get github.com/hashicorp/vault@v1.5.1 |
Affected Products
vaulthashicorpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/vault, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hashicorp/vault to 1.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fp52-qw33-mfmw is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.13 | openshift4/topology-aware-lifecycle-manager-rhel8-operator:v4.13.1-6 | RHSA-2023:3342 |
| RHODF-4.13-RHEL-9 | odf4/odf-rhel9-operator:v4.13.0-24 | RHSA-2023:3742 |
Frequently Asked Questions
Is GHSA-fp52-qw33-mfmw in your dependencies?
Find it across Go, including transitive dependencies.