# CVE-2023-25000: Vault Vulnerable to Cache-Timing Attacks During Seal and Unseal Operations

> Attackers can use cache-timing side channels during unseal operations to reduce the search space for recovering Shamir shares, potentially compromising secrets.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Mar 2023
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-vault-2023-25000, GHSA-vq4h-9ghm-qmrr, GO-2023-1709

## What is CVE-2023-25000?

CVE-2023-25000 is a medium-severity vulnerability in Hashicorp Vault, published on 30 Mar 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

HashiCorp Vault's implementation of Shamir's secret sharing used precomputed table lookups, and was vulnerable to cache-timing attacks. An attacker with access to, and the ability to observe a large number of unseal operations on the host through a side channel may reduce the search space of a brute force effort to recover the Shamir shares. Fixed in Vault 1.13.1, 1.12.5, and 1.11.9.

Weakness: CWE-203 (Observable Discrepancy), CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2023-25000?

8 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | All versions | 1.11.9, 1.12.5, 1.13.1 |
| `github.com/hashicorp/vault` | Go | All versions | 1.11.9 |
| `github.com/hashicorp/vault` | Go | All versions | 1.11.9 |
| `github.com/hashicorp/vault` | Go | From 1.12.0 | 1.12.5 |
| `github.com/hashicorp/vault` | Go | From 1.12.0 | 1.12.5 |
| `github.com/hashicorp/vault` | Go | From 1.13.0 | 1.13.1 |
| `github.com/hashicorp/vault` | Go | From 1.13.0 | 1.13.1 |
| `vault` | Bitnami | All versions | 1.11.9, 1.12.5, 1.13.1 |

Products: Hashicorp Vault.

## How do I fix CVE-2023-25000?

Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.11.9, 1.12.5 or 1.13.1.

## Is CVE-2023-25000 being exploited?

There is no known exploitation of CVE-2023-25000 in the wild and no public exploit code.

## 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-2023-25000 and fix it if it is affected.

What it is: CVE-2023-25000 is a medium-severity vulnerability in Hashicorp Vault, published on 30 Mar 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-25000 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.11.9, 1.12.5, 1.13.1
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.11.9
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.11.9
- github.com/hashicorp/vault (Go): affected from 1.12.0; fixed in 1.12.5
- github.com/hashicorp/vault (Go): affected from 1.12.0; fixed in 1.12.5
- github.com/hashicorp/vault (Go): affected from 1.13.0; fixed in 1.13.1
- github.com/hashicorp/vault (Go): affected from 1.13.0; fixed in 1.13.1
- vault (Bitnami): affected all versions; fixed in 1.11.9, 1.12.5, 1.13.1

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-2023-25000/ (Markdown: https://insights.sbomify.com/CVE-2023-25000/index.md)
```

## Sources

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

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