GHSA-f9ch-h8j7-8jwg
First published: Fri May 02 2025(Updated: )
Vault Community, Vault Enterprise (“Vault”) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| go/github.com/hashicorp/vault | >=1.10.0<1.19.1 | 1.19.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of GHSA-f9ch-h8j7-8jwg?
The severity of GHSA-f9ch-h8j7-8jwg is currently classified as critical due to the potential for authentication bypass.
How do I fix GHSA-f9ch-h8j7-8jwg?
To fix GHSA-f9ch-h8j7-8jwg, upgrade to Vault Community Edition 1.19.1 or Vault Enterprise 1.19.1, 1.18.7, 1.17.14, or 1.16.18.
What does GHSA-f9ch-h8j7-8jwg affect?
GHSA-f9ch-h8j7-8jwg affects the Azure authentication method in Vault, allowing a bypass of location restrictions.
What are the implications of GHSA-f9ch-h8j7-8jwg?
The implications of GHSA-f9ch-h8j7-8jwg include unauthorized access to systems if the vulnerability is exploited.
When was GHSA-f9ch-h8j7-8jwg disclosed?
GHSA-f9ch-h8j7-8jwg was disclosed as part of a security advisory related to Vault's authentication method.
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-f9ch-h8j7-8jwg
- alias/CVE-2025-3879
- agent/software-canonical-lookup
- agent/references
- agent/source
- agent/weakness
- agent/last-modified-date
- agent/tags
- agent/softwarecombine
- agent/first-publish-date
- agent/description
- agent/type
- agent/severity
- agent/event
- package-manager/go