Skip to content
Fencer Intel
medium 5.3

CVE-2022-30689 json

HashiCorp Vault improper configuration of multi factor authentication

published 4y ago modified 2mo ago also BIT-vault-2022-30689 , EUVD-2022-3515 , GHSA-c5wc-v287-82pc , GO-2022-0590

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

HashiCorp Vault and Vault Enterprise from 1.10.0 to 1.10.2 did not correctly configure and enforce MFA on login after server restarts. This affects the Login MFA feature introduced in Vault and Vault Enterprise 1.10.0 and does not affect the separate Enterprise MFA feature set. Fixed in 1.10.3.

Patch / fix

  • go github.com/hashicorp/vault 1.10.3
  • bitnami vault 1.10.3
  • hashicorp vault 1.10.3

Is CVE-2022-30689 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-2022-30689 updated cvss 5.3

vault: incorrect MFA enforcement after server restart

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-loki-rhel8 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/multiclusterhub-rhel8, rhacm2/cluster-curator-controller-rhel8, rhacm2/managedcluster-import-controller-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 odf4/cephcsi-rhel9, odf4/mcg-rhel9-operator, odf4/ocs-rhel9-operator, odf4/odf-rhel8-operator, odf4/odr-rhel8-operator, odf4/rook-ceph-rhel8-operator, +1 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

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

CVSS scores

assigned by version score vector
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.10.0, <1.10.3
1.10.3
bitnami vault
>=1.10.0, <1.10.3
1.10.3

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.