Cyber Resilience

CVE-2023-5954

Hashicorp Vault 1.13.7 – 1.13.10

Published
09 November 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0072 51th percentile
Risk Priority 47 floored blend · peak EPSS

Summary

CVE-2023-5954 is a medium-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Hashicorp Vault. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-401

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-4656Same product: Hashicorp Vault
CVE-2023-6337Same product: Hashicorp Vault
CVE-2026-5807Same product: Hashicorp Vault
CVE-2025-12044Same product: Hashicorp Vault
CVE-2025-6203Same product: Hashicorp Vault
CVE-2023-3774Same product: Hashicorp Vault
CVE-2024-6468Same product: Hashicorp Vault
CVE-2025-6000Same product: Hashicorp Vault
CVE-2023-3462Same product: Hashicorp Vault
CVE-2025-6011Same product: Hashicorp Vault

Affected Assets

hashicorp
vault
1.13.7 — 1.13.10 · 1.13.7 — 1.13.10 · 1.14.3 — 1.14.6

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

A.8.6 Capacity management partial match
finds

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References