Skip to content
Fencer Vulns
medium 6.8

CVE-2023-4680 json

Vault's Transit Secrets Engine Allowed Nonce Specified without Convergent Encryption

published 2023-09-14 3 y ago modified 2026-09-08 2 mo ago also BIT-vault-2023-4680 , EUVD-2023-2597 , GHSA-v84f-6r39-cpfc , GO-2023-2063

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

Summary

HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption disabled. The encrypt endpoint, in combination with an offline attack, could be used to decrypt arbitrary ciphertext and potentially derive the authentication subkey when using transit secrets engine without convergent encryption. Introduced in 1.6.0 and fixed in 1.14.3, 1.13.7, and 1.12.11.

Patch / fix

  • go github.com/hashicorp/vault 1.12.11, 1.13.7, 1.14.3
  • bitnami vault 1.12.11, 1.13.7, 1.14.3
  • HashiCorp Vault 1.12.0, 1.12.11, 1.13.7, 1.14.3
  • HashiCorp Vault Enterprise 1.12.0, 1.12.11, 1.13.7, 1.14.3
  • hashicorp vault_enterprise 1.12.0, 1.12.11, 1.13.7, 1.14.3

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-2023-4680 updated cvss 6.8

vault: HashiCorp Vault Improper Input Validation vulnerability in github.com/hashicorp/vault

  • Red Hat Openshift Container Storage 4 ocs4/cephcsi-rhel8, ocs4/mcg-rhel8-operator, ocs4/ocs-rhel8-operator, ocs4/ocs-must-gather-rhel8, ocs4/rook-ceph-rhel8-operator Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator, odf4/ocs-rhel9-operator, odf4/odf-rhel8-operator, +4 more
    affected: no fix planned “Out of support scope”

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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.6.0, <1.12.11
>=1.13.0, <1.13.7
>=1.14.0, <1.14.3
1.12.11
1.13.7
1.14.3
bitnami vault
>=1.6.0, <1.12.11
>=1.13.0, <1.13.7
>=1.14.0, <1.14.3
1.12.11
1.13.7
1.14.3

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise
  • hashicorp vault_enterprise

Classification

Weakness
  • CWE-323 Reusing a Nonce, Key Pair in Encryption
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns 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.