HashiCorp Vault vulnerable to incorrect metadata access in github.com/hashicorp/vault
Research is free — Hunters explains how the bug works, the root-cause code pattern, how the fix addresses it, and how to test whether a target is affected, in chat. Investigate & write exploit is a paid run — the engine reads the advisory and fix commits, then builds and validates a working proof-of-concept exploit with reproduction steps.
Affected versions
1.8.0 → fixed in 1.9.91.10.0 → fixed in 1.10.61.11.0 → fixed in 1.11.3
Details
HashiCorp Vault vulnerable to incorrect metadata access in github.com/hashicorp/vault
The fix
No fix commit could be resolved for this advisory (it may reference an issue tracker or a non-GitHub patch). See the references below.
References
- ADVISORYhttps://github.com/advisories/GHSA-7cgv-v83v-rr87
- ADVISORYhttps://nvd.nist.gov/vuln/detail/CVE-2022-40186
- WEBhttps://discuss.hashicorp.com
- WEBhttps://discuss.hashicorp.com/t/hcsec-2022-18-vault-entity-alias-metadata-may-leak-between-aliases-with-the-same-name-assigned-to-the-same-entity/44550
- WEBhttps://github.com/hashicorp/vault
- WEBhttps://security.netapp.com/advisory/ntap-20221111-0008