CVE-2023-5954 json
Vault Requests Triggering Policy Checks May Lead To Unbounded Memory Consumption
published 2023-11-09 2 y ago modified 2026-09-10 1 mo ago also BIT-vault-2023-5954 , EUVD-2023-2881 , GHSA-4qhc-v8r6-8vwm , GO-2023-2329
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
HashiCorp Vault and Vault Enterprise inbound client requests triggering a policy check can lead to an unbounded consumption of memory. A large number of these requests may lead to denial-of-service. Fixed in Vault 1.15.2, 1.14.6, and 1.13.10.
Patch / fix
- go github.com/hashicorp/vault 1.13.10, 1.14.6, 1.15.2
- bitnami vault 1.13.10, 1.14.6, 1.15.2
- hashicorp vault 1.13.10, 1.14.6, 1.15.2
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-5954 updated cvss 5.9
vault: inbound client requests can trigger a denial of service
-
Red Hat Openshift Data Foundation 4 odf4/odf-rhel8-operatoraffected: no fix planned “Will not fix”
-
Red Hat OpenShift Container Platform 4.17 openshift4/ose-installer-rhel9 v4.17.0-202409122204.p0.gdfd4c08.assembly.stream.el9fixed: vendor fix RHSA-2024:3718
-
Red Hat RHODF 4.15 for RHEL 9 odf4/mcg-rhel9-operator v4.15.0-39fixed: vendor fix RHSA-2024:1383
-
Red Hat OpenShift Container Platform 4.17 rhcos 417.94.202409121747-0, openshift4/frr-rhel9 v4.17.0-202409100034.p0.g377d02f.assembly.stream.el9, openshift4/ose-cli-rhel9 v4.17.0-202409111134.p0.gbc58b3a.assembly.stream.el9, openshift4/ose-pod-rhel9 v4.17.0-202409121706.p0.gd3adea4.assembly.stream.el9, openshift4/ose-etcd-rhel9 v4.17.0-202409100034.p0.g1fb3165.assembly.stream.el9, openshift4/ose-tests-rhel9 v4.17.0-202409130304.p0.g08f2f5f.assembly.stream.el9, +182 more Red Hat Openshift Data Foundation 4 odf4/ocs-rhel9-operator, odf4/odr-rhel9-operator, odf4/rook-ceph-rhel9-operator, odf4/odf-multicluster-rhel9-operator Red Hat RHODF 4.15 for RHEL 9 odf4/cephcsi-rhel9 v4.15.0-37, odf4/odf-cli-rhel9 v4.15.0-22, odf4/mcg-core-rhel9 v4.15.0-68, odf4/odf-console-rhel9 v4.15.0-57, odf4/ocs-rhel9-operator v4.15.0-79, odf4/odf-rhel9-operator v4.15.0-19, +19 morenot 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.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/vault | <1.13.10 >=1.14.0, <1.14.6 >=1.15.0, <1.15.2 |
1.13.10 1.14.6 1.15.2 |
| bitnami | vault | >=1.13.7, <1.13.10 >=1.14.3, <1.14.6 >=1.15.0, <1.15.2 |
1.13.10 1.14.6 1.15.2 |
Affected products
- HashiCorp Vault
- HashiCorp Vault Enterprise
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
-
discuss.hashicorp.com
/t/hcsec-2023-33-vault-requests-triggering-policy-checks-may-lead-to-unbounded-memory-consumption/59926
web, vendor-advisory, advisory
-
security.netapp.com
/advisory/ntap-20231227-0001/
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-5954
advisory, web
-
github.com
/hashicorp/vault
package
-
security.netapp.com
/advisory/ntap-20231227-0001
web
-
github.com
/advisories/GHSA-4qhc-v8r6-8vwm
advisory
Sources
- CVE List CVE-2023-5954
- GitHub Advisory GHSA-4qhc-v8r6-8vwm
- NVD CVE-2023-5954
- OSV BIT-vault-2023-5954
- OSV GO-2023-2329
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.