dbcve.org
VaultApplication · Hashicorp

CVE-2020-25594

MEDIUM · 5.3 CVSS v3.1 Published 2021-02-01
Fix available
A fix is available. Upgrade to 1.5.7 / 1.6.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HashiCorp Vault and Vault Enterprise allowed for enumeration of Secrets Engine mount paths via unauthenticated HTTP requests. Fixed in 1.6.2 & 1.5.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HashiCorp Vault and Vault Enterprise allowed unauthenticated enumeration of Secrets Engine mount paths via HTTP requests. An attacker could discover the structure of mounted secret engines without authentication, aiding in further reconnaissance.

MitigationUpgrade to Vault 1.5.7 or 1.6.2. Additionally, restrict network access to the Vault HTTP API to prevent unauthenticated requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VaultApplication
Affected:< 1.5.7>= 1.6.0, < 1.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Vault version
    Run 'vault version' or examine the Vault binary/package version
    Affected if Version is below 1.5.7, or between 1.6.0 and 1.6.2 (inclusive of 1.6.0 and 1.6.1)
  2. Verify HTTP API network exposure
    Review firewall rules, network ACLs, or Vault listener configuration to determine if the Vault HTTP API port (default 8200) is accessible from untrusted network segments
    Affected if The Vault HTTP API port is reachable by unauthenticated or untrusted users on the network
  3. Test unauthenticated mount path enumeration
    Send an unauthenticated HTTP GET request to http://<vault-address>:8200/v1/sys/mounts without providing an X-Vault-Token header
    Affected if The request returns a 200 OK response with a JSON payload containing the list of mounted secret engines
  4. Check for alternate enumeration endpoints
    Send unauthenticated requests to /v1/sys/internal/ui/mounts and /v1/sys/auth endpoints
    Affected if Any of these endpoints return mount path information without authentication

You are affected if your Vault version falls within the vulnerable ranges AND the HTTP API is accessible to unauthenticated users, allowing them to enumerate secret engine mount paths via direct HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.5.7 / 1.6.2 or later
Fixed in 1.5.71.6.2
Interim mitigation

Upgrade to Vault 1.5.7 or 1.6.2. Additionally, restrict network access to the Vault HTTP API to prevent unauthenticated requests.

Fix this in Vault Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25594 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data