Skip to content
Fencer Intel
low 2.9

CVE-2021-41802 json

Hashicorp Vault Privilege Escalation Vulnerability

published 5y ago modified last mo. also BIT-vault-2021-41802 , EUVD-2021-2251 , GHSA-qv95-g3gm-x542 , GO-2022-0618

cvss
2.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

HashiCorp Vault and Vault Enterprise through 1.7.4 and 1.8.3 allowed a user with write permission to an entity alias ID sharing a mount accessor with another user to acquire this other user’s policies by merging their identities. Fixed in Vault and Vault Enterprise 1.7.5 and 1.8.4.

Patch / fix

  • go github.com/hashicorp/vault 1.7.5, 1.8.4
  • bitnami vault 1.7.5, 1.8.4
  • hashicorp vault 1.7.5, 1.8.4
  • vault Arch Linux 1.9.0-1

arch linux advisories AVG-2294

Is CVE-2021-41802 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-41802 updated cvss 5.4

vault: Incorrect Permission Assignment for Critical Resource

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-loki-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-installer, openshift4/topology-aware-lifecycle-manager-rhel8-operator Red Hat Openshift Container Storage 4 ocs4/cephcsi-rhel8, ocs4/mcg-rhel8-operator, ocs4/ocs-rhel8-operator, ocs4/rook-ceph-rhel8-operator Red Hat Openshift Data Foundation 4 vault, odf4/cephcsi-rhel9, odf4/mcg-rhel9-operator, odf4/ocs-rhel9-operator, odf4/odf-rhel8-operator, odf4/odr-rhel8-operator, +2 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 2.9 CVSS:3.1/AC:L/AV:A/A:N/C:L/I:N/PR:H/S:C/UI:R
GitHub 3.1 2.9 CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:N/A:N
CNA 3.1 2.9 CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:N/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
<1.7.5
>=1.8.0, <1.8.4
1.7.5
1.8.4
bitnami vault
<1.7.5
>=1.8.0, <1.8.4
1.7.5
1.8.4

Classification

Weakness
  • CWE-269 Improper Privilege Management
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.