CVE-2023-0620 json
Vault Vulnerable to SQL Injection When Configuring the Microsoft SQL Database Storage Backend
published 2023-03-30 3 y ago modified 2026-09-10 1 mo ago also BIT-vault-2023-0620 , EUVD-2023-1105 , GHSA-v3hp-mcj5-pg39 , GO-2023-1685
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/hashicorp/vault 1.11.9, 1.12.5, 1.13.1
- bitnami vault 1.11.9, 1.12.5, 1.13.1
- HashiCorp Vault 1.11.9, 1.12.5, 1.13.1
- HashiCorp Vault Enterprise 1.11.9, 1.12.5, 1.13.1
- github.com/hashicorp/vault#19591 pull request
- github.com/hashicorp/vault/releases/tag/v1.11.9 release
- github.com/hashicorp/vault/releases/tag/v1.12.5 release
- github.com/hashicorp/vault/releases/tag/v1.13.1 release
- discuss.hashicorp.com/t/hcsec-2023-12-vault-s-microsoft-sql-database-storage-bac… advisory
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-2023-0620 updated cvss 6.7
vault: Vault’s Microsoft SQL Database Storage Backend Vulnerable to SQL Injection Via Configuration File
-
Red Hat Openshift Container Storage 4 ocs4/cephcsi-rhel8, ocs4/mcg-rhel8-operator, ocs4/ocs-rhel8-operator, ocs4/rook-ceph-rhel8-operatoraffected: no fix planned “Out of support scope”
-
Red Hat Openshift Data Foundation 4 ocs4/ocs-rhel8-operator, odf4/mcg-rhel9-operator, odf4/rook-ceph-rhel9-operator, odf4/odf-multicluster-rhel9-operatoraffected: no fix available, no fix planned “Will not fix”
-
Red Hat OpenShift Container Platform 4.13 openshift4/ose-installer v4.13.0-202305091542.p0.g44db7b2.assembly.streamfixed: vendor fix RHSA-2023:1326
-
Red Hat OpenShift Container Platform 4.14 openshift4/ose-installer v4.14.0-202310201027.p0.g03546e5.assembly.streamfixed: vendor fix RHSA-2023:5006
-
Red Hat RHODF 4.13 for RHEL 9 odf4/ocs-rhel9-operator v4.13.0-67, odf4/odf-rhel9-operator v4.13.0-24fixed: vendor fix RHSA-2023:3742
-
Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-loki-rhel8 Red Hat OpenShift Container Platform 4 openshift4/topology-aware-lifecycle-manager-rhel8-operator Red Hat OpenShift Container Platform 4.13 openshift4/ose-cli v4.13.0-202304190216.p0.g92b1a3d.assembly.stream, openshift4/ose-pod v4.13.0-202304211155.p0.gb404935.assembly.stream, openshift4/ose-etcd v4.13.0-202304190216.p0.gf70da9d.assembly.stream, openshift4/ose-tests v4.13.0-202305031828.p0.g893ae57.assembly.stream, openshift4/ose-console v4.13.0-202305031828.p0.ga551d28.assembly.stream, openshift4/ose-coredns v4.13.0-202304190216.p0.g5560e4a.assembly.stream, +174 more Red Hat OpenShift Container Platform 4.14 rhcos 414.92.202310210434-0, openshift4/ose-cli v4.14.0-202310201027.p0.g0c63f9d.assembly.stream, openshift4/ose-pod v4.14.0-202310210404.p0.gf67aeb3.assembly.stream, openshift4/ose-tests v4.14.0-202310201027.p0.g948001a.assembly.stream, openshift4/ose-console v4.14.0-202310201027.p0.gc16ab01.assembly.stream, openshift4/ose-coredns v4.14.0-202310201027.p0.gfd70cf1.assembly.stream, +180 more Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/odr-rhel9-operator Red Hat RHODF 4.13 for RHEL 9 odf4/cephcsi-rhel9 v4.13.0-35, odf4/mcg-cli-rhel9 v4.13.0-17, odf4/mcg-core-rhel9 v4.13.0-41, odf4/odf-console-rhel9 v4.13.0-85, odf4/mcg-rhel9-operator v4.13.0-41, odf4/odr-rhel9-operator v4.13.0-33, +16 morenot 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
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 20 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/vault | >=0.8.0, <1.11.9 >=1.12.0, <1.12.5 >=1.13.0, <1.13.1 |
1.11.9 1.12.5 1.13.1 |
| bitnami | vault | <1.11.9 >=1.12.0, <1.12.5 >=1.13.0, <1.13.1 |
1.11.9 1.12.5 1.13.1 |
Affected products
- HashiCorp Vault
- HashiCorp Vault Enterprise
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
discuss.hashicorp.com
/t/hcsec-2023-12-vault-s-microsoft-sql-database-storage-backend-vulnerable-to-sql-injection-via-configuration-
web, issue-tracking, patch, vendor-advisory, advisory
-
github.com
/hashicorp/vault/pull/19591
web, patch
-
security.netapp.com
/advisory/ntap-20230526-0008/
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-0620
advisory, web
-
github.com
/hashicorp/vault
package
-
github.com
/hashicorp/vault/releases/tag/v1.11.9
web
-
github.com
/hashicorp/vault/releases/tag/v1.12.5
web
-
github.com
/hashicorp/vault/releases/tag/v1.13.1
web
-
security.netapp.com
/advisory/ntap-20230526-0008
web
-
github.com
/advisories/GHSA-v3hp-mcj5-pg39
advisory
Sources
- CVE List CVE-2023-0620
- GitHub Advisory GHSA-v3hp-mcj5-pg39
- NVD CVE-2023-0620
- OSV BIT-vault-2023-0620
- OSV GO-2023-1685
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.