Vault Vulnerable to SQL Injection When Configuring the Microsoft SQL Database Storage Backend
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.13.1, 1.12.5, 1.11.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- HashiCorp Vault
From 1.13.0 · fixed in 1.13.1; From 1.12.0 · fixed in 1.12.5; From 0.8.0 · fixed in 1.11.9
- HashiCorp Vault Enterprise
From 1.13.0 · fixed in 1.13.1; From 1.12.0 · fixed in 1.12.5; From 0.8.0 · fixed in 1.11.9
- github.com/hashicorp/vaultGo
From 0.8.0 · fixed in 1.11.9; From 1.12.0 · fixed in 1.12.5; From 1.13.0 · fixed in 1.13.1
- github.com/hashicorp/vaultGo
From 0.8.0 · fixed in 1.11.9
- github.com/hashicorp/vaultGo
From 1.12.0 · fixed in 1.12.5
- github.com/hashicorp/vaultGo
From 1.13.0 · fixed in 1.13.1