ghsa-f9ch-h8j7-8jwg
Vulnerability from github
Published
2025-05-02 18:31
Modified
2025-05-06 19:12
Severity ?
Summary
Hashicorp Vault Community vulnerable to Incorrect Authorization
Details
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": [ { "package": { "ecosystem": "Go", "name": "github.com/hashicorp/vault" }, "ranges": [ { "events": [ { "introduced": "1.10.0" }, { "fixed": "1.19.1" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-3879" ], "database_specific": { "cwe_ids": [ "CWE-863" ], "github_reviewed": true, "github_reviewed_at": "2025-05-02T19:32:37Z", "nvd_published_at": "2025-05-02T17:15:51Z", "severity": "MODERATE" }, "details": "Vault Community, Vault Enterprise (\u201cVault\u201d) 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.", "id": "GHSA-f9ch-h8j7-8jwg", "modified": "2025-05-06T19:12:49Z", "published": "2025-05-02T18:31:38Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3879" }, { "type": "WEB", "url": "https://discuss.hashicorp.com/t/hcsec-2025-07-vault-s-azure-authentication-method-bound-location-restriction-could-be-bypassed-on-login/74716" }, { "type": "PACKAGE", "url": "https://github.com/hashicorp/vault" }, { "type": "WEB", "url": "https://pkg.go.dev/vuln/GO-2025-3662" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ], "summary": "Hashicorp Vault Community vulnerable to Incorrect Authorization" }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.