Skip to content
Noroxi
CVE-2023-0620· NVD / CVE Program· CNA HashiCorp

Vault Vulnerable to SQL Injection When Configuring the Microsoft SQL Database Storage Backend

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: HashiCorp Vault 1.11.9, 1.12.5, 1.13.1; HashiCorp Vault Enterprise 1.11.9, 1.12.5, 1.13.1.

Low priority for now. Upgrade to HashiCorp Vault 1.11.9, 1.12.5, 1.13.1; HashiCorp Vault Enterprise 1.11.9, 1.12.5, 1.13.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

HashiCorp Vault and Vault Enterprise versions 0.8.0 through 1.13.1 are vulnerable to an SQL injection attack when configuring the Microsoft SQL (MSSQL) Database Storage Backend. When configuring the MSSQL plugin through the local, certain parameters are not sanitized when passed to the user-provided MSSQL database. An attacker may modify these parameters to execute a malicious SQL command. This issue is fixed in versions 1.13.1, 1.12.5, and 1.11.9.

MediumCVSS 6.7 · v3.1—No exploit Fix available
Published
Mar 29, 2023
Updated
Jun 17, 2026
EPSS
0.3% · 30th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.7
CNA · HashiCorp
6.5
0.2 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-0620

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for hashicorp records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
hashicorpvault

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • hashicorp vaultbefore 1.11.9
  • hashicorp vault1.12.0 and later · before 1.12.5
  • hashicorp vault1.13.0 and later · before 1.13.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.

  • HashiCorp Vault

    • 1.13.0 and later · before 1.13.1affected · semver
    • 1.12.0 and later · before 1.12.5affected · semver
    • 0.8.0 and later · before 1.11.9affected · semver

  • HashiCorp Vault Enterprise

    • 1.13.0 and later · before 1.13.1affected · semver
    • 1.12.0 and later · before 1.12.5affected · semver
    • 0.8.0 and later · before 1.11.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/hashicorp/vaultfrom 0.8.0 · before 1.11.91.11.9
Gogithub.com/hashicorp/vaultfrom 1.12.0 · before 1.12.51.12.5
Gogithub.com/hashicorp/vaultfrom 1.13.0 · before 1.13.11.13.1

Same product

hashicorp: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.
    40Plan
  • CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates
    39Monitor
  • CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-41316Oct 12, 2022 · HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's
    21Monitor
  • ← EarlierCVE-2023-24999Mar 10, 2023 · Vault Fails to Verify if the AppRole SecretID Belongs to Role During a Destroy Operation
    32Monitor
  • Later →CVE-2023-0665Mar 29, 2023 · Vault PKI Issuer Endpoint Did Not Correctly Authorize Access to Issuer Metadata
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
HashiCorp Vault1.11.9Vendor (CNA)
HashiCorp Vault1.12.5Vendor (CNA)
HashiCorp Vault1.13.1Vendor (CNA)
HashiCorp Vault Enterprise1.11.9Vendor (CNA)
HashiCorp Vault Enterprise1.12.5Vendor (CNA)
HashiCorp Vault Enterprise1.13.1Vendor (CNA)
Go:github.com/hashicorp/vault1.11.9Package registry (OSV)
Go:github.com/hashicorp/vault1.12.5Package registry (OSV)
Go:github.com/hashicorp/vault1.13.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

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

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records