CVE-2020-16250: HashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to…
Noroxi assessment
Priority: Monitor (action score 32/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: 1.5% (FIRST EPSS); higher than 74.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a n/a 1.2.5.
Low priority for now. Upgrade to n/a n/a 1.2.5 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.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1..
- Published
- Aug 26, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.5% · 74th percentile
- CWE
- CWE-290
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| hashicorp | vault | cpe:2.3:a:hashicorp:vault |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hashicorp vault0.7.1 and later · before 1.2.5
- hashicorp vault1.3.0 and later · before 1.3.8
- hashicorp vault1.4.0 and later · before 1.4.4
- hashicorp vault1.5.0 and later · before 1.5.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.12 | vault | from 0.7.1 · before 1.4.7-r0 | 1.4.7-r0 |
| Alpine:v3.13 | vault | from 0.7.1 · before 1.5.4-r0 | 1.5.4-r0 |
| Go | github.com/hashicorp/vault | from 0.8.1 · before 1.2.5 | 1.2.5 |
| Go | github.com/hashicorp/vault | from 1.3.0 · before 1.3.8 | 1.3.8 |
| Go | github.com/hashicorp/vault | from 1.4.0 · before 1.4.4 | 1.4.4 |
| Go | github.com/hashicorp/vault | from 1.5.0 · before 1.5.1 | 1.5.1 |
Same product
hashicorp: all recordsOther 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 Certificates39Monitor
- 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-2020-10661Mar 23, 2020 · HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing nested-path policies…36Monitor
- ← EarlierCVE-2020-13223Jun 10, 2020 · HashiCorp Vault and Vault Enterprise logged proxy environment variables that potentially included sensitive credentials.30Monitor
- Later →CVE-2020-16251Aug 26, 2020 · HashiCorp Vault and Vault Enterprise versions 0.8.3 and newer, when configured with the GCP GCE auth method, may be vulnerable to…33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a n/a | 1.2.5 · description | Vendor (CNA) |
| alpine:vault | 1.4.7-r0 · Alpine:v3.12 | Package registry (OSV) |
| Go:github.com/hashicorp/vault | 1.2.5 | Package registry (OSV) |
| Go:github.com/hashicorp/vault | 1.3.8 | Package registry (OSV) |
| Go:github.com/hashicorp/vault | 1.4.4 | Package registry (OSV) |
| Go:github.com/hashicorp/vault | 1.5.1 | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-290 · Authentication Bypass by SpoofingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-461High
- Signature SpoofCAPEC-473
- Signature Spoofing by MisrepresentationCAPEC-476likelihood: Low · High
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- Masquerading: Invalid Code SignatureT1036.001
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls: Code SigningT1553.002
- Adversary-in-the-MiddleT1557
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.