Skip to content
Fencer Vulns
high 8.1

CVE-2024-2048 json

Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates

published 2024-03-04 2 y ago modified 2026-09-10 1 mo ago also BIT-vault-2024-2048 , EUVD-2024-0996 , GHSA-r3w7-mfpm-c2vw , GO-2024-2617

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

Summary

Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as trusted certificate. In this configuration, an attacker may be able to craft a malicious certificate that could be used to bypass authentication. Fixed in Vault 1.15.5 and 1.14.10.

Patch / fix

  • go github.com/hashicorp/vault 1.14.10, 1.15.5
  • bitnami vault 1.16.0
  • HashiCorp Vault 1.14.10, 1.16.0
  • HashiCorp Vault Enterprise 1.14.10, 1.16.0
  • hashicorp vault_enterprise 1.16.0

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-2024-2048 updated cvss 8.1

hashicorp/vault: Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates

  • Red Hat Openshift Data Foundation 4 odf4/mcg-cli-rhel9, odf4/mcg-rhel9-operator, odf4/rook-ceph-rhel9-operator
    affected: workaround, no fix planned “There's no mitigation available for this issue other than update the affected package to the version containing the fix.”
  • Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/odf-cli-rhel9, odf4/ocs-rhel9-operator, odf4/odf-rhel8-operator, odf4/ocs-must-gather-rhel8, odf4/ocs-metrics-exporter-rhel9 Red Hat Trusted Application Pipeline rhtap-task-runner Red Hat Trusted Artifact Signer ec-rhel9, cosign-rhel9, fulcio-rhel9, rekor-cli-rhel9, tuf-server-rhel9, rekor-server-rhel9, +10 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

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.15.0, <1.15.5
<1.14.10
1.15.5
1.14.10
bitnami vault
>=1.15.5, <1.16.0
1.16.0

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise
  • hashicorp vault_enterprise

Classification

Weakness
  • CWE-295 Improper Certificate 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.