# CVE-2024-2048: Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates

> Attackers can bypass authentication in HashiCorp Vault by crafting malicious certificates when a non-CA certificate is configured as trusted.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-vault-2024-2048, GHSA-r3w7-mfpm-c2vw, GO-2024-2617

## What is CVE-2024-2048?

CVE-2024-2048 is a high-severity authentication bypass vulnerability in Hashicorp Vault, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-2048?

6 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | All versions | 1.14.10, 1.15.5 |
| `github.com/hashicorp/vault` | Go | All versions | 1.14.10 |
| `github.com/hashicorp/vault` | Go | All versions | 1.14.10 |
| `github.com/hashicorp/vault` | Go | From 1.15.0 | 1.15.5 |
| `github.com/hashicorp/vault` | Go | From 1.15.0 | 1.15.5 |
| `vault` | Bitnami | From 1.15.5 | 1.16.0 |

Products: Hashicorp Vault, Openbao Openbao.

## How do I fix CVE-2024-2048?

Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.14.10 or 1.15.5.

## Is CVE-2024-2048 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2048 exists.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-12757](https://insights.sbomify.com/CVE-2020-12757/): Improper Input Validation in HashiCorp Vault (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2048 and fix it if it is affected.

What it is: CVE-2024-2048 is a high-severity authentication bypass vulnerability in Hashicorp Vault, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2048 exists.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.14.10, 1.15.5
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.14.10
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.14.10
- github.com/hashicorp/vault (Go): affected from 1.15.0; fixed in 1.15.5
- github.com/hashicorp/vault (Go): affected from 1.15.0; fixed in 1.15.5
- vault (Bitnami): affected from 1.15.5; fixed in 1.16.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2048/ (Markdown: https://insights.sbomify.com/CVE-2024-2048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2048
- OSV: https://osv.dev/vulnerability/CVE-2024-2048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2048/
Summaries are generated and may contain mistakes; the official description above is the record.